Re:Raphaël 2.0 is available
by jacobolus on Saturday October 01, 2011 @06:50PM
(#3061372)
I think Raphaël is a nice idea: it’s great for people who want their stuff to be compatible with old versions of internet explorer, and it makes it very easy to build trivial things.
To be honest though, I found that in trying to build anything more complex or with much user interaction, just working directly with SVG APIs and building up my own abstractions as necessary was easier and much more flexible. People shouldn’t be afraid to learn SVG: it’s pretty easy!
For anything driven by data, I recommend looking at D3, which is designed around some very powerful ideas.
Re:Raphaël 2.0 is available
by cubicle67 on Saturday October 01, 2011 @07:45PM
(#3061492)
We started on a new project Friday and decided to go with Raphael. I'm amazed at what it can do - awesome stuff. Why on earth would you decide to write your own cross browser (vml + svg) library when it's already been done and the result is already very good?
Re:Raphaël 2.0 is available
by jacobolus on Saturday October 01, 2011 @07:15PM
(#3061432)
Different projects obviously have different needs. I’m just pointing out that much of what I’ve heard people say about Raphaël is along the lines of “it’s nicer to use than raw SVG”, and providing a contrary data point.
Often, when trying to figure out what technology stack to use, developers look around at what seems to have chatter and hype. I think that in some cases they’d be better served by just learning the lower-level API, which isn’t too hard.
Re:Raphaël 2.0 is available
by pacomerh on Sunday October 02, 2011 @12:21AM
(#3062059)
Yeah, I like this library but SVG is still an issue on Android 2.3. Besides that it's great. I see video game companies using this to create Dashboards with stats for online gamers.
Re:Raphaël 2.0 is available
by exit on Sunday October 02, 2011 @08:04AM
(#3062643)
what puts me off raphael 1.0 is the lack of grouped transformations. you can collect elements into sets and perform operations on those, but that doesn't not give you a hierarchical transformation space.
i could be wrong but from a cursory glance it seems this is still the case with raphael 2.0.
To be honest though, I found that in trying to build anything more complex or with much user interaction, just working directly with SVG APIs and building up my own abstractions as necessary was easier and much more flexible. People shouldn’t be afraid to learn SVG: it’s pretty easy!
For anything driven by data, I recommend looking at D3, which is designed around some very powerful ideas.
Often, when trying to figure out what technology stack to use, developers look around at what seems to have chatter and hype. I think that in some cases they’d be better served by just learning the lower-level API, which isn’t too hard.
The UI of this slide deck is highly frustrating.
http://raphaeljs.com/reference.html
i could be wrong but from a cursory glance it seems this is still the case with raphael 2.0.