Re: What's the Cake-way to build a cms?
I only have a few general things to share. You have probably at least some of this in mind already but sometimes repetition is good :) First. It doesn't sound at all like you HAVE TO use plugins for what you describe. Plugins in cake can basically be two things. An optional functionality (a fractal generator is an optional image filter for Photoshop) or a reusable sub-application (debug-kit or maybe a forum module). You are talking about separating out your entire CMS into small plugins which can be done but is certainly not necessary. And I would choose to build it as one application and do the separation later when you find you have a rating-module that you want to re-use in more applications. Second. It sounds like your CMS does not have a clear purpose and set of requirements. It sounds like the one CMS to rule them all. This is very hard to design since almost nothing will be concrete or locked off. The answer to every design-question will be "maybe, it depends". I think you would do yourself a favor by deciding if you are building a blog, corporate CMS, portal software or some new hybrid. Even with a new hybrid you need to decide what it will be and (almost more importantly) what it will NOT be. You might get some inspiration by looking at how Wildflower and Neutrino (two Cake CMSes I have looked at). They are very different in their approach but both are quite general CMSes. best of luck Martin On Apr 20, 11:07 am, Evert wrote: > Well, the system that I thought required requestAction() was like > this: > I wanted to build a cms that's so complete you would only need to > create a new database and a new css-file to create a whole new > website. > Plugins are used as codeblocks. So if I have a page with some content > (an article or whatever), a rating-box for that content, comments for > that content (like a blog) and a poll in the sidebar that would be 4 > plugins. Those plugins are pre-build and basically all I'm doing when > I build that page is just putting the right info in the right tables > in the database. > > Now on IRC people told me I could just use the models and elements of > the plugins and then I wouldn't need requestAction(). > So basically the plugins don't have controllers. Maybe that's possible > for some plugins, but I think it isn't possible for all plugins.. > What about pagination? On that page I described earlier, the content > could be several pages long as well as the comments below that > content. > Pagination uses the URL to send it's page-information, right? So when > I go to page 5 of the comments and then I go to page 2 of the content, > then the comments would be on page 1 again, right? That wouldn't work > right.. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: What's the Cake-way to build a cms?
Well, the system that I thought required requestAction() was like this: I wanted to build a cms that's so complete you would only need to create a new database and a new css-file to create a whole new website. Plugins are used as codeblocks. So if I have a page with some content (an article or whatever), a rating-box for that content, comments for that content (like a blog) and a poll in the sidebar that would be 4 plugins. Those plugins are pre-build and basically all I'm doing when I build that page is just putting the right info in the right tables in the database. Now on IRC people told me I could just use the models and elements of the plugins and then I wouldn't need requestAction(). So basically the plugins don't have controllers. Maybe that's possible for some plugins, but I think it isn't possible for all plugins.. What about pagination? On that page I described earlier, the content could be several pages long as well as the comments below that content. Pagination uses the URL to send it's page-information, right? So when I go to page 5 of the comments and then I go to page 2 of the content, then the comments would be on page 1 again, right? That wouldn't work right.. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: What's the Cake-way to build a cms?
It really depends on why you are creating your CMS, as that would have a strong influence on your architecture. If you can provide more specific questions, maybe we/i can help :) To address your technical question, about plugins with requestAction - again, that depends on your architecture. I've never used requestAction before, keeping logic in the models and views where appropriate. Richard On Mon, Apr 20, 2009 at 9:09 AM, Evert wrote: > > I've tried to think of several ways to build a cms in cake. > But every system I could think of depended a lot on plugins. > One system might use several plugins with one page load and that would > be quite slow cause you needed to use requestAction() a lot. (In that > system plugins weren't like mini-apps, but like code-blocks) > And another system needed plugins to communicate with each other which > isn't really possible in Cake. > > So that kinda failed. > > So my question to you is: > What's the right way to build a cms in Cake? > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: What's the Cake-way to build a cms?
Ok, some people told me I didn't need to use requestAction as much as I thought. I'll try to build a cms with plugins by only using it's models and elements.. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
What's the Cake-way to build a cms?
I've tried to think of several ways to build a cms in cake. But every system I could think of depended a lot on plugins. One system might use several plugins with one page load and that would be quite slow cause you needed to use requestAction() a lot. (In that system plugins weren't like mini-apps, but like code-blocks) And another system needed plugins to communicate with each other which isn't really possible in Cake. So that kinda failed. So my question to you is: What's the right way to build a cms in Cake? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
