Rodrigo wrote:
But how about the /root part? Can mixed-up root dirs be seen as a
single root dir easily?
I'm interested in making a pluggable app as well. Seems like you and I
would want the ability to specify an arrayref for MyApp-config-{root},
and have that work. Poking around
On 28 Jun 2009, at 09:16, Robert Buels wrote:
Rodrigo wrote:
But how about the /root part? Can mixed-up root dirs be seen as a
single root dir easily?
I'm interested in making a pluggable app as well. Seems like you
and I would want the ability to specify an arrayref for MyApp-
Tomas Doran wrote on 6/28/09 10:08 AM:
On 28 Jun 2009, at 09:16, Robert Buels wrote:
Rodrigo wrote:
But how about the /root part? Can mixed-up root dirs be seen as a
single root dir easily?
I'm interested in making a pluggable app as well. Seems like you and
I would want the ability
Assuming that you're mandating a TT view for your pluggable parts, then you
can just subclass View::TT to have an INCLUDE_PATH which picks up the 'root'
directories from all your loaded 'Components'.
I usually have /static stuff too, mostly css and images.
Rodrigo wrote on 6/28/09 12:11 PM:
Assuming that you're mandating a TT view for your pluggable parts, then you
can just subclass View::TT to have an INCLUDE_PATH which picks up the 'root'
directories from all your loaded 'Components'.
I usually have /static stuff too, mostly css and images.
Hi all,
I have an application that has many features (or plugins, or extensions,
or bundles, or whatever, but I'll call it feature for uniqueness sake),
which are subsets of the app that may or may not be bundled into the
application, depending on the customer it will be shipped to.
What I'm
