Paper JS is a new way to write HTML entirely in your JavaScript.
raphael.js vs paper.js
Paper JS is a new way to write HTML entirely in your JavaScript.
I build my WebSite with Paper.js and D3.js, what you think about it?
Hey, looks really awesome! I've been aching to break into d3, how hard do you think it is to get started with it? The only criticism I'd have with the site itself would be the timeline background. I found it a bit straining on my eyes (but maybe that's just me).
In terms of English corrections:
-
"Softwares" in the navigation should be "Software"
-
"Spend" should be "Spent" on your timeline (2014). This paragraph could also read a bit better, maybe: "I spent almost a week building this website. I made it with love and JS. Thanks to the latest HTML standards I got the possibility to simply draw my decorations with lines of code, and without using any raster images."
-
On the second page of your timeline (2013 - 2014) it could read something like this: "I like to share even if it is not always easy. I don't just want to keep my swish-kniff tool for myself, so I build up some repositories with different projects:"
There are some more English mistakes in the other timeline items but I don't have enough time to go through. All in all it's legible and there are only some very minor mistakes.
Good job over all!
More on reddit.comVideos
Introducing Paper JS a new way to write and structure html entirely inside your JavaScript. Also leaving a small footprint on your website as the library comes in at only 800 bytes in size.
check out the GitHub to get started, also a star would be awesome, if you find an error or questions DM me.
Raphael uses SVG. Paper use Canvas.
That's the major difference.
In terms of what you can do with them, Canvas and SVG each have their own place, and are good for different things (although they are both capable of doing each other's thing as well if you ask them to). From a purely functional point of view, you need to consider what you want to do with the library before you decide which one you go with.
Browser compatibility is going to be a big issue, whichever one you use. This will possibly be a bigger issue than functionality, in fact.
Raphael has an advantage on the desktop because it detects older versions of IE (as far back as IE6) and falls back to using VML instead of SVG. This means it has excellent compatibility on virtualyl all desktop browsers. Canvas simply isn't supported on older IEs, and the Paper.js people don't really seem too worried about it.
But on mobiles, Paper.js may be better, because Canvas has much better support on mobiles than SVG. SVG isn't supported on most Android devices at all. This is changing: Android 3.0 introduced SVG support, but most Android devices being sold even now come with v2.x, so it'll be a while before you can rely on SVG working on a mobile.
For more info about browser support, see the CanIUse site:
- CanIUse SVG
- CanIUse Canvas
Hope that helps.
The most obvious difference is that Raphael targets SVG, and Paper targets the Canvas element. It also appears that Paper has far greater advanced features, whereas Raphael is just core SVG elements, which can then be expanded upon with plugins. Arguably, it depends more on your need, and which environments you wish to target. Canvas works well on some mobile browsers, SVG barely works on mobile environments at all.
As another side note: SVG, as I'm aware of it, is not hardware-accelerated in IE (9) or Firefox, and, again if my memory isn't failing me, Canvas is, at least in IE (9). As for IE 8 and below, you need a browser plugin, which most have, but it is a dependency to expect.
Introducing Paper JS a new way to write and structure html entirely inside your JavaScript. Also leaving a small footprint on your website as the library comes in at only 800 bytes in size.
check out the GitHub to get started, also a star would be awesome, if you find an error or questions DM me.
EDIT:
I really appreciate everyone's feedback to project, as it's definitely not perfect but was mostly created as a prototype or demo, of a custom js to html system. My next plan is to allow support with nodejs on the backend so you can build webpages on the serverside.