Re: PEAR Installer GUI project
| From: | Stig S. Bakken | Date: | Fri, 24 May 2002 12:45:50 +0000 |
| Subject: | Re: PEAR Installer GUI project | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-6388@lists.php.net to get a copy of this message | ||
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.
- Stig