|
From: Jitu D. <jit...@ho...> - 2001-08-30 15:02:24
|
IDE My Suggestion: For our IDE we will give a good functionality. As a = developer will need=20 more space for the documents he is working on, so while the focus on the = documents the=20 all entities except DocEntity will hide itself. The developer will be = able to keep visible=20 the particular EntityWindow by the pins on the EntityWindows. The JPG here with contains LEFT, RIGHT, CONTENT, BOTTOM, TOOL BAR,=20 MENUBAR and EXPLORER Bars. Here the Explorer bars will work for as the = container=20 for the handle to EntityWindow. This handles have behavior to open / = hide while mouse=20 over the particular Handle in explorer bar. For example, if the mouse = comes over the=20 project explorer handle, the project explorer will open in the LEFT pane = if it is hidden or=20 will get focus. These handles will behave the same with click events. DESIGN : As per the design structure developed till now, I have further developed = more classes in=20 the all the views (GUI, UI, API/Handler) GUI View * IDEFrame: An abstract of all containers. Contains ExplorerBars and = MenuBar * EntityWindow : An abstract of all the internal window container. * DocEntity : An abstract, contains Source Code, Debug Output and = Immediate, Design document, preview document * TextDocument : contains Code And plain text * PlainText : contains different type of plain text * CodeText : contains source code * DesignDocument : Contains design of document * PreviewDocument : Preview of the document * BrowserEntity : An abstract, contains different type of browsing = containers * TreeBrowser : contains Project tree, File system tree, Document = Object tree,=20 * TableBrowser : contains Properties table, Library table, Watch = Table, Bookmark Table etc. * TreeTableBrowser : contains API Reference, Element Reference, = Locals etc. * BeansEntity * BeansTray : container for Bean * Bean : contains the beans * DialogWindow : An abstract of dialog window. UI View * IDEEngine : An abstract of all the managers. * EntityManager : will manage all the EntityWindows commands, behavior = and layout. * CommandManager : will manage all the commands and will talk to API * BehaviorManager : will manage the API response and the IDE behavior * LayoutManager : will manage all the layout of EntityWindows * ProjectManager * FileManager : will manage Files in project and file system * LibraryManager : will manage project library and IDE library. * DocumentManager : will manage Document in all state * CodeManager : will manage Code and talks to SyntaxHandler * DesignManager : will manage the design of the document * ObjectManager : will manage all the objects in the document Handlers View * IDEHandler : An abstract of all the generalized handlings * APIHandler : Handles particular type of API * SyntaxHandler : Handles highlighting of syntax of all the API * Highlighters : High-lightening of particular code * CodeHelper : code helper for code completing. * FileHandler : Handles file types. * CoreFileHandler : Handles the IDE supported files and config files = (By Henrik) * DocFileHandler : Handle all the supported file types (By Hanrik) * ConfigFileHandler : Handle all the config files (By Hanrik) =09 * PluginFileHandler : Handles any plugin files for IDE (By = Henrik) |