KineticJS Project not supported anymore

[steffimueller]

It seem to me that the project is not supported anymore. Is there someone who will continue with this project?

[confile]

I am also thinking that this project might not be supported anymore.

[leohenning]

I'd like to keep using it. Is the community large enough to self support?

[lavrton]

Hello, guys! I was contributing to KineticJS awhile. I made many fixed, but I don't want to tag new version as I am not a maintainer. I was thinking about future developing, but for my project KineticJS is on very good state and improving it is not required. May be I will continue contributing soon, just for experience and practicing.

[zenix]

Ok. Maybe it's time to see other projects..

[confile]

Are the any similar alternative projects? What would you recommend?

[lavrton]

FabricJS and EaselJS are very close to KineticJS. If you are developing game - look at PhaserJS

[confile]

Which one is the best for mobile use?

[lavrton]

As I know all of them have very good support. In my tests EaselJS has very good performance. But it is really depends on type of application, so you should test youself.

[confile]

Does any of them support layers like KineticJS?

[nmehlei]

Are these just rumors or is it official that KineticJS is not supported anymore? Any word from the author?

[jfollas]

Eric took a hiatus due to being burned out. It was consuming all of his spare time to maintain the project. He left it in a pretty stable state, and Anton was great about committing bug fixes after the last official release (caveat: these fixes are in GitHub, but not in an official release).

If I had to guess, Eric will return to the project and make another official version release. But in the meantime, if Kinetic satisfied a need for your project, then there's nothing that will stop you from continuing to use it (or fork it to add your own features or fix bugs that you find, etc).

On Tue, Dec 2, 2014 at 11:24 AM, nmehlei notifications@github.com wrote:

Are these just rumors or is it official that KineticJS is not supported anymore? Any word from the author?

— Reply to this email directly or view it on GitHub https://github.com/ericdrowell/KineticJS/issues/1048#issuecomment-65257863 .

[nmehlei]

Thanks for clearing that up. We use KineticJS quite successfully at the moment, so long-term support (changes due to Browser updates etc.) is quite important to us, but as you said, currently it is very stable.

[confile]

Caching in the current version of KineticJS is a hugh problem. There are many issues that are open. We consider to change the project.

[confile]

@lavrton PhaserJS has the most stars on github is this also good for image manipulation, rotation, layers, filters?

[lavrton]

@confile you can use toImage approach if you have many issues with cache. About Phaser - I guess yes. Go to examples page.

[confile]

@lavrton Would you recommend PhaserJS or PixiJS for my case?

[lavrton]

Phaser JS is based on Pixi. It adds game specific stuff such as camera, physics, sounds, etc. Do you need it? Yes - Phaser JS. No - Pixi. Also one of the main feature of Pixi (Phaser) against Kinetic, Fabric, Easel is that Pixi have awesome build in WebGL support. So if all of your objects on canvas might be represented as picture - you must try it.

[confile]

@lavrton Does PixiJS also has a layer system like KineticJS?

[leohenning]

Seems very stable to me too.

[petersaints]

I would love to see this project continued. I mean... a few months ago I was selecting a good Canvas library for a project and among the biggest contenders were KineticJS, EaselJS and Fabric.js. I ended up choosing KineticJS due to its very good documentation and examples and its sad that is now unmaintained. I mean... the biggest issue that may arise in the future is the lack of browser support. So even if it was only maintenance mode project I'd love to see some sort of support for this awesome library.

If I knew this would happen I would probably have selected EaselJS. I mean Fabric.js is also fine but I think it is not as generic and robust as EaselJS and KineticJS (any opinions for future reference?)

[nmehlei]

Same for me, I decided between all the alternatives and chose KineticJS. As continued support and fast bugfixes (like KineticJS needed in the past due to Chrome bugs, if I remember correctly) are critical for us, we don't really have a choice than to plan migrating to a different library in the mid- or long-term.

[petersaints]

I mean. I can map most of the things I've done with KineticJS to something like EaselJS, but it will still be a considerable amount if time and effort to port everything. So for now I'll KineticJS and hope for the best. I mean... I'm not asking for more features, just bug fixes and compatibility updates would be more than fine for me.

[confile]

It is very said. I will move on to Pixi.js it seems to me to be the best alternative. Good bye KineticJS.

-1

[speedy32]

I can set it up on my hosting if you like. I just need a domain transfer from you. Would you like to do the transfer? I think that there are more people then only me who would like to continue this project and fix the bugs. Did you think about It?

[DavidPesta]

To uphold the world's confidence in FOSS, it is important for Eric to find a maintainer and point the domain to one of their servers to keep the project alive. KineticJS has become way too popular to just disappear like this.

[kangax]

I'd be interested to hear what Fabric is missing comparing to Kinetic (aside from support for seamless layering, which I always loved in Kinetic and which we're planning to add to Fabric in a near future).

[lavrton]

I will maintain KineticJS in a fork: https://github.com/lavrton/KineticJS