The power and flexibility of the jquery library is pretty awesome.  There are a number of reasons that you may want load the files one at a time, or the individual .js files on an as needed basis.

Last week, I completed a blog post on getting jQuery up and running (http://blogthingee.com/blog/getting-jquery-ui-working-drupal-6x)... Now we can see if it is working.

For now, let's just assume you want them all the time, and you want to test them right now, or you simply want to test that you have all of the jquery ui goodness at your fingertips, here is how I would go about it...

After several attempts, I believe that I have a pretty good system/process for getting jquery ui to work with drupal 6.x.  So I guess it's time to share :)

1. Check Current Jquery Version.
2. Update Jquery with Jquery Update Module
3. Download Jquery UI Module
4. Download the support files for the Jquery UI Module
5. Enable the Jquery UI Module

I would first check and make sure your current version of jquery is working/running on the site, as this entire process (which I have done several times for both fun and work) has worked best for me if I do each step in turn, then verity what I have done...

I looked for this a few times and didn't find it so I decided to write a quick blog post for future themers to discover. You see Drupal is full of forms and fields. There are any number of reasons that you may want an element on a form to be identified by a unique class or ID. I ran into this today when I wanted to theme a fieldset, provided by a module, that didn't have a class on the fieldset. Now there are many ways to theme a fieldset by using the divs that contain the fieldset. However, sometimes it's nice to just have a theme set for a fieldset, and apply that class when and where you need it.

Last week I wrote about preprocess functions and wanted to do a little follow-up because I was having even more fun making changes, adjustments, and alterations.  There is so much here for themers, there is an excess of options and they can be organized and structured very well.  Again, as I often say, I do not profess to be a php-guy (I continue to get better, and using it daily now, someday I will be where I want to be with it...) so this structure and framework has been completely awesome for me.  So what's next with preprocess...

The less tpl files the better.  Don't get me wrong... LOVE the tpl file, can't live without the tpl file... If I need several tpl files, let's do it... but, in some cases, one tpl file can provide enough power and flexibility to handle several content types, and keep the job of a themer a little easier.. o.k., not easier, but a little cleaner for my tastes.

The magic is the preprocess functions.  Here's a little about the preprocess function.

Sometimes... most of the times... I don't want the "split summary at cursor" option on the sites I develop. There are any number of reasons I don't want it. Most of the times, it just isn't relevant and others... I just don't want the users asking a milion quesitons.
And inevetibally, there is more stuff I don't want in my forms, want differently, or want moved.
My solution has been that on all the sites I develop I have a custom module. In this modules is one of my most used hooks... form alter. I have it all set up and commended out some of the lines but leave them in for quick reference...
I'll show it to you, then explain a little more....My module name is theme_thingee, and here's how I have it set up.

A Themer's Solution....
I have in my theme a directory called plugins. in there I have layouts and styles in styles I have a folder called thintop and... in there I have 2 files (tho I have commented out the template file in favor of this fancy rendering which gives me admin links and extra stuff in my pane... thintop.inc and THEME-NAME-thintop.tpl.php (based on http://drupal.org/node/495654) good info at http://drupal.org/node/427192

I came across this little extra nugget while looking for some stuff for preprocessing. How many times have I typed out base_path and path_to_theme... With this little gem I am just a few keys faster, and lovin it.

function themename_preprocess(&$vars, $hook) { $vars['theme_path'] = base_path() . path_to_theme() .'/'; }

Imagecache

project page
the world is a better place because of imagecache, imageAPI, and filefield image. Imagecache has more and more contributed/add-on modules... it is without a doubt the premier image handler in Drupal

Imagecache Profiles

project page
this little gem has saved me from delving into php code on so many occasions. The ability to consistently use imagecache is always a good thing.

The user login block is one of the most common blocks on any Drupal site. It might be in this region, or that region, or this header, footer, or block... the idea of this post is that it is that you, at some point, you will probably want to theme it... and maybe you'll use this post to help you through. I have spent part to the day working with a flexible way to make the user login block a little cooler. Specifically, I wanted it horizontal, and I wanted to change some of the values, and finally some css to finish it off... and eventually some jQuery if I can find the time. Through this process I was once again reminded of the power of Drupal.