Re: CakePHP and widgets

2009-11-26 Thread jaybhushi
.nabble.com/CakePHP-and-widgets-tp526535p4070408.html Sent from the CakePHP mailing list archive at Nabble.com. Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups

Re: CakePHP and widgets

2008-07-20 Thread Rafael Bandeira aka rafaelbandeira3
Andy Dawson's mini controllers still work the best for me - despite the name it really is a combination of Components and Elements Why not to use some model tricks inside a helper? Form helper does it... Grab your model whithin the ClassRegister and serve yourself... I've already done the

CakePHP and widgets

2008-07-13 Thread Steve
Hey, I was wondering what the best approach for creating widgets (type of elements) with Cake. What I mean by widgets is basically elements that pull data from something that may not relate to the current controller/ action the user is in. For example, the default layout may have a sidebar of

Re: CakePHP and widgets

2008-07-13 Thread Mark (Germany)
thats really a good question i would like to know that mysefl i found out though, that requesting might not be the best... the database querys went up by 30% especially if you get config details and session infos from the Database, they will be requested as often as you use this requestAction

Re: CakePHP and widgets

2008-07-13 Thread the_woodsman
An alternative to excessive use of requestAction is to put as much in the models as you can, and carefully load models in your controllers to pass stuff into views. For your example, you could: * give all models a random() and recent() method * Create a WithSnippets controller, and subclass

Re: CakePHP and widgets

2008-07-13 Thread Dr. Tarique Sani
On Mon, Jul 14, 2008 at 2:31 AM, Steve [EMAIL PROTECTED] wrote: I was wondering what the best approach for creating widgets (type of elements) with Cake. What I mean by widgets is basically elements that pull data from something that may not relate to the current controller/ action the user