Re: Passing xml documents between Java and a C library

  • From: "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx>
  • To: programmingblind@xxxxxxxxxxxxx
  • Date: Thu, 12 Aug 2010 11:21:25 -0500

OpenOffice is not accesible in Windows. We decided not to tie 
BrailleBlaster to any word processor for a number of reasons. It has its 
own specialized editor for both print and braille.

John

On Thu, Aug 12, 2010 at 02:52:17PM +0200, Kerneels Roos wrote:
>    While on the topic. I'm very excited about the Braille Blaster project!
>    But here's a thought. Could it not be integrated with the existing Open
>    Office suite? Just imagine in the near future every Open Office
>    installation offering superb Braille functionality. Now that would be
>    total proliferation of access technology! And why stop there, why not
>    start a drive to create a self voicing Open Office via NVDA or Orca? I
>    relish the thought of a day when the concept of a screen reader would be
>    a* strangely absurd notion because all applications would emerge out from
>    software vendors, speaking and brailling from square one.
> 
>    It is possible and would be order of magnatudes faster and far more
>    accurate than any *after the fact* slapped on attempts as is the common
>    norm today. Even if the self voicing requires the presence of a common
>    shared code base that forms part of the OS itself.
> 
>    On Thu, Aug 12, 2010 at 2:33 PM, Kerneels Roos <[1]kerneels@xxxxxxxxx>
>    wrote:
> 
>      Shot in the dark here, but since XML has a very low entophy -- a lot of
>      redundant data -- would it not make sense to attempt to either avoid the
>      direct rendering of the XML on both sides by passing something else
>      between the Java and C++ liblouisutdml library?
> 
>      I would speculate that the parsed XML contained in data structures in
>      the Java code and in the C++ code of liblouisutdml is a far more
>      efficient representation of the actual XML. If there could be an XML
>      parser API which the Java code and the liblouisutdml code could jointly
>      access the exchange of data would be very fast.
> 
>      What about the option of compressing the XML on both sides before
>      exchanging it? This introduces additional computation time for the
>      compression / decompression for each round trip, but it lowers the
>      lenght of time more memory would be required -- only during the
>      compression / decompression stages, not all the time in the case of
>      passing huge XML blobs.
> 
>      Lastly, is it not possible to call liblouisutdml API calls that directly
>      act on the XML from within the Java code instead of passing huge chunks
>      from one code base to the other? Haven't had time to check it out, but
>      the odt2brl Open Office plugin might very well do something like this?
> 
>      Regards
> 
>      On Mon, Aug 9, 2010 at 1:24 PM, Homme, James
>      <[2]james.homme@xxxxxxxxxxxx> wrote:
> 
>        Hi,
>        What would be a good light weight solution for this?
>        Thanks.
> 
>        Jim
> 
>        Jim Homme,
>        Usability Services,
>        Phone: 412-544-1810. Skype: jim.homme
>        Internal recipients, *Read my accessibility blog. Discuss
>        accessibility here. Accessibility Wiki: Breaking news and
>        accessibility advice
> 
>        -----Original Message-----
>        From: [3]programmingblind-bounce@xxxxxxxxxxxxx
>        [mailto:[4]programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Sina
>        Bahram
>        Sent: Saturday, August 07, 2010 10:25 PM
>        To: [5]programmingblind@xxxxxxxxxxxxx
>        Subject: RE: Passing xml documents between Java and a C library
> 
>        Don't get too carried away with some of these frameworks. JMX and the
>        rest might sound like awesome ideas, but heavy weight is not
>        where you necessarily want to be.
> 
>        Just a word of advice from someone who has done both sides of the coin
>        on java development.
> 
>        Take care,
>        Sina
> 
>        -----Original Message-----
>        From: [6]programmingblind-bounce@xxxxxxxxxxxxx
>        [mailto:[7]programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of John J.
>        Boyer
>        Sent: Saturday, August 07, 2010 9:26 PM
>        To: [8]programmingblind@xxxxxxxxxxxxx
>        Subject: Re: Passing xml documents between Java and a C library
> 
>        Thanks. This sounds helpful. We are still working out the architecture
>        of BrailleBlaster and figuring out what Java libraries or
>        packages we will need. We are definitely using Java 6.
> 
>        John
> 
>        On Sat, Aug 07, 2010 at 07:06:53PM -0500, Jay Macarty wrote:
>        > If you are using java 6 as your platform, there is an XmL binding
>        API
>        > called JAX-B which you might find helpful for this. JAX-B allows you
>        > to convert a java object into an XML string or to map an XML string
>        to
>        > a java object. We use this at work a lot because we are receiving
>        text
>        > based messages from queues and the message body is XML.
>        >
>        > In JAX-B you add java annotations to a java bean style data object
>        to
>        > tell it what the XML element and/or attribute names should be when
>        the
>        > object is converted to XML.
>        >
>        > ----- Original Message -----
>        > From: "John J. Boyer" <[9]john.boyer@xxxxxxxxxxxxxxxxx>
>        > To: <[10]programmingblind@xxxxxxxxxxxxx>
>        > Sent: Saturday, August 07, 2010 6:52 PM
>        > Subject: Passing xml documents between Java and a C library
>        >
>        >
>        > >For the BrailleBlaster project, the editor and user interface are
>        > >written in Java. The braille knowledge needed for translating annd
>        > >formatting is in the C library liblouisutdml. The two communicate
>        by
>        > >method calls and xml documents. We would like to pass the
>        documennts
>        > >back and forth inn a memory buffer, if possible. However, some
>        > >doccuments can be quite large, up to 6 megabytes. After UTDML
>        > >(Unified Tactile Document Markup Language) has been added to them
>        > >they can be 20 MB or more. Such large buffers seem impractical, so
>        we
>        > >will probably have to pass documents of that size as files.
>        However,
>        > >we would like to be able to pass smaller documents, say up to 100k,
>        > >in memory. How can this best be done on the Java end? liblouisutdml
>        > >expects xml documents in UTF-8 in an array of 8-bit charactors.
>        > >
>        > >Thanks,
>        > >John
>        > >
>        > >--
>        > >John J. Boyer; President, Chief Software Developer Abilitiessoft,
>        > >Inc.
>        > >[11]http://www.abilitiessoft.com
>        > >Madison, Wisconsin USA
>        > >Developing software for people with disabilities
>        > >
>        > >__________
>        > >View the list's information and change your settings at
>        > >[12]//www.freelists.org/list/programmingblind
>        > >
>        >
>        > __________
>        > View the list's information and change your settings at
>        > [13]//www.freelists.org/list/programmingblind
> 
>        --
>        John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc.
>        [14]http://www.abilitiessoft.com
>        Madison, Wisconsin USA
>        Developing software for people with disabilities
> 
>        __________
>        View the list's information and change your settings at
>        [15]//www.freelists.org/list/programmingblind
> 
>        __________
>        View the list's information and change your settings at
>        [16]//www.freelists.org/list/programmingblind
> 
>        This e-mail and any attachments to it are confidential and are
>        intended solely for use of the individual or entity to whom they are
>        addressed. *If you have received this e-mail in error, please notify
>        the sender immediately and then delete it. *If you are not the
>        intended recipient, you must not keep, use, disclose, copy or
>        distribute this e-mail without the author's prior permission. *The
>        views expressed in this e-mail message do not necessarily represent
>        the views of Highmark Inc., its subsidiaries, or affiliates.
>        __________
>        View the list's information and change your settings at
>        [17]//www.freelists.org/list/programmingblind
> 
>      --
>      Kerneels Roos
>      Cell/SMS: +27 (0)82 309 1998
>      Skype: cornelis.roos
> 
>      The early bird may get the worm, but the second mouse gets the cheese!
> 
>    --
>    Kerneels Roos
>    Cell/SMS: +27 (0)82 309 1998
>    Skype: cornelis.roos
> 
>    The early bird may get the worm, but the second mouse gets the cheese!
> 
> References
> 
>    Visible links
>    1. mailto:kerneels@xxxxxxxxx
>    2. mailto:james.homme@xxxxxxxxxxxx
>    3. mailto:programmingblind-bounce@xxxxxxxxxxxxx
>    4. mailto:programmingblind-bounce@xxxxxxxxxxxxx
>    5. mailto:programmingblind@xxxxxxxxxxxxx
>    6. mailto:programmingblind-bounce@xxxxxxxxxxxxx
>    7. mailto:programmingblind-bounce@xxxxxxxxxxxxx
>    8. mailto:programmingblind@xxxxxxxxxxxxx
>    9. mailto:john.boyer@xxxxxxxxxxxxxxxxx
>   10. mailto:programmingblind@xxxxxxxxxxxxx
>   11. http://www.abilitiessoft.com/
>   12. //www.freelists.org/list/programmingblind
>   13. //www.freelists.org/list/programmingblind
>   14. http://www.abilitiessoft.com/
>   15. //www.freelists.org/list/programmingblind
>   16. //www.freelists.org/list/programmingblind
>   17. //www.freelists.org/list/programmingblind

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

__________
View the list's information and change your settings at 
//www.freelists.org/list/programmingblind

Other related posts: