Discussion:
[GRASSGUI] menu help
Michael Barton
2007-11-14 22:56:49 UTC
Permalink
If anyone out there who is not working on the other code is feeling
energetic and/or has a bit of time on their hands, we could use having the
wxPython menu updated to match all the commands and structure now in the
TclTk one.

We could also use an artistic type for icon design. I already need a couple
that don?t yet exist (for overlay layers and map display decorations).

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-gui/attachments/20070329/3dc672a5/attachment.html
Daniel Calvelo
2007-11-14 22:56:49 UTC
Permalink
Post by Michael Barton
If anyone out there who is not working on the other code is feeling
energetic and/or has a bit of time on their hands, we could use having
the wxPython menu updated to match all the commands and structure now
in the TclTk one.
could a script do it?
For the most part, I think so. But in the tcl version (and also in the
python counterpart) there are some commands embedded in the
definitions. Those must be hand-tuned to each back-end.

I suggest porting the menu structure to JSON (in preference of XML)
with special markers for these actions, and use the same source for
building both tcl and python guis. That would also allow for
different menu combinations switchable at run-time depending on user
preferences. (AFAICT wxGRASS does present a different interface
according to the "user level" in which it is started.)

I could do the python part, but I'm practically illiterate in tcl.
automation is good.
Absolutely. Just as duplication is bad... in code anyway.

Daniel.
--
-- Daniel Calvelo Aros
Jachym Cepicky
2007-11-14 22:56:49 UTC
Permalink
what about moving the GUI to XML ? this would make it possible to use
one file in many tools..

j
Post by Daniel Calvelo
Post by Michael Barton
If anyone out there who is not working on the other code is feeling
energetic and/or has a bit of time on their hands, we could use having
the wxPython menu updated to match all the commands and structure now
in the TclTk one.
could a script do it?
For the most part, I think so. But in the tcl version (and also in the
python counterpart) there are some commands embedded in the
definitions. Those must be hand-tuned to each back-end.
I suggest porting the menu structure to JSON (in preference of XML)
with special markers for these actions, and use the same source for
building both tcl and python guis. That would also allow for
different menu combinations switchable at run-time depending on user
preferences. (AFAICT wxGRASS does present a different interface
according to the "user level" in which it is started.)
I could do the python part, but I'm practically illiterate in tcl.
automation is good.
Absolutely. Just as duplication is bad... in code anyway.
Daniel.
--
-- Daniel Calvelo Aros
_______________________________________________
grassgui mailing list
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
Jachym Cepicky
2007-11-14 22:56:49 UTC
Permalink
Post by Jachym Cepicky
what about moving the GUI to XML ? this would make it possible to use
one file in many tools..
sorry, not the "GUI", but "menus" or all common conf. parts in general

j
Post by Jachym Cepicky
j
Post by Daniel Calvelo
Post by Michael Barton
If anyone out there who is not working on the other code is feeling
energetic and/or has a bit of time on their hands, we could use having
the wxPython menu updated to match all the commands and structure now
in the TclTk one.
could a script do it?
For the most part, I think so. But in the tcl version (and also in the
python counterpart) there are some commands embedded in the
definitions. Those must be hand-tuned to each back-end.
I suggest porting the menu structure to JSON (in preference of XML)
with special markers for these actions, and use the same source for
building both tcl and python guis. That would also allow for
different menu combinations switchable at run-time depending on user
preferences. (AFAICT wxGRASS does present a different interface
according to the "user level" in which it is started.)
I could do the python part, but I'm practically illiterate in tcl.
automation is good.
Absolutely. Just as duplication is bad... in code anyway.
Daniel.
--
-- Daniel Calvelo Aros
_______________________________________________
grassgui mailing list
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
--
Jachym Cepicky
e-mail: jachym.cepicky gmail com
URL: http://les-ejk.cz
GPG: http://www.les-ejk.cz/pgp/jachym_cepicky-gpg.pub
Michael Barton
2007-11-14 22:56:49 UTC
Permalink
Probably a good idea. But I don't know how to parse this in TclTk--and don't
know it that well in wxPython either.

Michael
Post by Jachym Cepicky
Post by Jachym Cepicky
what about moving the GUI to XML ? this would make it possible to use
one file in many tools..
sorry, not the "GUI", but "menus" or all common conf. parts in general
j
Post by Jachym Cepicky
j
Post by Daniel Calvelo
Post by Michael Barton
If anyone out there who is not working on the other code is feeling
energetic and/or has a bit of time on their hands, we could use having
the wxPython menu updated to match all the commands and structure now
in the TclTk one.
could a script do it?
For the most part, I think so. But in the tcl version (and also in the
python counterpart) there are some commands embedded in the
definitions. Those must be hand-tuned to each back-end.
I suggest porting the menu structure to JSON (in preference of XML)
with special markers for these actions, and use the same source for
building both tcl and python guis. That would also allow for
different menu combinations switchable at run-time depending on user
preferences. (AFAICT wxGRASS does present a different interface
according to the "user level" in which it is started.)
I could do the python part, but I'm practically illiterate in tcl.
automation is good.
Absolutely. Just as duplication is bad... in code anyway.
Daniel.
--
-- Daniel Calvelo Aros
_______________________________________________
grassgui mailing list
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
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
Jachym Cepicky
2007-11-14 22:56:49 UTC
Permalink
In python this is no big problem.

