[GRASS-dev] module header definitions add: text/multiline and latex support?
kratochanna at gmail.com
Wed Jan 14 10:25:22 PST 2015
On Wed, Jan 14, 2015 at 1:15 PM, Nikos Alexandris <nik at nikosalexandris.net>
> On 14.01.2015 19:13, Paulo van Breugel wrote:
> These text elements could help to unclutter the interface if used
>> 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
> 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
Yes, I know about it, that shouldn't be too difficult.
> grass-dev mailing list
> grass-dev at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the grass-dev