jMaki Ajax Framework Releases 1.0 with Support for Java, PHP, and Ruby
Almost two years ago, in the Land of the Rising Sun, work began on a project known as jMaki. Simply put, jMaki is a client/server framework for developing AJAX applications. The primary focus has been geared towards corporate developers although they are working to broaden their scope. Eventually the jMaki team
...would love to see jMaki become the Wordpress of Ajax functionality.Murray explained that,
Basically we want jMaki to provide a framework where you can create standards based applications that use your code along with the best of breed toolkits and functionalities out there. This might include Dojo or Yahoo Widgets, use Google Gears for local storage, Scriptataculus / Protoscript for effects, and use services such as Yahoo or Google Maps.Additionally, Murray made the point clear that jMaki is not an "all or nothing framework",
jMaki is good as a single widget (such as a chart or the revolver) and it is also good for applications. The framework is designed to perform well. The client-side script containing all the core functionality is 18KB. Further, size is determined by what you decide to use and we have also gone through great pains to make sure the toolkits we use are tuned to work very well.
The release of jMaki 1.0 provides developers with a plethora of features and capabilities which Murray explained when answering InfoQ's question, If you had the opportunity to sit with a web application developer who was about to start a new application, what would be the top five features or capabilities that you would point out?
- Defaults set when you use a widget /extension
- Standardizes Event / Data Models
- Consistent programming model
- Portable Widget / Extension libraries
- Platform Independence
jMaki adheres to convention over configuration. There are well known locations for putting widgets /extensions that get picked up. Especially when you use a tool you will get a working widget when you drag it in the page. The templates we use have inlnine data (data can also be loaded using Ajax calls).
We provide plugins for Netbeans / Eclipse and have Ant tasks for building web applications
We have a consistent way of describing widgets and interactions with widgets. This allows you to learn one model and you can apply it across toolkits. We manage the differences in the widget wrappers we have written.
The way to interact with a widget is consistent across toolkits. The use of Actions for example is a single way of handling events on widgets declaratively. We have glue to allow for a programatic way of handling events on widgets, extensions, or user behavior.
jMaki widgets are portable and they can also be aggregated into libraries which include all of their need resources. This allows a user to upgrade or share a set of widgets in a simple zip file package format that can be loaded by tools
jMaki has full support for Java (JSP / JSF 1.1-2 / Facelets / Portlets), PHP 5.x, Phobos, and now Ruby (though we don't have the proxy implemented do to there not being a standard XSLT processor).
The release of jMaki 1.0 is a culmination of a lot of hard work and time by the community. However, with a 1.0 release date of September 25, Murray and the rest of the team have already begun discussion jMaki 1.1. Future enhancements include improving the consistency of the client-event bus connection with the server component, improving the breath of widgets (i.e. jQuery and Protoscript) and increase the utilization of the server to improve the over the wire experience.
Chris Mattmann Apr 15, 2014