🚀 go-pugleaf

On 12/29/2004 at 11:23:51 AM, Alan Shiers wrote:

> When I open a saved file, I wound up manually iterating over every
> instance of the TargetPanel(s) and calling installDnD() on each one in
> order to reinstate each TargetPanel as being a viable drop target for
> transferable components.  Is this usual? Wouldn't this functionality be
> saved. I shouldn't have to do that should I?

I can see no reason that you should have to, if serialization worked well
with Swing components.  But there have always been problems with Swing and
serialization, and Sun recommends against using it.  I tried serializing
Swing components back with JDK 1.2 and I quickly gave up on the idea.
Over the years I have seen many people try it, and they all had
significant problems.

There have been members that were marked as transient that held important
state, so that the state was lost when the component was deserialized.
There have also been members that were not marked as transient, but were
not serializable either, so serialization would fail.  In some cases,
these members were only set under specific circumstances, so the
serialization would only fail on occasion - usually after the code was
deployed.

What I have found works very well is to persist the model and to build the
view components from scratch when you launch your program.  You may have a
few view attributes that you want to save, but it is much easier to
persist just those attributes and apply them when you build the UI.  You
will have far fewer problems with this approach.

-- 
Regards,

John McGrath [TeamB]

---------------------------------------------------
Before sending me e-mail, please read:
    http://www.JPMcGrath.net/newsgroups/e-mail.html