GWT Designer 生成的代码
我试图更好地理解 GWT 及其关联的设计器插件。在您的应用程序中使用最新版本的 GWT Designer 和 GWT 2.* 之一，您能否让我了解
1) 您需要手动开发多少额外的 (UI) 代码（在 GWT Designer 之外），也许作为粗略百分比？这段代码通常负责 MVC 的模型接口和控制器部分吗？
2) 您在“设计和代码视图”之间切换的能力如何——即在补充手写代码后继续使用 GWT Designer 进行 GUI 布局？
I'm trying to understand GWT and its associated Designer plugin better. Using one of the more recent versions of GWT Designer and GWT 2.* in your application, can you give me a sense for
1) how much additional (UI) code you needed to develop by hand (outside GWT Designer), perhaps as a rough percentage? Was this code generally doing the model interface and controller part of MVC?
2) how well were you able to go between "design and code view" -- i.e. keep using GWT Designer for your GUI layout after you supplemented with hand-written code?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
1) 它的作用很像它生成 html 代码和 ui:fields 并将 ui:field 与 java 类中的变量绑定。您必须写信给您的处理程序。它手工完成模型界面和控制器。
2）对我来说，切换视图花了很多时间，对我来说，设计器的性能很差，我尝试在切换到代码视图之前完成设计器内的工作。
1) It does a lot like it generates html code, and ui:fields and binds the ui:field with a variable in java class. You have to write to your handlers. It does the model interface and controller done by hands.
2) To me it took a lot of time to switch views, to me the designer's performance was poor and I try to finish nt work inside the designer before switching to code view.