Thanks for the references.

I would rather choose jcommander, it looks to be to what I want to do....

I will start working on my JAMES-1649 branch :
https://github.com/chibenwa/james-project/tree/JAMES-1649

If you want to take a look...

Le 16/12/2015 14:54, Antoine DUPRAT a écrit :
> On 16/12/2015 09:38, Benoit Tellier wrote:
>> Hi,
>>
>> @matthieu : we can make commands case insensitive.
>>
>> @aduprat : completion seems hard to achive but maybe we can think of
>> supporting partial unambiguous commands... What do you think of it ?
>>
>> We can add a ./james-cli.sh help command
>>
>> What do you want by "better result presentation"?
> I've not investigate a lot on this subject, may be you can check:
> http://jcommander.org/
> http://www.crashub.org/
> 
> I've already some experience on CRaSH, and may help you on my spare time.
>>
>> I'll open the jira.
>>
>> Le 16/12/2015 09:07, Antoine DUPRAT a écrit :
>>> Hello,
>>>
>>> It seems to be a good idea.
>>>
>>> May be it's also the time to investigate on a tool providing us
>>> additional features to the cli:
>>> - completion
>>> - help
>>> - better result presentation
>>> - ...
>>>
>>> Antoine
>>>
>>>> Hi,
>>>>
>>>> Today I want to raise an issue :
>>>>
>>>>    - It is nearly impossible to read James CLI help message
>>>>    - James CLI command line naming is obscure, too long and too
>>>> monolitic
>>>>
>>>> Having a lot of commands does not seem bad to me, but they should be
>>>> organised better than just grouped all together.
>>>>
>>>>
>>>>
>>>> I think something like :
>>>>
>>>> james-cli.sh DOMAIN ADD toto.org
>>>> james-cli.sh DOMAIN LIST
>>>> james-cli.sh DOMAIN REMOVE
>>>>
>>>> will be better than
>>>>
>>>> james-cli.sh ADDDOMAIN toto.org
>>>> james-cli.sh LISTDOMAIN
>>>> james-cli.sh REMOVEDOMAIN toto.org
>>>>
>>>> It will get even better with "cryptic" commands like :
>>>>
>>>> james-cli.sh ADDADDRESSMAPPING user domain fromAddress
>>>>
>>>> would be :
>>>>
>>>> james-cli.sh MAPPING ADDRESS ADD user domain fromAddress
>>>>
>>>> The global syntax I propose is :
>>>>
>>>> james-cli.sh FUNCTIONNALITY [EXTRA SPECS...] COMMAND [ARGS... ]
>>>>
>>>>
>>>>
>>>> On the help display it might help as :
>>>>
>>>>    - Related commands will be grouped together, CLRF isolated from
>>>> other
>>>> groups
>>>>    - We can add a help message to explain the functionality
>>>>    - As they are space separated, command names will get easier to read
>>>>
>>>>
>>>> If peoples thinks this might help, I am motivated to :
>>>>
>>>>    - 1/ open a jira issue
>>>>    - 2/ code this up (this seems not that complicated)
>>>>
>>>> And of course, if you have feedbacks, you will be very welcome.
>>>>
>>>> Benoit
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [email protected]
>>>> For additional commands, e-mail: [email protected]
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to