-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Christopher,
Christopher H. Laco via RT wrote:
| Now that this is a plugin, it would be nice if you could specify a
| namespace that all of the magic would be created under.
|
| In other words, in an existing app, set namespace: /admin, then you
| would go to /admin/<tablename>
Yep, that's a good suggestion, which others have requested as well. I
should add it to the TODO because it'll happen soon enough.
In the meantime, with Apache, you could run LFB as a separate app but
handle the /admin url differently in the Apache configuration, and pass
the rest through to your main App.
There are a few related issues here - there is the Namespace of the Perl
modules (e.g. Model::DBIC::Foo, etc), also the Configuration File
namespace (i.e. LFB config vars in their own key in the config hash),
and finally there is the App url namespace as you mentioned above.
Lots for me to consider, so any Good Ideas are welcome!
Thanks for the feedback,
- --
Oliver Gorwits, Network and Telecommunications Group,
Oxford University Computing Services
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org
iD4DBQFIo9cs2NPq7pwWBt4RAuZLAJdd+wcKgpQbEe1XT3SuY451Msq8AKDbCWFw
+aEOfEDeOkjqedNY3RRfaA==
=LzIR
-----END PGP SIGNATURE-----