I have no clue about tcl..


maybe we could just reuse the "python" syntax: use simple textfile
with indentation

j
Post by Michael Barton
Probably a good idea. But I don't know how to parse this in TclTk--and don't
know it that well in wxPython either.
Michael
Post by Jachym Cepicky
Post by Jachym Cepicky
what about moving the GUI to XML ? this would make it possible to use
one file in many tools..
sorry, not the "GUI", but "menus" or all common conf. parts in general
j
Post by Jachym Cepicky
j
Post by Daniel Calvelo
Post by Michael Barton
If anyone out there who is not working on the other code is feeling
energetic and/or has a bit of time on their hands, we could use having
the wxPython menu updated to match all the commands and structure now
in the TclTk one.
could a script do it?
For the most part, I think so. But in the tcl version (and also in the
python counterpart) there are some commands embedded in the
definitions. Those must be hand-tuned to each back-end.
I suggest porting the menu structure to JSON (in preference of XML)
with special markers for these actions, and use the same source for
building both tcl and python guis. That would also allow for
different menu combinations switchable at run-time depending on user
preferences. (AFAICT wxGRASS does present a different interface
according to the "user level" in which it is started.)
I could do the python part, but I'm practically illiterate in tcl.
automation is good.
Absolutely. Just as duplication is bad... in code anyway.
Daniel.
--
-- Daniel Calvelo Aros
_______________________________________________
grassgui mailing list
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
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
--
Jachym Cepicky
e-mail: jachym.cepicky gmail com
URL: http://les-ejk.cz
GPG: http://www.les-ejk.cz/pgp/jachym_cepicky-gpg.pub
Michael Barton
2007-11-14 22:56:49 UTC
Permalink
Well,

I'm hoping that the TclTk menus will remain reasonably stable now. It's not
hard to make a manual tweak now and then if necessary.

The best thing for the long run would be work work with the keyword section
of the interface description that Markus set up and arrange the keys so that
they could build a menu automatically. Then we wouldn't have to manually
maintain the hundreds of commands.

Michael
Post by Jachym Cepicky
In python this is no big problem.
I have no clue about tcl..
maybe we could just reuse the "python" syntax: use simple textfile
with indentation
j
Post by Michael Barton
Probably a good idea. But I don't know how to parse this in TclTk--and don't
know it that well in wxPython either.
Michael
Post by Jachym Cepicky
Post by Jachym Cepicky
what about moving the GUI to XML ? this would make it possible to use
one file in many tools..
sorry, not the "GUI", but "menus" or all common conf. parts in general
j
Post by Jachym Cepicky
j
Post by Daniel Calvelo
Post by Michael Barton
If anyone out there who is not working on the other code is feeling
energetic and/or has a bit of time on their hands, we could use having
the wxPython menu updated to match all the commands and structure now
in the TclTk one.
could a script do it?
For the most part, I think so. But in the tcl version (and also in the
python counterpart) there are some commands embedded in the
definitions. Those must be hand-tuned to each back-end.
I suggest porting the menu structure to JSON (in preference of XML)
with special markers for these actions, and use the same source for
building both tcl and python guis. That would also allow for
different menu combinations switchable at run-time depending on user
preferences. (AFAICT wxGRASS does present a different interface
according to the "user level" in which it is started.)
I could do the python part, but I'm practically illiterate in tcl.
automation is good.
Absolutely. Just as duplication is bad... in code anyway.
Daniel.
--
-- Daniel Calvelo Aros
_______________________________________________
grassgui mailing list
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
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
Michael Barton
2007-11-14 22:56:49 UTC
Permalink
Daniel,

I can help with the TclTk part. But I need to know what to do.

I am not familiar with JSON.

Michael
Post by Daniel Calvelo
Post by Michael Barton
If anyone out there who is not working on the other code is feeling
energetic and/or has a bit of time on their hands, we could use having
the wxPython menu updated to match all the commands and structure now
in the TclTk one.
could a script do it?
For the most part, I think so. But in the tcl version (and also in the
python counterpart) there are some commands embedded in the
definitions. Those must be hand-tuned to each back-end.
I suggest porting the menu structure to JSON (in preference of XML)
with special markers for these actions, and use the same source for
building both tcl and python guis. That would also allow for
different menu combinations switchable at run-time depending on user
preferences. (AFAICT wxGRASS does present a different interface
according to the "user level" in which it is started.)
I could do the python part, but I'm practically illiterate in tcl.
automation is good.
Absolutely. Just as duplication is bad... in code anyway.
Daniel.
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

Loading...