XSL transform engine
Windson Viana de Carvalho <windson-BrPEIg3vEJlfyO9Q7EP/[email protected]> Thu, 5 Feb 2004 00:14:28 -0300 (BRT)
| Newsgroups | gmane.text.xml.o-xml |
|---|---|
| Message-ID | <[email protected]> |
Martin, I read the documents about o:xml and now i undestood more. So, for do what i want, i have to build a XSL transform engine o:xml to mobile languages? I searched at the site the engine to transform o:xml in java/c++, but i didn´t find. Do you have plans to make this? I'm very interested in make this work. Thanks for the help, Windson On Sat, 31 Jan 2004, Martin Klang wrote: > > Windson, welcome to the list! > > (see below for initial message) > > the ObjectBox is an o:XML compiler/interpreter, it doesn't do code > transformations per se. The technology used so far for o:XML -> Java > transformations is by XSLT, but this is still incomplete. > > There are as I see it two options available: > 1) port an interpreter runtime to J2ME > 2) complete a transformation method of o:XML to J2ME code > > I think 1) would require the least work with the current status of > transformations, but 2) would be more interesting long term. > Also I think there is a lot that could be done in describing mobile > application components using a specialized XML vocabulary, with hooks > for o:XML code, that could be transformed to either o:XML (for further > transformation) or device-specific code directly. > > For what it's worth, I would probably separate out the project into > two, or three, parts: > - define the XML vocabulary that best (most > expressive/flexible/suitable/extensive) describes the type of mobile > app that you want to produce > - design and build the tools for creating that XML (desktop GUI app?) > - design and build the tools for turning the XML into device code > > this way the XML vocabulary has value in it's own right, as a language > for capturing a specific domain. The tools for creating/manipulating > the data are also not tied into a particular transformation method, and > vice versa. So you end up with more loosely coupled components. > If there is an existing language (eg XUL) which comes close to what you > want to describe, then you could possibly define a set of > domain-specific extensions to that language, instead of inventing a new > one. > > o:XML is a vocabulary describing programming logic. If you want to > include (OO or procedural) application code in your XML then you could > benefit from using it. It could also be useful for building the web > service and other tools. > > > best regards, > > /m > > > > PS2:Curiosity, where are you from? > i'm swedish, based in london! > > On 30 Jan 2004, at 01:55, Windson Viana de Carvalho wrote: > > > Martin, > > > > Thanks for your answer. When I said to port o-xml to mobile devices, i > > was > > thinking in write a transformer o-xml to j2me(and Superwaba), like > > o-xml > > to java (adding interface components, security capabilities and > > connection by http). I undestood that Object Box do the process o-xml > > to > > C++ e o-xml to Java, but i think that i was wrong or not? > > My idea for my work is a tool on desktop that the programmer uses xml > > to > > discribe a mobile application that access a web service and the tool > > create > > the code in "native code", j2me for mobile phones and superwaba for > > palm > > and pocket pcs. Now, i´m looking for a xml language that permit do this > > (I found a lot like UIML, XUL, XForms) but o-xml do more then that > > languages.I´m right? > > > > PS: I´m at the maillist now > > PS2:Curiosity, where are you from? > > > > Thanks again, > > > > Windson > > > > > > On Thu, 29 Jan 2004, Martin Klang wrote: > > > >> > >> Hi Windson, > >> > >> No need to apologise for your english - in any case I'm not english > >> myself! > >> I think that o:XML running on mobile devices for generating and > >> processing XML is extremely interesting, not least for > >> connectivity-type applications. > >> It should be possible to get the full ObjectBox running on J2ME but I > >> think it would be a bit of a squeeze. I've long been meaning to > >> separate out the runtime libs from the compiler, something which would > >> make it much easier, as you don't need much at all to run compiled > >> ObjectBox programs (in object form. possibly serialized to > >> disk/media). > >> However, the _really_ interesting use of o:XML for mobile devices lies > >> IMHO in transforming the source code into a device-friendly form. > >> I'm hoping to do more work on o:XML -> Java transformations (as well > >> as > >> other languages) in the near future. > >> In the mean time, do let me know if there is anything in particular > >> that I can help with. > >> > >> best regards, > >> > >> ps - do join the mailinglist! see http://lists.pingdynasty.com/ > >> > >> /m > >> > >> On 29 Jan 2004, at 15:08, [email protected] wrote: > >>> > >>> > >>> Message from: Windson. > >>> > >>> Hi, I'm master degree student, and I want to know if it is > >>> insteresting to port o-xml for J2ME e SuperWaba(languages for mobile > >>> devices) e if is not so difficult to extends Object Box for do this? > >>> > >>> PS: Pardon for my poor english > >>> > >>> > >> > >> > >> ______________________________________________________________________ > >> __ > >> This email has been scanned for all viruses by the MessageLabs Email > >> Security System. For more information on a proactive email security > >> service working around the clock, around the globe, visit > >> http://www.messagelabs.com > >> ______________________________________________________________________ > >> __ > >> > > > > _______________________________________________ > o-xml mailing list > o-xml-zRfLyl9bSvv/[email protected] > http://lists.pingdynasty.com/mailman/listinfo/o-xml >