[sourcecode language='jscript']

function ajax(){
var pagePath = window.location.pathname;
var opcoes =
{
"method":"post",
"data": "{}",
"urlEncoded": "false",
"headers": {
"Content-Type": "application/json; charset=utf-8"
},
"onComplete": completou
};
var ajaxObj = new Ajax(pagePath + "/testeAjax", opcoes).request();
}

function completou(result){
var obj = Json.evaluate(result);
alert(obj.d); // se tiver usando .net framework >= 3.5
alert(obj); // qualquer outro .net framework
}
[/sourcecode]

O que o pagepath faz?
Apenas pega o conteudo da url e concatena com o nome do pagemethod que foi implementado no code-behind.
Ex.:

http://localhost/default.aspx = default.aspx/testeAjax

No code behind:

[sourcecode language='csharp']
[WebMethod()]
public static string testeAjax()
{
return "teste";
}
[/sourcecode]

Well, Prototype + Scriptaculous are serious pain in the neck, but I've moved on. I guess many Javascript developers have moved on from those two as well.

I still like Mootools. Their website is always so sexy, and the documentation is always clear. (+ 654768864 points for Mootools)

But I now know why I like Mochikit better:

"Mochikit does not mess with Base Object properties."

Mochikit is simply a library of useful functions. Functions that make Javascript development more pleasant, and I like that.

Side Notes:

• I never used Dojo, so I don't know anything about them. That being said, Dojo is massive! 4.1 Mb of tar.gz file.
• GWT doesn't count in my preference list, because it's a JAVA library that writes Javascript. Not my cup of tea.

References:

• Mochikit Documentation
• Mootools Documentation
• Prototype Documentation
• Scriptaculous Documentation
• Dojo Documentation
• GWT Documentation

It doesn’t represent only a “small revision”, but adds more flexibility to the code and a lot of internal enanchements: better performances (speed and structure), less lines of code, more components. I highly recommend to update the previous version with this more powerful and complete last one.

Now let’s see the major changesets and new features:

• new Fx.Cycles effects: inOutLeft and inOutRight
• new Fx.Cycle tranistion, linear, to change the slides without a particular animation
• new internal engine of Fx.Cycle and Fx.Cycles to allow to create thumbnail based and timed animations
• new Virtual transition: fold and new Virtual option: adjustStyles to allow the boxes to appear in the correct positions on window resizing
• new Plug-In: Tutorial, which allows to create professional step-by-step presentations (cycled or not)
• new Plug-In: Tabs, which allows to create professional tab based presentations
• new Overlay rendering: performance improved especially for IE6
• new internal structures to make the whole result more robust and flexible

As for the code, the examples section is now updated and you will find some new demos:

• Tutorial
• Tabs
• Tabs Fixed
• Cycles Extra

As for the previous releases, the blog and the forum are always opened and tips, suggestions, bug reports and responses are highly welcomed.

Now do stop talking and try moo.rd 1.3.2 out!

(Via moo.rd - Blog.)

Para solucionar o problema, tente usar o seguinte código, no final da página:

$each = function(iterable, fn, bind) {
if (iterable && typeof iterable.length == 'number' && $type(iterable) != 'object'){
for (var i = 0, j = iterable.length; i < j; i++)
fn.call(bind, iterable[i], i, iterable);
} else {
for (var name in iterable)
fn.call(bind || iterable, iterable[name], name);
}
};

Alla fantasia di ognuno va l'utilizzo ;)

DEMO

CODE

ARTICLE

• PDF
• PNG

2. Addison-Wesley’s JavaScript Reference Card – PDF

3. JavaScript and Browser Objects Quick Reference

• PDF

4. The most common DOM methods at a glance – PDF

5. JavaScript Quick Reference Card/Cheatsheet

• PDF

6. mootools 1.2 cheat sheet

• PDF

7. jQuery Cheatsheet

• PNG

8. jQuery 1.2 Cheat Sheet

• PDF

9. jQuery Visual Map – PNG

]]> http://janckos.wordpress.com/?p=263 Fri, 04 Jul 2008 01:41:17 +0000 janckos http://janckos.wordpress.com/?p=263 MooTools is a compact, modular, Object-Oriented JavaScript framework designed for the intermediate to advanced JavaScript developer. It allows you to write powerful, flexible, and cross-browser code with its elegant, well documented, and coherent API.

MooTools code respects strict standards and doesn't throw any warnings. It's extensively documented and has meaningful variable names: a joy to browse and a snap to understand.

Descargar: MooTools 1.2

