JSConf 2010 Slides

For those of us who didn’t make it, I’ve compiled a list of slides + blog posts from the JSConf 2010 Track A speakers

Alex Russell – “Google Chrome Frame”
Post: http://alex.dojotoolkit.org/
Slides: http://alex.dojotoolkit.org/10/jsconf/gcf.html

Francisco Tolmasky – “Socratic: Documentation Done Right”
GitHub: http://github.com/tolmasky/socratic
Slides: ?

Aaron Newton – “Programming To Patterns”
Slides: http://www.slideshare.net/guest2ee5e2c/programming-to-patterns-presentation (not up-to-date)

Jed Schmidt – “A (fab) approach to web apps”
GitHub: http://github.com/jed/fab
Slides: http://www.flickr.com/photos/tr4nslator/sets/72157623883700702/show/

Dmitry Baranovskiy – “Raphaël the Great”
Slides: http://www.slideshare.net/Dmitry.Baranovskiy/raphal-js-conf

Douglas Crockford – “Really, JavaScript?”
?

Tobias Schneider – “Flash is dead, long live Flash!”
GitHub: http://github.com/tobeytailor/gordon
Slides: http://www.slideshare.net/ConfEcho/flash-is-dead-long-live-flash

Makinde Adeagbo – “Primer: Facebook’s 2k of JavaScript to power (almost) all interactions”
Slides: http://www.slideshare.net/makinde/javascript-primer

Steve Souders – “The Best of Steve”
Slides: http://www.slideshare.net/souders/jsconf-us-2010

Jenn Lukas – “JavaScript and Web Standards Sitting in a Tree”
Slides: http://www.slideshare.net/JennLukas/javascript-and-web-standards-sitting-in-a-tree

Ryan Dahl – “Less is More in Node.js”
Slides: http://nodejs.org/jsconf2010.pdf

Billy Hoffman – “JavaScript’s Evil Side”
Slides: ?

John David Dalton – “All you can leet”
Slides: http://www.slideshare.net/johndaviddalton/jsconf-all-you-can-leet

Aaron Quint – “Making Bacon / Making Code”
GitHub: http://github.com/quirkey/sammy
Post: http://www.quirkey.com/blog/2010/04/20/making-baconmaking-code-jsconf-2010/
Slides: http://swinger.quirkey.com/#/preso/aq-jsconf/display/1
Video: http://bit.ly/9j7u3L

Dion Almaer, Ben Galbraith, and Matt McNulty – “The mobile web”
Slides: http://www.slideshare.net/dion/the-mobile-web-2010-jsconf

This post has 15 responses

Posted in Blog, Client side 4 months ago

Socket.IO: sockets for the rest of us

Over at LearnBoost, I just released Socket.IO, a normalized Socket API that hides the complexity of the realtime transports.

With code as simple as this:

socket = new io.Socket('localhost');
socket.connect();
socket.send('some data');
socket.addEvent('message', function(data){
    alert('got some data' + data);
});

you’ll be leveraging:

Continue reading

This post has 9 responses

Posted in Client side 6 months ago

TextboxList 0.4 for jQuery is here!

Big update for my dear jQuery users. I’m rolling out TextboxList for jQuery 0.4 with these updates:

  • [FEATURE] Autocompletion with on-demand server querying

  • [ENHANCEMENT] All classes moved to $. to avoid global namespace pollution. Please make sure to prepend $. to TextboxList if you are upgrading from an older version:

       new $.TextboxList('#element');

  • [FEATURE] Easier jQuery-friendly initialization like this:

       $('#element').textboxlist({options});

    However, if you still need to access the TextboxList instance to call additional methods (like add), you’ll have to continue to use new $.TextboxList

  • [BUGFIX] GrowingInput now works in noConflict mode

  • [BUGFIX] Fix for GrowingInput to handle special characters and correctly calculate the input length.
  • [BUGFIX] Fix for support of multiple addKeys
  • [BUGFIX] Fix for focus problem when TextboxList gains focus through focusing an editable input
  • [BUGFIX] Autocomplete search term is now trimmed (thanks Mike Feng)
  • [BUGFIX] Fix for when the max option is used
  • [BUGFIX] Fix for unique = true and autocomplete.

