Re: HTML_SetupWizard and more ....

I'm +1 on HTML_SetupWizard Only issue i see is you have some defines that don't follow the PEAR CS, i think the SW4P_* constants should all be HTML_SetupWizard_* -joshua eichorn Laurent Laville wrote:

Hi all, In past i've tried to present a proposal package called HTML_SetupWizard. Now i'm pretty sure that nobody are interesting by this application. I've followed all rules of PEAR coding ( error handling, OOP, ...) in hope that my package will be at same side as some of the best of PEAR. I've learnt a lot especially by studing packages as QuickForm, Config, Page, CSS, Log, MDB, I18N, TreeMenu, and last but not least PackageFileManager. For all newbies, as i was myself few months ago when i discovered PEAR community, and futur package-proposal owners, i've only one suggestion to give : Even if your idea is not recognize, for many reasons (good or bad), don't forget that the way of your making as probably enriched Open Sources Community and perharps Open Minds of some of their members (and give new ideas). A presentation of a new product, concept, is not so easy; i've just tried it again with a shockwave flash (411 Kb) available at http://farell.free.fr/en/pear/sources/HTML_SetupWizard/ Sorry for the watermarks, but i've used ViewletBuilder 3.5.4 (freeware version) from http://www.qarbon.com I know it could not help to see the presentation in good conditions, but it's not my fault. BTW, i've a suggestion to all authors of packages. Making API doc is a good begin, but for all others users than yourself, examples by practices is better. Don't forget it. Tutorials and real context of uses, and perharps a list of tips and tricks. I know it's more easy to tell than to do ! Have nice days of programing :o) Laurent Laville