[brailleblaster] Re: Views and XML

  • From: "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx>
  • To: brailleblaster@xxxxxxxxxxxxx
  • Date: Thu, 3 Jan 2013 14:22:52 -0600

Hi Keith,

We will continue using StyledText. I considered developing something 
different, but it would be a major project in itself. The plan for 
handling editing is to keep a record of the starting and ending 
positions in StyledText of each text node, or rather the element that is 
its parent. We can get the cursor posiktion with a method call. From 
that we can figure out which text node is being edited. If the user 
creates new paragraphs we will know the position of the previous element 
in the document. And so on. 

Incidentally, we will need UTDML to show what text corresponds to each 
Braille line. This would be an alternate format for the print view. I 
know ViewPlus wants something like that, and I'm sure many users will 
also.

The "document model," for want of a better name is contained in the 
semanticsList ArrayList. It's members are the embeded class 
ElemantSemantics which contain information about each element to be 
considered, including the starting and ending points of its child text. 
When elements are created or deleted the ArrayList is updated.

Michael's point about splitting the document processing into two parts 
is a good one. Besides the classes in the documentmodel package there 
wil be one in the wordprocessor to mediate between the views and the 
document model.

I hope I'm not using terms in a confusing way. Things can be renamed if 
that would help.

Again, we have been over much of this ground before.

John

On Thu, Jan 03, 2013 at 07:02:54PM +0000, Keith Creasy wrote:
> John and all.
> 
> Any strategy for how we are going to map changes in our edit views with the 
> XML content? Are we sticking with the styled text view? Obviously if someone 
> edits the content the corresponding node has to be updated. Also, if someone 
> presses return a new node has to be created. In some cases removing a 
> paragraph break means two nodes have to be merged.
> 
> 
> Keith Creasy
> Software Developer
> American Printing House for the Blind
> KCreasy@xxxxxxx
> Phone: 502.895.2405
> Skype: keith537
> 

-- 
John J. Boyer; President, Chief Software Developer
Abilitiessoft, Inc.
http://www.abilitiessoft.com
Madison, Wisconsin USA
Developing software for people with disabilities


Other related posts: