Re: preview of PEAR_PackageFile2Manager

Greg Beaver wrote:

The most important API difference is that PEAR_PackageFile2Manager extends the PEAR_PackageFileManager_v2_rw class. This means all of the low-level stuff that was handled by setOptions() in PEAR_PackageFileManager has been removed. In other words, instead of: $pfm->setOptions('package' => 'blah', 'version' => '1.0.0', 'state' => 'stable'...) you will do: $pfm->setPackage('blah'); This change will affect packages like PEAR_PackageFileManager_Gui_Gtk only that instead of using getOptions(), you will retrieve the values individually using the API from PEAR_PackageFile_v2 (like $pfm->getPackage(), $pfm->getVersion(), etc.)

Thank you! The set* and get* methods will make developing interfaces much easier. It will allow much more fine grain control when a uesr inputs data. On a somewhat related note, I think the GTK front end for this package should be PEAR_PackageFile2Manager_GUI_Gtk2. The 2 at the end means PHP-GTK 2. The reason I even bothered mentioning this is because PHP-GTK 2 requires (will require actually) PHP 5.1. I am assuming that PEAR_PackageFile2Manager will not require PHP 5 since PEAR 1.4.0 doesn't require PHP 5. Are there any major objections to this idea? The main resoning for this is that before any gui can be declared stable, PF2M will need to be stable. Before that can happen, PEAR 1.4.0 will need to be stable. By that time PHP-GTK 1 will be deprecated. Maintaining a package based on a deprecated extension doesn't sound like much fun to me. Thanks, -- Scott Mattocks scott@crisscott.com http://www.crisscott.com