[brailleblaster] Re: The GUI Prototype
- From: "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx>
- To: brailleblaster@xxxxxxxxxxxxx
- Date: Mon, 7 Feb 2011 11:59:15 -0600
Laura,
You have probably answered your own questions by now, but this may help
some of the less technical people on the list. The browser control is
part of SWT. Javascript and CSS would be handled by the platforrm's own
native rendering engine. Java and Javascript can call each other.
John
On Mon, Feb 07, 2011 at 11:39:50AM -0600, qubit wrote:
> The more I think of it the better this sounds, but where does swt fit in?
> Sorry, I'm still compiling native code and am reading the java discussion
> with interest.
> Since the core file would be javascript, then how would the javascript
> methods be called? From html in the source document? Sorry, I am answering
> my own question, unless I am turning things around. Feel free to correct.
> --le
>
>
>
>
> ----- Original Message -----
> From: "Alex Jurgensen" <asquared21@xxxxxxxxx>
> To: <brailleblaster@xxxxxxxxxxxxx>
> Sent: Monday, February 07, 2011 10:48 AM
> Subject: [brailleblaster] Re: The GUI Prototype
>
>
> Hi John and All,
>
> Here is my idea on how we should design the HTML portion of the GUI.
>
> We should use one JS file for the core functionality, exposing one function
> for each action such as save and open. Then we should have a backend file
> that interfaces with the Jetty code and expose one function for each
> external command such as translate.
>
> We can then wire up the buttons to the actions.
>
> The idea of using a core Javascript file to do all the heavy lifting such as
> managing the document's interface would allow us the greatest amount of
> flexibility for running our app either natively or remotely as a web
> application.
>
> Just my thoughts.
>
> Regards,
> Alex,
>
>
> On 2011-02-07, at 8:21 AM, John J. Boyer wrote:
>
> > Making a GUI pr9ototype sounds like an excellent idea. It can be
> > standalon, relying only on SWT and whatever else is required, such as
> > Jetty. It will not do translation. Thus there will be no need for the
> > native libraries to test it. It will not do input or output, just allow
> > the user to enter and edit text. It must have both the Braille and Daisy
> > views, so the ability to move them around and resize them can be tested.
> >
> > The menu structure will be done in SWT from the first. We can then see
> > if the combination of the SWT browser control and Jetty will give us
> > what we need, and we can also do some work on presenting the content
> > using basic SWT.
> >
> > One question that I have is if we present the content in html how will
> > the menu items be linked to the content, for example to change the type
> > font?
> >
> > I think that the GUI prototype should be the next milestone in
> > BrailleBlaster development, now that the emboss milestone has veen
> > achieved, more or less.
> >
> > 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:
