Why don't you allow an Elements instance as input? about floatingtips

[lorenzos]

Can't do it because when I have a string like:

new FloatingTips('myLink');

I have to choose to use it as selector or as element id. I cannot magically understood if a string is an element id or an elements selector :)

If you cannot live without new FloatingTips('myLink'), try to add this at the end of my plugin code:

var RolfFloatingTips = new Class({
    Extends: FloatingTips,
    initialize: function(element, options) {
        if (typeof(element) == 'string') {
            this.parent('#' + element, options); // Call parent class
        } else {
            this.parent(element, options); // Call parent class
        }
    }
});

And then use:

new RolfFloatingTips('top');

[rolfnl]

Quick reply, nice..
I understand I can extend it to fit my own needs, I actually have that on the to-do for tomorrow :)

But I would suggest making it the default.
You could do something like:

elements = Array.from(document.id(elements) || $$(elements));

And work with that.. Slick will be able to parse a string selector with the $$(elements), so it would work if you throw in whatever really. (have to test to make sure of course).

or with document.getElements(selector) as the Slick demo does here: http://mootools.net/demos/?demo=Slick.Finder
Again, throw in whatever you want (string or element)..it'll just work and is more flexible. (correct me if I'm mistaken!)

[lorenzos]

I will try. If I'm not wrong, you say to give the string input to document.id, and then if it returns an Element, use it, else use the string as selector as before. Correct?

[lorenzos]

Closed because not applicable without changing constructor behavior.
If needed, extend the class as I suggested or edit sources.