[brailleblaster] Re: DocumentManager + WPManager changes
- From: "Vic Beckley" <vic.beckley3@xxxxxxxxx>
- To: <brailleblaster@xxxxxxxxxxxxx>
- Date: Wed, 23 Jan 2013 14:00:43 -0500
Brandon,
I built using Ant and the tabs are working well for me when I create new
documents. When I try to open an XML file BB crashes and disappears
completely with an error to the prompt window. If this isn't expected I can
get the error. The accessibility of the tab interface will need a little
tweaking but should work great. I am glad to see Control-N back for starting
a new document. Looks like great work so far.
From: brailleblaster-bounce@xxxxxxxxxxxxx
[mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of Brandon Roller
Sent: Wednesday, January 23, 2013 11:20 AM
To: brailleblaster@xxxxxxxxxxxxx
Subject: [brailleblaster] DocumentManager + WPManager changes
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
Other related posts:
