I gave this talk: I know jQuery. What now? at jQuery UK 2013, but instead of my usual approach of post-it explosion on my desk, I wrote a post first, and created the slides from the post. So here is my (fairly unedited) quasi-ramble on how I used jQuery, and how I’m looking at where I’m using native browser technology.
Excellent blog post with full of tips, snippets and examples by Remy Sharp
Read the entire article here.
Our friends on the AlloyUI team at Liferay have been hard at work on version 2.0. This new version will bring a lot of improvements that they will be sharing at JAX next week. Zeno Rocha (@zenorocha), Front-end Engineer at Liferay and co-founder of BrazilJS Foundation (http://braziljs.org/), is presenting both the conference keynote and a workshop entitled “Getting started with YUI 3 and Alloy UI”. We are excited to see what the AlloyUI team has in store for the YUI community, and we encourage you to check out the conference!
Original post here.
A jQuery Plugin to make masks on form fields and HTML elements.
http://igorescobar.github.com/jQuery-Mask-Plugin/
So, I decided to take a punt at writing a NodeJS application. Not a big application, or anything that would get me slashdoted, but an application that would help me understand the language, and give me a taste of what it is so many people are talking a bout. I have worked with JavaScript for quite a while now, and NodeJS seems like one of those “just right” languages, that you pick up in an afternoon and come to love it after writing a few lines of code. I read a few tutorials on the subject. And then decided to dive straight into building a small application that uses GitHub’s API. There were three things I wanted to take out of it:
Installing everything was painless, but I have to admit getting NodeJS to build on a Raspberry PI wasn’t the most straight forward thing I’ve ever done. Not because it wouldn’t work, but because building it from source took forever. Just to clarify, I didn’t need to run it on a Raspberry PI, but just wanted to prove myself I could. This mini project had 5 elements to it:
Three from which you don’t even need to install (as they are npm modules). Just by adding them as dependencies on the package.js file, they get installed into your project, so deploying is made easier (in theory), as you don’t actually need to install anything other than NodeJS.
Now you might be asking yourself why I say “in theory” when taking about deployment. The fact is that deploying a NodeJS application is a pain, since all you end up doing is making [your preferred webserver here] proxy all the calls to your local application. Why? you may be asking…
The fact that each NodeJS application you create establishes its own server, means anything will clash with your already installed webserver, since you can only have one webserver per TCP port. So if you want to host all your applications as well as any new node project you come up with, then you will end up taking this route. It’s not terrible, but just means you now need to support yet another thing. There are tools out there to help you with such thing, but let’s not digress.
Building the application was fairly painless, and using Jade was the big highlight for me. For a while now I had looked into templating engines, and really wanted to delve into it a little more. I had previously looked at jQuery Templates, Ext and Dust.js, but Jade is totally different, in a way that actually pleases the eyes (except when it doesn’t 
).
Did I become a NodeJs expert? No way!
Will I keep looking and building sexy applications with it? Heck yeah!
Enough about me though.
Have a look at the application I wrote here, and make sure to send me pull requests if you would like to improve it.
Original article here.
Creating, testing and maintaining a large JavaScript code base is not easy — especially since great resources on how to do this are hard to find. This page is a collection of the best articles, videos and presentations we’ve found on the topic.
We come across a lot of great articles on creating, testing and maintaining large JavaScript applications. This page is a continously updated list of articles that help explain the syntax of JavaScript, how to organize your projects, how to test your code, and what’s on the horizon. Have fun!
Another slider plugin? Yes! The motivation for the development of SSSlider came from the difficulty in finding a simple plugin, focused on showing content. On the web there are many sliders made for images and adapted to receive other content. In this case SSSlider is just for the content.
This plugin is in ALPHA! Bugs can be found and if you fix one, send us a message. The ideal is to make a fork on GitHub, correct and send a pull request.
As for the license, it does not exist. You can do whatever you want with the code. No credit is needed. Just make good use and get to put on the air, send me the link to take a look and see if you did right!
The plugin requires a simple HTML markup. Just follow the example below, styling according to your preference.
Are you are interested in making JavaScript run blazingly fast in Chrome? This talk takes a look under the hood in V8 to help you identify how to optimize your JavaScript code. We’ll show you how to leverage V8′s sampling profiler to eliminate performance bottlenecks and optimize JavaScript programs, and we’ll expose how V8 uses hidden classes and runtime type feedback to generate efficient JIT code.
Daniel Clifford
This article is the third in our new series that introduces new, useful and freely available tools and techniques, developed and released by active members of the Web design community.
The first article covered PrefixFree; the second introduced Foundation, a responsive framework that helps you build prototypes and production code.
This time, we’re presenting Sisyphus.js, a library developed by Alexander Kaupanin to provide Gmail-like client-side drafts and a bit more.
Read the article and code here.
Just a quick follow up to our last meeting. Extra big thanks to Greg, Holly and Christophe for coming out! We had standing room only on campus (60+) and the online Connect room maxed out at about 36 people. Great turn out for a great meeting. For those of you on the Connect session I don’t have to point out that we had a few audio glitches here and there. We’re in the process of pulling the actual video footage that was shot and we’ll see what we can pull together between it and the archived Connect session. (Note to self: Just go buy a few more audio cables, connectors, etc to avoid this in the future).
There were a lot of open source projects thrown out during the presentations. I thought I’d put together a list of links of the ones I remember being brought up:
Great meeting. Thanks for coming out. We’ll post our next meeting in the next few days