Since each view extends AbstractViews, initialize Views could be an abstract method in the class, then implemented for each View. -Brandon On Thu, Jan 17, 2013 at 12:20 PM, Keith Creasy <kcreasy@xxxxxxx> wrote: > Hi John. > > We could do that. I'm sort of leaving it to Brandon and Chuck but what I > had in mind is to just have methods in each view like: > > onInitialUpdate > > and > > onUpdate > > Each view is bound to the document and so in these two methods they would > just make whatever calls to the document they needed to initialize and > update themselves. > > Since we have several different kinds of views we might also want to > define an interface that each view can implement to handle communication > with the document. > > This is much cleaner I think than having something that has to know about > each view and initialize it. > > > Keith Creasy > Software Developer > American Printing House for the Blind > KCreasy@xxxxxxx > Phone: 502.895.2405 > Skype: keith537 > > > -----Original Message----- > From: brailleblaster-bounce@xxxxxxxxxxxxx [mailto: > brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of John J. Boyer > Sent: Thursday, January 17, 2013 12:13 PM > To: brailleblaster@xxxxxxxxxxxxx > Subject: [brailleblaster] Proposal: a new class in views package > > I think it would be a good idea to have a class in the views package > called something like innitializeViews . It would call on methods in > DocumentBase to provide the text and Braille associated with elements and > would call another method to transmit back the starting and ending > positions of the text in the StyledText view. This information would later > be used to find the location in the document corresponding to the cursor > location. It would be updated when the document is edited. > > John > > -- > John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc. > http://www.abilitiessoft.com > Madison, Wisconsin USA > Developing software for people with disabilities > > > >