[GRASS-dev] module header definitions add: text/multiline and latex support?

Paulo van Breugel p.vanbreugel at gmail.com
Wed Jan 14 11:47:44 PST 2015

On Wed, Jan 14, 2015 at 7:25 PM, Anna Petrášová <kratochanna at gmail.com>

> On Wed, Jan 14, 2015 at 1:15 PM, Nikos Alexandris <nik at 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 from which the user need to select one (grouping of options
>>> using tabs is another option, but not always a good one).
>> I agree, tabbing is always efficient.  Just an idea:  instead of
>> "tabbing", could the "guisection", or a similar function, stack stuff in a
>> box with slightly, yet distiguishable, different colored background? Along
>> with other stuff in the same tab?
> I am not sure how this would work with wxPython, maybe possible, but isn't
> it too complicated? There is still a lot modules which have terrible layout
> of options and using current possibilities we can improve them. Let's do
> that first. I don't say we shouldn't think about improvements in the
> meantime.

This may be complicated in terms of programming, and I agree that in that
case it may not be a very high priority.. but from an interface point of
view, I think this is a very good idea, and it is something often used in
other programs. Another way of grouping used in menus of other programs is
headers for groups and indents, something like:

Option group 1
  option 1
  option 2
Option 3
Option 4

I guess that could work too if it is easier to implement than using
different background colours or borders.

>>  Yes, from the manual page the user can find out he/she needs to select
>>> one, but I am
>>> convinced that for many it would be beneficial if it also is clear at one
>>> glance from the interface.. similar to how the red asterisk helps the
>>> user
>>> to see at one glance which parameters are obligatory.
>> Note, the "tooltips" pop only when the cursor floats over some
>> descriptive text.  Can they also appear when the cursor points directly in
>> an/the input box?
> Yes, I know about it, that shouldn't be too difficult.
>> Nikos
>> _______________________________________________
>> grass-dev mailing list
>> grass-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/grass-dev
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20150114/de87112b/attachment.html>

More information about the grass-dev mailing list