Re: PEAR Installer GUI project

le 24/05/02 14:45, Stig S. Bakken à ssb@fast.no a écrit : > On Fri, 2002-05-24 at 12:48, Bertrand Mansion wrote: >> Hi all, >> >> I have heard some time ago someone (sorry I don't remember who) talk about a >> php-gtk version of the PEAR installer with a GUI. Is this a project or is it >> already started ? >> >> I have some time this afternoon to code a PEAR Installer GUI for MAC OSX >> with Objective-C. My main concern is how to detect if php is installed as >> cgi and, if not, to install it. Do you believe installing php from the PEAR >> installer is a good idea or not ? > > Hi, > > I'd love to get some help with the Gtk version. But please don't start > a separate project with a different codebase, because the installer > already have a PHP infrastructure for different user interfaces. > > Right now all the PEAR commands are implemented in a UI-neutral way > (take a look at the files in php4/pear/PEAR/Command/*.php). All user > interaction should go through a frontend class > (php4/pear/PEAR/Frontend/*.php). I have added a skeleton for the Gtk > class there. If you have php-gtk installed and run "pear -G" it will > start the installer in Gtk mode, but right now all it does is open a > window. ;-) > > I have lots of ideas on how to design this technically, which has lead > to the current command/frontend architecture. I'm not completely > confident about the user interaction scheme yet, right now it does > interaction calls "on demand", which may not give the best results in > Gtk. For example, if the user should confirm something, the UI class > does not know this until the command code requests confirmation, so it's > not possible to render a screen in Gtk with a checkbox for the > confirmation. It has to be a pop-up window right now. The alternative, > that would allow for Gtk screens with all options laid out in advance, > is using an XML-based form format, but that's much more complex so I > wanted to try this approach first. My first thought was just to make a wrapper for the unix command 'pear' with tables and buttons and menus and preferences and so on... It would take the result from the pear command, parse it and display it in the GUI. This is quite simple to do with MACOSX and cocoa. On the other hand, I know nothing about GTK. It's not that I don't want to learn but it looks ugly compared to MACOSX interface. No one will probably ever use the php-gtk extension on MACOSX. And why would you use a GUI interface to set up pear if you already know how to compile php on MACOSX (which is not the easiest task at the moment) with the php-gtk extension ? I don't even know if GTK works on MACOSX out of the box. IMO the best thing for macosx users would be a GUI developed in Cocoa (objective-c), you would just have to drag-drop it on your disk and it would install. But I reckon it would be better if all the interfaces could look the same. So I will wait a while see how it goes, see if I can help and if I am still motivated and find the time, will make a cocoa version of the php-gtk frontend. I hope this is ok for you, if not, tell me why. Thanks Bertrand Mansion Mamasam