• Core

1. Core
2. Browser

• Native

1. Array
2. Function
3. Number
4. String
5. Hash
6. Event

• Class

1. Class
2. Class.Extras

• Element

1. Element
2. Element.Event
3. Element.Style
4. Element.Dimensions

• Utilities

1. Selectors
2. DomReady
3. JSON
4. Cookie
5. Swiff

• Fx

1. Fx
2. Fx.CSS
3. Fx.Tween
4. Fx.Morph
5. Fx.Transitions

• Request

1. Request
2. Request.HTML
3. Request.JSON

Wird das DON3 von Grund auf neu gebaut? Diese Frage steht momentan tatsächlich im Raum. Wir überlegen, ob wir nicht vielleicht, bevor wir das DON3 wirklich bauen, eine Solideren Unterbau schaffen und ganz neue Features einbauen.Zu dieser Frage führt uns unter anderem das Release des MochaUI 0.9 und Mootools 1.2

Zuerst würden wir am Unterbau einiges ändern.

• neue Funktionen
• Konstanten erschaffen
• perfekte Einbindung von MochaUI und Mootools
• neuen Template Parser

Durch dieses neue DON3 wären wir in der Lage, das DON3 noch effizienter zu gestalten. Das bringt auch viele Pluspunkte für Entwickler die durch modernste Technologie (Mootools 1.2) und einfach zu benutzende Funktionen (DON3.functions) noch bessere Programme für das DON3 bauen können.

Wie gesagt ist das noch nicht sicher. Ein weiterer Grund ist Snow Leopard, das neue Betriebssystem von Apple, das keine neuen Funktionen bieten wird sondern die alten Funktionen stark verbessern möchte.

Seien wir gespannt, was aus dem DON3 wird. Fertig wird es auf jeden Fall!

mfg, Kurt Höblinger

Les recomiendo le den una mirada, está muy bueno.

mootools
notification
javascript
roar
plugin

Not only has the API been completely revamped, but there have been several significant changes to the site and the way the MooTools community interacts.

Why the Rush?

You may have noticed that the 1.2 release has come, quite literally, overnight. Over the past few months, we’ve come to realize that the 1.2 beta is even more stable than the “stable” 1.11 release. In fact, many developers (including some of us on the Moo team) have been using 1.2 in critical applications for some time now.

Users coming into #mootools asking for support have been unofficially told to by us to upgrade to 1.2 for months. Reluctant as we were to let ourselves call our work on 1.2 “complete”, the reality finally hit us that it was time to officially offer our release to the entire development community. We therefor decided to “just do it”, flipping the final switch and changing to the new version of the site before this blog post and some areas of the site were completely functional.

Where Have the 1.11 Docs and Demos Gone?

The 1.11 docs have been moved to http://docs111.mootools.net. Conversely, the 1.2 docs have been moved from http://docs12b.mootools.net to the main docs subdomain (http://docs.mootools.net). The same is true for demos.

• 1.11 Documentation
• 1.11 Demos
• 1.2 Documentation
• 1.2 Demos

1.2 is Totally New

Don’t let the version number fool you. 1.2 is not merely a minor revision of 1.11. As those of you who have been reading the blog will be aware, 1.2 has a completely updated API and is not compatible with 1.11 code. You can, however, utilize the compatibility layer that has been built to make the transition to 1.2 easier.

• Core Compatibility File
• Plugin Compatibility File

Since most of the changes between 1.2 and 1.11 have been documented in earlier posts to this blog, I won’t go into the details here.

Offsite Hosting of Version Management, Tickets, and Discussions

Because of the increasing popularity of this project of ours, we have been under an increasing amount of stress to keep the various parts of this site running in good order. You may have experienced downtime relative to MooTools recently. We understand that many developers utilize MooTools in critical components of their projects, and such downtime is completely unacceptable.

To solve these issues for the 1.2 release, we have moved our critical components offsite to the best provider of each component, granting MooTools users with the highest possible uptime of all areas of the site. A major benefit of this move is being able to completely reinvent the way we interact with our community of users (aka you guys!).

Git

Along with the 1.2 release comes our shift from Subversion to Git. Git is a huge step forward to our development
model, allowing everyone who wants to contribute to MooTools the ability to create their very own fork. Each fork can then be merged
into the main core as seen fit or used on its own as an alternate version of MooTools. This allows us to release faster, iterate to
better versions and better handle the contributions of the community.

This allows would-be contributors to play in their own sandbox without worrying about whether or not their suggestions are appropriate. So get forking!

