[GRASS-dev] [GRASS GIS] #2077: implement drop-down menu for barscale styles

[GRASS GIS]

#2077: implement drop-down menu for barscale styles
--------------------------+-------------------------------------------------
  Reporter:  martinl      |       Owner:  grass-dev@…              
      Type:  enhancement  |      Status:  reopened                 
  Priority:  major        |   Milestone:  7.0.0                    
 Component:  wxGUI        |     Version:  svn-trunk                
Resolution:               |    Keywords:  d.barscale               
  Platform:  All          |         Cpu:  All                      
--------------------------+-------------------------------------------------

Comment(by martinl):

 Replying to [comment:16 wenzeslaus]:
 > The GUI should depend on documentation not the other way around, so 2 or
 1 are the right options.

 Agreed, I would suggest to move barscale thumbs to `display/d.barscale`
 and copy them to `$GISBASE/docs/html` (similarly to `r.colors`'s color
 tables).

 > Do we know that documentation is always in `$GISBASE/docs/html` on all
 platforms? Are there any distributions which put the documentation
 somewhere else? The first option (redundancy) would be the safest option
 in this case.

 Not sure about that.

 > Currently, the documentation path in the GUI is used for accessing the
 pages, e.g. in module dialogs/forms. So, the option 2 (things in
 docs/html) is already used and it seems to work. (But are we sure that it
 is always `$GISBASE/docs/html`?)
 >
 > By the way, I'm wondering how the compilation of HTML works in non-unix
 enviroments. Do I need to have `sed` installed?

 AFAIK, `sed` is required.

 {{{
 grep -w 'sed' --include=Makefile -R | cut -d':' -f1 | uniq
 macosx/app/Makefile
 macosx/Makefile
 raster/r.colors/Makefile
 lib/python/script/Makefile
 lib/python/ctypes/Makefile
 lib/init/Makefile
 mswindows/Makefile
 include/Makefile
 demolocation/Makefile
 vector/v.colors/Makefile
 display/d.barscale/Makefile
 }}}

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/2077#comment:17>
GRASS GIS <http://grass.osgeo.org>