On Wed, Apr 16, 2008 at 5:08 PM, Max <[EMAIL PROTECTED]> wrote:
> Is it something which is planned for next versions? I see this is very
> much needed when you make plugins for editor or any other module for
> that matter. I'm trying to enable drop-folder plugin functionality.
QND coding shows t
Is it something which is planned for next versions? I see this is very
much needed when you make plugins for editor or any other module for
that matter. I'm trying to enable drop-folder plugin functionality.
Check my blog:
http://www.gigapromoters.com/blog/2008/04/15/designing-for-reusability-tak
On Tue, Apr 15, 2008 at 12:40 AM, Max <[EMAIL PROTECTED]> wrote:
>
> I've been looking for the very same thing from last few hrs..
> Changeset 6189 (https://trac.cakephp.org/changeset/6189) suggests that
> JS and CSS support is added, but I cant seem to even access css/js
> files inside my plugin
I've been looking for the very same thing from last few hrs..
Changeset 6189 (https://trac.cakephp.org/changeset/6189) suggests that
JS and CSS support is added, but I cant seem to even access css/js
files inside my plugin directory.
What folder am I supposed to keep inside my plugin folder? webr
submit a patch with the relevant test case.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email t
Well, i realize this is a bit of a dillema: performance vs.
architectural. I just think it would be cleaner if a plugin could also
contain its own images, since layout- and viewtemplates are also
included in a plugin. But i agree there could be some performance
backdraws. I think if this were to b
Having things like css, js and images (mostly static content) served
directly by the webserver from the document root (bypassing cakephp
routing) is a good thing in terms of performance, and makes easy to
serve that from a server farm using a light webserver (i.e. lighty).
On Thu, Apr 10, 2008 at
Well, if images aren't supported yet, i think i rather wait with the
whole plugin idea... it is quite a hassle to change everyting for a
plugin, so if i do it, i really want it to pay off...
Isn't this ticket worthy?
On 10 apr, 04:06, Gwoo <[EMAIL PROTECTED]> wrote:
> /plugin/plugin_name/vend
/plugin/plugin_name/vendors/css/your_css.css
$html->css('/plugin_name/css/your_css.css');
The only thing that is not added yet is image support. I suppose this
could happen easily.
Have a look at the test cases with the changeset. They might help to
explain how things work a little bit more.
B
