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: | Common form editor usage and api | ||
---|---|---|---|
Product: | guibuilder | Reporter: | Peter Nabbefeld <epdv> |
Component: | App Framework | Assignee: | issues@guibuilder <issues> |
Status: | NEW --- | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Peter Nabbefeld
2008-03-17 21:17:48 UTC
I just want to add/clarify some ideas: 1. The hiding issue is, of course, not only related to the editor, project-specific hiding should be possible. 2. The editor should have a multi-pane facility, it shouldn't be built be every form editor 3. The editor should accept files on a set-base, not based only on the primary file, e.g. there should be a possibility to distinguish the set of ("java","form") from ("java","myform"). Further, there should be the possibility to filter for generated source code, comments, signatures etc., e.g. a file type for OOo-UNO should be able to plug-in into the "acceptance chain" before the standard java editor. If a java file is to be edited, it could the ask the file loader, if the java file is of the specialized type. 4. *After* accepting the file type, the multi-pane should be built using sth. like multi.add(new editor(multi, fileobject)) with each editor adding its label (e.g. "form" or "design") and its actions (to create buttons from them; separators could just be given as null). Also a NOI18N-name is needed (see 5). 5. The different editors need to interact which each other, so sth. like multi.getConcurrentEditor(name) is needed. 6. The editors should communicate on the base of properties (Using generated code regions directly would specialize this to work for code only, but not for xml files. However, the regions need to have a defined name, of course, best if the same for the whole NB project). 7. Of course, in the case of form editors, the palette should be independent from the form editor (and vice versa). So, there should be only few editors: one GUI editor for all forms, CASA, ... Of course, if this all is already implemented and I just couldn't find the docs for that, I'd be VERY HAPPY if You could point me there, but I've already asked at the mailing lists (without any answer, so don't really know, if the docs and/or the implementation are missing)! |