This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Faster alternative to EditorCookie | ||
---|---|---|---|
Product: | platform | Reporter: | Jaroslav Tulach <jtulach> |
Component: | Text | Assignee: | issues@editor <issues> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | dkonecny, issues, jglick, mpetras, pkuzel |
Priority: | P2 | Keywords: | API, ARCH, PERFORMANCE |
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 38273 |
Description
Jaroslav Tulach
2000-03-28 20:50:45 UTC
Is somebody really intersted in this? I can see no huge requests... Marek, if you have time, consider adding this cookie and implementing it correctly in CloneableEditorSupport. Reassign to new owner of openide/editor This cookie could be used by scanners. Currently search and TODOs functionality. I plan to profile scanning from Documents to find out whether document loading is bottleneck or not. For JavaDataObject I get 50% gain by using direct access (Util.getContent() in java module) comparing to document based access. Document loading was 20% of my overall algorithm so I got 10% speedup. I do not know if anybody needs the Writer (also there is the semantics prob Jesse described). One semantical note, the Reader should eliminate guarded section markers. Definitelly more important than issue #38218. Ah, here is the long-lost RFE I was looking for. :-) There FileEncodingQuery now: http://bits.netbeans.org/dev/javadoc/org-netbeans-modules-queries/apichanges.html#FileEncodingQuery FileEncodingQuery would be helpful in implementing this, but it is not the same. This is about having a single method pair to read or write from a given file - using the Document if it exists, else directly using the FileObject streams (which would require FEQ). Reassigning to new module owner mslama. |