加速Web开发：Practical Webix实战指南

需积分: 10 119 浏览量更新于2024-07-17 收藏 7.15MB PDF 举报

"《Practical Webix》是一本专为现代Web开发者编写的实用指南，作者是Frank Zammetti。在科技日益繁多、选择复杂的Web开发领域，本书旨在帮助读者快速提升和优化Web应用开发技能。面对众多技术栈、架构和方法论，作者理解开发者面临的挑战，提倡直接使用HTML、CSS和JavaScript的基本工具，即使在经验丰富的开发者也可能因决策压力而感到困扰。该书详细介绍了如何在实践中应用Webix，这是一种强大的前端框架，能够简化开发过程，提高效率。通过阅读这本书，读者可以学习到如何构建现代Web应用程序，包括但不限于组件化开发、响应式设计、用户体验优化以及如何利用Webix的特性如数据绑定、拖放功能和动态UI更新来构建高效的应用界面。《Practical Webix》不仅提供理论知识，还包含实战案例和步骤，让读者能够在实际项目中快速上手。书中还特别强调版权问题，所有内容受到版权保护，禁止未经许可的复制、重印或任何形式的传播，包括电子版本的改编和存储。商标名、标志和图像的使用遵循编辑性使用原则，旨在尊重知识产权。如果你是一名寻求提升Web开发技能，或者正在寻找一个易于学习且功能强大的框架来加速项目开发的开发者，《Practical Webix》将是一个宝贵的资源。它不仅帮助你掌握Webix的核心概念，还能让你在日益激烈的市场竞争中保持竞争力。无论你是初级开发者还是经验丰富的专业人士，都能从这本书中学到实用的技巧和策略，从而更好地应对当今的Web开发挑战。"

xix

Acknowledgments

I would like to acknowledge all of those who helped bring this book to reality at Apress,

among them Nancy Chen, Louise Corrigan, James Markham, and Dhaneesh Kumar

(and to anyone else not listed, I heretofore acknowledge you as well). Thanks, folks. I just

write the words; in my opinion, you all do the actual hard work!

I’d also like to acknowledge my technical reviewer, Toby Jee. This is actually the first

book, if memory serves (which it frequently does not these days, but I’m pretty sure

about this!), that I haven’t had the same tech reviewer (not for any specific reason; it’s

just the way things go). Toby did, in my estimation, an excellent job throughout on his

first tech reviewer job. Thanks, Toby!

Finally, I’d like to acknowledge XB Software, creators of Webix. Aside from creating

an excellent product, they helped me a number of times during the writing of this book

with issues (Maksim Kozkuhk, Nick Maksimenko, and Tasiana Drozd specifically) and

also graciously provided me with a Webix Pro license to use. Thank you, all. I very much

appreciate it!

xxi

Introduction

Creating a modern web app is tough. There are so many different technology choices, so

many different approaches, and so many different architectures, theories, and methods.

You can even forego all of that and just use “naked” HTML, CSS, and JavaScript. The

decisions can drive even an experienced developer nuts in short order!

I’ve been doing this exact thing for two decades now (seriously!), so I’ve seen it all,

many times over. One of the key things I’ve learned is that simplicity is one of the most

important considerations. Simplicity is easier to maintain, and writing maintainable

software is a key aspect of professional development.

So, when I stumbled upon Webix, I was immediately smitten with its simplicity! It

allows you to do some pretty advanced things with a minimum of code. It also doesn’t

require a big, complex toolchain nor does it require you to learn a bunch of specialized

domain-specific languages. It’s basic HTML, CSS, and JavaScript against a generally

clean API, and that’s about it!

In this book, I’ll take you through the many capabilities that Webix brings to the

table. We’ll explore things such as application architecture, the widgets that Webix

provides, and the components that you can build a user interface from. Eventually,

together we’ll build a real application using Webix, but before then you’ll have a solid

foundation of knowledge from which to build upon.

In keeping with the title of this book, the application we’ll build will be very practical,

meaning it won’t be some grossly simplified, dumbed-down, and contrived example. It’ll

be a real app, and along the way you’ll see many aspects that went into its development,

including in some cases the problems I faced in putting it together and the solutions I

came up with! In doing so, you’ll get solid, hands-on experience with using Webix in a

real-world way—a way that will prepare you for building your own apps later.

You’ll also learn some things tangential to building the app including how to make it

a mobile app using the popular PhoneGap (Cordova) library and how to build a server

for the app to interact with. See, it’s practical, not just some pointless sample that will

leave you wanting for more!

some portion of it to be dynamic. Maybe that meant inserting markup to show a list of

products, how many visitors the page had over the past week, or myriad other things.

The big point was that it was the server that did the dynamic work. Every time some

content had to be generated or some user interaction handled, a request had to be made

to the server.

Eventually, the limitations of CGI became apparent (most notably the fact that it was

typically a one-request-at-a-time deal and so performance suffered when the number

of incoming requests increased too much), so dynamic server languages were created.

Things like Microsoft’s Active Server Pages (ASP) and Sun’s Java servlets came about,

among many others whose time mostly came and went quickly.

But, again, that key point remained: the server was doing the work of executing code.

The client simply displayed the content that the server created.

Web Development: TheTeen Years

At roughly the same time, JavaScript came on the scene. A creation of Brendan Eich (in

just ten days, unbelievably!), JavaScript provided developers with the ability to have

dynamic elements on their sites without the need for the server to do the work. No

longer did you need the server to do all the heavy lifting; the client itself could do some

of it by generating content or altering existing content.

There was a lot of experimentation that went on during that time and a lot of lessons

learned. One of the biggest that people began to realize quickly was simply that the Web

could do more than just simple static web pages or even dynamic content (which, in

many ways, still looked like static content to the end user). Developers started to realize

that what we had was, in fact, a platform to build applications on. There was a fair bit of

consternation about this at first and a lot of doubt about whether building applications

was possible with HTML and JavaScript. There was a lot of debate about whether the

classic model of having the server do everything was still better or not either way (and

frankly, that debate is still going on today in some circles). There was a lot of testing the

limits to see just how far this web app thing could be pushed, and that went on for quite

a few years.

Building a complex graphical user interface (GUI) with JavaScript at that point

in time was an exercise in frustration and you had to code everything yourself, not to

mention all the differences between browsers that you had to cope with. There wasn’t

the plethora of libraries, frameworks, toolkits, and developer tooling that we have in the

Chapter 1 Better WeB Development WithWeBix

www.allitebooks.com

剩余419页未读，继续阅读

StardustEncoder

粉丝: 0
资源: 10

加速Web开发：Practical Webix实战指南

webix文档CHM

Practical Webix - Learn to Expedite and Improve your Web Development

Practical Webix Learn to Expedite and Improve your Web Development epub

practical linux security cookbook, 云盘

practical uvm step by step pdf

practical contiki-ng pdf

Embedded Linux Primer: A Practical, Real-World Approach

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

mastering opencv with practical projects源码

practical guide to splines carl de boor

最新资源