Re: Learning PEAR

Reading the documentation and examples for the quickforms rendering engine, I was able to write a new renderer (for flexy templates) in just a couple of hours. There's nothing wrong with the documentation, at least as far as renderers are concerned. I don't think any of the developers on this list mind constructive criticism, or feature requests, so long as users are somewhat polite and don't just rant about what they feel to be shortcomings of one aspect or another of a package. This problem of users whining about anything they don't like seems to be endemic to the open source community. But that's the marvelous thing about open source! Don't like something, submit a fix. While, getting feedback from users is good, when they start the whining that their free software doesn't scrub the toilets or do the dishes, I say, "put up or shut up" (Or pay me ;) ) -Ron (contributor, but not slave, to open source) Alexey Borzov wrote:

Hi! James 'Chip' Kaufman wrote:

The only way I've been able to get Quickform to do anything useful for me is to read the source. I suspect most potential users won't be willing to do that.

A note: there are usage examples available. They are far more complex than the stuff that is inside the docs and they really show you how QuickForm works while the docs are 'static'. Docs + examples are far more powerful than just docs.

Let me know how I can help and I'll try to pitch in.

Why don't you do HTML_QuickForm_group's API documentation? P.S. Once again, I don't mean to be rude. But: I am not the original QuickForm author, I joined its development to 'scratch my itches'. Documentation is *not* my own itch, I do it to help users. And I don't really understand why they have time and energy to bitch and moan and don't have them to scratch their itches (to write docs).