[Seaside] Seaside redirects, really?

Philippe Marschall philippe.marschall at gmail.com
Sun Oct 2 16:20:27 UTC 2011

2011/10/2 Sebastian Sastre <sebastian at flowingconcept.com>:
> On Oct 2, 2011, at 12:30 PM, Philippe Marschall wrote:
> UX is King.
> That's why we need the redirects so the back button and the refresh
> button don't break the application.
> yes I know what you mean. I'm using seaside after all. Is not that is a
> completely invalid way to see things of course.
> But the problem I have with that comes with the experience.
> Most of the times you have to make the components to know how to present a
> fresh view of the model either if the "rendered page" is coming from a back
> button click or a refresh button click or a click on a permalink.
> So if you have to design the app to make it capable to rebuild the
> presentations, then all the juggling to magically recover UI state is...
> less valuable (to put it softly)

Sure, but then you shouldn't use Seaside. The problem is not the
redirect at all but that you're using Seaside in a way it's not
supposed to be used. That's why everything is not painful. If that's
your problem then switch to an other framework.


More information about the seaside mailing list