Free opensource tooltip class.
Opentip is a free opensource Java-Script tooltip class.
As of Version 2.0 Opentip does no longer depend on Prototype. You can choose any adapter you want so you can work with the framework of your choice.
Supported frameworks are:
The easiest and recommended way to install opentip is with ender:
$ ender build opentip
If you don't use ender, just download
and include them in this order.
You should include opentip's CSS as well. It's in
With HTML data attributes:
$'elementId'opentip'Content' showOn: "click" options ;
For the complete documentation please visit www.opentip.org.
Become library independant. I'm currently working on extracting all prototype functionality, so I can switch library easily. The next library I'll support will be jquery, and then mootools.
Add more skins.
Add cooler loading animation.
Implement unit tests.
If you have ideas, please contact me!
The latest stable version is always in the master branch (which always points at the latest version tag).
The latest development version is in the develop branch.
Use the develop branch if you want to contribute or test features.
Please do also send pull requests to the
To start the test environment install node first if you haven't done so already.
Then go into the
test/ directory and install all dependencies. (You only have
to do this the first time):
$ cd test/$ npm install
And you're ready to launch the server:
Now simply visit
http://localhost:3000 in your browser to see the tests.
It should look like this:
All tests are located in
assets/js/tests/ and are written in coffeescript but
compiled on the fly.
If you add a change, please make sure that all tests pass!
To compile and bundle the library use
Just type the command without any arguments
$ cake in the source directory to list all commands available.
To compile all source files:
$ cd path/to/opentip-source$ cake build
You don't have to do this if you simply want me to merge a change. The test webserver compiles on the fly, and I only build and bundle the files before I release a new version.
Those are the major changes you should look out for when migrating from 1.x to 2.x:
Tips object anymore. Everything is done through
The recommend way to create opentips now is to call
new Opentip(element, content, title, options), or with the framework of
your choice (eg, ender:
$("#my-div").opentip(content, title options))
The instantiation of new tips inside an event (eg:
is no longer supported! This would create new opentips everytime the event
Opentip.debugging = true; does no longer exist. Use
Opentip.debug = true;
Positions are no longer of the weird form
[ "left", "top" ] but simply
"top left" or
stem.size has been dropped in favor of
Most of the design is now done in JS since the whole thing is a canvas now.
The way close buttons are defined has completely changed. Please refer to the docs for more information.
Tagging in this project is done with my tag script.
Opentip is written by Matias Meno.
Website design by Tjandra Mayerhold.
Thanks to the following people for providing bug reports, feature requests and fixes:
If I forgot somebody, please just tell me.
(The MIT License)
Copyright (c) 2012 Matias Meno <email@example.com>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.