ThickBox : Has anyone used it in their template ?

As I am exploring new avenues to enhance my templates, and love the LightBox concept, I was thinking what about using this kind of stuff to have not only images but inline content or login box or whatever is appropriate for this kind of technique (as usual, I’ll be very cautious not to overdo it...).

So I looked and found ThickBox 2.0 (much powerful than GreyBox)
And first impression : it really seems to be quite cool !
Check out the demo

Yet, I am eager to have some feedback as to "real life" usage, pro-cons input about this...
Has anyone tried it out in their template ?
What do you think of it in terms of user experience : does it break the navigation flow, would it confuse users ?

Any input much appreciated from you guys

I’ve used ThickBox on 2 different sites so far one of which is a MODx run site.
A breeze to implement. I quite like jsQuery.

On one of the sites it’s used to display a summary of pdf documents before people download it. I’ve had very good reactions from people especially for this use because they can make a better judgement before downloading huge pdf files. You can see it here: http://www.rivers.gov.au/lww/toc_rain.htm (and no the design is not mine, no not a modx site and yes the html needs recoding)

The only time I am having a problem is when I’m logged into the manager and view the site (that’s teh other site ). For some reason quickedit causes a problem with css transparency in Internet Explorer so when a thinkbox pops up the background goes black instead of a transparent dark grey. Not a big problem though, who cares what I see, what others see is more important

I just plonked the necessary bits into a template, adjusted a few paths and set some classes. Worked first time.

Thanks a lot for your input... I have read that there could be issues with jsQueries when you also use prototype... I guess you had no such problem ?

Quote from: davidm at Aug 22, 2006, 11:37 AM

Thanks a lot for your input... I have read that there could be issues with jsQueries when you also use prototype... I guess you had no such problem ?

Well perhaps that was the cause of the problems I had when being logged in. Quickedit uses prototype doesn’t it? I don’t use prototype in my page templates themselves so I don’t really know.

Yeah QuickEdit does...

I’ll do some trials but the jQuery doc sums it up :

Because the behaviour of Prototype and jQuery is different, when it comes to the $() function, it is recommended that you do one of two things:
Un-ambiguous Selectors

Always be explicit when you search by a single ID. For example, use this:

$("#pre")

and not this, which is ambiguous:

$("pre")

Doing that will solve any problems straight away.

Prototype Short-hand

If you want to continuing using the Prototype short-hand, you must keep one rule in mind: Never name any of your IDs the same as a DOM Element type, otherwise you will have strange results. For example:

$("pre")

would work, if there were no pre elements in the page, but once one was added, your code would break. A better example is:

$("body")

which will always break (since the body element is required).

In a nutshell: Either use smart un-ambiguous IDs, or don’t name your IDs the same as element names.

See http://jquery.com/docs/PrototypeAndJQuery/