|
Yes
No
|
Neil Roberts,
BitMethod
Just the data, please!
When rich internet application developers are tasked with updating a web p...
READ MORE
Just the data, please!
When rich internet application developers are tasked with updating a web page based on data loaded from a server, they have a limited number of options. We have resorted to either loading HTML from the server and dumping it into the page or writing meticulous instructions for how this new data will alter the document. The current solution to the problem involves using rich templating languages on the server side. Server side templating, while commonplace, increases load and reduces speed.
A more efficient solution is browser-based templating. Implementating a browser-based rich templating language requires solving many problems: identifying the most flexible syntax, turning a template into a set of instructions for modifying the document, and drawing and redrawing the template blazingly fast.
This presentation will demonstrate how two programmers used the open source community to develop solutions for browser-based templating. One programmer wrote the code, and one needed the solution. It will cover the decisions made in building a browser-based rich templating language, problem solving processes, and a real-world implementation. Attendees will gain a new understanding of how they can make their sites and web apps more efficient and more flexible by separating HTML from data using a client-side, browser based templating language based on Dojo's implementation of DTL.
Web Apps / Widgets Django, Dojo, JavaScript
|
|
Yes
No
|
Kyle Simpson,
Getify Solutions
We all know that web performance optimization is important, especially if you care about Google/SEO ...
READ MORE
We all know that web performance optimization is important, especially if you care about Google/SEO value and your users. But most developers only consider the checklist items in YSlow and PageSpeed. These tools, however, barely scratch the surface. Get ready to get your hands really dirty.
* why should I *really* care about web performance optimization?
* how can I plan for optimal web performance without hindering my development processes?
* debunking myths about many of the (sometimes self-conflicting) rules in YSlow and PageSpeed (and other tools).
* how does page-load optimization (resource loading, etc) really impact web performance and UX?
* what role does "middle-end" architecture play in optimization?
* how does run-time performance of CSS and JavaScript affect performance?
* how crappy/unmaintainable application code leads to crappy/unaddressable web application performance.
* what are the differences between desktop and mobile optimization?
* how does the underlying architecture of the internet (DNS, HTTP, etc) affect optimization, and what can we do about it?
* what role do browsers (and standards!) play in improving web performance?
* how can I convince my boss that performance is important to the end-customer?
As this burgeoning Web Performance Optimization industry blossoms, it's ever more important you get beyond toe-dipping and really dive into this topic. It's not for the faint-of-heart, but you CAN truly optimize your webs.
Front-End Programming JavaScript, optimization, performance
|
|
Yes
No
|
Jason Garber,
Viget Labs
This panel will feature a group of exceptionally intelligent folks getting together and discussing i...
READ MORE
This panel will feature a group of exceptionally intelligent folks getting together and discussing issues relevant to the curious web designer and front-end developer as of March, 2011. Subject matter may include (but is not limited to) jQuery, CSS3, HTML5, Smashing Magazine, and beer.
New Technology / Next Generation CSS3, HTML5, JavaScript
|
|
Yes
No
|
Joe McCann,
frog design
HTML5 is no question the "buzzword du jour" in tech nowadays, but looking past the vernacular cruft ...
READ MORE
HTML5 is no question the "buzzword du jour" in tech nowadays, but looking past the vernacular cruft one will discover that the HTML5 technology STACK is actually an incredibly powerful & useful framework for apps well beyond the traditional web browser. Massive companies like Google and Hewlett Packard are placing huge bets on the future of "HTML5 App development". From HP/Palm's WebOS to be used in their mobility products to Google's Chrome OS, HTML5 is not simply another buzzword that can be treated as a mere passing trend, but should actually be taken seriously for app development.
But what makes up the HTML5 stack and how will it truly be the future of software? What are the benefits & risks associated with using the HTML5 stack? Prove to me it works. All of these questions & demands will be answered & showcased in the presentation including important issues such as:
What constitutes the HTML5 stack
Benefits of using the HTML5 stack
Use a single codebase
Rapidly prototype an app targetting multiple devices including: iPhone, iPad, Android Devices, Chrome OS Devices, Mobile Webkit Browsers, Desktop Browsers
Target thousands of developers for extensibility & community development
See code & install an actual working HTML5 app that works on a number of devices
See code best practices in use for tailoring the UI based on the user's device
See code using Phonegap to create native mobile apps
See code using Titanium to create native desktop apps
HTML5 android, JavaScript, mobile
|
|
Yes
No
|
Alex Sexton,
yayQuery Podcast
'Regressive Enhancement' is using HTML5 in your apps right now. There are countless ways to make you...
READ MORE
'Regressive Enhancement' is using HTML5 in your apps right now. There are countless ways to make your site work with HTML5 without breaking backwards compatibility in older browsers. We've decided to pool together the topic experts in our wildly broad definition of HTML5 and ask them very specifically 'why they think the HTML5 family of technologies and specs are important' and 'how to solve the backwards compatibility issues.'
HTML5 has outgrown its strict definition, and has become the new cool-kid buzzword to mean "anything new that browsers are now supporting and didn't before." This is fine. Let's embrace this umbrella term and talk about how to get this family of technologies working. Topic experts in CSS3, HTML5, ECMA5, and other HTML5-related technologies will each talk specifically about their field of expertise, why it's important, and how it can be used.
A section will be dedicated to "how to sell HTML5 to your boss" and how the panel members handle similar situations in their respective workplaces. The goal of the panel is to make HTML5 a practical option for the every-day web developer, and getting approval for it is sometimes the hardest part. There are a slew of reasons why you'd want to use it in your every-day websites and we'll try to get some good ideas for you to get the ball rolling at your place of business, or directly between you and your clients.
The panel will wrap with an audience Q&A section.
Front-End Programming CSS3, HTML5, JavaScript
|
|
Yes
No
|
John Hann,
unscriptable.com
Modern JavaScript frameworks rock! Dojo, jQuery, MooTools, Prototype... They alleviate us from brows...
READ MORE
Modern JavaScript frameworks rock! Dojo, jQuery, MooTools, Prototype... They alleviate us from browser quirks so we can concentrate on coding awesome web sites. But none of these offer any guidance whatsoever -- and hardly any tools -- for building enterprise-worthy, ultra-rich web applications.
A few javascript-based, in-browser Model-View-Controller endeavors have popped up to help provide solutions. They just don’t get it. MVC sucks for web development.
Here’s why:
1) Current page layout techniques rely on floats and/or JavaScript.
2) Animations, such as fades and wipes, use JavaScript instead of pure CSS.
3) Popular frameworks, such as jQuery, offer way too many seductive tools to make matters worse.
All of these create dependencies between the CSS, HTML, and JavaScript. Dependencies slow down the team because team members must collaborate to get anything done. They also severely limit code reuse and maintainability while increasing the complexity of the project.
cujo.js was specifically designed to eliminate these interdependencies. Yes, it’s an MVC framework, but it’s different. Here’s how:
1) cujo.js avoids float-based or javascript-driven layouts. Layouts using inline-block, box offsets, and box-flex don’t inherently cause dependencies.
2) cujo.js encourages and enhances CSS3 transitions.
3) cujo.js does much of its magic by adding several CSS2.1 and CSS3 features to all modern browsers--even IE6, 7, and 8! Just write standards-compliant CSS!
Front-End Programming CSS3, HTML5, JavaScript
|
|
Yes
No
|
Jeremy Carbaugh,
Sunlight Foundation
Based on the infamous political discussion show, The McLaughlin Group, this panel will discuss hot b...
READ MORE
Based on the infamous political discussion show, The McLaughlin Group, this panel will discuss hot button issues of the day. Pundits will argue over contentious issues with the crotchety moderator making the final determination of truth and metaphysical certitude. The focus of the panel will be on the future of HTML 5 and related JavaScript and CSS standards.
HTML5 HTML5, JavaScript, punditry
|
|
Yes
No
|
Aaron Gustafson,
Easy! Designs, LLC
Let's face it: writing CSS3 sucks because we have to fork our code for each browser-prefixed impleme...
READ MORE
Let's face it: writing CSS3 sucks because we have to fork our code for each browser-prefixed implementation. -webkit- this and -moz- that... why can't we just user border-radius like the W3C intended? Thankfully, with eCSStender, a lightweight JavaScript library, you can write proper CSS that just works. In this session, you'll get an overview of how eCSStender works and how to use it to make your job easier. You'll also get a taste of how eCSStender can be leveraged to pave the way for future versions of CSS.
CSS browsers, JavaScript
|
|
Yes
No
|
Jen Strickland,
Ink Pixels Paper
JavaScript Breakdown for Designers: Don't get lost in the syntax.
JavaScript is always the elus...
READ MORE
JavaScript Breakdown for Designers: Don't get lost in the syntax.
JavaScript is always the elusive programming technology to designers. Rooted in information from Jeremy Keith's DOM Scripting, Douglas Crockford's JavaScript: The Good Parts, & John Resig's Pro JavaScript Techniques, JavaScript Breakdown for Designers will provide a clear explanation of the DOM, unobtrusive JavaScript that is accessible, flexible, and readily styled using CSS, and provide a path to compelling interaction, providing user feedback, & validating client-side form inputs. An understanding of JavaScript allows the designer to to call upon the power of libraries like jQuery and Dojo to do the JavaScript heavy lifting on browser variations. Like me, you just might find yourself in love with this incredibly powerful language that is initially so intimidating, and might even lead to understanding other scripting languages, like Actionscript.
Front-End Programming design, JavaScript, jQuery
|
|
Yes
No
|
Jeremy Hubert,
Yahoo! Inc
When I walked into Yahoo!, I was told it would take three months to get up to speed and start protot...
READ MORE
When I walked into Yahoo!, I was told it would take three months to get up to speed and start prototyping for the User Experience team. Two days later, against all expectations, we produced our first fully functional prototype. We are no longer living in a world where three months of dead time is acceptable. Powerpoint presentations don't sell an idea nearly as well as a working demo.
I will tell you my approach to prototyping and how you too can use it to break down walls, sway opinions and truly start turning your vision into a reality. Hopefully, I will also make you laugh a few times. :)
Front-End Programming innovation, JavaScript, Prototyping
|
|
Yes
No
|
Mars Hall,
Scout Labs by Lithium
Build interactive graphs & visualizations using the Raphaël javascript library http://raphaeljs.com...
READ MORE
Build interactive graphs & visualizations using the Raphaël javascript library http://raphaeljs.com/ Walk through the process of building SVG/VML visualizations on the client-side: bezier curves, path-based primitives; importing shapes; iterator-friendly data; painting the layers with drawing loops; user-interaction with DOM events; leveraging HTML elements, the legend; browser development environment, debugging & limitations. Break away from the pre-prepared package offerings like FusionCharts, Google Chart API, dojox.charting, etc. Learn to roll your own ultimately creative data visualizations. This presentation will most benefit those familiar with writing javascript in web browsers.
HTML5 design, interface, JavaScript
|
|
Yes
No
|
Jordan Kasper,
TripLittle
The "Save" button (and "Update" button for that matter) is a relic. In today's web there is no need ...
READ MORE
The "Save" button (and "Update" button for that matter) is a relic. In today's web there is no need to place so much significance on a user remembering to click that nearly hidden element on your form. With current JavaScript frameworks the process of automatically saving user-input has been streamlined and can be almost dropped in. This presentation will discuss some methods for accomplishing this goal, and why you may not want to completely get rid of that button just yet. We'll also cover some of the user experience issues with auto-saving and traditional button-saving, including how the user is supposed to know what to do.
User Experience JavaScript, user experience, web forms
|
Link to this page