Roadmap

We really think we found something with eureka.js, but what software shouldn't look towards an infinite horizon? Here we document our plans for the future of eureka.js.

0.1.0

Anything considered to be "core functionality" for the ability to browse and upload media is complete. Provided endpoints to consume JSON over XHR, eureka.js allows web developers this component as a simple media browser. localStorage is used to remember user preferences and app states and a muckboot.eureka.js script is available for non-HTML first workflows.

Note: eureka.js does not do things like close or destroy itself when an image is chosen, it simply dispatches a EurekaFoundIt event. This is due to the un-opinionated nature of eureka.js; you may have to do a little more work with things like manually animating out and destroying the component but the flexibility of the user's experience is yours.

0.2.0

Legacy compatibility. IE 9 isn't down with some of the modern JavaScript used in eureka.ts, the source file of eureka.js. To support older browsers, we plan to first abstract as much as we can to make the JavaScript source as DRY as possible before creating jQuery 1.x Driver for legacy browsers that don't "cut the mustard". Additionally, messy JavaScript may be needed to support or mimic the flexible layout being used. eureka.css is written for modern browsers and uses no floats; it sinks.

0.3.0

• JS Drivers
  • React Driver
  • Angular Driver
• <picture> support