Re: New package questions

On Wed, 01 Sep 2004 01:19:33 -0500, Jsnell <jsnell@e-normous.com> wrote: > Hi, > > I'm looking to suggest a new PEAR project that I've been working on > which allows a user to easily leverage existing DB_DataObject code to > create a Pager (via the Pager class) with a minimal amount of work for > use with rapid prototyping. I realize there are already a few other > ways to do this, but none of the ones I looked at provide easy > mechanisms for query generation, table output, page size controls, and > column sorting by the user. It also extends the mechanisms of Pager to > pass information between pages, making it easy to create forms on the > same page as the displayed Pager which help to filter the information > shown. Callbacks are supported to provide more complex data formatting, > as well as to assist in creating rows which are combinations or > calculations of other rows. In order to assist rapid prototyping, a > basic link to an edit page can be created easily by specifying a field > for the text source and another for the key used to generate the link. > It is compatible with PEAR's QuickForm field titles for the column > headings, they can be specified, or the field name can be used by > default. Multiple tables can be used in the select by taking advantage > of DB_DataObject's joinAdd() and selectAdd() can be used to add field > aliases in cases where field names would conflict. > Sounds like it has lots of nice features. It also sound slike it has basically the same hting as Structures_DataGrid. There was recently a large discussion on this list about integrating DB_DataObject into DataGrid. > The code is fairly close to completion and I would like to submit a > proposal for it. My only planned changes are to document it, modify it > to use PEAR errors and config files, and then to use the previous to get > my own css out of the class. You can write up a draft proposal and work on it until you're ready to release it, then upgrade its status. > > I read the PEAR docs and it said to send any questions here. My first > question is regarding the name of the package. I have tentativley named > it DB_DataObject_Pager since the goal of it is to leverage and extend > both classes. Is this a bad name? Do I need to finish the code before > submitting the proposal? Must it be fairly working or tested before > submitting or is this only necessary prior to release? The name seems ok to me, but I'm sure there will be discussion as this also creates HTML. The code doesn't have to be finished, but it's nice to have at least a working example so that people can see what it actually does. If you porpose with unfinished code you're going to get lots of comments on what should be fixed. I would suggest making sure you're following the PEAR coding standards before proposing. > > Source can be found here: > http://www.e-normous.com/nerd/DB_DataObject_Pager.phps > > I can set up a running example if it helps. It would. ;-) > > thanks, > Jon Snell > -- DB_DataObject_FormBuilder - The database at your fingertips http://pear.php.net/package/DB_DataObject_FormBuilder paperCrane --Justin Patrin--