On Thu, Apr 23, 2009 at 8:57 AM, Terry Brown <[email protected]> wrote: > > On Thu, 23 Apr 2009 06:45:36 -0700 (PDT) > "Edward K. Ream" <[email protected]> wrote: > >> 1. Given substantial work, one can imagine an @settings tree that >> describes the desired screen layout of all or parts of Leo's main >> window. > > Without wishing to be a source of stop energy here, if Leo had a > solution to the I expect quite difficult problem of schema driven > hierarchical data objects
maybe this is somehow related to http://blog.ianbicking.org/2009/04/20/treating-configuration-values-as-templates/ or maybe not. (i.e. XML but doesn't need to look like it to > the user), it would be able to make .ui files for free. > > The two issues are that (a) you need to parse some kind of schema > (XML-Schema, RELAX-NG, others?) to be able to inform the user which > elements are allowed and *which types and values are allowed*, and (b) > what's the best way to display something which will ultimately be XML > in leo? Should attributes be nodes, or uAs on nodes, displayed in a uA > editor? > > Cheers -Terry > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
