[brailleblaster] Re: What will the text view show?
- From: Keith Creasy <kcreasy@xxxxxxx>
- To: "brailleblaster@xxxxxxxxxxxxx" <brailleblaster@xxxxxxxxxxxxx>
- Date: Wed, 23 Jan 2013 17:45:47 +0000
OK, I'll try again to explain this.
I've always thought the format of the text in the views should be controlled
from within the views and that the view should just use the XML and do the
formatting. Semantics might still come into play but anything that controls how
the text or braille gets rendered on the medium, in this case the screen, gets
done by the view or one of it's member objects.
This keeps the view and the rendering process encapsulated.
The procedure might look like this:
1. DocumentManager creates an instance of DocumentBase and the views associated
with the document.
2. XML is opened and processed through LibLouisUTD to create the internal
document model.
3. Once the document is parsed and the model is complete DocumentManager
informs the views to perform an initial update.
4. Each view calls methods that access the document model to pull content, in
the form of XML that has the UTDML markup included.
5. The view, or one of it's members, processes a segment of the XML in order to
render content. In the case of the braille view, for example, it would get
braille elements and create the formatted braille and add the newly formatted
content to the StyledContent object and the view would display it.
In this way any view gets it's content in the form of XML and knows what to do
with it.
Does it make any sense? Please ask questions if it isn't clear.
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: Wednesday, January 23, 2013 12:22 PM
To: brailleblaster@xxxxxxxxxxxxx
Subject: [brailleblaster] Re: What will the text view show?
Hi Keith,
Let me hear your approach, so it's a two-way street.
John
On Wed, Jan 23, 2013 at 04:53:58PM +0000, Keith Creasy wrote:
> Hi John.
>
> Well, since I'd have used a different approach to most of this I guess you
> are the driver here. What would you like? We are all anxious to see how the
> views get the content they need to display and how it is linked back to the
> elements in the XML.
>
>
> We can even add an additional view if that's what folks want.
>
> 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: Wednesday, January 23, 2013 11:50 AM
> To: brailleblaster@xxxxxxxxxxxxx
> Subject: [brailleblaster] What will the text view show?
>
> If I remember right, in the original spec what is now called the text view
> would present an appearance like that of a simple word processor, with
> paragraphs, headings, tables, etc. Alternatively, it could be switched to
> show the original print for each line in the Braille view. I would like to
> know the present "views" on this matter, so I know what to develop in the
> document package.
>
> Thanks,
> John
>
> --
> John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc.
> http://www.abilitiessoft.com
> Madison, Wisconsin USA
> Developing software for people with disabilities
>
>
--
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:
