The purpose? Ah, good question. More variety of configuration options. I
expect that I'll want to configure my widgets separate from my code. (At
least the types of widgets I'm thinking about)
So this gives me the option to configure them elsewhere, save them (freeze),
and have my code thaw all the widgets that it cares about. FURTHERMORE, if I
want to give others the chance to configure some or all widgets - I can
allow them to modify the saved definition and resave it as I deem
appropriate.
The widget has to know how to freeze and thaw itsself because of course that
is implementation dependant to some degree. IE/ Data::Dumper would dump out
the hash that holds all of the widget properties - which in itsself is an
implementation detail.
Jay
> At 10:05 AM 6/6/2001 -0400, Jay Lawrence wrote:
> >One other thing I really wanna see is thaw/freeze support. Scary? Not
> >really. Obviously if you don't wanna thaw and freeze widgets ever this
will
> >be no skin off your nose - it is optional to use.
> >
> >I belive that one thing needs to happen in the thaw phase - that is a
"use"
> >for the widget's class. There is no guarantee that you've "use"d that
widget
> >class already.
> >
>
> Interesting idea.
> What is the purpose of freezing and thawing widgets?
>
> Stephen
>
>
>
|
