[jQuery] Re: [ANNOUNCE]: clueTip Plugin Beta
Karl Swedberg wrote: Optimize ajax loading to avoid multiple requests for the same clueTip content. Done! That is something Mike Hosteler is or may be working on. At least a bit discussion/specification can be found here: http://docs.jquery.com/AjaxQueue Caching is mentioned there yet, but should be a good addition to the plugin. -- Jörn Zaefferer http://bassistance.de
[jQuery] Re: [ANNOUNCE]: clueTip Plugin Beta
Stephan Beal wrote: On Jul 13, 8:08 pm, Jörn Zaefferer [EMAIL PROTECTED] wrote: About sticky tooltips: I'd find it much handier to be able to click anywhere outside the tooltip to close it, instead of a tiny close link. I'd even consider replacing the close-link alltogether: The user then i disagree. Normal tooltips can be dismissed this way, but stickies should have their own close button. That makes them usable as a sort of popup dialog replacement for some contexts. Sure, but that is still the case with a click-out-side-to-close mechanism. Clicking somewhere else is so much more easier then clicking-that-little-button-over-there. The functionality would be the same. -- Jörn Zaefferer http://bassistance.de
[jQuery] Re: [ANNOUNCE]: clueTip Plugin Beta
One cool thing is that the tooltip is being positioned out of the position of the hovered element rather than attached to the mouse cursor position. That is a sooo much more cleaner result IMO. Karl Swedberg wrote: Hey everyone, Just thought I'd let you all know that I (finally) posted a blog entry announcing the official beta version of the clueTip plugin: http://www.learningjquery.com/2007/07/cluetip-plugin-beta I'd love to hear what you think. Here's a snippet from the entry: The new clueTip plugin allows you to easily set a link, or any other element, to show a tooltip when the user's mouse hovers over it. If the link includes a title attribute, its text becomes the heading of the clueTip. The contents of the clueTip can come from a separate file via AJAX, an element on the current page when set to local, or the title attribute with a designated delimiter. The clueTip offers smart positioning and takes advantage of Brian Cherne's fantastic hoverIntent plugin if it's available. (Just include it in a script tag if you want the clueTip to use it.) It comes with many options, all of which are documented in the source comments and on the demo page. thanks, --Karl _ Karl Swedberg www.englishrules.com www.learningjquery.com
[jQuery] Re: [ANNOUNCE]: clueTip Plugin Beta
Olivier Percebois-Garve wrote: One cool thing is that the tooltip is being positioned out of the position of the hovered element rather than attached to the mouse cursor position. That is a sooo much more cleaner result IMO. Yep, that is really cool. About sticky tooltips: I'd find it much handier to be able to click anywhere outside the tooltip to close it, instead of a tiny close link. I'd even consider replacing the close-link alltogether: The user then has to find out how to close it, which could be ugly, but most likely he will try to click either the tooltip or outside of out, therefore very quickly learning how to close it. That may be worth to avoid that he ever bothers with the close-link when he doesn't have to. For hoverIntent integration: You could pass through defaults.hoverIntent when calling it. That'd force you to seperate the call to hover and hoverIntent, but may be worth it. I hope the pngfix plugin is ready soon enough, currently its undo method is broken for background-images. Funny to see that jquery.cluetip.js is exactly one line less then the latest jquery.tooltip.js :-) -- Jörn Zaefferer http://bassistance.de
[jQuery] Re: [ANNOUNCE]: clueTip Plugin Beta
Jörn and Olivier, Thanks so much for the feedback! One cool thing is that the tooltip is being positioned out of the position of the hovered element rather than attached to the mouse cursor position. That is a sooo much more cleaner result IMO. Olivier, glad you like the positioning. I spent a lot of time trying to figure out where to put the clueTip, and there are still a couple edge cases that I think I could refine a bit. Actually, it does get positioned relative to the mouse position as a fallback -- if the clueTip is attached to a block-level element or to an element so wide that the clueTip wouldn't be able to fit either to the right or to the left of it. About sticky tooltips: I'd find it much handier to be able to click anywhere outside the tooltip to close it, instead of a tiny close link. I definitely see your point there. I'll add that to the to-do list. I'd even consider replacing the close-link alltogether: The user then has to find out how to close it, which could be ugly, but most likely he will try to click either the tooltip or outside of out, therefore very quickly learning how to close it. That may be worth to avoid that he ever bothers with the close-link when he doesn't have to. Not sure I'd want to get rid of the Close link altogether, but I'll give it some thought. For hoverIntent integration: You could pass through defaults.hoverIntent when calling it. That'd force you to seperate the call to hover and hoverIntent, but may be worth it. I thought that's what I was doing, but I'm probably misunderstanding what you're saying. If you don't mind elaborating on this one, I'd love to hear it. I hope the pngfix plugin is ready soon enough, currently its undo method is broken for background-images. me too! for now, though, I think the png fix that I've implemented (taken and stripped down from your excellent tooltips plugin) works well enough. Funny to see that jquery.cluetip.js is exactly one line less then the latest jquery.tooltip.js :-) Cool! Speaking of lines/file size -- I wrote tons of inline documentation, so I hope the uncompressed file size (13.5kb) doesn't scary people off. If you strip out all the comments, it gets quite small (4.9kb) and packing it with Dean Edwards's Packer makes it smaller still (3.3kb). (Man, i've got to learn how to use that automated Ant stuff!) --Karl _ Karl Swedberg www.englishrules.com www.learningjquery.com On Jul 13, 2007, at 2:08 PM, Jörn Zaefferer wrote: Olivier Percebois-Garve wrote: One cool thing is that the tooltip is being positioned out of the position of the hovered element rather than attached to the mouse cursor position. That is a sooo much more cleaner result IMO. Yep, that is really cool. -- Jörn Zaefferer http://bassistance.de
[jQuery] Re: [ANNOUNCE]: clueTip Plugin Beta
Karl Swedberg wrote:
For hoverIntent integration: You could pass through
defaults.hoverIntent when calling it. That'd force you to seperate
the call to hover and hoverIntent, but may be worth it.
I thought that's what I was doing, but I'm probably misunderstanding
what you're saying. If you don't mind elaborating on this one, I'd
love to hear it.
From what I saw in your source code, there is no way for me to
customize the hoverIntent behaviour without modifying your source. You
can fix that by just passing through options I specify for your plugin
to hoverIntent, though it would be a good idea to pass them in their own
object:
$(...).cluetip({
hoverIntent: {
delay: 50,
...
},
...
});
Speaking of lines/file size -- I wrote tons of inline documentation,
so I hope the uncompressed file size (13.5kb) doesn't scary people
off. If you strip out all the comments, it gets quite small (4.9kb)
and packing it with Dean Edwards's Packer makes it smaller still
(3.3kb). (Man, i've got to learn how to use that automated Ant stuff!)
Try to add this to build.xml:
target name=cluetip description=Build cluetip plugin.
antcall target=generic
param name=name value=cluetip /
/antcall
/target
--
Jörn Zaefferer
http://bassistance.de
[jQuery] Re: [ANNOUNCE]: clueTip Plugin Beta
beautiful! thanks for the tips!
--Karl
_
Karl Swedberg
www.englishrules.com
www.learningjquery.com
On Jul 13, 2007, at 3:22 PM, Jörn Zaefferer wrote:
Karl Swedberg wrote:
For hoverIntent integration: You could pass through
defaults.hoverIntent when calling it. That'd force you to
seperate the call to hover and hoverIntent, but may be worth it.
I thought that's what I was doing, but I'm probably
misunderstanding what you're saying. If you don't mind elaborating
on this one, I'd love to hear it.
From what I saw in your source code, there is no way for me to
customize the hoverIntent behaviour without modifying your source.
You can fix that by just passing through options I specify for your
plugin to hoverIntent, though it would be a good idea to pass them
in their own object:
$(...).cluetip({
hoverIntent: {
delay: 50,
...
},
...
});
Speaking of lines/file size -- I wrote tons of inline
documentation, so I hope the uncompressed file size (13.5kb)
doesn't scary people off. If you strip out all the comments, it
gets quite small (4.9kb) and packing it with Dean Edwards's Packer
makes it smaller still (3.3kb). (Man, i've got to learn how to use
that automated Ant stuff!)
Try to add this to build.xml:
target name=cluetip description=Build cluetip plugin.
antcall target=generic
param name=name value=cluetip /
/antcall
/target
--
Jörn Zaefferer
http://bassistance.de
[jQuery] Re: [ANNOUNCE]: clueTip Plugin Beta
Looking great, Karl!
The examples page #6 shows an error in the firebug console: 503
Service Temporarily Unavailable
So that you show that you have completed your desired features. I
just want to ask if my feature request got canned: to cache results
from ajax results so that the same clue wouldn't have to be requested
from the server multiple times? If so, I guess that's okay since I
expect most of the data to be small.
Can't wait until it becomes a final version!!!
On Jul 13, 12:30 pm, Karl Swedberg [EMAIL PROTECTED] wrote:
beautiful! thanks for the tips!
--Karl
_
Karl Swedbergwww.englishrules.comwww.learningjquery.com
On Jul 13, 2007, at 3:22 PM, Jörn Zaefferer wrote:
Karl Swedberg wrote:
For hoverIntent integration: You could pass through
defaults.hoverIntent when calling it. That'd force you to
seperate the call to hover and hoverIntent, but may be worth it.
I thought that's what I was doing, but I'm probably
misunderstanding what you're saying. If you don't mind elaborating
on this one, I'd love to hear it.
From what I saw in your source code, there is no way for me to
customize the hoverIntent behaviour without modifying your source.
You can fix that by just passing through options I specify for your
plugin to hoverIntent, though it would be a good idea to pass them
in their own object:
$(...).cluetip({
hoverIntent: {
delay: 50,
...
},
...
});
Speaking of lines/file size -- I wrote tons of inline
documentation, so I hope the uncompressed file size (13.5kb)
doesn't scary people off. If you strip out all the comments, it
gets quite small (4.9kb) and packing it with Dean Edwards's Packer
makes it smaller still (3.3kb). (Man, i've got to learn how to use
that automated Ant stuff!)
Try to add this to build.xml:
target name=cluetip description=Build cluetip plugin.
antcall target=generic
param name=name value=cluetip /
/antcall
/target
--
Jörn Zaefferer
http://bassistance.de
[jQuery] Re: [ANNOUNCE]: clueTip Plugin Beta
Hi Shelane,
thanks for the feedback!
I fixed example #6. should work now.
Your feature request didn't get canned. In fact, I noted it in the
Known Issues' section of the demo page:
Optimize ajax loading to avoid multiple requests for the same
clueTip content. Done!
thanks again. Really appreciate you taking a look at it (and giving
me such great feature ideas way back when).
--Karl
_
Karl Swedberg
www.englishrules.com
www.learningjquery.com
On Jul 13, 2007, at 5:25 PM, Shelane wrote:
Looking great, Karl!
The examples page #6 shows an error in the firebug console: 503
Service Temporarily Unavailable
So that you show that you have completed your desired features. I
just want to ask if my feature request got canned: to cache results
from ajax results so that the same clue wouldn't have to be requested
from the server multiple times? If so, I guess that's okay since I
expect most of the data to be small.
Can't wait until it becomes a final version!!!
On Jul 13, 12:30 pm, Karl Swedberg [EMAIL PROTECTED] wrote:
beautiful! thanks for the tips!
--Karl
_
Karl Swedbergwww.englishrules.comwww.learningjquery.com
On Jul 13, 2007, at 3:22 PM, Jörn Zaefferer wrote:
Karl Swedberg wrote:
For hoverIntent integration: You could pass through
defaults.hoverIntent when calling it. That'd force you to
seperate the call to hover and hoverIntent, but may be worth it.
I thought that's what I was doing, but I'm probably
misunderstanding what you're saying. If you don't mind elaborating
on this one, I'd love to hear it.
From what I saw in your source code, there is no way for me to
customize the hoverIntent behaviour without modifying your source.
You can fix that by just passing through options I specify for your
plugin to hoverIntent, though it would be a good idea to pass them
in their own object:
$(...).cluetip({
hoverIntent: {
delay: 50,
...
},
...
});
Speaking of lines/file size -- I wrote tons of inline
documentation, so I hope the uncompressed file size (13.5kb)
doesn't scary people off. If you strip out all the comments, it
gets quite small (4.9kb) and packing it with Dean Edwards's Packer
makes it smaller still (3.3kb). (Man, i've got to learn how to use
that automated Ant stuff!)
Try to add this to build.xml:
target name=cluetip description=Build cluetip plugin.
antcall target=generic
param name=name value=cluetip /
/antcall
/target
--
Jörn Zaefferer
http://bassistance.de
[jQuery] Re: [ANNOUNCE]: clueTip Plugin Beta
On Jul 13, 8:08 pm, Jörn Zaefferer [EMAIL PROTECTED] wrote: About sticky tooltips: I'd find it much handier to be able to click anywhere outside the tooltip to close it, instead of a tiny close link. I'd even consider replacing the close-link alltogether: The user then i disagree. Normal tooltips can be dismissed this way, but stickies should have their own close button. That makes them usable as a sort of popup dialog replacement for some contexts.
