Both the TOC (Table of Contents) components from samaxesJS JavaScript library have been updated.
Changes include:
Reduced file size by removing duplicated code using a for loop when defining and processing indexes (1.8KB for the minified jQuery TOC plugin). Added a new option: context, allowing the TOC to list headings from only a portion of the page. Please report any bug you may find in the project Issue Tracking.…
This example was greatly inspired by the Stripes and jQuery AJAX Forms article from Freddy Daoud, but with some nice improvements
Last week I was working on a new Stripes / AJAX example. It involves having a table listing entities, being the last row of the table a form for adding new ones.
The form gets submitted via AJAX, using jQuery, and the response is validated in order to check if the HTTP session is still valid.
If everything is OK, the list is refreshed and a success message appears. On the other hand, if validation errors occur, the list is refreshed and an error message appears.
Also, if the user’s session has expired on the server, an alert is shown to inform the user that his session is invalid, and the page is reloaded so the user can login once more.
samaxesJS is a set of utilities and controls, written in JavaScript, for building rich interactive web applications.
The first extension is a dynamic Table of Contents script.
The TOC control dynamically builds a table of contents from the headings in a document and prepends legal-style section numbers to each of the headings:
adds numeration in front of all headings, generates an HTML table of contents, degrades gracefully if JavaScript is not available/enabled.…
Today I stumbled on an article from 5ThirtyOne about an IE7 JavaScript library simply called IE7.
IE7 is a JavaScript library to make IE behave like a standards-compliant browser. It fixes many CSS issues and makes transparent PNG work correctly under IE5 and IE6
Impressive……
Brendan Eich, creator of JavaScript, give a keynote at The Ajax Experience.
Ajaxian have placed the presentation online so everyone can read up on some of the thoughts and discussion on JavaScript 2 and more.
Here we got to hear from the mouth of someone deep into the ECMA process about what we are going to see in JavaScript 2 and importantly why:
Motivation for JS2
Fix problems in JS1 that bug people daily A type system to enforce invariants instead of writing/debugging lots of value-checking code optional annotations, an extension to JS1 Programming in the large Package system Visibility qualifiers (namespaces, private internal public) Optional static type checking Support bootstrapping and metaprogramming Self-host most of the standard objects Self-host compiler front end and type checker Reduce need for future ECMA Editions As Brendan flicked through these slides, I couldn’t help buy realise how important the decisions are.…