On Jul 10, 1:58 pm, "Chris Hartjes" <[EMAIL PROTECTED]> wrote:
> Given that you have something that works why would you try to move it
> to CakePHP?
Ok thank you for your interest. I'm not trying to move to cakePHP,
I'm trying to move to a more widely accepted framework than my
proprietary framework. (I don't care whether it's CakePHP or not. My
original post starts out "I'm looking for a framework that....") The
reason is- when I hire people, it's easier to hire people that know a
widely accepted framework than to teach them my proprietary one. I
could (and may) release my framework open source, but truly, I'm not
interested in running an open source php framework project. (I have
other ideas for open source projects that I'd like to do, but a php
framework doesn't interest me.) Sadly, since most frameworks don't
serve the example I gave in this thread, maybe I have no choice.
>
> 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. ;)
As stated in the original post, and a few times in my responses- AJAX
doesn't maintain the integrity of the URL. If you start clicking on
certain parts of the page, the URL no longer represents the page.
According to the original HTTP design, that's ok if they're POST
requests, but pages that result from GET requests ought to maintain
URL integrity. Users expect this, and they SHOULD.
My framework does maintain URL integrity, as described in some of my
responses here. I wish some other did.
Let me tell you- once you have and use a framework that supports this,
you stop thinking of it as an "edge case". It overtakes the way you
write web applications, for the better. Instead of writing
applications that generate web pages, you generate apps that make
*parts of* web pages. The development of your apps feels more like
desktop apps- you are truly building "components". You can put them
on any page, along side other apps, and they get their own namepsace,
unbeknown to them. This is not an edge case, it's a new paradigm.
(really, it's an OLD paradigm, lost by framework developers.)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
