Re: [jboss-as7-dev] proposed cli changes

It was a long discussion - but let me see if I can summarize what drove this. There are some subjectivity in parts of this but mostly its driven by not making the shell being "weird" compared to what users otherwise sees in the wild...thus / is suggested as a separator to match filesystem and url paths. When starting up the cli it also just feels so weird and wrong to require typing / to get to a command (unless of course you are an IRC guy - but thats not really the audience we cater to is it ?:) Thus my suggestion was to make the logic so if you just type a string, i.e. "help" then it will mean "execute the command or alias named help" nothing else. Just like a normal shell. If you want to "execute" something in the current node/path you need to (just like in a bash/zsh etc. without a PATH setup) to put ./<path>:<operation> to execute it. so the suggested syntax allow you to type things like: jboss-admin.sh $ connect [/] # default connect is root. $ cn subsystem=web [/subsystem=web] $ :read-resource-configuration #executing operation against current node. $ ..:read-resource-configuration # executing against parent node (not sure if this should actually be ../:read-resource-configuration?) $ cn ../hosts=undefined/server=server1 # up one level and into the path. [/hosts=undefined/server=server1] $ /subsystem=web:read-resource-configuration # execute based on root ignoring the current node [/hosts=undefined/server=server1] $ rr # a command/alias that will execute :read-reosource-configuration <return the result> We even discussed if it should be legal to do: [/hosts=undefined/server=server1] $ =server2:read-resource-configuration # execute the operation in context of current nodetype, but change the name vs requiring eplicit typing. $../server=server2:read-resource-configuration With this tab completion still can know if it should be completing names, children or operations AND we get a "navigational" syntax that mimicks well known paths. We could even go all the way and allowed / instead of = you could actually copy the paths directly between your curl/browser and the cli - only diff would be the operation syntax. Hope that gave some more context - at least with these changes the CLI navigation doesn't feel so alien to newbies...their brains can spend more energy to actually understand the semantics of the operations than the syntax. /max /max http://about.me/maxandersen