Javascript

I've been using yslow to review a few sites and always leave one last step out: move javascript to the bottom of the page

So, on a test site I just moved my

Other than this there isnt really much that strikes me as being overly weird about javascript but I cannot find any good documentation on this syntax that I have seen around because I dont know what it does! Any suggestions or documentation would be great thanks, its just been bugging me...

(function() {
 // ...
})();
(function() {
 // ...
})(var);
function() {
 // ...
})();

has anyone documented the drupal js functionality for use with Aptana ?

Hello everybody,

I'm sure this is not the right place to post this. It's just that I'm not sure where to post it and I'm about to pull whats left of my hair out messing with this ajax stuff. I have an idea for a niche website and am working to develop it. I want to throw in some ajax and jquery in order to enhance the user experience. So I'm trying to learn how to do things with ajax.

I plan to make an inline search module for D6. Basically it would provide a UI for various pages such as permissions, modules, menu, and other core ( and well supported module pages ) to provide a very fast way to narrow down the page content to find what you want.

Over on the MySite project we're having a recurring issue with handling the JavaScript for Google Gadgets on our pages. It looks as though there is a problem with the order in which the JS are executed -- but that's really a guess on my part.

Sometimes, Flash embeds don't fully load: http://drupal.org/files/issues/gadgets.png

Sometimes, the JS loads the same element repeatedly: http://drupal.org/files/issues/GoogleWidgetScreenshot.png

Expert 'scripters exploring the issue would be much appreciated.

http://drupal.org/node/170660

Hi,

I wonder how hard it would be to make an iframe resizable, much like textareas are resizable in Drupal (with the textarea.js).
The reason i ask this, is because i have created a module to integrate the "Whizzywig" WYSIWYG editor into Drupal (see http://drupal.org/project/whizzywig).
This editor replaces the textarea with an iframe to allow WYSIWYG editing.

I just added a new slideshow mode to the Views Slideshow module. You can see a demo at Drupal Hub. It uses JQuery and views, so any type of view could be made into a slideshow. The current modes are single frame, as seen in the left sidebar of the demo page, and with 'thumbnails' as shown on the content of that page.

I also revamped the themes for it, making it easier to theme specific elements of the slideshow.

We're going to be having the first all-day jQuery mini-conference October 27th, here in Boston, MA. Already, a large portion of the jQuery team will be attending and giving talks - so if you're interested in meeting some of the people who've helped to make jQuery possible and chatting with fellow developers, then this is a fantastic place to do it! (Note: jQuery is the JavaScript library that's used to power Drupal.)

Hi Everyone,
I just wanted to let you know about a new views related module, Dynamic Views. (http://drupal.org/project/dynamic_views) It allows you to dynamically update the main content area (no page reload) when you click a node link in a view block. It also allows you to change dynamically update a view using a filter at the top. You can combine it with some elements of the jquery interface library for some pretty cool effects. (see http://warnerbrosrecords.com/artists)

I just created the Spry Framework Module to facilitate the implementation of some Spry Goodness into Drupal.

The Spry framework for Ajax is a JavaScript library for web designers that provides functionality that allows designers to build pages that provide a richer experience for their users. It is designed to bring Ajax to the web design community who can benefit from Ajax, but are not well served by other frameworks.

Has anyone had a chance to check out the new JQuery UI? I think it is what people have been referring to as Interface2.

Update: It looks like Dimitri has created the UI project to deal with jQuery UI in D6. I have just created the jQuery UI Backport project to allow the library to be used in D5 without breaking anything.

Ran across this 'speedtest' page today, it has interesting results especially cross-browser:

http://mootools.net/slickspeed/

If you run it on FF ( at least on my iMac and a nearby Vista machine ) moo and prototype are much faster, but extjs wins hands down on Safari ( OS X ) and IE7 on Vista. jQuery is middling IMHO the benefits in developer satisfaction are worth the speed cost vs prototype.

Discuss.

With the announcement today of another four weeks before Drupal 6 freeze, we have another chance to get some critically needed Javascript patches into Drupal core.

Very few Javascript patches go through, mostly for lack of in-depth reviews. Please, everyone on this list, take your turn in reviewing Javascript patches! Better yet, wade in and help make improvements to the patches.

Here's a link to Javascript issues needing review:

http://drupal.org/project/issues/drupal?components=javascript&states=8%2...

A few highlights:

I would really love if some enterprising member of this group would submit a patch for core where we uprgade to latest jquery. you really don't want to stick with 1.0 for another year, do you?

At minimum, the patch should swap jquery.js and fix anything that breaks. For bonus points, do whatever refactoring makes sense based on new jquery features.

I'm a js novice - just cheerleading on this one. Go Team!

Just a quick pointer to the jQuery Interface Sortable module that we added last week. In 5.x, it depends on the excellent jQuery Update and jQuery Interface modules. In 6.x (or HEAD -- I'm still trying to figure out how I got that 6.x release node in there), it only requires jQuery Interface.

Because there does not seem to be active development around the JavaScript localization issue, I figured I'll try to get some attention from the Javascript group. The issue at hand deals with enabling string localization in JavaScript files. Because Drupal 6 will be a big push in the multilingual direction, localizing JavaScript files should also be actively on the table. If you have time, please look into this patch or at least drop in your two cents. Thanks!

As part of SWF Tools you can embed Flash into the webpage in 2 obvious ways:
- directly embedded into the html.
- with a flash replacement technique (eg. SWFObject, jquery.flash.js, and UFO to come)

So, say my choice, as administrator, is SWFObject. But what if the user has javascript turned off? I think the result is no flash (even though the use might want to see it).

I posted a module today that will be of interest to anyone wanting to use tabs on their site without having to do custom coding.

It's called Panels Block, http://drupal.org/project/panelsblock. With it you can expose a set of panels as a block via a new option on the panels edit form. (Only the content added to the 'left' area is made available as a block.) There are two ways to display the content: default (sort of like a regular panel) and tabs. (The tabs.module, part of Javascript Tools, is required.)

Okay, so the story goes like this:

1) The SPAjax module (4.7 only) has a feature that allowed you to apply (Scriptaculous) Javascript effects to Drupal messages - allowing the "fade yellow" technique, pulsating, or shaking of the message divs. I missed this on my Drupal 5 sites and wanted to implement it in JQuery. Easy, right?

2) JQuery's effects library is called Interface. I couldn't find a version of Interface that would work with JQuery 1.0.1 (the version in Drupal core).

3) In order to update the JQuery in core, you need John Resig's compat-1.0.js script which allows backwards compatibility with scripts written for JQuery 1.0.x (such as everything in Drupal core). So now we need a module to include the compat-1.0.js file.

4) Interface.js is a relatively large file ~80K. It's "parts" (individual effects) are available separately, but this only increases the possibility that two modules will include the same (or worse two different versions of the same) scripts. So... now we need a central module to include a single interface.js file on the page when needed.

So here's what we ended up with: