＋设为首页 ＋添加到收藏夹
some believe that rich guis are expensive to build. we argue that rich user interfaces can be built at the same cost, if not less expensively, than html-based user interfaces. additionally, until recently, a case could be made that another disadvantage to rich guis was deployment. well address this issue by detailing the significant progress made in java deployment technologies to drive deployment costs to a level comparable to the cost of deployment of html user interfaces.
the case for rich user interfaces 【推荐阅读:SYS-CON to Announce 】
most java developers intuitively understand the advantages of using a rich java swing user interface instead of an html interface. the fact that rich user interfaces provide a better experience for the user has often been cited as the primary reason they should be employed in a particular application.
in this article, however, we provide four factors that support the claim that rich user interfaces may be the better choice for many applications - and not just because they provide a better user experience.
we begin by illustrating that rich guis can be developed and maintained at a lower cost than html-based user interfaces. we then argue that since web services are typically highly interactive in nature as opposed to being a data delivery system, rich guis may be more appropriate than html interfaces for web services. and finally, we describe a new architecture, which we refer to as the application canvas, for development of web services-based applications that allow for integration of autonomous web services on the client. as the application canvas is user-programmable, the user is able to link outputs of one web service to the inputs of another, thereby, allowing the user to derive functionality not foreseen by systems developers.
pros and cons of rich user interfaces
rich user interfaces are composed of high-level user interface components, such as tabbed panes, table widgets, and tree widgets. compare an html tabbed pane with a tabbed pane in a rich user interface.a tabbed pane is a single component in the swing component set, and the properties of this component are standardized and well documented. in contrast, an html interface can display a tabbed pane; however, the designer must put a tabbed pane together from lower level graphics, html, and possibly javascript components. the construction of the html tabbed pane is likely to be nonstandard and may entail the development of a significant amount of scripting code. therefore, developing a user interface that requires a tabbed pane in java swing will require less code to be written than a user interface with the same functionality developed in html. thats why sophisticated html user interfaces, especially when combined with javascript, may prove to be more expensive to build and maintain than rich user interfaces composed of high-level user interface components.
maintenance and cost ... 下一页