Hi all, On 12/05/2012 11:01 AM, Philippe Auphelle wrote: >> Please don't use the IRC for decisions that affect EVERYONE. It's >> fine for talking with another developer or support but it was not >> designed for that purpose. Use the mailing list. neither IRC nor E-Mail is really the proper thing for that purpose ;). But since we don't have defined procedures like regular "meetings", you are right and sending an E-Mail is the better approach.
On the other side a lot of discussions and developing happens in the irc channel (reminder: #freerdp on freenode). So don't be shy and join if you can. > Looks like an unfair shot to me. > Ain't this very thread the actual proof that Marc-André > - uses *both* IRC *and* the mailing list, > - tries very hard to accomodate everybody, and > - takes advice from both sources into consideration? > > Not even mentioning the fact that he also actually writes the corresponding > code in near realtime... absolutely agree with Philippe. Marc-André put really a lot of effort and thinking in the new command line syntax and parser. As you saw it's definitely nothing randomly chosen. Having a working version of the new syntax for testing and basis for discussion it's a good idea imho. - I haven't seen any pull request on this issue with other suggestions for the syntax we could try.... >From integrators (thin client developers, people scripting freerdp, ..) and the systems administrator point of view a new syntax is horrible and a needs some extra time fixing scripts and related stuff. True. And it sucks but having a well designed, usable command line we stick with for the future is more important and the changes would only be required once. Not doing a clean cut or supporting different syntaxes (maybe on different systems) is not a good solution and will end in tears on the long run if you ask me. Also we should not forget *end users*. The current syntax is not very intuitive and has grown along with freerdp but even if I use xfreerdp daily I need to look up how to use plugin x regularly. That definitely needs change! Having a simple and practical command line interface is really worth much. I know this is a potential flame statement but POSIX/GNU or not - is it really important in this case? Usually I'm in favor of using standards and conventions like POSIX or GNU where possible but if you have different requirements and needs why not ignore them and use a different better approach if it makes sense? - I don't see any good reason why we need to be compliant with freerdp. Only because it's commonly used this doesn't mean it is a good approach for us and if you use a program for the first time you need to look up the syntax anyway. Now having added my two cents I suggest that we stop putting energy on compatibility discussions, accept changes and try to find a easy and usable solution for the command line syntax we are happy with and that sticks. >From the technical side the new syntax must definitely be usable with shell scripts (maybe also with power shell or cmd). So we should make sure that this works. Also as Kevin mentioned we need also be cautious with argument if they are a valid filename (like "/admin"). If the new syntax is final we definitely need some "migration guide" with mappings (I'm volunteering to create this). Best regards, Bernhard ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
