Re: Re: PhpBeautify draft
| From: | Stefan Neufeind | Date: | Thu, 13 May 2004 21:59:29 +0000 |
| Subject: | Re: Re: PhpBeautify draft | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-29231@lists.php.net to get a copy of this message | ||
On 13 May 2004 at 22:31, Davey wrote:
> Claudio Bustos wrote:
> > PEAR devs:
> > I create the draft for a new Package, PhpBeautify. Some time ago, Jens
> > Bierkandt and I proposed this app, the group suggest some improvement,
> > but we didn't have time to solve the topic.
> > The principal features of the Package are:
> > - Automatic indentation of PHP source code according to given number of
> > spaces
> > - Automatic newlines, if required
> > - You can use the web frontend, command line or the class.
> > - Plug-in architecture, by the use of Filters. The control of beautify
> > proccess is delegated on the Filters. Pear specs are one these.
> > - The code to beautify can make callbacks to the base class and the
> > filters. So, you can set the options for the beautify inside the same file
> > - Batch processing
> > The main diff with others applications is the use of Filters, I think.
> > You can freely use and create new Filter to make your code looks like
> > you want it.
> >
> > Now, I rewrite the code for Php 5. Before change the status to
> > 'Proposal', I need help:
> > - Name of the Package: I think the best group is 'Tool and Utilities',
> > but maybe 'PHP' it's okay. In the first case, the main class will be put
> > in /PEAR/ and others on /PEAR/PhpBeautify. In the second case, the core
> > class will be renamed to /PHP_Beautify and the others files will be
> > moved to /PEAR/PHP/Beautify
> > - Docs: English doesn't my native language (you notice that, rigth?).
> > So, I need people who read the docs and made the necessary corrections
> > on gramar and ortography.
>
> I believe this should be called PHP_Tidy - to follow in the same vein as
> HTML Tidy.
Haven't yet had a much of a look at the tool itself. But I agree with
Davey that calling it PHP_Tidy might be a good idea.
I'm a bit confused about your licensing in PhpBeautify.class.php. I
suggest you drop the GPL-license part and use the PHP-License that's
already present above it :-) Well, file-naming etc. is another thing
... but we'll talk about that some day later.
Need some sleep right now. Cheers,
Stefan