can't get it to work

[heaversm]

trafficstars

Is this code still valid? How do I import it? Your sample code doesn't work, and when I attempt to import the class I get an error about using a reserved word. Do you have any code I can download from an html level so I can see how the class is imported and used?

[michael]

I pretty sure this is no longer compatible with the latest processing.js release. You should probably look into Tween.js, which is actively maintained:

https://github.com/sole/tween.js

[heaversm]

Thanks - yeah - I'm actually trying to update your donut code to the latest processing release, but I've noticed a problem here, around 297 -

public setSelectedSlice(DonutSlice s) { ... }

For some reason by simply updating processing to the latest release and referencing your code, it no longer allows this function. Do you have any idea why that might be? I love this visualization and it would work perfectly for a project I'm building.

On Tue, Nov 1, 2011 at 7:07 AM, Michael Aufreiter < [email protected]>wrote:

I pretty sure this is no longer compatible with the latest processing.js release. You should probably look into Tween.js, which is actively maintained:

https://github.com/sole/tween.js

Reply to this email directly or view it on GitHub: https://github.com/michael/tween/issues/2#issuecomment-2589021

Mike Heavers 917-345-6634 AIM: mikeheavers

[michael]

Sorry, I'm afraid I can't help here, as I didn't keep up with the latest processing.js versions. :(

If you want to use the Donut, without too much adaption and debugging work, you should stick with the old processing.js version included in the Donut repo.

P.S.: What you could also do, if you got time, is to port the donut code to D3.js to get a lasting solution. :)

[heaversm]

Thanks for the idea! I had actually started down that road with raphael.js

• but it's good to know about D3. Just out of curiosity, why would you say that's a more lasting solution than processing.js?

On Wed, Nov 2, 2011 at 5:07 AM, Michael Aufreiter < [email protected]>wrote:

Sorry, I'm afraid I can't help here, as I didn't keep up with the latest processing.js versions. :(

If you want to use the Donut, without too much adaption and debugging work, you should stick with the old processing.js version included in the Donut repo.

P.S.: What you could also do, if you got time, is to port the donut code to D3.js to get a lasting solution. :)

Reply to this email directly or view it on GitHub: https://github.com/michael/tween/issues/2#issuecomment-2601037

Mike Heavers 917-345-6634 AIM: mikeheavers

[michael]

With Processing there's an intermediate code compilation step, since Processing code is written in Java syntax. I mean this makes a lot of sense if your're porting existing processing code to the web or if you want to target both, web and desktop platforms. However if your visualization is dedicated to the web and you start from scratch, a native javascript library is probably a better idea (more lightweight, closer to the metal => easier to debug etc.)

D3.js is my personal favorite, it operates directly on the DOM (much like in the fashion of jQuery) and you can use CSS-transitions etc.

If you prefer the Canvas API for rendering, Paper.js could be an option.

Cheers,

Michael