karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Schneider <ch...@die-schneider.net>
Subject Re: Add a scope feature-url
Date Tue, 22 May 2012 13:54:31 GMT
Yes fragmentation is an issue. We have to make sure the informations on 
the top level are good enough so people know what subshell to look into.
Of course we can still provide a help list of all commands too so people 
can grep it if they are unsure where a certain command is located.

On the other hand I think a hierarchy makes a lot of sense. Currently we 
have 142 commands at the top level (with a default karaf). This is quite 
overwhelming for users.
If they would simply see 10 subshells with nice descriptions of the 
purpose that would probably be a much better guidance.


Am 22.05.2012 15:35, schrieb Guillaume Nodet:
> Not sure how feasible that is, because it impacts lots of things, but why not.
> I'm not sure separating too much is a good idea, as you kinda loose
> the overview of what commands are related.
> If we'd do what you suggest, completion would only show resources, and
> I suppose the help command too, so it kinda fragments things a bit.
> I guess that would make sense if we end up with dozens of commands in
> the same subshell, for the features we only have a handful, and we are
> even talking about reducing that number.
> On Tue, May 22, 2012 at 3:19 PM, Christian Schneider
> <chris@die-schneider.net>  wrote:
>> How about:
>> jms:queue:browse
>> jms:queue:clear
>> jms:topic:browse
>> jms:connection:list
>> So you can enter a subshell in two levels.
>> On the jms level you see:
>> queue:browse
>> queue:clear
>> topic:browse
>> connection:list
>> On the jms:queue level you see:
>> browse
>> clear
>> This is even quite near the concept we have now. We just need to use a ":"
>> instead of the "-".
>> Coming back to the feature case perhaps we can do this:
>> feature:url:add
>> feature:url:remove
>> feature:url:list
>> feature:install
>> feature:uninstall
>> feature:list
>> (We could also use repo instead of url. Not sure about that though.)
>> The downside to the above is that completion is not better than today but it
>> would nicely implement the resource view already.
>> Christian

Christian Schneider

Open Source Architect
Talend Application Integration Division http://www.talend.com

View raw message