I already tested the tab control and it works great. We plan on having keyboard shortcuts to move between documents too. You can actually run and test it now just by opening BB and creating a second new document. -----Original Message----- From: brailleblaster-bounce@xxxxxxxxxxxxx [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of John J. Boyer Sent: Wednesday, January 23, 2013 11:35 AM To: brailleblaster@xxxxxxxxxxxxx Subject: [brailleblaster] Re: DocumentManager + WPManager changes Sounds good. Will BrailleBlaster run well enough so these changes can be tested for accessibility? John On Wed, Jan 23, 2013 at 11:19:31AM -0500, 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 -- John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc. http://www.abilitiessoft.com Madison, Wisconsin USA Developing software for people with disabilities