[ve-dev] How about separating the UI frame codes from those control code

[吴 明石 <gypsy_x@xxxxxxxxxxx>]

 Hi everyone there! I'm new to this mailing list.
 First must say you've done a great job, that's what I'm looking for since 
I've met with those boring swing matters, you know, especially those 
layouts. Being a java newbie, I'm totally unfamiliar with layouts, heh.

 And I've had the idea of separating UI codes from my "true source codes" 
after using VE for about 2 days. That idea is not new, it's copied from the 
.frm file used in Delphi, they use them to describe the form layouts, 
components, etc. Though not very familiar with MVC pattern, I think it's 
focusing on this matter too. And from some articles introducing (or maybe 
advocating ;^) XAML in Longhorn, the next generation of windows platform. 
Actually it's a trivial (in my own personal opinion) technique about using 
XML to describe the User Interface, and all they were advocating is just 
that Avalon could interpret XAML to windows Form style as well as to a web 
page style. So if microsoft could, why couldn't we?

 To support this feature will give us much more flexibility, and we could 
ask someone who's good at UI design to "draw" the interface, we just write 
our own codes, as event handlers to UI components, or some background works 
with or without UI businesses. This also helps to make codes much clearer, 
and change SOME UI features without changing any codes.
 I've seen Dave have raised this problem with "How about XMI" 
blah...thinking maybe we're meaning the same thing.

_________________________________________________________________
与联机的朋友进行交流，请使用 MSN Messenger:  http://messenger.msn.com/cn