Best Of

Everyone, we're really happy to announce that Enact, the successor to Enyo, has now been publicly released. You can read the Enact release announcement on our blog.

Enact includes many of the same features that made Enyo great, but is now based upon the React ecosystem. We now fully embrace modern JavaScript and web standards. Our source is available on GitHub and is licensed under the same permissive Apache license Enyo was released under: https://github.com/enactjs/enact

As a necessary part of our shift in focus to this new framework we're going to officially stop monitoring this forum. Please continue to support each other as you have been.

1. Update any custom libraries to 2.7 (recursion!)2. Fix any automated unit or functional tests that have been commented out, or are out of date. Properly written automated tests are a great way to prevent bugs from creeping in during conversion.3. Delete files not used by your project, such as deploy.md, Theme.less, CONTRIBUTING.md, etc.4. Split your app's utility code into functional units. If a function is only used in one Component, consider moving it there. Split automated and functional tests likewise.5. Analyze your globals, and refactor to a smaller scope, if possible. If a global is properly used by two parts of your app, move it to its own file, so it can be converted to a module, later.

Those of you who've been paying attention should know by now that we've been working on polishing up the 2.7.0 public release. I'm happy to announce that your days of waiting are over. Enyo 2.7.0 has hit the streets. Its little brother enyo-dev has also reached its 1.0.0 milestone and is available on npm. In fact, getting started with 2.7 is as easy as doing:

npm install -g enyo-dev
enyo init MyNewProject

You'll probably want to check out the new templates that are available in enyo-dev. A simple

We've made good progress getting Enyo ready for release. We're at the point now where we have tagged a release candidate so we have a marker in the sand. The release candidate allows us to begin our internal testing.

If you are interested in checking out this version of Enyo, you can use the 2.7.0-rc.1 tag. To use this with "enyo init" you can update your .enyoconfig file as follows:

There will certainly be more changes before the official 2.7.0 release.

We are also nearing the 1.0.0 release of the enyo-dev tool. If you would like to start using this tool, you'll need to check out the master branch directly from github. This version requires node version 4 or higher.

jQuery, like Enyo, has its own event system such that custom events, of which plotclick is, aren't bubbled up via the DOM hierarchy. Instead, the flow through jQuery's internal event system. Unfortunately, this hides those events from Enyo. Not sure why Ben's suggestion worked before and not now unless either Flot or jQuery has changed. I'm guessing the former if either.

Good news is that you can patch those events into Enyo pretty easily by adding enyo.dispatch as the listener for the custom events.

We have opened up our developer guide for community input. Documentation is available under the Creative Commons BY 4.0 license. The included source code is licensed under the same Apache license that Enyo is. Check the README.md file for more information.