remove prototype dependency from path.js
Frank
I was trying to use path.js in a project together with extjs and run
in some problems. Thus I removed the dependency to prototype.js as it
mainly is only used to create classes. In my opinion it would be great
to remove the dependency in trunk as the library can be easier used
together with other libs. What do you think? If you are interested I
can post my code.
Thank you,
Frank
Ryan Schmidt
Hallo Frank. I've thought of bringing up this topic myself before, but
since nobody complained, I left it as is. I do enjoy the convenience
of Prototype but realize using it in a library makes it difficult to
use that library with another framework, so I am open to the
possibility of removing that dependency. This applies to Canviz as
well as Path, though Canviz makes use of many more Prototype features
than Path. I haven't yet looked into what it would take to remove
Prototype from Path, so if you already have the changes made and could
post them here, that would be great. Submitting your changes as a
unified diff against the latest version of path.js would make them
easiest for me to evaluate.
I'm also glad to hear from you because you're the first to mention
using Path, I presume separately from Canviz. Path was made to be used
separately, but was grown out of Canviz's needs. I'd be interested to
hear your feedback on using it as a separate library, and if you have
a URL of your project to share, I'd love to see it.