Karl, I¹ve been really excited to see the progression of this plugin. It¹s looking really great and there has been a lot of wonderful feedback. I think it¹s one of the best documented plugins I¹ve seen. I don¹t see a ³remaining issues² list. How far are we from going 1.0? Can¹t wait :-)
Thanks much, Shelane On 8/23/07 9:49 PM, "Karl Swedberg" <[EMAIL PROTECTED]> wrote: > On Aug 22, 2007, at 11:01 PM, Mitchell Waite wrote: >> Now I am sure j Tip is faster, but faster might not be the right word. Its >> like this. The very first time I hover over your cluetip I can actually see >> the divs and such being assembled. jTip doesn't have that flaw, it comes up >> whole. > Okay, I'm just not seeing this, so I'll have to take your word for it. I also > wasn't able to reproduce the other bug that you reported when I ran it in IE7 > and went to another window and back. But I'll keep my eyes open for it. > > I've packaged up the plugin again with the changes Rey suggested (making > .show() the default for opening the cluetip). I set the first two jTip-themed > examples in the demo to hoverIntent: false so you can see if it's responsive > enough for you. Also, feel free to compare it to Cody's plugin on my server (I > really hope you were comparing the plugins while they were running on the same > server. Otherwise, as I mentioned before, the speed comparisons were probably > worthless). > > Download the plugin (or don't): > http://jquery.com/plugins/project/cluetip/ > > Compare > clueTip: http://jqueryjs.kswedberg/plugins/cluetip/demo/ > jtip: http://plugins.learningjquery.com/jtip/ > > By the way, I do see that the Cody's plugin shows the jTip's "frame" while > it's still loading the the contents that are being ajaxed in while the clueTip > waits until everything is loaded in before showing anything.. The jTip plugin > can only do this because it doesn't account for the content being cut off at > the bottom of the viewable area or where to put it vertically if the jTip is > taller than the window height. As I mentioned (repeatedly) before, the clueTip > makes many more positioning adjustments depending on its width, height, and > position within the viewable area and the linked element's width: > > # switches from the right side of the link to the left side, if there is not > enough room between the link and the right edge of the browser window > # moves up until the whole clueTip is visible, if the link is too close to the > bottom edge of the browser window. > # moves back down until the clueTip's top is at the top edge of the browser > window, if the clueTip is taller than the window (the viewable area) > # sits to the right or left of the mouse position, if the link is a > block-level element or if the link is so wide that the clueTip can't > completely fit to the left or the right of it. > # drops below the mouse position, if the clueTip itself can't fit to the right > or left of the mouse position. Moves above the mouse position only if (a) > there isn't enough room below without being cut off, and (b) there is enough > room between the top of the viewable area and the mouse. Whether above or > below, it is centered horizontally, relative to the mouse position, unless the > centering would cut part of it off, in which case it adjusts to stay in the > viewable area. > > By contrast, this is what the jTip (Cody's version) does for positioning: >> # the tool tip will flip horizontally depending upon the space between the >> tool tip and the right side of the window. > > This is not at all to disparage Cody's plugin. It's a fine plugin -- it's very > lightweight and it does the job it sets out to do. > > If none of the extra positioning is important to you, and if you don't need > any of the other clueTip features such as the ability to load content from the > same page or from the title attribute, or to show or hide with other effects, > or to remain visible until you close it, or to easily change the position and > text of the "close" link, etc., then definitely go with the jTip. > > --Karl > > > >
