[mapguide-psc] MapGuide's 1st RFC!

[Jason Birch]

Or why not make "interactive" the default behaviour when you run the application, and only have the help show up if you do /help or /? or --help?  This would be more in keeping with other apps I'm familiar with.
 
Can we change the process to require posting the RFC to DEV first for discussion then forward to PSC once any discussion is firmed up?  Otherwise we'll be in crosspost hell forever.  All of us should be on the dev list anyway.
 
I'm really looking forward to seeing what the advanced join RFC is about BTW (just to throw in another tla)...
 
Jason

________________________________

From: Tom Fukushima
Sent: Tue 2006-10-31 7:22 PM
To: psc at mapguide.osgeo.org; dev at mapguide.osgeo.org
Subject: RE: [mapguide-psc] MapGuide's 1st RFC!



Yes, I would like to see both formats ("/" and "-") supported as well.

But when the user gets the command line help by typing "mgserver -?" or
"mgserver --help" (note the double dash), I propose that we only show
the "-" versions of the options.  Of course, this is a bit confusing to
those users who want to figure out what /interactive means; Bruce, why
are we changing "interactive" to "run"?  Or will "mgserver -interactive"
also work?


So typing "mgserver --help" outputs:

The following is a list of supported command line options:

  -? or --help
      Displays this information.

  -install <Name>
      Installs the server as a service. Automatically starts the
service.

      Default service display name installed:
      "MapGuide Server"

      You can use a different display name for the service if you
specify an
      optional "Name".

  -run
      Runs the server interactively as an application instead of a
service.

  -start
      Starts the server service. Note: The service must be installed.

  -stop
      Stops the server service. Note: The service must be installed.

  -testfdo <Filename>
      Runs the FDO unit tests.

      Default output of the FDO unit tests will be the console unless
you
      specify an optional "Filename". The output to the "Filename" will
be
      in XML.

  -test <Test> /o <Filename>
      Runs the server unit tests.

      By default all of the unit tests will be run unless you specify an
      optional "Test" to run. If you specify "List" as the test to run
you
      will get a list of the available unit tests.

      Default output of the unit tests will be the console unless you
specify
      an optional "Filename". The output to the "Filename" will be in
XML.

  -uninstall
      Uninstalls an installed server service. Automatically stops the
service
      before uninstalling.


Note: Only 1 command line option can be used at a time.


-----Original Message-----
From: Bruce Dechant
Sent: Tuesday, October 31, 2006 2:49 PM
To: psc at mapguide.osgeo.org
Subject: RE: [mapguide-psc] MapGuide's 1st RFC!

I will be easy enough to support both. I'll update the RFC to reflect
this.

Bruce

-----Original Message-----
From: Andy Morsell [mailto:amorsell at spatialgis.com]
Sent: October 31, 2006 12:42 PM
To: psc at mapguide.osgeo.org
Subject: RE: [mapguide-psc] MapGuide's 1st RFC!

I agree, it's probably not a big issue.  It depends on how much work it
would be on Bruce's end to support backwards compatibility.  If it would
be relatively easy, then may as well do it.  If it would require a large
effort, then the current console response to an incorrect parameter
should be sufficient for users to figure it out on their own.


Andy

-----Original Message-----
From: Paul Spencer [mailto:pspencer at dmsolutions.ca]
Sent: Tuesday, October 31, 2006 11:29 AM
To: psc at mapguide.osgeo.org
Subject: Re: [mapguide-psc] MapGuide's 1st RFC!

I am normally a big fan of backwards compatibility too, but I really
don't see this as a big issue.  Perhaps if the tool just spits out an
appropriate message if called with incorrect parameters?

Then again, windows users are most likely used to the / style of adding
parameters so perhaps that makes it worthwhile supporting both?

Paul

On 31-Oct-06, at 2:08 PM, Andy Morsell wrote:

> I agree with Frank in that keeping it backwards compatible with the
> older command line parameters while in the future only documenting the

> new ones would be the best.  There are many references, mostly in
> archived messages in the mapguide-users mailing list, to the current
> parameter syntax that new users are bound to run across (and try to
> use) when doing research.
>
> Regarding the RFC format, that seems to work very well.
>
> Andy
>
> From: Bruce Dechant [mailto:bruce.dechant at autodesk.com]
> Sent: Tuesday, October 31, 2006 10:20 AM
> To: psc at mapguide.osgeo.org
> Subject: [mapguide-psc] MapGuide's 1st RFC!
>
> Hi All,
>
>
>
> I wrote up a simple MapGuide RFC to give our process a trial run.
>
>
>
> http://wiki.osgeo.org/index.php/MG_RFC_1_-
> _Commandline_parameter_changes
>
>
>
> Please have a look and post any feedback.
>
>
>
> Thanks,
>
> Bruce
>
>
>
>

+-----------------------------------------------------------------+
|Paul Spencer                          pspencer at dmsolutions.ca    |
+-----------------------------------------------------------------+
|Chief Technology Officer                                         |
|DM Solutions Group Inc                http://www.dmsolutions.ca/ |
+-----------------------------------------------------------------+