Hi again Lee,
> I started something like that (in Perl) a couple of years ago. Lost
> interest cause I was in need of a job at the time. Never went back to it
> unfortunately.
>Know the feeling.
> Do / will modules be auto-detected, so if one calls another that doesnt
> exist, it doesnt crash out, just let it be known and carry on ?
>Absolutely. Currently, module selection it done via the rewritten URL, i.e.
a URI of, '/phactory/content/view/this/is/an/article/' will select the
'content' module, the 'view' action and pull an article with the key
'this/is/an/article' from the database. This allows the entire application
to be hierarchal and search-engine friendly. However, it is possible to set
defaults, so if the content module wasn't available, you could set a default
module to load. Or alternatively, you could use an extension of PEAR_Error
to handle these errors (which would be the default in my view). The webapp
would never crap out though, all errors would be handled intelligently, with
no parse errors printed to screen.
> Are / will modules be auto-installed similarly, ie. no need to update
> this conf file of that ini file or add thi sto the list over there. Just
> place file in modules directory and next time app runs, tehmodule gets
> noticed, imported, parsed. etc.
>Currently this functionality isn't available, but I would intend having
modules installed from the shell, with install scripts (written in PHP).
This would be necessary mostly for security, to avoid the possibility of the
Apache user being allowed write to the filesystem. However, I would avoid
the use of config files, I would intend using a phactory_settings table in
the database as a registry of sorts. The only actual config file would be
the master database connection, which would be read-only. All users would be
authenticated using the PHPMyAdmin advanced auth model, where they have to
enter their username and password to access the database. Permissions would
work in the same way. Related to this, database selection would be via
HTTP_HOST.
> As for front end. It would be nice to support Mozilla but a folly to
> support it alone until it gets a non-hacker userbase (maybe when AOL
> releases it to its grubby masses).
>> Still, many things can easily be done cross-browser with Mozilla
> and MSIE, as long as you keep long-term goals in sight, and avoid
> quick'n'dirty hacks as much as possible.
>I don't entirely agree, I would be inclined to make Mozilla the default, and
make it downloadable from the distribution site. I'm willing to listen to
reasoned argument though.
> Reading back on your original mail, I'm still wondering if you had a
> specific question, or just making your plans known ?
>I'm essentially looking for volunteers to work on / contribute to this
project. They don't ncessarily have to be frontend or backend coders, even
thinkers will do. At the moment, I would like to set up a mailing list, get
a few people who are interested on it, and have a chat about the basics.
adam
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
