[Seaside] SeasideRest and complex structures

Norbert Hartl norbert at hartl.name
Sat Apr 23 07:44:52 UTC 2011

Am 19.04.2011 um 23:02 schrieb Esteban Lorenzano:

> Hi,
> I now understand how to use SeasideREST, and I'm trying to use it in a real application. 
> What's the problem? well... I want my rest filters to replace a portion of the screen and not all of it. Let's say I have this structure 
> app {
> 	menu { option1, option2, option3, etc. }
> 	contents: { hereAComponentForEachOption }
> }
> yeah, you need to be a little imaginative to understand what I'm trying to describe, but I think is clear: a main "div" with app, and then two divs, one with the menu and other with contents.
> In my current application, if I press "option1" I can say contents show: option1Component.
> So... I want to get same result if I do: 
> http://localhost:8080/app/option1
> any idea how I can proceed?
Do you want to have a rest handler as a filter of your application that gives additional control or do you want to receive the whole thing via a rest dedicated handler? 


More information about the seaside mailing list