On 7/10/07, MrKrinkle <[EMAIL PROTECTED]> wrote: > > I am more than happy to "just build it, damnit". But the question is, > which framework to build it with. (And has one done this job > already.)
As one of the founding fathers of the "just build it, damnit" club, CakePHP chapter, I am reading this thread and wondering back to your original comment: "I've written a framework that does this- handles most of the work. The multiple controllers are in a hierarchy and their namespace is a reflection of their position in the tree. But I was hoping this already exists in some other php framework." Given that you have something that works why would you try to move it to CakePHP? When I look at your problem I think to myself "why would you want to do this anyway" as I am having a hard time visualizing a way to solve this without resorting to Ajax-type functionality where you update divs that contain the pagination elements you require. I say this because I have no idea of the actual problem domain, but have no problem being flippant. My usual response would be "edge case, move on" but I'd at least like to hear (read?) how this type of navigation (two different sets of pagination on a page) would be beneficial to the users of a site, because I just don't see the point in something like it other than as some sort of masochistic display of programming ability. Being lazy, I don't like pain. ;) -- Chris Hartjes Senior Developer Cake Development Corporation My motto for 2007: "Just build it, damnit!" @TheBallpark - http://www.littlehart.net/attheballpark @TheKeyboard - http://www.littlehart.net/atthekeyboard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
