Hello Guys,
Any help for below points.
Thanks!
Shadab Shaikh
On Sat, Jul 11, 2009 at 12:19 PM, Shadab Shaikh wrote:
> Hi James, Robert & Other crew members,
>
> Thanks for all your answers. I appreciate all senders’ comments.
>
> I think we are near to our requirements.
>
> I like the Robert an
I too am aware of Joomla, and have wondered how cake would do
something similar. I am only relatively new to cake, when reading the
docs the closest thing I could see were Elements (but I don't know
their limitiations).
It may be worthwhile posting a more generic question, such as: how do
cake
I think elements can be cached. So you may get around querying the
Models (which themselves use caching for when you do so) if the
contents of the elements are not updated often.
I came to Cake from Joomla as well and would like to hear about how to
do this. So far it seems that elements (with s
@James:
from my experience, using
ClassRegistry::init() instead of App::import()
creates the model instances only once (so called Singleton Pattern)
therefore you dont have that much more memory usage..
using this inside elements might not be MVC like, but it would come
close to the above "Joom
Any modular system is going to be written to meet specific needs. The
main issue that I see with CMS-rivaling system is the need to tie it
in at all stages of the application: model, view and controller.
Modules themselves would need a database presence, requiring models. A
notification system tha
A helper in conjunction with elements would likely be the closest
thing you'll get to a Joomla module. Elements would contain the
presentation logic for each "module", and the helper could be written
to act like a "module bucket" - pull in the modules for that page,
pass data to the elements and r
Yes, I agree. An element is just a partial view, and would have to be
copied into and reworked for every application. Not to mention that
you can't link an element to content in the database.
I think setting up the core of the modules as a Model would allow for
a lot of flexibility. An Observer p
Hello James & Robert,
Thanks for sharing your ideas with me.
But I think we should use Helper rather than element would be good idea as
element having certain limitation but helper is more extensible.
If any one having other idea please share with us.
Thanks!
Shadab Shaikh
On Wed, Jul 8, 2009 a
There is no entity in CakePHP that work like Joomla modules out of the
box. The closest thing would be elements - elements are "mini-views"
that can be included in layouts or views. However, since they are
intended to be reliant on the information passed to the view they're
included in, they lose
Building any kind of module/modular system has certain complexities,
and if there is any form of public implementation it's unlikely to be
"one size fits all". The first thing is to be very clear what
funtionality you want from the system, and what behaviour you want it
to exhibit.
Modules relate
Hello All,
Greetings of the day!
I want to develop some robust application in CAKE PHP. I would like to
use Joomla module idea in it. Let me clear what is Joomla module, who
are not familiar with Joomla. Joomla module is logic with interface
which can placed at multiple pages at well defined pos
11 matches
Mail list logo
