[GRASSGUI] Re: [GRASS-dev] changing data for parser

[Jachym Cepicky]

Hi,
I agree, that we should improve --interface-description rather than
get rid of it. It can be used in the future for *any* other interface.

Wolf, you can script some class, which would produce wxpython codde on
it. This way, the input forms could be bound into any other GUI, also
for non-grass developers, who want to use GRASS modules in their
program

thanks a lot

jachym

2007/3/22, Wolf Bergenheim <wolf+grass at bergenheim.net>:
> On 22.03.2007 07:31, Michael Barton wrote:
> > menuform.py uses the xml text generated by "<command>
> > —interface-description" to create the autogenerated dialogs. This dates
> > to 2001.
> >
> > I was just reminded in a recent post to the grass developer list that
> > there is a richer interface description output called by "<command>
> > --tcltk". This has been developed over the past year or so. I give an
> > example below (part of the output from "d.vect —tcltk"). We might want
> > to consider switching the autogenerated panels to be created by the
> > —tcltk code.
> >
> > Besides being a richer set of descriptions (includes prompt for notebook
> > tabs and color picking dialogs), it looks easier to parse than the
> > —interface description xml. It would also mean that we would not need sax.
>
> You are having problems parsing XML? Have you looked at the
> xml.dom.minidom package? It provides a clean and easy DOM parser. If you
> want I can write the parser (: (yay something I can do for the GUI).
>
> Another, perhaps easier, alternative would be to add a --python flag
> which would make the parser spew python code.
>
> --Wolf
>
> --
>
> <:3 )---- Wolf Bergenheim ----( 8:>
>
> _______________________________________________
> grassgui mailing list
> grassgui at grass.itc.it
> http://grass.itc.it/mailman/listinfo/grassgui
>


-- 
Jachym Cepicky
e-mail: jachym.cepicky gmail com
URL: http://les-ejk.cz
GPG: http://www.les-ejk.cz/pgp/jachym_cepicky-gpg.pub