Wednesday, September 26th, 2007

jMaki 1.0 Final Release: Ajax for Java and PHP

Category: Java, jMaki, Library

Greg Murray has put the stake in the ground and released jMaki 1.0. The release comes with “bundles” for PHP and Java which you can choose on the download area.

Included in the bundles:

  • The core jMaki framework.
  • Sample applications.
  • Ant task for creating applications and adding widgets and necessary dependencies to those applications.
  • All the scripts and widget libraries.

To see more, check out the jMaki Samples.

jMaki 1.0

Posted by Dion Almaer at 8:47 am

3.6 rating from 35 votes


Comments feed TrackBack URI

I like the whole widget idea and all, but i still don’t understand why so many additional layers of complexity have to be added for al those frameworks…
i’m getting headaches just looking at it..

Comment by SchizoDuckie — September 26, 2007

Hi ShizoDukie,

The life-cycle pays off when you consider default templates, the shared data models, multiple components, themeing, and tool integration in the mix. With jMaki we have tried to focus at making the end experience really easy and architecturally sound. As for the lifecycle diagram this is more for widget developers ( a common user would not see this).

Thank you for giving jMaki a look.


Comment by Greg Murray — September 26, 2007

The samples need some polish me thinks, but I’m just superficial.

Comment by Mike — September 26, 2007

Hi Mike,

If you like design we would love to have you on the team ;-)

Comment by Greg Murray — September 26, 2007

The Jamki framework is excellent and works well, but there is abit of a learning gap between the traditional javascript event model (i.e onclick , onsubmit e.t.c) and the publish/ subscribe model used in this program.

Can we have a backward compatibility model which allows for simple things like onclick e.t.c with the components ..?

Comment by Ehi — October 24, 2007

Hi Ehi,

With jMaki you can really easily edit the widgets component.js and add your own listeners (or add them in the template). The other option you have is to give the widget an id and process it like you would any other JavaScript component. See the following blog jMaki Form Processing talks about this more.

Beyond this what might you suggest?

Comment by Greg Murray — November 2, 2007

Leave a comment

You must be logged in to post a comment.