Hi Alex -- perhaps, but I am thinking of operations that are performed on portions of the document rather than on the document as a whole. Your foundation class appears to contain commands that operate on the whole file. I am thinking of a situation where the user wants to manipulate one object in the document, say, by writing something in latex and having brailleblaster translate that into mathml. I am not exactly sure what all is going to be required of the UI, but the javascript should be prepared to handle localized operations. Hope that makes sense. JohnB, if you are awake, please comment. Good start on the javascript however. --le ----- Original Message ----- From: "Alex Jurgensen" <asquared21@xxxxxxxxx> To: <brailleblaster@xxxxxxxxxxxxx> Sent: Tuesday, February 08, 2011 2:16 AM Subject: [brailleblaster] Re: Javascript Library Hi, The math equation may already be covered by the "BBFoundation.translate()" method. I may devide the method to be clearer on this aspect. Regards, Alex, On 2011-02-07, at 11:03 PM, qubit wrote: > This sounds a lot like a "file menu". > Did you mean for your methods to cover only high level operations? > How about things like editing operations such as inserting or deleting > text, > or translating a math equation or rendering a graphic? > I'm not suggesting you add these, just trying to clarify what your > foundation class is for. > --le > > > --le > > > ----- Original Message ----- > From: "Alex Jurgensen" <asquared21@xxxxxxxxx> > To: <Brailleblaster@xxxxxxxxxxxxx> > Sent: Tuesday, February 08, 2011 12:05 AM > Subject: [brailleblaster] Javascript Library > > > Hi All, > > Here are the proposed methods that I think should go into my backend > Javascript class. > > BBFoundation.emboss(); > > BBFoundation.open(); > > BBFoundation.save(); > > BBFoundation.saveAs(); > > BBFoundation.translate(); > > These are only the methods that interact with the Java code. > > Can anyone think of others? > > Regards, > Alex, > > > >