On Jul 10, 1:06 pm, AD7six <[EMAIL PROTECTED]> wrote:
>
> <snip>
> By "custom url box", I mean permalinks. It's the same challenge.
>
> I don't see much of a challenge. If you follow the ajax route which
> was one of 2 suggestions I made, you just need a "pull both pagination
> states and send me to a url that identifies them both" function.
The challenge is to maintain the integrity of the URL in the location
bar of the web browser, that's the challenge. It must represent the
page at all times, except POST requests. (That's how this whole HTTP
thing was designed.) If I do it with a custom url box or permalink, I
have all the same work to do, plus a klunky interface that the user
isn't used to.
And you're going to need more than a "pull both pagination states and
send me to a url that identifies them both" function. That's the
serialization part. You're also going to need the deserialization
part. "figure out which namespaces belong to which controllers".
Further, every (internally pointing) hyperlink on the page needs to
encapsulate the state of every controller on the page. It's not
trivial. And on top of that, you ought to have something that
creates the namespaces automatically. Pretty much all of this should
be automatic; it's in the framework's domain. (My framework does this
stuff.)
All of this is something the framework should deal with, not me. My
controllers should all be unaware that namespaces exist. And that's
why choosing the right framework matters.
> Unless you want to pay me to do it, I'm not
> willing to suggest any more ;)
Fair enough, I can't argue with that, thanks,
mk
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