Please note that the Subversion repository will no longer keep up with changes to MooTools. You will have to check out the Git
repository for that.

To keep the core lean and mean, we have created a separate repository for plugins, called “More”. Plugins are defined as specialty components which aren’t crucial to the core functionality of MooTools. This includes modules which have been part of the core distribution until now.

You’ll also notice that the download page has been split into two pages, one for Core and one for More. (Further repositories may be coming in the future if we can think of more rhyming names.)

GitHub

We’re using GitHub to host our new Git repositories. We now have one respository for Core and another for More. The folks over there have given us an extremely warm reception, and we are likewise very happy to have such a great service at our disposal.

Bug Tracking by Lighthouse

We have abandoned our Trac, which has been giving us problems over the past weeks, for Lighthouse. Lighthouse allows us to integrate our ticketing system with our new Github account and should provide everyone with a comparable experience to our previous system.

You can visit the new Lighthouse account here.

New MooTools User Group

As part of our offsite initiative, we have moved the community forum to Google, where it hopefully will not crash and die. The forums will be back shortly, but only as a read-only archive.

Join Us on IRC

While we’ve been partying in the IRC room for quite some time, the IRC link to #mootools on Freenode has been added to the main page of MooTools.net. If you have not visited us there before, please feel free to stop by to ask your questions or just hang out. We love chatting with new users.

New Faces

One last note is that we’ve added two new members to the MooTools production team, Jan Kassens and Thomas Aylott. Both of them have been working extremely hard for quite some time now to bring you a better framework, and we’re very happy to give them formal recognition.

Links In Case You Missed Them

Docs and Demos

• 1.11 Documentation
• 1.11 Demos
• 1.2 Documentation
• 1.2 Demos

Compatibility

• Core Compatibility File
• Plugin Compatibility File

Git Repositories

• Core Repository

• Plugin Repository

  THE SUBVERSION REPOSITORY WILL NO LONGER BE UPDATED.

Bug Tracking / Tickets

• MooTools at Lighthouse

Community Discussion

• MooTools Users at Google Groups
• #mootools on Freenode

(Via MooTools - Home.)

Sabemos que una página al ser invocada por el navegador va solicitando los objetos a medida que se van necesitando, o van siendo leídos. Es decir que el servidor envía la página y el navegador lo primero que ve es la etiqueta <HTML> luego la etiqueta <HEAD> y carga cada una de las etiquetas que están dentro del HEAD de forma secuencial, y así sucesivamente con cada línea de nuestra página.

El problema se presenta cuando intentamos ejecutar un método Mootools y la librería aun no se ha cargado, o cuando necesitamos asignar un evento a un objeto y el objeto aun no ha sido cargado. En estos casos vamos a tener una Excepción de javascript.

Para evitar esto, debemos asegurarnos ejecutar los métodos y funciones cuando ya estemos seguros que no van a fallar por que el objeto aun no existe. Mootools nos facilita esta tarea, al ayudarnos a detectar la carga de la página. Estos eventos son:

Doomready: Ocurre cuando se ha cargado todo el contenido de la página excepto imágenes.

Load: Ocurre cuando todos los objetos de la página han sido cargados.

Estos eventos son los que nos permiten informar al usuario de que la carga de la página está en proceso o ya finalizó al estilo de aplicaciones como GMAIL.

Para utilizar estos eventos vamos a usar el método AddEvent de Mootools, y lo vamos a asignar al objeto Window.

Ejemplo:

window.addEvent('domready',function(){

// CODIGO …

});

El método addEvent permite asignar a cualquier objeto un evento, y ejecutar una función específica al momento de disparar el evento.

La sintaxis es:

miObjeto.addEvent( 'click' , mifuncion )

Un ejemplo para adicionar un evento click a un link podría ser así:

window.addEvent('domready',function(){

$('elLinkID'). addEvent('click',function(){

Alert("Esta es una prueba…");

});

});

En donde la definición del link dentro del HTML sería:

<a href="#" id="elLinkID">click aquí</a>

Listo, ahora ya tenemos un evento capturado con Mootools. Básicamente los eventos se llaman igual que en HTML pero sin el prefijo "on" es decir el "onClick" ahora es "click".

Y así con los demás eventos como blur, mouseover, etc.

Esto funciona igual con la versión 1.2 ya que es algo estándar y básico del framework.

otra vez publicando de afan, espero que pueda hacer cada vez mejores mis publicaciones...

mootools
ajax
javascript
web2.0

