[brailleblaster] Re: Newdesign build broken...
- From: Keith Creasy <kcreasy@xxxxxxx>
- To: "brailleblaster@xxxxxxxxxxxxx" <brailleblaster@xxxxxxxxxxxxx>
- Date: Wed, 2 Jan 2013 16:03:55 +0000
John.
I'm not sure I think what you are outlining here is the best way to accomplish
the braille view. What exactly is the difference between your semantic action
files, as applied to an XML DOM, and what a style sheet does? The document
being displayed is not UTDML, it's something else, XHTML or DTBook.
In fact, the more I think about this process, I think a better approach would
be to use a braille CSS and XSLT in an HTML editor.
The communications problem probably are the result of a couple of things.
First, I'm really not clear on how you expect all this to work; using any
vocabulary of XML, directly editing print and braille on that document, styling
in the views, and very confusing is how the semantic actions get applied, when,
and where. The second problem is that, because I don't entirely follow it, I'm
not certain it's even the best approach. I'm sure you know what you are doing
but I'm not sure who else does. G
About MVC architecture:
M- Model. The data being used such as a database, XML document, or something
else.
V- View, seems self-explanatory except that in this design pattern the view
only controlls how the data is rendered; i.e. displayed in a window. It has
methods that perform actions on the data by calling the controller and recieves
update events from the controller.
C- Controller, Provides an interface to the data (Model), performs actions on
the data based on actions from the views. Notifies the views when to update
their data and what data to use. In many cases the controller has one dataset
attached to it; i.e. an XML document and one or more views.
Here is a simple scenario:
1. An XML document is opened and a DOM created. It is attached to the
controller.
2. The controller creates a set of views and they are attached to the
controller. For BB that might be the braille and print edit controls. The
controller passes semantic actions to the view when it is created so that it
can manage the XML data that gets passed in. I think this could also be done
with CSS and XSLT.
3. Someone working in the print view adds a new paragraph, inserting a new line.
4. the view calls an "insert" method of the controller.
5. The controller changes the content, XML DOM, with the new paragraph.
6. The controller tells each attached view to update using the provided data.
7. Each view takes the modified content and renders it. The braille view and
the print view would not do exactly the same thing because the rendering would
be different in each view.
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 02, 2013 10:27 AM
To: brailleblaster@xxxxxxxxxxxxx
Subject: [brailleblaster] Re: Newdesign build broken...
Hi Keith,
We will have to give some attention to communicating clearly. I've been
surprised at how difficult that can be, but maybe it isn't surprising.
Everything needed for the Braille view is contained in the UTDML which is added
to the document by liblouisutdml. Layout information is contained in the
newpage and newline elements. The xy attribute of the latter gives the position
of the line on the page and indentation. The UTDML part actually contains the
rendering of the print document. It is handled by the UTD class in the
wordprocessor. The only action required is the one for calling that class.
Could you expand on the mvc model as it applies to BrailleBlaster?
Thanks,
John
On Wed, Jan 02, 2013 at 03:04:22PM +0000, Keith Creasy wrote:
> OK John. I'll continue on the public list.
>
> In my opinion this all needs to be done using an MVC architecture.
>
> The document model is an XML DOM, plain and simple. You are invisioning that
> it can be any vocabulary/document type. We are planning to use XOM as the
> interface to the DOM.
>
> The views are what we have planned on all along; braille, text(or print if
> you prefer), and HTML. An XMLEditor using tree, attribute, text, and HTML
> views on the same document.
>
> The 'C' or "controller" part of this is critical because it is what ties the
> XML DOM to the views via the semantic actions.
>
> Possibly the semantic actions need to be tied in with the braille view? They
> are responsible for the styling of the content, right? I think you are trying
> to tie the semantic actions with the actual document but I think it's more
> part of the view. Explain if that's not right.
>
>
>
>
> Keith Creasy
> Software Developer
> American Printing House for the Blind
> KCreasy@xxxxxxx
> Phone: 502.895.2405
> Skype: keith537
>
>
> -----Original Message-----
> From: John J. Boyer [mailto:john.boyer@xxxxxxxxxxxxxxxxx]
> Sent: Wednesday, January 02, 2013 9:40 AM
> To: Keith Creasy
> Cc: Chuck Myers; brandon.r.roller@xxxxxxxxx
> Subject: Re: Newdesign build broken...
>
> Hi Keith,
>
> This method was removed. It's been compiling for me. I wonder why. There must
> be an old class around. In any case, this code is to be changed.
> The DocumentManager class needs extensive rewriting.
>
> Let's start putting our messages on the BrailleBlaster list instead of
> writing to each other. That will stimulate interest in a wider commuunity and
> may give rise to some new ideas.
>
> Brandon, please subscribe to both the liblouisliblouisxml and brailleblaster
> lists. Go to http://www.abilitiessoft.com . You will find links to sites
> where you can subscribe. Do you have the command for cloning the
> brailleblaster.newdesign repository?
>
> To all, I'm working on the documentmodel package. It's coming along rather
> slowly, but I have confidence in it.
>
> Thanks,
> John
>
> On Wed, Jan 02, 2013 at 02:01:50PM +0000, Keith Creasy wrote:
> > John.
> >
> > The newdesign does not compile. Here is the error. I can make it build by
> > commenting out the offending code block...
> >
> > [javac]
> > D:\workspace\brailleblaster\src\main\org\brailleblaster\wordprocessor\SaveOptionsDialog.java:55:
> > error: cannot find symbol
> > [javac] if (BBIni.useUtd()) {
> > [javac] ^
> > [javac] symbol: method useUtd()
> > [javac] location: class BBIni
> > [javac] 1 error
> > [javac] 1 warning
> >
> >
> > I can probably fix it but need to be sure I understand what this is
> > supposed to be doing.
> >
> > 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
>
--
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:
