Are these improvements(?) on the Swixml queue?

I've only used Swixml on a small program, and the same for Thinlet.  
However, I'm quite enthusiastic about this approach and Swixml seems to be a 
good choice.  But ... 

My target audience is college students in their first few Java courses.  
Currently I teach Swing GUI programming, and there's much good to be said 
about GUI programming and what it teaches, but it's a big step for beginners 
and it often overwhelms the logic of the problem.  The XUL philosophy offers 
a lower entry cost to GUI programming with it's own benefits in the 
separation of logic and user interface.  So I'm looking for Swixml features 
that make small student programs easier. 

Two features that were immediately apparent. 

* The default window closing operation is not EXIT_ON_CLOSE.  This is
 not the default on JFrame tho it probably should have been.  Would
 it be possible for Swixml to use this more desirable default?
 It would remove one small obstacle for the students. 

* Packing.  I was surprised to see window dimensions in every example.
 Students aside, this seemed primitive.  Are there plans to pack
 instead of setSize? 

 -- Fred