Oracle Jet实战：企业级JavaScript应用开发指南

需积分: 9 20 浏览量更新于2024-07-17 收藏 6.1MB PDF 举报

"《Practical Oracle JET：用JavaScript开发企业级应用》是由Daniel Curtis编写的实用指南，专为解决内部后台和企业网络环境中常见的应用程序问题而设计。Oracle Jet是Oracle提供的一款先进的JavaScript扩展工具包，旨在创建美观、高效且易于使用的应用程序，尤其适合那些在快速变化的开发环境中寻求稳定性的开发者。这本书详细介绍了如何利用Jet的强大功能，如列表、输入控件和可视化组件，来构建功能性应用。本书的核心内容围绕Oracle Jet的实际应用展开，从基础概念入手，逐步引导读者掌握如何运用这个工具包进行企业级应用的开发。通过阅读和实践书中的实例，开发者不仅能够学会构建功能丰富的票据系统应用，还能深入理解更高级的主题，如数据绑定、用户界面设计和性能优化。本书的特点在于其实战性和实用性，不仅提供了理论知识，还配以详尽的操作示例，确保读者能够在实践中快速掌握技能。每一章节都包含清晰的步骤和代码示例，使得即使是初学者也能顺利上手。此外，作者强调版权保护，确保内容的合法使用，同时也提醒读者尊重商标和知识产权。《Practical Oracle JET》是一本适合所有希望提升前端开发能力，特别是对Oracle技术栈感兴趣的开发人员的宝贵参考资料，无论是对于个人项目还是企业级项目的开发，都能提供有价值的指导。通过阅读这本书，读者不仅能提升技术实力，还能跟上Oracle Jet技术的最新动态，以适应不断发展的IT环境。"

D. Curtis, Practical Oracle JET, https://doi.org/10.1007/978-1-4842-4346-6_1

CHAPTER 1

User Experience

inEnterprise Applications

User experience is a term often used when developing any kind of web interface. Such

an interface could be for a web site or web application. Implementing user experience

essentially requires getting the right balance between the end goals of the business,

technical restraints, and preferences of end users. User experience involves much more

than just reducing the amount of clicks a user takes to achieve a goal. A lot of factors are

considered in getting it right.

A report conducted by Nielsen indicated that intranet (enterprise) users are stuck at

a low level of productivity, and the average employee success rate at basic intranet tasks

decreased over time. Web sites were said to have a much higher success rate. Why is this?

Enterprise systems can be very complicated, and often, a lot of different functionality

can be required in a single system. Imagine an application for a mortgage broker that

processes mortgage applications. Applying for a mortgage is complicated in itself when

you are one buyer dealing with one bank. Imagine designing an interface that has to

integrate with 30 different banks. Each one of these banks may have different data

required in different formats, so you could end up having to design 30 different user-

interface forms to achieve the same requirement within a single application. If we throw

in different levels of user access, so that different people can work on different parts of

the application, you can see how quickly it can become complex and potentially cause

usability issues.

As the design becomes more complicated, the development can too, leading to

functionality challenges. With tight deadlinesit is possible to end up with a scenario in

which the design and user experience analysis takes a back seat to getting the business

functionality delivered. This is a common scenario, illustrated in Figure1-1, and

results in applications that may achieve the functionality set out in the requirements

The benefits of this kind of architecture are massive for enterprise applications,

the speed of interactivity being most noticeable, but also the scalability. Servers no

longer have to be monolithic to handle the processing of hundreds or thousands of

concurrent users.

This leads me to believe that we are at a point of transformation in the enterprise

industry. With client-side toolkits becoming increasingly popular, and cloud computing

becoming more mature, we may finally be at the cornerstone of building really great

enterprise solutions.

Closed Source Usability

Closed source systems, in which a developer does not have direct access to view or

modify the source code of the framework being used, can have an indirect impact on

the usability of an application. Although these kinds of frameworks have many benefits,

such as rapid development and enterprise support, they force the developer to use the

components and technology that the framework provides. These components will have

been trialed and tested against common business use cases; however, real-life use cases

may have differing requirements that are not supported.

Even the smallest unsupported requirement can have a huge impact on time lines,

as a developer struggles to “fight against the framework” to achieve the desired outcome.

If this is not possible, an alternative may be presented that still achieves the desired

functionality, at the cost of the user experience.

Ideally, we want a toolkit that completely eliminates any struggle against framework

components. Developers shouldn’t be restricted by the tools they are using. They should

be able to pull from the open source community and have a multitude of different

options available.

Improving Usability

Enterprise applications should be more successful than web sites, as designers will have

a smaller subset of users to design for, and have easier access to usability data, resulting

in a product for which the requirements have been thought out more efficiently.

Part (but not all) of the problem is owing to the technology choices that are made for

enterprise applications. By addressing the following points, some fundamental usability

issues can be prevented.

Chapter 1 User experienCe inenterprise appliCations

Client-side framework: Move away from the traditional client-server model. Choose

a technology that runs the application on the client, mitigating the need for a round-trip

to the server every time a change occurs on the page.

By running the application on the client, it opens up the potential

for a faster, fluid, and more responsive experience for users, in

addition to a multitude of other benefits that will be explored

during the course of this book.

Designer/developer harmony: Choose a toolkit that already has some design

guidelines in place (and can be easily extended), so that designers have clear visibility of

the toolkit’s components and capabilities. Ideally, the toolkit should help to close the gap

between design and development teams.

Open source: Development teams should have the ability and freedom to customize

code to achieve the desired requirements outlined by both the business and design

experts. Developers should also benefit from being able to harness the ever-expanding

sea of component libraries available and customize any component libraries included

within the vendor toolkit.

Keeping up with trends: Enterprise frameworks can often be quite behind the latest

trends, to ensure they have stability, and upgrading can sometimes be an expensive task.

The issue then is that user-interface trends change very quickly, so systems can become

outdated before they are even launched. Ideally, it is best to get a good balance between

stability and newer features, without the need to have monolithic yearly upgrades

that take ages to implement and are still way behind the latest technologies. Smaller,

incremental upgrades throughout the year can help with this.

Summary

This book is not about how we should visually design an application. (There are plenty

of other books that cover the best practices for that.) It is more of a means of highlighting

the issues with enterprise applications and how you, as a developer, can use a toolkit that

will provide the necessary components to develop great applications with the least effort

possible required for design thought. Although, as a developer it is good to consider

design, the basic UX principles should be provided to you by the tools that you are using.

Chapter 1 User experienCe inenterprise appliCations

剩余242页未读，继续阅读

iebukes

粉丝: 9
资源: 132

Oracle Jet实战：企业级JavaScript应用开发指南

Oraclejet是一款Oracle的JavaScript扩展工具包

Practical streptomyces Genetics.pdf

docker cookbook: over 100 practical and in...

a practical guide to tpm 2.0教材.pdf

practical contiki-ng pdf

4754-15776-3-PB.pdf

practical uvm step by step pdf

practical node.js, 2nd edition

practical time series analysis aileen nielsen pdf download

"[string \"/home/tpy/practical-cryptdb/wrapper.lua\"]:6: /home/tpy/practical-cr"

最新资源