On Sat, Oct 16, 2010 at 9:12 PM, pancake <[email protected]> wrote:
> I think that would be really nice. In fact is that json can represent > mostly the same structures as xml. And it is far more easy for humans. > > What i dont see here is how cdata can be represented. Because it will break > json compatibility.. Maybe adding a comment in a specific form? Like /*-- > ...--*/ > Dealing with another markup parser will be made more easy in the up-coming versions. However, the current choice of XML is based on the fact that XML only has namespace support. YAML and JSON need a way to emulate that.. (g-point-something is an option) My opinion on embedding code in a JSON 'markup' would be to simply have the 'free code' (actually class member code) begin *after the JSON definition ends*. What do you think? > > The g:public will not be a valid json dict key. So maybd g.public can be > used here. > > As we need to parse comments , this will require a self written json > parser. > > It shouldnt be hard to write a proof of concept in perl to translate json > to xml before running gtkaml.. Or internally in gtkaml. If file extension is > .gtkson it will do the translation and then inteernally parse the xml. > I will soon provide an example of a decoupled XML parser in gtkaml, which can be used for coding a JSON or YAML one > > Will think on that. I think it will be an interesting feature to have. > > Another thing i would love to havd in gtkaml is support for fastvapis. Any > volunteer here? > I need to study that. Any details will be good:) Vlad BIG P.S. by the way, QML has the advantage of being Javascript-executing too. Maybe a such javascript-enabling of a GUI markup would benefit Gtk+ too? I was first thinking at writing a GModule-outputting GtkAML that can be embedded into the application at runtime, useful for my own previewing editor, but what would the JavaScript interaction would be like then?
_______________________________________________ vala-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/vala-list
