karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Achim Nierbeck <bcanh...@googlemail.com>
Subject Re: Add a scope feature-url
Date Tue, 22 May 2012 17:57:18 GMT
I second Ioannis on this, right now I don't see much of a difference
either and not much
benefit of it.

regards, Achim

2012/5/22 Ioannis Canellos <iocanel@gmail.com>:
> The idea of nesting sub shells seems interesting, but currently there is
> little need for it. As it already have been added it adds too much
> fragmentation.
> Now regarding to the original comment about separating the features:url-*
> commands. I think that it doesn't change much.
> Usually the user will type go by typing something like: feat <TAB> ->
> features: and then press an other letter or two and complete the rest of
> the commands. So we have 2 tabs so far and maybe one more to specify
> url-add, url-remove etc. Total 3 <TAB>s.
> If we add a new scope say: feature-url, then the user will go: feat<TAB> ->
> features and then will need to either press ":" or "u" and <TAB> again and
> so on.
> So in both cases we have the same ammount of effort unless the user types
> the whole scope and part of the command name by himself before using
> completion.
> So I don't see much of a difference.
> *
> **
> Blog: http://iocanel.blogspot.com
> **
> Twitter: iocanel
> *


Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
Committer & Project Lead
OPS4J Pax for Vaadin
<http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project
blog <http://notizblog.nierbeck.de/>

View raw message