Hi Mark, First let me say that your request might be better suited for the jquery-dev list.
As the author of hoverFlow I'm not quite sure if and how hoverFlow should be included in core. I think that hoverFlow doesn't solve a general problem with animations, it solves a special issue that arises from the combination of animation and mouse interaction (hovering). I think we have to wait and see how frequent this problem comes up in order to qualify it for core. > like for example that you can say to the animate > function to run once and not build up the queue? It's not about running once, it's about running under certain conditions. And these conditions are tied to the mouse events (that is why hoverFlow requires you to pass in the event type as its first argument). Currently I can't see how this could be best reflected in the jQuery API (maybe adding the event type to the animation options hash). I see that people don't really want to add another plugin to their stack just to solve this litte problem. Many suggestions to overcome animations buildup can be found on http://www.learningjquery.com/2009/01/quick-tip-prevent-animation-queue-buildup (the post that inspired me to build the plugin). In many situations, variations of the stop()-method work quite well. For submenu navigations, the solution presented at the bottom of http://www.2meter3.de/code/hoverFlow/submenus.html is suitable. However, most solutions fail with long animation durations. Ralf
