Attached is a patch that I think would be useful. It allows for the
following code:
blah blah
Here's the text of the tooltip
click here!
Here's another tooltip text.
$('.MyTooltips').cluetip({ autoid: true, local: true });
To me, it seems to make sense, as long as you are willing to name
As I somehow posted in another thread, sometimes the other attributes are
already in use. In this case, the href is already pointing to content, I
can't use it for the help text.
I posted a little bit of code in the other thread, I may work on
embellishing it a bit.
On Fri, Jul 4, 2008 at 10:33
Sure, feel free to ask for feature enhancements here.
Forgive me if you're already aware of this, but I thought I'd point
out that you do not need to use the rel attribute to grab the content.
You can use whatever attribute you'd like. In fact, if you're pointing
to local content, it would
Yes, I think I can, now that I can use the local element concept. I was
afraid before that I'd have to have a $('something').cluetip("dynamic") line
for every row - and since that data is dynamic, I couldn't reference another
file.
Is this the proper place to ask for feature enhancements for clue
David,
Is there any way that you can just reference a separate file with your
script in it? That's the preferred way. You can then put src="yourfilename.js"> in the head of your document. Then in
yourfilename.js, you put the cluetip line inside a document ready:
$(document).ready(funct
Oh son of a .
My entire layout has a table (I know, I know) and so I had to move the
script call to the footer file. At least I can now stick the tooltip text
in a span that gets hidden and avoid looping again.
On Fri, Jul 4, 2008 at 7:01 PM, David Morton <[EMAIL PROTECTED]> wrote:
> wait,
wait, that still doesn't quite explain it all...
The other way I tried it was to have a span right after the link that
contain the tooltip text, with a class matching the rel link in the anchor.
Then I called the script to load local after the table, after the form
actually.
On Fri, Jul 4, 2008 a
erg. The data is available in a loop while in the table... I'll have to
loop again to output the javascript. Drat that IE stuff.
I'll give it a shot. Maybe I can capture the javascript string in variable
as I loop and then output it later.
I have tried to get rid of the tables altogether, but
Hi David,
Seems that IE does not like the script being executed from within a
table cell. If you move the scripts out of the body and put them in
the or in a separate file (and make sure you're calling cluetip
from within a document ready), it should work. I had to clear my cache
before
Well, I wondered about that, there are some funny characters, so I changed
it. Now the text being loaded is just one word. Still errors out.
On Fri, Jul 4, 2008 at 10:42 AM, Karl Swedberg <[EMAIL PROTECTED]>
wrote:
>
> Hi,
>
> I can't tell from the information what is causing the problem, but i
I even changed it to just have the tip in the call:
two
$("#link_529806").cluetip("two");
three
$("#link_550060").cluetip("three");
And that crashes.
>
> On Fri, Jul 4, 2008 at 10:42 AM, Karl Swedberg <[EMAIL PROTECTED]>
> wrote:
>
>>
>> Hi,
>>
>> I can't tell from the information what is c
Hi,
I can't tell from the information what is causing the problem, but if
I had to guess, I'd suggest looking at the content that is being
loaded. I've seen problems before when invalid markup, usually caused
by unclosed tags, is inserted into the cluetip. Not sure if this is
the problem
12 matches
Mail list logo
