This sounds like great work. I never quite understood why it wasn't done using tabs before. I didn't quite get why it was so difficult to determine the active document and so send commands only to that document, but by the sound of it the cause was using multiple shells.
I haven't tried what you have done, but if it works as described in solving the problems then keep up the good work.
Michael Whapples On 23/01/2013 16:19, Brandon Roller wrote:
I have just pushed some major changes to the repository. In order to handle multiple documents more smoothly, I have altered these to classes to use a tab, as opposed to new shell for each new document as before. I think this approach reduces a lot of overhead in determining which document is active.The WPManager is, in essence, the shell of BrailleBlaster. It controls the toolbar and the SWT tabfolder. The document manager is each tab created within the tab folder. New documents or opened documents will open as a tab. The DocumentManager controls the current three views: tree, text, braille. The views appear when a tab is selected.By using this design, the amount of running shells is minimized to one. Other shells are only open when dialog windows appear. In addition, a single display is hosted in the WPManager. Any other class that needs access to display can easily access it via the WPManager or DocumentManager.If there are any issues we can always rollback to an older repository. Just thought I would explain some of the rationale behind the current changes in the wordprocessor package.-Brandon
