» Java开发网 » Java GUI 设计
打印话题 寄给朋友 订阅主题
于 2003-10-21 12:24
For me in practice:
1. All the GUI (the View) drag-and-draw under SunONE 4.x (don't know why but as recommended by our supervisor; I bet if you do keep the MVC pattern clear in you design, there isn't any problem to work with other GUI editor).
2. All the user event/interaction code (the GUI level Controller) will be manually program under Eclipse. At this point, I used to have a separate GUI controller class developed but sometimes for testing or prototyping I might embedding them into the view as well.
3. All the domain class (the Model) will be manually program or generated under Eclipse.
I feel comfortable with my approach that:
1. If user want to change GUI layout, I can isolate my changes remain in the View.
2. If user interaction to be changes, I can isolate my changes remain in the View and the Controller.
Of course, there would be chances to have all classes got changes impact under the existence of *innovative* business people
Indeed, when you going further detail from individual GUIs into a serious application. You will finally forming a framework amongs your GUIs. For example, the common validator, interaction event mediator, I18N/L10N messaging/dialog mechanism, etc. So, for a long run, you should either have you own framework or get used to a oepn one.
who am i?
Powered by Jute Powerful Forum® Version Jute 1.5.6 Ent |
Copyright © 2002-2018 Cjsdn Team. All Righits Reserved. 闽ICP备05005120号
客服电话 0592-8750026 客服信箱 firstname.lastname@example.org 客服QQ 714923