As usual, head to the project page for download.

This post has 47 responses

Posted in Client side 10 months ago

TextboxList 0.4: On-Demand suggestions

TextboxList 0.4 is out, with new features:

  • check option, which can allow you to specify a function to filter out new boxes that do not meet a requirement
  • encode now receives the complete values, not only the id or string of the bit. This gives you full control of what you want to send to the server.

  • Autocomplete now works with on-demand suggestions. As easy as this:

    new TextboxList('form_tags_input_4', {unique: true, plugins: {autocomplete: {
	minLength: 3,
	queryRemote: true,
	remote: {url: 'autocomplete2.php'}
}}});

And some bugfixes:

  • Fixed missing index when unique: false and autocomplete were used, which resulted in an error
  • Fixed problems with items with id 0, which incorrectly evaluated as false.

Head to the demo to see the new autocomplete in action, and as usual, report any bugs you might encounter.
Update: 0.5 is out already, which fixes a bug with the traditional use of Autocomplete. Sorry for the trouble!

This post has 44 responses

Posted in Client side about 1 year ago

An IE6 post

Addressing an old subject again, misaddressed by many.

No matter how much we all hate IE6, we never seem to agree on what’s the best way to finally get rid of it. Web designers and developers alike have realized that investing too much time and effort in fixing its quirks is not viable from a business perspective, but they still want to reach that audience.

This ambivalence is what still drives people, like myself, to keep writing about the infamous browser.

Continue reading

This post has 21 responses

Posted in Client side about 1 year ago

TextboxList 0.3 and jQuery version out!

Moo TextboxList 0.3 changes:

  • HTML for bits not showing properly fixed
  • highlightSelector not working (due to a typo) fixed
  • GrowingInput missing pad function added (only affected if you customized growing.mini option)
  • Improved clicking the whole widget behavior
  • Other tiny enhancements / cleanup

Secondly, in the best interest of the JavaScript community, I’ve ported TextboxList to jQuery. The API changes slightly due to the different OOP approach, but all the functionality is intact. Head to jQuery TextboxList project page for more.

Update: 0.2 is out for jQuery. Bugs in autocompleter and IE have been addressed.

This post has 46 responses

Posted in Client side about 1 year ago

JavaScript RegExp based highlighting for MooTools and jQuery

How it works

A regular expression looks for text outside HTML tags. It uses a callback function to perform replacements to simulate native lookahead support.

When is this sort of replacement suitable ?

  • Remote HTML responses (ajax) highlighting
  • Autocompleters suggestion highlighting
  • User-typed HTML, WYSIWIGs, etc.

Generally speaking, the only downside of this method, since it deals with the innerHTML, is that all attached events and properties are lost when the replacement is performed.

Continue reading

This post has 8 responses

Posted in Client side about 1 year ago

The APNG Class

If you’re looking for an object-oriented, straightforward way to animate those alpha transparent PNGs, look no further.

Check out Devthought’s latest release, APNG 0.1

This post has 7 responses

Posted in Client side about 1 year ago

More please.

mootools

You wanted more, we give you More. Today the new MooTools More RC1 is being released, with an outstanding number of new plugins. More functionality, but with the quality you come to expect from the MooTools framework.

Most of the new components come from the excellent Aaron’s Clientcide library. I contributed to the improvement, refining and testing of some of his vast code, which brings More to its present state.

The goal here is to provide more great, simple and extensible tools to make developers’ lives easier. I suggest you head to the Docs or Builder page right away to start trying out the new stuff. As always, head to Lighthouse to report the bugs you encounter, or even to suggest new additions or features.

This post has 1 response

Posted in Client side about 1 year ago

Don’t repeat your moo

Given the Object-Oriented nature of the MooTools framework, code repetition is something that is long forgotten (or should be) in the scripts your write. With the avoidance of code repetition comes code reusability, which results in your website being easier to read, extend and maintain, and your scripts smaller in size.

At this point there’s no doubt in anyone’s mind that DRY is a principle we should stick to. However, let’s examine how to achieve this in the right way.

Continue reading

This post has 22 responses

Posted in Client side about 1 year ago