Re: Splitting of Structures_DataGrid into subpackages?

Greg Beaver wrote:

Olivier Guilyardi wrote:

One may argue that package.xml could be where to configure such subcategorization... But some fields on the "New package" form at pear.php.net could also do the trick.

package.xml is used for installation only. In other words, this only affects the way people view the packages. As such, this information belongs solely on the server in REST and in the categorization. Sub-categories would be an easy way to support this, but then again, someone would need to code the actual support, as always :)

AFAICS, package.xml is not only used for installation, but is also read by the web site backend in order to display the changelog, etc...

From an installation perspective, package.xml already has full support for sub-packages through optional package groups. For instance, if you define a group named "all" that contains all the drivers, users can install all of them with: pear install Structures_DataGrid#all

That's excellent. Then we could have two groups : datasource and renderer. Do you believe that it's possible for the web site backend to read package groups and reflect them on the online package browsing interface ? If so, I'll post a feature request that goes in that sense. There's no hurry anyway. It's just to make the web site experience more comfortable. For now there's 17 drivers, but in 6 months there may be 10 more... -- og