I see... I serialize an object to preserve its state in persistent memory. It does little overhead, and occupies 4kb of non-expensive harddisk space. I guess there are other reasons for this since you need to ask.
Your assumption that I serialize all my GUI is coming from..where?
Who are "us"?
In your favor I will assume you are desperately trying to teach me some do's and dont's when it comes to serialization, in a smart-***, rhetoric fashion, but so far you have not managed to get to your point, nor give any hints whatsoever if you are able to answer MY questions.
There are a number of states that could be of interest, titles, tooltips, fileviews etc. There are a number of needs outside my own.
What comprise a good design move is always up for discussion. For most people, that is. In my book simplicity is a huge factor in a good design. This is simple, even if I need to add 2 lines to set the Look and Feel.
There may be issues in the serialization concept that I do not know about. Perhaps I may run the risk of cascade serialization due to listener objects, or similar. This I would like to discuss, perhaps not with you.
But I still need some tip regarding setting the Look and Feel for a JFileChooser object.