Seedre / flotr

Automatically exported from code.google.com/p/flotr
0 stars 0 forks source link

Library Agnosticism #178

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Has anyone had thoughts about completely removing any library dependency from 
flotr?

Any ballpark for how difficult this would be?

I've seen several APIs used - Class, Event, Array, and selectors.  What else?

Advantages would include:

* Smaller footprint for mobile platforms.
* Larger accessibility to other frameworks, communities (YUI, jQuery etc.)
* Single trunk (no more MooTools and Prototype).
* Might be more straight forward to add touch events.

What are disadvantages?

Original issue reported on code.google.com by cesuther...@gmail.com on 3 Apr 2011 at 10:53

GoogleCodeExporter commented 8 years ago
<< I posted this.

Original comment by carl%hum...@gtempaccount.com on 3 Apr 2011 at 10:55

GoogleCodeExporter commented 8 years ago
I already tried to do this, with a Flotr microframework with all the basic 
functions, and I also made Prototype and Mootools adapters, in order to take 
advantages of these libs. I even think I still have it in a local copy, but 
I'll have to work back on it to adapt it to the last commits.

Original comment by fabien.menager on 4 Apr 2011 at 6:05

GoogleCodeExporter commented 8 years ago
Was the work completed or only partial?  Any particular problems you 
encountered?

Maybe a branch could be created for it.

Original comment by cesuther...@gmail.com on 13 Apr 2011 at 3:47

GoogleCodeExporter commented 8 years ago
It was partial, but I would need to review all that I did as all is messed up 
with SVN conflicts :(

Original comment by fabien.menager on 13 Apr 2011 at 7:03