Replace Enyo by vue.js

[bzg]

Sugarizer relies on the Enyo JS framework but does not use anything from Enyo that makes it mandatory.

Replacing Enyo by vue.js would clarify and modernize the code base, while attracting more developers.

[usmanmuhd]

@llaske I am interested to work on this. Could you please provide me some pointers on where to get started with?

[ksraj123]

@llaske I would like to work on this as a part of my gsoc proposal. Before replacing enyo with vue in the core platform, Porting some activities first which use enyo would be a starting point I think.

The activities which currently use enyo framework are -

• Tank Operation
• Foodchain
• Abecedarium
• Tam Tam Micro
• Video Viewer
• Last One Loses

I would like a start working on porting a few of these. Which one among these would be a priority?
Requesting suggestions.

[llaske]

@ksraj123 Thanks for this proposal.
BTW I don't see any good reason to migrate these activities:

• No benefit for users: the activity will not work better
• No benefit for developers: there is no maintenance issue today and dependency to Enyo framework didn't not prevent recent improvements on these activities

So a best way to prepare migration is to invest in Vue.js for new activities. Not to rewrite old activities.
Conversely to Gtk2/Python2 issue in Sugar, using a deprecated Enyo version has no impact on Sugarizer deployment.

[quozl]

Well said. We're not porting to Python 3 because we want to, but because we have no other way to benefit the users.

[ksraj123]

@llaske I agree with you. It sounds reasonable. As Enyo is a comparatively old and less talked about framework there are not as many resources for us (student developers) to learn more about it or refer to if something does not work, as there are for vue. I made some contributions to some of the enyo activities I mentioned recently and faced these problems myself as I didn't had much prior experience with it, seeing an open issue on this I thought maybe others are facing these problems as well. But I agree with you on porting will not make the old activities work better and I guess changes to the core platform are not that frequent to justify porting. So I agree with you on investing in vue for future activities. Thanks.

[llaske]

For information, it's a WIP here https://github.com/llaske/sugarizer/tree/feature/v2