On Jan 8, 1:35 pm, "Dr. Tarique Sani" <[EMAIL PROTECTED]> wrote:
On 1/8/07, AD7six <[EMAIL PROTECTED]> wrote:
> you still have to put the css and js files in the
> webroot and remember to delete/update them should you remove/update
> your extension.
This is what restricts the actual plug and play as well as portability
of plugins currently but I don't think allowing multiple webroot(s)
scattered all over the place is a good idea at all.
Tarique
--
=============================================================
PHP Applications for E-Biz:http://www.sanisoft.com
Cheesecake-Photoblog:http://cheesecake-photoblog.org
=============================================================
I wouldn't propose multiple webroots, unless you understand what I'm
about to write as such..
Given that for quite some time (with 1.2)
/js/a_name/notinthewebrootjsfolder.js makes cake look for
/vendors/js/a_name/notinthewebrootjsfolder.js (and the same for css)
why not extend this so to check for
/app/plugins/a_name/js/notinthewebrootjsfolder.js, (if the plugin
folder exists)
or
/app/something/a_name/webroot/js/notinthewebrootjsfolder.js or whatever
other logic would work..?
I am only really concerned with serving js and css files, not sure if
there are any other situations being considered.
On Jan 8, 1:35 pm, Dieter wrote:
On 1/8/07, AD7six <[EMAIL PROTECTED]> wrote:
it's a nice feature though, that you can just add some code in your
bootstrap to tell cake to load some more models/controllers/.. from the
paths you specify. But letting cake look automatically in a specific
directory would make much more sense to me. (like it does for
plugins/vendors)
I think you misunderstand Dieter, if you specify these path variables,
they are checked 100% transparently.
I.e. if you specify modelPaths you don't say to cake "load this model
from there", cake looks in the paths you specify whenever it loads a
model. So, for example if you have a user model in your app, and a
special user model in a path you specify in the modelPaths var, as I
understand it the special model will be loaded.
So as a further example, you create
app
etc.
special
controllers
fantastic_controller.php
models
fantastic.php
views
fatastic
index.thtml
You define modelPaths, controllerPaths and viewPaths to point to the
special folders in your bootstrap
You browse to /fantastic and it works
You undefine modelPaths, controllerPaths and viewPaths to point to the
special folders in your bootstrap
You browse to /fantastic and it does not work
You delete the folder special
repeat ad infinitum.
I don't think cake should look anywhere except where it expects things
to be out of the box, and with a minor edit to the bootstrap you can
turn on and off these merge-ins with only the css/js problem left to
solve.
Am I convincing anyone :D?
HTH,
AD7six
Please note:
The manual/bakery is a good place to start any quest for info.
The cake search (at the time of writing) erroneously reports less/no
results for the google group.
The wiki may contain incorrect info - read at your own risk (it's
mainly user submitted) :) You may get your answer quicker by asking on
the IRC Channel (you can access it with just a browser
here:http://irc.cakephp.org).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
