From: Shaun M. <sh...@ae...> - 2004-04-28 01:43:59
|
On 27 Apr 2004, at 21:55, Matthew McNaney wrote: > > As for the future, what do people feel about a module installing its > own > libraries? Should boost have a parameter for library files? > That would be useful although I tend to use my systems PEAR libs instead of the phpWebSite lib/pear versions. I don't know if there's a way boost could do a 'pear install/upgrade blah' but that may be preferable to some. I imagine some users are blissfully unaware of the pear commands. Maybe that's going too far though. > > Another reason for us to consider this is for javascript. Some folks > may > want their custom javascripts to install into the javascript/ directory > when their module installs. > That kind of functionality might also be useful for other reasons. eg. wysiwyg editors and installing themes that require javascript. Almost all of my themes include one or two bits of javascript to fix Internet Explorer bugs like transparent PNG support and some CSS bugs. It'd be nice to open up boost for theme installs. > So, how much do we help the site admins? Should they be responsible for > copying these files over or should the software help them out? Provided version/dependancy checks are done before copying, it would help. You have to remember that some site admins have no command line access as well and limited knowledge of PEAR and *NIX. Shaun aegis design - http://www.aegisdesign.co.uk |