[Interest] QtArg version 2.0.0

[Igor Mironchik]

On 26.01.2016 16:31, Dmitry Volosnykh wrote:
> From what I see by the moment, QtArg usage help message displays list 
> of supported commands with all the details on using them, while 
> QCommandLineParses provides context dependant usage messages. For 
> example, at the top level it may list supported commands (not sure if 
> it can provide commands' arguments at this point), and once user has 
> provided command usage message displays corresponding list of 
> arguments. This process may be repeated for the arbitrary list of 
> commands (positional arguments).

I think both solutions have right to the life :)

Something you can do better with QCommandLine*, something with QtArg...

What about help printing with QtArg you can write "tool --help command" 
and you will see help for the given command.

And, for example, how to parse next command line: "tool --crazy add, add 
add file.txt", where two first add is values of --crazy and third add is 
the command that receive value file.txt? Just for fun :)

And I always open for communications and can fix a bug in a day, or 
implement some functionality in few days... :)

>
> On Tue, Jan 26, 2016 at 3:49 PM Igor Mironchik 
> <igor.mironchik at gmail.com <mailto:igor.mironchik at gmail.com>> wrote:
>
>     Hi,
>
>
>     On 26.01.2016 15:21, Dmitry Volosnykh wrote:
>>     Igor, as far as I can see form documentation QCommandLineParser
>>     is able to support commands too. For example, see
>>     http://doc.qt.io/qt-5/qcommandlineparser.html#clearPositionalArguments.
>>     How does you library compare to just mentioned functionality? If
>>     it does something more and/or better, have you considered hacking
>>     on QCommandLineParser?
>
>     I have to play with QCommandLine* to answer your questions better.
>
>     For true, I've never used QCommandLine* and for my projects I
>     already use QtArg...
>
>     I will play with QCommandLine* and answer in this mailing list later.
>
>     But what I understood from this example, that positional argument
>     can be any word, may be it's a plus, may be minus... With QtArg
>     you can specify set of commands and only this set of commands can
>     be present in command line otherwise will be an error of parsing...
>
>
>>
>>     On Tue, Jan 26, 2016 at 3:00 PM Ben Lau <xbenlau at gmail.com
>>     <mailto:xbenlau at gmail.com>> wrote:
>>
>>         On 26 January 2016 at 19:52, Igor Mironchik
>>         <igor.mironchik at gmail.com <mailto:igor.mironchik at gmail.com>>
>>         wrote:
>>
>>             Hi,
>>
>>             On 26.01.2016 14:11, Nikos Chantziaras wrote:
>>
>>                 On 25/01/16 13:48, Igor Mironchik wrote:
>>
>>                     Hello guys,
>>
>>                     I'm glad to present QtArg version 2.0.0
>>
>>                     In new version were
>>
>>                       * implemented commands in command line,
>>                       * improved hierarchy of argument classes,
>>                       * improved help system,
>>                       * improved syntax,
>>                       * fixed different issues.
>>
>>
>>                 Maybe it would be a good idea to tell people what the
>>                 heck this is first :-P
>>
>>
>>             Sorry, I thought that many people know about QtArg. It's
>>             very simple. QtArg - this is classes to parse command
>>             line arguments. Like QCommandLineOption and
>>             QCommandLineParser, but with support of commands, i.e.,
>>             for example, "git add file.txt" - "add" - this is
>>             command... :)
>>
>>
>>         Hi Igor,
>>
>>         Interesting. I would suggest to add a license file or stay
>>         the license of your library in README.md.
>>
>>         Moreover, will you consider to publish your library on qpm.io
>>         <http://qpm.io> ?
>>
>>
>>         _______________________________________________
>>         Interest mailing list
>>         Interest at qt-project.org <mailto:Interest at qt-project.org>
>>         http://lists.qt-project.org/mailman/listinfo/interest
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20160126/d2d41428/attachment.html>