Hi Wolf, and happy holidays to all. I have a few thoughts (or personal opinions) in the matter of event handling for xml2swing.
As I stated before, the mechanism that thinlet uses (assigning a pseudo-code method call to the action attribute) to bind UI to code is probably not a good idea. This puts too much knowledge of the implementing code in the XUL. I prefer a mechanism where there are *no* action attributes or any kind of callback specifications in the XUL. When the implementation is ready to write code for an action, then the code can register a listener to the component. When there are no listeners to a component's actions, then the actions are lost. This keeps it very simple and in line with Swing. This also fits in well with how I prefer develop thinlet apps: I design the XUL first; once I like the layout of the components, I go back to the code and put in the implementations for the actions. This is a pain in thinlet because I have to edit both the UI and the code, despite the fact that I had the UI portion already "done". john __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
