Re: role="publicweb" issue

Hi, The prompts are only a part of the configure options for building, and the code to do the prompts is hard-coded in the middle of the Installer's install method. I'm not sure a prompt is a good idea for anything but installation. Another solution that occurs to me which is better, is to use a relative path, so if I need to access HTML_TreeMenu's publicweb files, I use < script source="../../HTML/TreeMenu/blah.js" /> etc., so I'm not sure the publicweb_uri is really necessary after all. I do think it would make sense to implement the phase attribute of scripts sooner rather than later, as this will allow scripts to be written that do the prompting that is needed, and modify the appropriate area of PEAR. Greg Alan Knowles wrote:

Wasnt there general support for prompting for things on install. (eg. like pecl packages needing to know config paths) I think as you dig deeper into this area of application/web installation, you will see more and more things that need to be configured. A generic prompt mechanism, that can do regex's in files based on the values would probably be more suitable.. Regards Alan Greg Beaver wrote:

Hi, I was just experimenting with the code I wrote to implement role="publicweb" and realized that another config variable needs to be added, which is the relative URI to use as a base for PEAR files. In other words, on my system, publicweb_dir = C:\Web Pages\chiara\pear, but I need a publicweb_uri = http:\\localhost\pear\ Are there any other bright ideas on how to configure this so that it will work? What this really means is that all .css and .js files will need to use the replacements feature of the pear installer, in order to replace the publicweb_uri value, which adds a bit of complexity, and makes it impossible to install the packages just by untarring them. Greg