|
> > I'm working on one, but parsing UIM source in RPG is > > non-trivial, > > I think I would not parse the UIM stuff. Maybe a > more general approach like : > > * do the screen painting on a pc > * store the design information in XML > * write an XML <=> UIM translator > > would be easier. *Generating* UIM source is pretty trivial. But a tool that can only generate source, and not be used to develop it further, is kinda pointless. Can you imagine if SDA couldn't be used to read existing DDS source? I suppose you could constrain the tool to only work with the XML source, but that limits its usefulness. Plus, I'm not keen on a green-screen design tool that can't be used on a green screen! What I have done so far has been written using UIM -- the aim is for the 1.0 release of the tool to be able to process itself. > > plus I have exactly zero spare time > > that's why I only have some ideas on this > perhaps after the summer there will be more > time We can dream... -- Paul +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.