Web Info & Tutorials

Un très joli Yorkshire mâle un vrai bijoux.Agé de 9 semaines propre sur papier jjournaux..Examen complèt chez le vétérinaire.Vacciné,vermifugé et carnet de santé.Il est noir et feu il pèse 2 livres.S

Dylan Schiemann of Dojo and Sitepen has expounded asking What is bloat?.

We do hear a lot of people talking about the Xkb of JavaScript that they are willing to put in a page/app, yet bloat is a lot more than that (as Dylan attests).

At the core of this article we hear loud and clear:

• We need better tools to minimize bloat of various flavours
• We need better tools to be mindful of the bloat
• When users have 6 tabs open with rich ajax apps within them, it isn’t fun right now

Where does Dojo fit into this?

Dojo will be working over the coming months to improve performance, which is something we have been doing with each release of Dojo. But improving toolkit performance is not enough… we also need to share best practices on how to get the most out of our browsers, and to ask for more from browser vendors (they’re already listening). We will be writing a series of posts on performance tuning and testing, and we look forward to reading your comments and trackbacks, and learning from your performance tips. We as a community need to fix this issue before Ajax suffers the same fate as DHTML. After all, no one likes to be bloated.

Ninjawords is a simple dictionary service that uses Ajax to ping resources to retrieve dictionary content.

To feel lucky in this app, you click random.

As we become to the modify of 2006, we wager that Ajax and Web 2.0 are broad up on the Google Zietgeist for 2006.

1. define promiscuous
2. define web 2.0
3. define ftw
4. define calidad
5. define ajax
6. define ensayo
7. define ciencia
8. define administracion
9. define harlequin
10. define filosofia

Since this is the delimitate list, does it stingy grouping hit no cement what this means? It is hornlike to undergo what to attain of it supported on the another entrants on the itemize too.

Anyway, it has been a enthusiastic assemblage for Ajax, and we countenance nervy to the maturement of the expanse in 2007.

( via Mark Holton )

It’s the time of year to be posting random predictions for 2007. Here are 2007 Ajax predictions from Dion and myself, please post your own in the comments.

Dion predicts:

• Ajax beats AJAX in all but bad newspapers.
• Someone tries to coin Ajax 2.0.
• A large amount of apps have flash AND ajax, and users don’t know or care.
• Many frameworks consilidate or die.
• A widget api means componts can run on many frameworks using one api.
• Ajax wpf/e interop.
• Dashboards become front boards.
• More desktop apps get written with javascript.

Michael predicts:

• 2005 was the year that developers learned all about Ajax and by 2006 everyone else in the industry had caught up. In 2007, is is mainstream users who become acutely aware of the trend towards rich applications inside the browser, and discover that even word-processors and spreadsheets - along with a wide array of workplace applications - can be webified. At the same time, users remain oblivious - and rightly so - to the underlying technologies that power them.
• The boundaries of Ajax harden, with most developers gaining a clear understanding of what it can and can’t do with modern browsers and managers in a better position to decide on application architecture (whether to use Ajax, Flash, desktop, etc.).
• More attention on Ajax accessibility due to some government report or court case.
• Google Office. Finally!
• Backlash against Google Office as managers learn that their data must be hosted externally in order to use it. Pressure from bloggers and some analysts to make an Office appliance that can live behind the firewall, but it’s not happening in 2007.
• The advertising and media communities finally become aware that page view metrics are no longer the only way, but generally treat it as a problem and fail to see that the situation is actually better than before.
• Several fringe technologies heat up as developers notice they are already being used in some applications and learn how to apply them: HTTP Streaming (Comet), Virtual Workspace (Live Scrolling - never-ending scrollbars), Cross-Domain JSON (along with JSONP, JSON APIs, JSONRequest, and a general lack of awareness about the JSON security issues), Unique URLs (bookmarkability/back button), Lazy Registration (personalized functionality before formal signup). Comet in particular … it may be 8 or 9 years old, but it’s big news in 2007.
• Other fringe technologies grow, but remain, well, fringe. Such as Host-Proof Hosting and applications involving offline storage.
• With its excellent documentation and pattern language integration, the Yahoo UI library becomes the standard weapon of choice among mainstream developers seeking a pure Javascript framework. In the Java world, GWT makes great strides as the platform becomes richer and design patterns emerge.
• Mobile web development continues to suck.
• Javascript increasingly recognised as the world’s most popular “second language” and becomes popular as a lingua franca to describe generic programming concepts. Several attempts at server-side Javascript frameworks.
• IE7 causes more than a few headaches.
• Firebug is installed by pretty much any developer using Firefox.
• CSS is back, baby! Echoing the recent mass adoption of Javascript, developers who previously had a fleeting familiarity with CSS now become fluent practitioners.

Best wishes for 2007, however you play your Ajax!

Another day, another article bashing the Javascript toolkit everyone loves to hate - Prototype. The complaints can be narrowed down to a few points:

• “it breaks the ‘for in’ loop” - no it doesn’t - you were probably using ‘for in’ where you shouldn’t have. Javascript is a flexible, powerful freedom language, and its _okay_ if your framework uses that to the full extent. That means you and your development team need to be educated and aware of the ramifications of it if you want to play ball. The stuff that Prototype did to Object in earlier versions, btw, was a bit too much and has been removed in the latest versions. (related reading here)
• “its too big” - eh, cache it, compress it on the server side, or use a stripped down version.
• “its has no docs” - although I’m disappointed to see that Sergio hasn’t updated his excellent reference since May, there are still so many fantastic howto’s and tutorials written using Prototype. Plus the books out now that base much of their code on Prototype. One official reference doc somewhere would be very nice, however.

My main gripes right now with Prototype would be what looks like a low level of activity in the source and this doc project, and the lack of any good references on how to do solid TDD or BDD in Javascript (with Prototype, or otherwise I suppose). I’m aware of rspec clones in javascript, but what I’m missing is the big picture on how to integrate those tests into the main test suite and what to use for mocks and stubs. I want to be able to write the bulk of my JS tests in textmate, without having to start a browser or use anything like Selenium.

Je elegant un uromastyx du mali noir ou très coloré, un uromastyx du niger aussi très coloré, un uromastyx egyptien ou autres form à vendre pas chèr ou que je pourrais échanger contre un mes

John Resig has posted on The Path to jQuery 1.1 which is not backwards compatible with 1.0. That being said, a compatibility plugin will be available to help the transition.

The planned changes are:

• Methods like .oneclick() and .unclick() will be going away in favor of .one(”click”) (new) and .unbind(”click”). We found that these methods weren’t used enough to warrant the 70+ API entries that they required.
• Selectors :nth-child(), :gt(), :lt(), and :eq() will all be starting count at 1 instead of 0, in line with the CSS specification. (This is a bug fix, but causes an incidental API change)
• Some CSS helper methods are going away, like: .color() and .background(). You should start moving over to using .css(”color”) and .css(”background”) instead.
• Some attribute helper methods like .title() and .rel() are going away. You should start using .attr(”title”) and .attr(”rel”) instead.

In other jQuery news, Rob Gonda has released AjaxCFC for jQuery which is a port of the client side.

this is the adsense member aggroup :

link to this place : adsense