Hi,
As you may notice, I've commited something I wish to name
'preliminary initial cli glimpse'.
I like the idea Thomas sugested because it's likely that CGI
and CLI will diverge more and more in the future.
Since we've now a bunch of new text (and I didn't yet deleted
the old documentation, we might need the phrases for CGI) we
can start putting this in shape as you guys decide.
cheers,
- Markus
On Fri, May 10, 2002 at 11:06:19PM +0200, Thomas Sch�fbeck wrote :
> Hi there,
>
> the current existing differences can grow, and since CGI and CLI are
> different modules in also different dirs, I'd suggest to make a <chapter>
> "Using PHP from the command line" as is, but now divided in <sections>
> like "CGI Module" and "CLI Module", so that a TOC would look like
> Using PHP from the command line
> CGI Module
> CLI Module
>
> just my 2 cents,
> Thomas
>
>
> Gabor Hojtsy wrote:
>
> > > Write a single CLI chapter, explaining all of the CLI
> > > features and telling people where this differs from the CGI
> > > CLI interface or put up a separate page for the CGI?
> > >
> > > Personally I'm for documenting everything, for which I think
> > > keeping CGI command line separate would be a good thing. So
> > > we woukd have a command CLI chapter, documenting fully CGI in
> > > one part and fully CLI in the other. However I'm not that
> > > familiar what's best for docbook organization with such
> > > things.
> >
> > Uh, this is not to make our work easier... The command line features
> > are quite the same with CLI and CGI (except parameters I guess). So it
> > may be quite messy to mix the current command line chapter with CLI
> > and CGI explanations... I still don't know what's the best...
> >
> > Goba
>
--
Please always Cc to me when replying to me on the lists.
GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc
"I'm not stupid, you know? :)" - Jani Taskinen
