Re: New Package: HTML_DB

On Thu, 24 Apr 2003 echo15@delirium.ch wrote: > yet, not even fully implemented. That's why I wanted them not to be > used by anyone for now but still post the source to have you guys tell > me if there's a place for it on PEAR or not. I'm just not willing to > post a piece of software that's resembling a Swiss cheese - with holes > here and holes there. If it's LGPL'd and it breaks, nobody can complain - and at least that way they can legally modify their copy (which means, when they fix it, they can send the changes back). As for documentation, well, that's something that most PEAR classes don't seem to have anyway, so I don't think that's going to be a major sticking point... <g> > >> DB_FORM > > Don't know whether it's functionality crosses OOH_Form, though (and I > > can't tell > > because OOH isn't documented, either, and it's code is thoroughly > > opaque). > > I don't know OOH_Form. Where can it be downloaded? It's not really a It's in PEAR CVS. I'm pretty sure there's packages for it. > AFAIK, Apache mods work with HTAuth only, with the little password > requester windows. (Or not? If not, what is PEAR Auth good for?) Two I think that's pretty much it. When you said you could make a drop-in replacement for apache auth modules, I thought you meant you were implementing the HTTP Authentication stuff in PHP. > It's a SQL table to HTML list renderer. You create a list object from > an SQL table and add columns to it. There are properties to tweak the > way the content is displayed, you can add action buttons to each row > etc. Finally you call the render method and get a HTML table displayed > based on the list object you've just created. This HTML table (the > list) has built-in core functionalities such as sorting (little arrows > in the column header), pageing (like search engines split results on > several pages) and search. The idea is to use DB_List to Browse DB > content and then link with action buttons to link to a second page with > DB_Form to insert/update/delete content. Together with DB_Form you have > to create only two simple pages to have a complete frontend for an SQL > table. Very cute. > (It's somewhat inspired by ASP.net, I wanted to create SQL DB frontends > at the same pace and flexibility as I could do with ASP.net.) And that run on something other than the evil empire's stuff. <g> > And - there will be a documentation with examples and all. That is where most of the PEAR classes fall down - there's no decent documentation. If you can properly document your stuff, you'll have me as a loyal user, that's for sure. <g> > Hope this helps to get an idea of what I'm cooking here. Again, my aim > to submit this at this quite early stage is to figure out if it's good > for PEAR, as I wouldn't implement some useful features that I'm not > gonna use myself at this point. My suggestion is to implement what you find useful, and keep the code documented and clean. Then everyone else can add what features they find useful. Limits the amount of work you have to do, and avoids featureitis (since everything in the class would have to be used by at least one person). - Matt