If you want to build your organization’s next web application with HTML5, this practical book will help you sort through the various frameworks, libraries, and development options that populate this stack. You’ll learn several of these approaches hands-on by writing multiple versions of a sample web app throughout the book, so you can determine the right strategy for your enterprise.
- Rebuild the sample app, first with jQuery and then Ext JS
- Work with different build tools, code generators, and package managers
- Build a modularized version of the app with RequireJS
- Apply test-driven development with the Jasmine framework
- Use WebSocket to build an online auction for the app
- Adapt the app for both PCs and mobile with responsive web design
- Create mobile versions with jQuery Mobile, Sencha Touch, and PhoneGap
About the Author
Yakov Fain is a Managing Director at Farata Systems, a company provides consulting and training services. He authored several books on Java and Flex and dozens of articles on software development. Sun Microsystems has nominated and awarded Mr. Fain with the title of Java Champion, which was presented to only a hundred people in the world. Yakov is Certified Adobe Flex Instructor. He holds MS in Applied Math. You can reach him at email@example.com.
Dr. Victor Rasputnis is a Managing Principal of Farata Systems. He's responsible for Farata consulting and mentoring practice, providing architectural design to companies implementing RIA with Adobe Flex, Air and Livecycle technologies. He holds a PhD in Computer Science from the Moscow Institute of Robotics. Victor is Certified Adobe Flex Instructor. Victor lives in New York with his wife Aziza and his daughter Alice. He likes playing tennis and skiing with his friends. You can reach him at firstname.lastname@example.org.
Anatole Tartakovsky is a technology consultant, emerging technologies enthusiast and problem solver. He is a Managing Principal of Farata Systems and is responsible for creation of frameworks and reusable components. Prior Anatole played roles as Technology Consultant, Project Manager, CTO, and Mentor for various enterprises. Anatole authored number of books and articles on Flex, AJAX, XML, and client-server technologies. His education includes MS in mathematics and post graduate work in Expert Systems. You can reach him at email@example.com.
Viktor Gamov is a senior software engineer at Farata Systems. He consults financial institutions and startups in design and implementation of Web Applications with HTML5, Flex and Java. Viktor is passionate about writing the code, open source community and JVM ecosystem. He holds MS in Computer Science. Viktor is a co-organizer of the Princeton JUG and NJ Flex meetup http://www.meetup.com/NJFlex. He tweets at @gamussa. You can reach him on email firstname.lastname@example.org.
Most helpful customer reviews
1 of 1 people found the following review helpful.
Keeping it for reference on my desk at work
By Cristina Fierbinteanu
I bought the book after reading the drafts online and attending an online course with two of the authors. Now I keep it on my desk at work, as a reference. I find it very helpful. Thanks to the authors for writing it!
8 of 8 people found the following review helpful.
Good Scope and Content; Imperfect Balance of Show vs Tell
By Jeff Nyman
Updating my review a bit: different title; same star rating for now.
I will say this: I wouldn't be writing a review or updating it if the book wasn't engaging me. While it frustrates me a bit in its presentation, I still stand by the ambition and scope of this book. I'm not quite to adding another star ... yet.
== Initial Review
I actually like much of the content of this book and I think its aim and approach is exactly the right way to handle it. However, so far, the presentation and setup offers enough issues to make this book problematic to recommend.
I do plan on updating my review as I get further into the book.
As just two examples:
On page 16, there's the meta http-equiv that's used in the book listing. That's not in the chapter1 code repo. Should it be?
On page 17, there is a clearfix div block in the book listing. That same block is not in the source code repo. However, there are clearfix CSS entries in the code repo but those are not mentioned at all in the book listings.
One thing that bothers me about this is that, quite frankly, I found all of this in my first read-through. It's glaringly obvious. So that being said, I find it hard to believe that a test reader (reviewer, as opposed to editor) could not have done this for the authors prior to release.
== Update to Review
It does not contain the geolocation code that we laboriously added over five iterations in chapter 1. Why not? Should it be there? Even if the authors are going to reimplement it for the reader, they haven't done that in the book by the time someone is looking at project-01-donation-ajax-html. I realize the geolocation code does not matter for the bit of Ajax the authors are showing by that point in chapter 2. But, again, attentive readers are going to notice.
This is similar to what happened with the Modernizr code that was introduced in the book and in \chapter1\project-08-1-Modernizr-geolocation-maps but is then apparently removed in the project examples for the rest of chapter 1 and chapter 2. Why?
Yet another example. In chapter 2, the authors introduce sending XHR errors to the footer area of the HTML in the book (where they even call out the specific CSS to use). However, that's not in the code repository for any of the chapter 2 projects.
But does any of this matter? Well, for me, I want a *consistent* application that I modify as I go. I don't want to have to wonder why parts are left out here and there.
All this said, I suppose it depends on if the reader is going to take the authors' advice and just open up the existing projects in WebStorm. If so, that would be a bad way for a reader to learn in my opinion. Readers will always learn more by actually typing out the code themselves which forces them to engage more with it. I'm that type of reader and that's definitely where my friction is coming in. I really like the scope and content in the book but it's a struggle to implement if, like me, you are a reductionist reader that wants to stick with a consistent code base through all examples.
2 of 2 people found the following review helpful.
See all 3 customer reviews...
A very good book for a big picture of enterprise web development
By Ailin Mao
The book, by no means, cover the large number of topics in details, and it's already 600+ pages.