You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -173,7 +173,7 @@ <h2>Getting Started <a href="#">⇑</a></h2>
173
173
174
174
<h3>1. Load jQuery and include Tooltipster's files</h3>
175
175
176
-
<p>After you <ahref="https://github.com/iamceege/tooltipster/archive/master.zip">download Tooltipster</a>, load jQuery and include Tooltipster's CSS and JavaScript files in your page.<br/></p>
176
+
<p>After you <ahref="https://github.com/calebjacob/tooltipster/archive/master.zip">download Tooltipster</a>, load jQuery and include Tooltipster's CSS and JavaScript files in your page.<br/></p>
@@ -184,7 +184,7 @@ <h3>1. Load jQuery and include Tooltipster's files</h3>
184
184
</pre>
185
185
<p>Compatibility note: jQuery 1.7 is enough except if you need SVG support in IE (then use jQuery 1.10+). Tooltipster does not work at all with jQuery 1.8 in IE9.</p>
186
186
187
-
<p>Bonus: available on <ahref="https://github.com/iamceege/tooltipster" target="_blank">GitHub</a> but also on <ahref="https://www.npmjs.com/package/tooltipster" target="_blank">Npm</a>, <ahref="https://libraries.io/bower/tooltipster" target="_blank">Bower</a> and <ahref="https://www.jsdelivr.com/projects/jquery.tooltipster" target="_blank">jsDelivr</a>.<br/>
187
+
<p>Bonus: available on <ahref="https://github.com/calebjacob/tooltipster" target="_blank">GitHub</a> but also on <ahref="https://www.npmjs.com/package/tooltipster" target="_blank">Npm</a>, <ahref="https://libraries.io/bower/tooltipster" target="_blank">Bower</a> and <ahref="https://www.jsdelivr.com/projects/jquery.tooltipster" target="_blank">jsDelivr</a>.<br/>
188
188
Bonus 2: if you need .gz files, running <spanclass="code">grunt compress</span> will gzip all files within the dist folder.</p>
<p>Sometimes, when a plugin adds no options or instance methods, or is auto-activated, you might not have to declare it in the options. Anyway, each plugin will give you its installation instructions.</p>
1449
1449
1450
-
<p>Under the hood, Tooltipster's plugin system is built on our event system. Plugins register to the core and may react to Tooltipster's many events. A guide for plugin creation is available [here](https://github.com/iamceege/tooltipster/blob/master/plugins.md).</p>
1450
+
<p>Under the hood, Tooltipster's plugin system is built on our event system. Plugins register to the core and may react to Tooltipster's many events. A guide for plugin creation is available [here](https://github.com/calebjacob/tooltipster/blob/master/plugins.md).</p>
1451
1451
1452
1452
<p>Let us know if you decide to create and share your own plugin, we will list it here!</p>
<p><ahref="https://github.com/iamceege/tooltipster/issues/538">An Angular directive for Tooltipster</a> by <ahref="https://github.com/campbeln">campbeln</a></p>
1681
+
<p><ahref="https://github.com/calebjacob/tooltipster/issues/538">An Angular directive for Tooltipster</a> by <ahref="https://github.com/campbeln">campbeln</a></p>
1682
1682
1683
-
<p>Did you do something awesome with Tooltipster? <ahref="https://github.com/iamceege/tooltipster/issues" target="_blank">Tell us</a> and we'll post it up here!</p>
1683
+
<p>Did you do something awesome with Tooltipster? <ahref="https://github.com/calebjacob/tooltipster/issues" target="_blank">Tell us</a> and we'll post it up here!</p>
1684
1684
</section>
1685
1685
1686
1686
<sectionid="faq">
@@ -1693,7 +1693,7 @@ <h4>"I need help to implement Tooltipster"</h4>
1693
1693
1694
1694
<h4>"I found a bug, how do I reach you?"</h4>
1695
1695
1696
-
<p>Head on over to Tooltipster's issue tracker on GitHub: <ahref="https://github.com/iamceege/tooltipster/issues">https://github.com/iamceege/tooltipster/issues</a></p>
1696
+
<p>Head on over to Tooltipster's issue tracker on GitHub: <ahref="https://github.com/calebjacob/tooltipster/issues">https://github.com/calebjacob/tooltipster/issues</a></p>
1697
1697
1698
1698
<p>Before opening a new issue, please be sure to search through the backlog to see if your bug has already been submitted. Thank you! :)</p>
1699
1699
@@ -1718,8 +1718,8 @@ <h4 id="faq_positioningissue">"The position of the tooltip is consistently incor
1718
1718
<ul>
1719
1719
<li>Make sure the cache is not disabled, either client-side (browser settings) or server-side (cache headers). Read above for explanations.</li>
1720
1720
<li>Generally speaking, if enabling the <spanclass="code">trackTooltip</span> option solves it, it's your tooltip content that changes size after opening.</li>
1721
-
<li>Are you sure the position is actually incorrect? Read <ahref="https://github.com/iamceege/tooltipster/issues/673" target="_blank">this issue</a>.</li>
1722
-
<li>Is <spanclass="code">position: relative</span> set on the body? You probably shouldn't do that. Please read <ahref="https://github.com/iamceege/tooltipster/issues/514" target="_blank">this issue</a> for instructions.</li>
1721
+
<li>Are you sure the position is actually incorrect? Read <ahref="https://github.com/calebjacob/tooltipster/issues/673" target="_blank">this issue</a>.</li>
1722
+
<li>Is <spanclass="code">position: relative</span> set on the body? You probably shouldn't do that. Please read <ahref="https://github.com/calebjacob/tooltipster/issues/514" target="_blank">this issue</a> for instructions.</li>
1723
1723
</ul>
1724
1724
1725
1725
<p>If the error still occurs, please open an issue on GitHub.</p>
@@ -1751,7 +1751,7 @@ <h4>"How compatible is Tooltipster with old versions of Internet Explorer ?"</h4
1751
1751
</section>
1752
1752
1753
1753
<footer>
1754
-
Tooltipster, the <ahref="http://iamceege.github.io/tooltipster/" class="white">javascript tooltip</a> library.<br/>
1754
+
Tooltipster, the <ahref="http://calebjacob.github.io/tooltipster/" class="white">javascript tooltip</a> library.<br/>
1755
1755
Developed and maintained by <ahref="https://plus.google.com/116532683962309427991?rel=author" class="white">Caleb Jacob</a> and <ahref="https://github.com/louisameline" class="white">Louis Ameline</a> under the <ahref="http://opensource.org/licenses/MIT" class="white">MIT license</a>
Copy file name to clipboardExpand all lines: plugins.md
+6-6
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ Now let's start over with explanations.
43
43
44
44
## <aname="naming"></a>1. Find a name for your plugin
45
45
46
-
The plugin name must be namespaced in order to resolve conflicts in case somebody writes another plugin of the same name. Use your initials or something random. Preventing conflicts is explained in the [Plugins](http://iamceege.github.io/tooltipster/#plugins) section of the documentation.
46
+
The plugin name must be namespaced in order to resolve conflicts in case somebody writes another plugin of the same name. Use your initials or something random. Preventing conflicts is explained in the [Plugins](http://calebjacob.github.io/tooltipster/#plugins) section of the documentation.
47
47
48
48
## <aname="level"></a>2. Determine if you'll work at core or instance level, or both
49
49
@@ -69,11 +69,11 @@ The special private `__destroy` method of your plugin, if it exists, will be cal
69
69
70
70
## <aname="methods"></a>4. Create your public, protected and private methods
71
71
72
-
* Methods that do not start with an underscore are public, which means that the user will be able to call them, just like any of the native methods described in the [Methods](http://iamceege.github.io/tooltipster/#methods) section of the general documentation
72
+
* Methods that do not start with an underscore are public, which means that the user will be able to call them, just like any of the native methods described in the [Methods](http://calebjacob.github.io/tooltipster/#methods) section of the general documentation
73
73
* Methods that start with a single underscore are protected, which means that the user *should not* call them, but that other plugins may. Unless you plan on creating a plugin that can interact with others, you should not use them
74
74
* Methods that start with a double underscore are private. The user won't be able to call them, and other plugins shouldn't try to
75
75
76
-
If two plugins add public/protected methods of the same name at the same level (core or instance), there will be a conflict. The way to resolve conflicts is described in the [plugins](http://iamceege.github.io/tooltipster/#plugins) section general documentation. There can be no conflicts between private methods.
76
+
If two plugins add public/protected methods of the same name at the same level (core or instance), there will be a conflict. The way to resolve conflicts is described in the [plugins](http://calebjacob.github.io/tooltipster/#plugins) section general documentation. There can be no conflicts between private methods.
77
77
78
78
## <aname="tooltipster"></a>5. Use Tooltipster's protected methods
79
79
@@ -125,7 +125,7 @@ There are also two instance protected properties that you can use: `instance._$t
125
125
126
126
## <aname="events"></a>6. Use Tooltipster's events
127
127
128
-
When something happens in Tooltipster, events get fired on the instance and/or core emitters. Most of the time, that's how you will add features: listening for a type of event and reacting to it. All events are listed in the [Events](http://iamceege.github.io/tooltipster/#events) section of the general documentation. And don't forget to use the protected event methods listed above.
128
+
When something happens in Tooltipster, events get fired on the instance and/or core emitters. Most of the time, that's how you will add features: listening for a type of event and reacting to it. All events are listed in the [Events](http://calebjacob.github.io/tooltipster/#events) section of the general documentation. And don't forget to use the protected event methods listed above.
129
129
130
130
For example, when a tooltip must be opened, Tooltipster's main script does nothing but send a `reposition` event. Then it's `sideTip` who listens to this event and positions the tooltip on a side of the origin, and sends a `repositioned` event when it's done. When `follower` is used instead of `sideTip`, it does more or less the same thing.
131
131
@@ -244,7 +244,7 @@ $('.tooltip').tooltipster({
244
244
});
245
245
```
246
246
247
-
Keep things simple and don't tell them to declare it as `'yourNamespace.yourPlugin'`, even if it would work. If your users run into a conflict with another plugin, tell them to read the [Plugins](http://iamceege.github.io/tooltipster/#plugins) section of the documentation.
247
+
Keep things simple and don't tell them to declare it as `'yourNamespace.yourPlugin'`, even if it would work. If your users run into a conflict with another plugin, tell them to read the [Plugins](http://calebjacob.github.io/tooltipster/#plugins) section of the documentation.
248
248
249
249
## <a name="goodpractices"></a>10. Conventions and good practices
250
250
@@ -432,7 +432,7 @@ If your plugin has instance methods, it will automatically be plugged upon initi
432
432
433
433
Sometimes it's fine because you want your plugin enabled only if the user explicitly asks for it. For example the `follower` plugin should not be enabled on all tooltips, in case the user wants to use `sideTip` on some of them.
434
434
435
-
But sometimes there is no harm in enabling a plugin on all tooltips and save the user the trouble of having to list it in the `plugins` option. That's the case for the [`SVG`](https://github.com/iamceege/tooltipster/blob/master/src/js/plugins/tooltipster/SVG/tooltipster-SVG.js) plugin which improves Tooltipster in case the origin is an SVG element, and does nothing if it's not. To achieve it, we just listen to the core for newly created instances and manually plug ourselves on these instances.
435
+
But sometimes there is no harm in enabling a plugin on all tooltips and save the user the trouble of having to list it in the `plugins` option. That's the case for the [`SVG`](https://github.com/calebjacob/tooltipster/blob/master/src/js/plugins/tooltipster/SVG/tooltipster-SVG.js) plugin which improves Tooltipster in case the origin is an SVG element, and does nothing if it's not. To achieve it, we just listen to the core for newly created instances and manually plug ourselves on these instances.
0 commit comments