allí tenemos la documentación de la versión anterior en mootools

Mootools: Página oficial

Bueno entraremos a analizar esta nueva versión para ver que cosas nuevas trae y como va a estar la compatibilidad con  plugins de la versión 1.1.

Ahora me tocó modificar la entrega 2 de los post sobre mootools que estaba haciendo, aun no se que va a pasar con la versión 1.1 y si va a tener mas soporte, yo creería que no pero vamos a ver que pasa y como se porta esta nueva versión.

Por ahora resta esperar que la página esté completamente lista y que más información van a plublicar... ya me descargue la version 1.1 que pesa apx 60k. empesaré a usarla...

link

I guess pretty much everyone has seen Barack Obama’s website by now, which is clearly one of the prettiest of all candidates we’ve heard of so far. Not only is it an example of state-of-the-art design, but it’s also nice to navigate and interact with.

I decided to imitate the homepage slideshow. I had already experimented with similar animated lists, which allowed me to have it ready within minutes

The creation

I took my previous class (SlideList), and made a few changes here and there. It works with MooTools 1.2, and supports all kinds of shape transformations (top and left coordinates, and height and width properties), which means it can now be used with vertical, horizontal, or even irregular lists.

I extended it and came up with a new class that receives the images and loading spinner as parameters (note: it’s arguable whether this is the best decision OOP-wise, but due to the simplicity of this script, this was the right call)

The code

To ensure all images are loaded before the user makes any interaction, the MooTools Assets component is used.

The CSS plays a major role (as in every other animation-focused script). I suggest you analyze it carefully before implementing it in your applications or websites. You’ll probably need to adjust the ids, or use classes instead to keep your stylesheets clean.

The markup is meaningful and simple. Two lists are used (one for the images and the other for the links). The loading element is included in the HTML, but it’s probably better to inject it from the script directly.

The pictures

The beautiful pictures were taken from Flickr with permission of the owners, unless they were directly released for non-commercial use. Thanks vgm8383, dogonnit, M. TANIGUCHI, GustavoBuriola & others!

The demo

Click here to see it in action or download it

(Via Devthought - Guillermo Rauch's Blog.)

I've had lots of people I work with raving about Dojo, but from the little play I had before with it, I wasn't that impressed. Although to be fair it makes a lot more sense now. Certainly it seems pretty powerful, but then it really should be for a 15MB sized library of javascript files. I'm still not entirely convinced by it though.. I found some of the widget behaviour was rather strange and I was very unimpressed with the documentation. I did like the simplicity of the event handling and xhr request/reply though.

Having a quick look at the other toolsets out there, mootools does look rather interesting. And this is built on the protoptype toolkit which I did actually quite like.

I've recently acquired a new domain, so I'm intending to have a play with javascript to build a new website. Although I have to admit, I still haven't seen anything I can do which wouldn't be a lot nicer and simpler in Flash. The week has really reinforced for me the fact that Flash really is a very cool and very powerful tool. And I probably need to update my version too.. I bet there is some cool new functionality I'm missing! Yikes, I'm starting to sound like a developer! ;-)

But all of this is focussed on how quickly JavaScript runs in the browser and in the case of JavaScript libraries, how quickly they run, once they have been downloaded to the browser. And that's the key point. There is still an easy performance gain to be had by eliminating the time and resources required to download these libraries from your server to the client's browser.

So Google have begun hosting a selection of the most commonly used JavaScript libraries so that over time, they will be cached on a lot of users' machines.

At present, if I visit a shopping web site that uses jQuery and I then visit a travel information web site that also uses jQuery then my browser will have to download the jQuery library once when I visit the shopping site and then again when I visit the travel information site even though both sites are using the same file.

If both sites download the jQuery library from a common source, in this case Google, then the file only has to be downloaded once and is available for any other sites that use jQuery as well.

By using this method, you'll take some of the pressure off your own web server, save a bit of bandwidth and make initial performance of your site better. The latter is something that your visitors using dial up or in countries with slow connectivity will definitely appreciate.

At the moment, the libraries provided are:

• dojo
• jQuery
• MooTools
• prototype
• script.aculo.us

Google will be expanding this selection in future and its success is dependent on uptake.

You can see Dion Almaer annouce it below and full details are at code.google.com/apis/ajaxlibs/documentation/

Ele foi desenvolvido sobre a biblioteca mootools e é bem fácil de manipulá-lo.

Site: http://www.phatfusion.net/imagemenu/
Fonte: http://www.noupe.com/css/13-awesome-java-script-css-menu.html