Another thing for example... i have plugin users, also i have controller
users... if i have to access the action login in plugin users and
controller users... the url would be /users/users/login, it would be nice
if the plugin checks if there isnt a controller called login, if not it
sends the
I *think* he was talking about case [1] to be honest AD. In the example
given, it was to change a plugin due to database table clashes. I would
hope that if it was your own plugin, then database table clashes would
have been thought about beforehand.
Some clarification would indeed be peachy
On 22/06/12 04:03, Jamie wrote:
On Thursday, June 21, 2012 9:23:44 AM UTC-7, Ratty wrote:
You should not be changing any plugin code anyway. That's why they
are
plugins...
You update them straight from github when you need to. If you want
to modify
the behaviour of a
Also, if we are adding functionality to a plug-in, or fixing something that
doesn't quite work. We should probably committing that code back with the
owner of the plug-in. Considering most plug-in developers are scratching
their own itch, and not necessarily doing a market needs assessment to
TOTALLY agree Vinnie.
I believe that's what Open Source is all about.
Steve.
On 22/06/12 11:56, SpazzyV wrote:
Also, if we are adding functionality to a plug-in, or fixing something
that doesn't quite work. We should probably committing that code back
with the owner of the plug-in.
On Thursday, 21 June 2012 18:23:44 UTC+2, Ratty wrote:
On 21/06/12 14:44, Andr� Luis wrote:
It�s not the cause of being appropriate or not, but i would like to
use plugins folder ONLY for really PLUGINS, wich i dont change
anything, just use... Modular will work ONLY for that
Re the difference with plugins - I get your point, but if I want to have a
plugin with multiple models and controllers etc, then surely I still end up
losing that module structure, and end up with /Controllers and /Views
lumping things together?
My best reasoning for this is:
* easier to
On Thursday, 21 June 2012 12:07:27 UTC+2, the_woodsman wrote:
Re the difference with plugins - I get your point, but if I want to have a
plugin with multiple models and controllers etc, then surely I still end up
losing that module structure, and end up with /Controllers and /Views
It´s not the cause of being appropriate or not, but i would like to
use plugins folder ONLY for really PLUGINS, wich i dont change
anything, just use... Modular will work ONLY for that application.
The reason for modular programming is:
imagine you have /products/categories wich uses Category
On Thursday, 21 June 2012 15:44:26 UTC+2, André Luis wrote:
It´s not the cause of being appropriate or not, but i would like to
use plugins folder ONLY for really PLUGINS, wich i dont change
anything, just use... Modular will work ONLY for that application.
So - put your modules in the
On 21/06/12 14:44, André Luis wrote:
It´s not the cause of being appropriate or not, but i would like to
use plugins folder ONLY for really PLUGINS, wich i dont change
anything, just use... Modular will work ONLY for that application.
You should not be changing any plugin code anyway. That's why
On Thu, Jun 21, 2012 at 6:07 AM, the_woodsman elwood.ca...@gmail.com wrote:
* Encourages less coupled code - in theory these modules could almost be
framework agnostic,
That's what the Vendors folder is for. Anything in there that's
Cake-specific should be in Plugins. And *those* are called
On Thursday, June 21, 2012 9:23:44 AM UTC-7, Ratty wrote:
You should not be changing any plugin code anyway. That's why they are
plugins...
You update them straight from github when you need to. If you want to
modify
the behaviour of a plugin model for example then you can extend it in
On Friday, June 22, 2012 10:03:57 AM UTC+7, Jamie wrote:
On Thursday, June 21, 2012 9:23:44 AM UTC-7, Ratty wrote:
You should not be changing any plugin code anyway. That's why they are
plugins...
You update them straight from github when you need to. If you want to
modify
the
+1 for being able to configure Cake like this!
IMHO, there's something much more elegant in the dir structure:
/Users
/controllers
/models
/views
/Articles
/controllers,
etc!
Many other frameworks take this approach, and to me it seems easier to
modularise your code - for example,
On Thursday, June 21, 2012 7:26:44 AM UTC+7, the_woodsman wrote:
+1 for being able to configure Cake like this!
IMHO, there's something much more elegant in the dir structure:
/Users
/controllers
/models
/views
/Articles
/controllers,
etc!
There's practically no difference
No,
but you can group mvc files by adding additional paths in
bootstrap.php (see doc comments), but this is not best solution.
(performance and some other issues on how cake includes view files)
On Aug 26, 11:09 pm, Mech7 chris.de@gmail.com wrote:
Is there way to setup modules in cake... I
Well, you could just write plugins that take advantage of this
functionality - i.e. write a Blog plugin that will use a Tag plugin if
it exists.
On Aug 26, 2:09 pm, Mech7 chris.de@gmail.com wrote:
Is there way to setup modules in cake... I don't mean plugins which
are seperate
But plugins are not convenient to use for this purpose as they have
their own layout / script etc files.. And not really share anything
from the main application
On Aug 27, 4:36 pm, Jamie jamie@gmail.com wrote:
Well, you could just write plugins that take advantage of this
functionality -
On Oct 10, 3:24 pm, stefanb [EMAIL PROTECTED] wrote:
Thank you for the second half of your reply. The first half didn't
help me at all.
The first part should help you realize that you should first invest
some time by looking at the manual. If you don't have time to do it
why do you think ppl
Though the first half is the correct one.
On Oct 10, 10:24 am, stefanb [EMAIL PROTECTED] wrote:
Thank you for the second half of your reply. The first half didn't
help me at all.
On Oct 10, 3:12 pm, Christian Winther [EMAIL PROTECTED] wrote:
Did you even bother to look in the manual
... and yet you took the time to answer my basic question. How will I
then learn the lesson? ;)
On Oct 11, 12:41 pm, Marcin Domanski aka kabturek [EMAIL PROTECTED]
wrote:
On Oct 10, 3:24 pm, stefanb [EMAIL PROTECTED] wrote:
Thank you for the second half of your reply. The first half didn't
So a plugin is not the same as a module? Now I'm confused.
On Oct 11, 12:43 pm, dardosordi [EMAIL PROTECTED] wrote:
Though the first half is the correct one.
On Oct 10, 10:24 am, stefanb [EMAIL PROTECTED] wrote:
Thank you for the second half of your reply. The first half didn't
help me
No, the plugin part is right
But the first part about you not bothering to search for answer first is also
true
-Original Message-
From: cake-php@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of stefanb
Sent: 11. oktober 2007 13:39
To: Cake PHP
Subject: Re: Modules?
So
You can consider plugins to be modules of CakePHP as they are built to
be able to integrate with any Cake installation.
On Oct 11, 7:39 am, stefanb [EMAIL PROTECTED] wrote:
So a plugin is not the same as a module? Now I'm confused.
On Oct 11, 12:43 pm, dardosordi [EMAIL PROTECTED] wrote:
] On Behalf Of stefanb
Sent: 11. oktober 2007 13:39
To: Cake PHP
Subject: Re: Modules?
So a plugin is not the same as a module? Now I'm confused.
On Oct 11, 12:43 pm, dardosordi [EMAIL PROTECTED] wrote:
Though the first half is the correct one.
On Oct 10, 10:24 am, stefanb [EMAIL
PROTECTED] On Behalf Of stefanb
Sent: 11. oktober 2007 13:39
To: Cake PHP
Subject: Re: Modules?
So a plugin is not the same as a module? Now I'm confused.
On Oct 11, 12:43 pm, dardosordi [EMAIL PROTECTED] wrote:
Though the first half is the correct one.
On Oct 10, 10:24 am, stefanb [EMAIL
Thank you, finally a reasonable answer! :)
On Oct 11, 3:32 pm, savagekabbage [EMAIL PROTECTED] wrote:
You can consider plugins to be modules of CakePHP as they are built to
be able to integrate with any Cake installation.
On Oct 11, 7:39 am, stefanb [EMAIL PROTECTED] wrote:
So a plugin is
true
-Original Message-
From: cake-php@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of
stefanb
Sent: 11. oktober 2007 13:39
To: Cake PHP
Subject: Re: Modules?
So a plugin is not the same as a module? Now I'm confused.
On Oct 11, 12:43 pm, dardosordi [EMAIL PROTECTED
Did you even bother to look in the manual or the group ?
Its called plugins in cake
-Original Message-
From: cake-php@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of stefanb
Sent: 10. oktober 2007 10:36
To: Cake PHP
Subject: Modules?
Does Cake support the use of modules?
Thank you for the second half of your reply. The first half didn't
help me at all.
On Oct 10, 3:12 pm, Christian Winther [EMAIL PROTECTED] wrote:
Did you even bother to look in the manual or the group ?
Its called plugins in cake
-Original Message-
From: cake-php@googlegroups.com
31 matches
Mail list logo
