JavaScript has enjoyed a long and storied history since its creation in 1995. As a prototype-based scripting language, JavaScript quickly became useful as a mechanism to implement dynamic logic and interactivity on web sites — and combined with the latest features of HTML5 and CSS3, JavaScript has evolved into a required technology for delivering powerful web applications.
But web development also has a frustrating past, and for many software developers JavaScript and CSS remain tricky to learn. Older Internet browsers delivered wide variations in the ECMAScript and CSS specifications which led to many problems creating applications compatible across browsers and devices. Rather than trying to implement this cross-browser code themselves, developers often turned to JavaScript libraries like Prototype (2005), jQuery (2006) and Ext JS (2007).
Over the years, Sencha has evolved with the needs of enterprise web applications, and our customers look to us for direction and leadership as these web technologies continue to advance.
Defining Best Practices
HTML5 has proven itself to be a reliable and powerful platform for building robust applications across a variety of devices. However, as web technology continues to evolve at a rapid pace, it can be difficult for developers to stay on top of the latest tools and techniques.
Our customers frequently ask our advice on the subject of “best practices” — and while we’ve covered many of these concepts in past webinars and at SenchaCon, we wanted to start 2015 by releasing a more robust collection of recommendations for building enterprise web applications with JavaScript and HTML5.
A lot of this advice is used internally at Sencha and certainly applies to building applications with Sencha frameworks — but this JavaScript style guide can also help teams building applications with any framework, or even just vanilla JavaScript. These recommendations are based on our own experiences, as well as direct interaction with our enterprise customers.
The overall goal for this document is to help you evaluate what Sencha considers to be the important aspects of “quality” code, and ultimately create your own readable, maintainable and scalable JavaScript projects. These best practices stand as a baseline from which your teams can implement your own strategy for building a high quality JavaScript codebase. We encourage you to fork our GitHub repo!
Hear More from the Experts
To go a step further, Sencha has organized a panel of experts to discuss a variety of topics in our January webinar titled Best Practices for Building HTML5 Applications. Join thought leaders from Sencha, Netflix, Salesforce, Apigee, Swarm Online and Modus Create as we examine:
- Strategies for building scalable and maintainable code
- Approaches to consider when building web applications for mobile or desktop
- Which tools and resources the experts recommend
Best Practices for Building HTML5 Applications
January 22, 2015
10:00am PST
How can we do live streaming using ExtJS and HTML 5
Why is Sencha Touch still missing from the Senchacon materials? Is Sencha Touch a dead framework? C you confirm that Sencha Touch 3 will exist, and will not have a jump in price from free to over $3,000? Why has the entire Sencha Touch team been fired or left?
@Aiman – That question is best suited for the forums.
@MH – Have a look at the blog post and comments here: https://staging.sencha.com/blog/senchacon-2015-call-for-papers-is-open/
Touch is far from “a dead framework”… I would expect to find out a lot more at SenchaCon this year, and I imagine you’ll be happy with some of the things we have cooking!
I just find it odd that the “omission” of Touch was never fixed. That’s not a good signal, along with other signals:
– The entire Touch team was disbanded. A lot of questions there.
– In the past year, 25 ExtJS blog posts, 6 Touch blog posts
– No new Touch features since Oct 1, 2013
Competitors’ roadmaps are very clear, but Touch’s future has been opaque for 1 1/2 years. Please send a positive signal to the market. I’m not asking you to telegraph your punches, but sharing some piece, however small, would go a long way.
@M.H: ST2 never die guys. You can integrate to Phone Gap to build an app or find another simple solution to fix bugs. I’ve seen many problems of ST2 but they were also problem of CSS3 and HTML5 not only ST2.
Hey Arthur, I was wondering if you had a suggestion for making the hero image scale depending on different screen sizes? I used my own hero image for this tutorial, which is about 6000 x 5000. I’d like it to shrink rather than stay the same size and get cropped. It makes it hard to see what my hero image is. Thanks!
You can choose the right splash screen by first detecting the browser window size first and then choosing the right splash screen. Here is an older post on how to create a splash screen. Consider using media queries to assign the splash screen file.
https://staging.sencha.com/forum/showthread.php?230118-Splash-Screen
If you unable to get it working, don’t hesitate to post your question in the Ext JS 6 forum
https://staging.sencha.com/forum/
Its so great and perfect site for the all because here we get more things for the enjoy and its so easy for the all user.