[GRASS-dev] Re: [GRASS GIS] #1239: wxGUI command layer broken and unusable

[GRASS GIS]

#1239: wxGUI command layer broken and unusable
-------------------------+--------------------------------------------------
 Reporter:  garu         |       Owner:  grass-dev@…              
     Type:  defect       |      Status:  new                      
 Priority:  major        |   Milestone:  6.4.1                    
Component:  wxGUI        |     Version:  6.4.0                    
 Keywords:               |    Platform:  MSWindows XP             
      Cpu:  Unspecified  |  
-------------------------+--------------------------------------------------

Comment(by cmbarton):

 Replying to [comment:4 garu]:
 > Michael, i just began to scratch the Grass surface and for sure i've not
 explored yet all the option and subtleties that the wxGUI interface
 offers, so my opinion could be of scarce value, but afaik i've seen at
 least two reasons to maintain the command layer:
 >
 > 1) it looks that Grass commands counts in the order of hundreds, do
 really all of them have their graphical layer correspondence? I doubt, so
 i think the command layer is the only option if a user wants to introduce
 in the map stack some "esoteric" command.
 >
 > 2) in OS env, like Windoz, where shell programming is a real pain,
 command layers can be a real help for rapid prototyping while still being
 able to avail of the many facilities of the graphical interface.
 >
 > I really hope you will reconsider your position, imo throwing away
 command layer would be a real loss.
 >
 > Gabriele

 Gabriele,

 You don't seem to understand how the command layer works. This is a place
 to type *display* commands only. Nothing else will work here. These are a
 very limited subset of the GRASS command set.

 Let me announce to the readers yet again, AFAIK, GRASS will maintain the
 ability to be controlled through typed commands into the farthest
 foreseeable future. The ability to type commands is critically important
 to the ability to script GRASS and some users love typing commands. Since
 the first full GRASS GUI, I and the other people writing GUI code have not
 only NOT tried to eliminate commands but have spent a fair amount of
 coding to create special command processors in GUI for users (primarily
 Windows) who don't have terminals and to make command use easier. Note
 that all GUI dialogs have always have allowed you to cut/copy the command
 they generate and paste it into a terminal, other command processor, or
 script.

 Any power user of GRASS should investigate the use of commands and
 scripting. I suggest that you give the command console a spin. It is
 accessed through a tab at the bottom of the main GIS control window. It
 has command auto-completion, tool-tips (type 'tab'), command history, and
 the ability to cut and paste commands.

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