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...

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 year I would have tried to approach this problem with some kind of image/text replacement... This year it's a whole new ballgame.  The Drupal theming layer is like an onion and I continue to pull back the outer pieces and get to better and better stuff.  Maybe it is more like a Parfait (thanks Donkey from Shrek) ;)

So here's what I wanted to do. Drupal gives us a teaser output with comment links.

3 comments  |  2 new comments

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() .'/'; }

Am I the only one that wants a t-shirt that says "I Don't Support IE6"? Let's face it, not many people would get it, and I would just give the impression that I am a negative person. The fact is... I am a realist, and IE6 is going to be around for a while longer, at least long enough for me to keep finding newer better stronger ways to work around troublesome browser.

I have been envious of my MAC wielding friends since seeing the features and capabilities of the Coda text editor. I have used Dreamweaver, Notepad, Notepad++, and tried software such as Aptana (which I really like), Programmers Notepad, Komodo Edit, Top Style, and Ultra Edit. They all have some good features and do things well, but not quite what I wanted. I have just stumbled upon WeBuilder 2008 and I have to say that so far (it's been about 24 hours) I really like it! So I decided to create a quick blog entry to share this resource would be a good idea.

I spend the majority of my time around Drupal in the areas of website building and in the theme layer. Anytime I can find things to make my theming life easier in either... I take it.

One of the 'limitations' (using that friendly) is the options for theming. IMPORTANT to note... Drupal 6 ROCKS!! THEMING!!. One of the important 'additions' I try to create when working in the theme layer is to improve my ability to use CSS. Some sites require fancy, creative, and/or custom stuff revolving around menus.
[inline:newlinks.png]