Seaside components within Pier, and their state.
nickbrown at fastmail.fm
Fri Dec 18 12:13:28 MET 2009
I'm producing a internal website for my employer, (essentially a front
end for an ancient, somewhat-relation database...), and I've built a few
seaside components (by subclassing WAComponent) for this purpose.
I'm thinking that maybe the best way to structure the site is to allow
these seaside components (tabular displays, forms, etc) to be embedded
I've downloaded the Pier 1.2 image from the piercms.com site, have
loaded my seaside components in, and am able to create links to the
My question is: how do I go about preserving the state of my components?
For example, a tabular report will have an ivar which holds a reference
to a query object, which itself holds (among other things) the name of
the database table. After creating the component and setting the table
name via the web browser, returning to the pier home page, and folling
the links to go back to my component, I'm actually given a new instance
of my component, which of course has newly initialized variables. (I can
see the new instances accrewing in the image by exploring
Presumably there is some mechanism within Pier for dealing with this.
What do I need to do with my components to tie into this?
Also, note that I'm not talking about achieving Magma-style object
persistence here; saving the image periodically will do just fine for my
More information about the smallwiki