...@lists.osgeo.org
[mailto:grass-dev-boun...@lists.osgeo.org] On Behalf Of Nikos Alexandris
Sent: 15. januar 2015 23:05
To: Moritz Lennert
Cc: Paulo van Breugel; GRASS-dev
Subject: Re: [GRASS-dev] module header definitions add: text/multiline and
latex support?
On 15/01/15 13:34, Nikos Alexandris wrote
@
lists.osgeo.org] On Behalf Of Nikos Alexandris
Sent: 15. januar 2015 23:05
To: Moritz Lennert
Cc: Paulo van Breugel; GRASS-dev
Subject: Re: [GRASS-dev] module header definitions add: text/multiline and
latex support?
On 15/01/15 13:34, Nikos Alexandris wrote:
Just a very quick mockup, all
Anna Petrášová wrote:
If I am not wrong, we are still missing the relations in the modules' xml
representation. So it has to be first added there and then the python class
Task must incorporate it. Then we start working on the GUI.
r64226 adds the rule information to the
On Thu, Jan 15, 2015 at 8:33 AM, Markus Neteler nete...@osgeo.org wrote:
A question: If I run general/g.parser/test.py the GUI runs a kind of
test case TestTask rather than the expected GUI. Is there a
namespace collision?
I don't have an idea how it works. GUI does not appear for sh and pl
On Thu, Jan 15, 2015 at 3:13 AM, Glynn Clements gl...@gclements.plus.com
wrote:
Vaclav Petras wrote:
Requiring raster OR vector is possible already.
#%rules
#% requires: raster, vector
#%end
Can this have a description? I'm not sure where we would show it but it
might be
On 15/01/15 13:34, Nikos Alexandris wrote:
Just a very quick mockup, all-in-one page:
http://imgbin.org/index.php?page=imageid=21809. Note, the Help
button and the Manual are duplicates, if I am not wrong. This adds
up
in overloading the interface.
On 15.01.2015 14:55, Moritz Lennert
On 15/01/15 08:46, Glynn Clements wrote:
Requiring raster OR vector is possible already.
#%rules
#% requires: raster, vector
#%end
This should be required (at least one of the options must be given).
If you want exactly one option to be given, you need both required
and exclusive, e.g.
On Thu, Jan 15, 2015 at 9:37 AM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
On 15/01/15 08:46, Glynn Clements wrote:
Requiring raster OR vector is possible already.
#%rules
#% requires: raster, vector
#%end
This should be required (at least one of the options must be given).
If
On 15/01/15 09:50, Markus Neteler wrote:
On Thu, Jan 15, 2015 at 9:37 AM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
On 15/01/15 08:46, Glynn Clements wrote:
Requiring raster OR vector is possible already.
#%rules
#% requires: raster, vector
#%end
This should be required (at
Just a very quick mockup, all-in-one page:
http://imgbin.org/index.php?page=imageid=21809. Note, the Help
button and the Manual are duplicates, if I am not wrong. This adds up
in overloading the interface.
Nikos
___
grass-dev mailing list
Markus, a small typo on
http://trac.osgeo.org/grass/changeset/64180/grass/branches/releasebranch_7_0/general/g.parser
I think:
On line 191 it now read
#%required altitude,elevation
This should be:
#%required: altitude,elevation
On Thu, Jan 15, 2015 at 9:50 AM, Markus Neteler
On 15/01/15 13:34, Nikos Alexandris wrote:
Just a very quick mockup, all-in-one page:
http://imgbin.org/index.php?page=imageid=21809. Note, the Help
button and the Manual are duplicates, if I am not wrong. This adds up
in overloading the interface.
Interesting, but I have to admit that I do
On Thu, Jan 15, 2015 at 1:45 PM, Paulo van Breugel
p.vanbreu...@gmail.com wrote:
Markus, a small typo on
http://trac.osgeo.org/grass/changeset/64180/grass/branches/releasebranch_7_0/general/g.parser
I think:
On line 191 it now read
#%required altitude,elevation
This should be:
On Wed, Jan 14, 2015 at 7:25 PM, Anna Petrášová kratocha...@gmail.com
wrote:
On Wed, Jan 14, 2015 at 1:15 PM, Nikos Alexandris n...@nikosalexandris.net
wrote:
On 14.01.2015 19:13, Paulo van Breugel wrote:
These text elements could help to unclutter the interface if used
properly.
Like
On Wed, Jan 14, 2015 at 9:13 AM, Huidae Cho gras...@gmail.com wrote:
On Wed, Jan 14, 2015 at 3:42 AM, Pietro peter.z...@gmail.com wrote:
Dear devs,
sometimes I would like to add some multiline text on the module GUI to
help to understand the meaning of the parameter, and/or understand the
On Thu, Jan 15, 2015 at 2:46 AM, Glynn Clements gl...@gclements.plus.com
wrote:
Requiring raster OR vector is possible already.
#%rules
#% requires: raster, vector
#%end
This should be required (at least one of the options must be given).
If you want exactly one option to be given,
Requiring raster OR vector is possible already.
#%rules
#% requires: raster, vector
#%end
This should be required (at least one of the options must be given).
If you want exactly one option to be given, you need both required
and exclusive, e.g.
#%rules
#% required: raster, vector
#%
On Wed, Jan 14, 2015 at 3:59 PM, Vaclav Petras wenzesl...@gmail.com wrote:
Can this have a description? I'm not sure where we would show it but it
might be useful.
I did a naive mockup showing two options with OR relationship.
However, I'm against introducing some general inter-option
info,
On 14.01.2015 16:13, Huidae Cho wrote:
[..]
Requiring raster OR vector is possible already.
#%rules
#% requires: raster, vector
#%end
Can't the above be reflected, when used, in the GUI in a way such as
Pietro thinks?
Nikos
___
grass-dev
Moritz:
I personally am not in favour of such additional text in the module.
I think
it would clutter the interface. There is a reason there are man
pages and we
should not encourage users to skip them...
Pietro:
Why? I don't see the reason why we should educate the users...
I provide a
On Wed, Jan 14, 2015 at 5:27 PM, Pietro peter.z...@gmail.com wrote:
On Wed, Jan 14, 2015 at 3:59 PM, Vaclav Petras wenzesl...@gmail.com
wrote:
Can this have a description? I'm not sure where we would show it but it
might be useful.
I did a naive mockup showing two options with OR
On 14.01.2015 19:13, Paulo van Breugel wrote:
These text elements could help to unclutter the interface if used
properly.
Like the example provided by Pietro, they could for example help to
group
the inputs from which the user need to select one (grouping of
options
using tabs is another
On Wed, Jan 14, 2015 at 1:07 PM, Nikos Alexandris n...@nikosalexandris.net
wrote:
Moritz:
I personally am not in favour of such additional text in the module. I
think
it would clutter the interface. There is a reason there are man pages
and we
should not encourage users to skip them...
On Wed, Jan 14, 2015 at 1:15 PM, Nikos Alexandris n...@nikosalexandris.net
wrote:
On 14.01.2015 19:13, Paulo van Breugel wrote:
These text elements could help to unclutter the interface if used
properly.
Like the example provided by Pietro, they could for example help to group
the inputs
Dear devs,
sometimes I would like to add some multiline text on the module GUI to
help to understand the meaning of the parameter, and/or understand the
logic of the module.
Do you think that would be possible to have a description option that
it does not take any input but allow us to be more
+1 for adding description option
On Wed, Jan 14, 2015 at 9:42 AM, Pietro peter.z...@gmail.com wrote:
Dear devs,
sometimes I would like to add some multiline text on the module GUI to
help to understand the meaning of the parameter, and/or understand the
logic of the module.
Do you think
Pietro,
this thread
http://lists.osgeo.org/pipermail/grass-dev/2014-November/071908.html
is of interest, I guess, as well.
+1 for LaTeX. That would be awesome.
Nikos
___
grass-dev mailing list
grass-dev@lists.osgeo.org
On Wed, Jan 14, 2015 at 10:19 AM, Nikos Alexandris
n...@nikosalexandris.net wrote:
this thread
http://lists.osgeo.org/pipermail/grass-dev/2014-November/071908.html is
of interest, I guess, as well.
Thanks Nikos, I've missed this thread! It is really interesting
perhaps should be possible to
On 14/01/15 09:42, Pietro wrote:
Dear devs,
sometimes I would like to add some multiline text on the module GUI to
help to understand the meaning of the parameter, and/or understand the
logic of the module.
Do you think that would be possible to have a description option that
it does not take
On 14/01/15 11:59, Pietro wrote:
On Wed, Jan 14, 2015 at 10:33 AM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
Do you think that would be possible to have a description option that
it does not take any input but allow us to be more descriptive inside
the module interface?
If you add
On Wed, Jan 14, 2015 at 10:33 AM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
Do you think that would be possible to have a description option that
it does not take any input but allow us to be more descriptive inside
the module interface?
If you add
#% label
and
#% description
On 14/01/15 09:42, Pietro wrote:
Dear devs,
sometimes I would like to add some multiline text on the module GUI
to
help to understand the meaning of the parameter, and/or understand
the
logic of the module.
Do you think that would be possible to have a description option
that
it does not
On Wed, Jan 14, 2015 at 2:04 PM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
I personally am not in favour of such additional text in the module. I think
it would clutter the interface. There is a reason there are man pages and we
should not encourage users to skip them...
Why? I don't
On Wed, Jan 14, 2015 at 3:42 AM, Pietro peter.z...@gmail.com wrote:
Dear devs,
sometimes I would like to add some multiline text on the module GUI to
help to understand the meaning of the parameter, and/or understand the
logic of the module.
Do you think that would be possible to have a
34 matches
Mail list logo
