BTW I wound up using Merlin and my copy of the event bus instead because of time constraints to build a GUI. I really wanted the custom lifecycle you have to snap in a component onto the event bus. I would like to see these kinds of features made as pluggable aspects to Merlin. The GUI app stuff seemed a little too new and complex for me or at least too complex for me to understand within a couple of hours. But I do intend to focus more on
it in the near future: I have not given up. There are some excellent concepts there for those that want to make their GUI components real components in the Avalon sense.
The most complex part of GUIApp is really the config file. It doesn't map logically to the way a Swing GUI person would think. That is enforced somewhat due to the way Fortress reads in the configuration, so I am thinking about how to improve that in the future. But specifics about GUIApp belong on the d-haven list.
What is relevant to Avalon though is that more and more the configuration file formats lend a great deal to the perceived complexity of the containers. As LSD has been good to point out, too much magic is not good. Sylvain put it best as "Too much magic spoils the confidence". If you can't readily see how something maps at a glance, you tend not to trust it.
Perhaps a lesson for moving forward...
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
