ja...@la... wrote:
>Bingo!
>
>I suggest that a widget contain a list of properties to be saved when frozen
and to be recalled when thawing.
>
>@freeze_props=qw(fname size width colour shape foo bar);
>
>Other properties will no doubt exist for any given widget but only the above
actually get frozen or thawed.
-nod- makes sense to me. I'll sit on it a bit and think -- I want the
freeze/thaw process to have the following properties:
trivial for the widget developer - a widget should only have to worry about
itself, not it's parent classes.
trivial for the widget user - only use $widget -> freeze and Widget ->
thaw($data).
I think the @freeze_props idea is the right way to do this, but want to make
sure I see how it all fits together before committing to it.
--
James Smith <JG...@TA...>, 979-862-3725
Texas A&M CIS Operating Systems Group, Unix
|
