Re: How many Plug-ins Is Too many

> Just seems like a lot to load

Nothing is loaded until you use it - and it won't make any difference if you _are_ using a file, whether they are all located in one app/plugin, or organized in plugins.

AD

On Wednesday, 22 May 2013 08:57:50 UTC+2, advantage+ wrote:

I guess the question already will depend on the size / scale of the site.

But with everything moving towards packaging components / helper and such as plugins is there a better way or does it really matter?

 

Bootstrap / facebook / twitter / js compressor / css compressor / UserManger / ContentManger / SeoManager / ContactManager / GalleryManager / BritaPurifirer / LESS / Sluggable / Cacheable

 

Just seems like a lot to load. Then on demand ones like Upload / Cropper / Publisher………I can go on all night.

 

Is there a best practice? Most of these run universally and required everywhere so it's not so much a pick and choose when to load them.

 

But if you created a site with no plugins for example and have say the mentioned above ones as straight controllers / models in the respective directories would it be the same thing?(would not do that obviously)

Is there an overhead to deal with or does Cake treat it as if was a regular model / controller as if it was sitting in the model / controller folders?

--
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP
 
---
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscribe@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.