On Aug 19, 11:52 pm, Mitch <[EMAIL PROTECTED]> wrote:
> I will look into ClueTip. I like the way this coder set things up but
> he did not do a good job laying out how to use it, and compared to
> other plugin specialists here, he did not set up the plugin for
> automatic use, I had to play with before I saw how it really worked.
> Maybe ClueTip did a better job of documentation, because for me that
> is as important as the plugin itself.
jTip is small and sweet, but I quickly ran into ergnomic issues in our
frame mode mail system layout where the top left frame has the message
listing and upon user request, they want these stupid previews when
hovering over a message link. Well, the preview box would be cut off
for links near the bottom of the frame, and we envision fasinated
users will swoop the mouse over the links to popup the previews. This
would hit the server uselessly. So I looked to changed jTip to add
smarter placement of the view and to add a delay to tthe popup. But
before I did that I (I hate changing other people's code and I had
downloaded the jTip zip that included jQuery but I didn't really know
of jQuery)), I wrote to the author about it (no response) and searched
to find outer "balloon tip" libraries. That is when I found ClueTip
and jQuery as well. That was two weeks ago and I'm having a ball with
this stuff. :-)
ClueTip covered the two features I wanted very nicely and then some.
I agree, docs is important. I don't recall but I hink I used the
example/demo source to see how it works.
> Oh and I am still curious how people deal with battling CSS. Firebug?
Not sure what you mean? Battling how?
Honestly, I found Firebug about 3 weeks ago and jQuery about 2 weeks
ago. :-) FireBug is basic debugger with traditional debugger ideas so
its quick to learn and use (for me). jQuery is an oddity :-) I
like the "jQuery Theory" but on the other hand the more I use it with
other people plugins is raising a concern. Something I put to the
side for the moment, but I am seeing more than usual cross-browser
issues. i.e, what might work great under FF doesn't under IE.
Anyway, thats a different matter. :-)
---
HLS