Dirty Components

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Dirty Components

Michael Niessner
Does seaside have any concept of dirty components?

Like is the following scenario possible?

MyRootComponent
--- UserListComponent (displays a list of users)
--- UserDetailsComponent (displays details of a user)
--- EditUserComponent    (some editable fields for the user)

Have the UserListComponent and UserDetailsComponent observe  
EdituserComponent and mark themselves as dirty if a specific change  
occurs (for example: UserDetailsComponent would be dirty for any  
change, but UserListComponent would only mark itself as dirty if the  
name changed).

Then submit the form via ajax, have the EditUserComponent save the  
changes, and then let seaside respond by rerendering just the dirty  
components.

Thanks,
Michael Niessner
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Dirty Components

Philippe Marschall
2009/3/26 Michael Niessner <[hidden email]>:
> Does seaside have any concept of dirty components?

No.

Cheers
Philippe
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside