And now, a Version 2 is out for trial…

Well, enough reasons to decide to give a new and fresh look to the current website and also redesign the logo which, until now, looked like this:

But this time, we decided to ask for your help in the choice of our future logo.

Thanks in advance !

Please have a look at those new examples and download the version 2 for tests.

If you followed the story, you may know this new version is more about a change in the inner logic than a set of new features.

However we think this new architecture will enable us to go further with the library.

The main changes are described here: Version 2 Release Notes. You will also find in the article a mini-guide to upgrade your templates still using PURE version 1.

In the coming weeks, the wiki will be updated with a refreshed documentation.

Any suggestion, ideas about how to structure it in a better way is highly welcome.

Heads & hands to write some parts too

Please have a look at the material above and send your feedback.

Today, we fully support it!

From now on, we are also supporting the JS library MooTools in addition to jQuery, DOMAssistant and Prototype

Once again, a big thank you to Carlos Saltos and Borja Vazquez for the MooTools support.

The source code and examples featuring the different libraries and Sizzle are available in our master repository

Only Dojo is still hanging in our development queue and any expert is welcome to help us on the task.

Just pass by our discussion group and let us know if you’re planning on doing something in this respect.

The code is not in the master repository yet, but you can get it in the branch of PURE created by Carlos.

They are also working on the MooTools support.

With the announcement of the DOMAssistant support a few weeks ago, and jQuery initially, it is now three JavaScript libraries that are supported.

Stay tuned

From revision 1.7 on, there is a new shortcut available to concatenate strings.

We’ll take a similar HTML as our basic Hello World example:

Now we remove the “Hello ” string:

Here is the JSON we’ll use to render this HTML:

And now the directive that will link them both:

Direct assignation continues to work.

For more information and examples, visit the dedicated Wiki page

Stay tuned

All your own tips are more than welcome. Just send us an email with what you’ve got.

And to end this post on really good news, Douglas Crockford, the man behind JSON, just added PURE on JSON.org main page.

Stay Tuned

Since we are using jQuery as our main JS library in the development of our BeeLit (called BeeBole now) solution, it was obvious to start with this one.

Today, we are happy to announce that PURE has moved another step closer to our initial goal as it now also works with DOMAssistant.

I must say, we haven’t really played a big role here. Everything started with a simple message on the DOMAssistant discussion group

Lim Cheng Hong (one of the three developers behind the library) took the challenge in his hands and made the 6 examples of our Getting Started page working with DOMAssistant in just two days.

You can discover those 6 examples with the DOMAssistant library here

So thank you Lim Cheng Hong and thanks to the DOMAssistant team.

We will soon update our wiki and the PURE website with those new examples.

The next steps will be to port PURE on Prototype, MooTools and Dojo.

If you are ready to get your hands dirty with those adaptations, your help will be more than welcome.

Stay tuned

This release contains a few corrections but also a lot of new features:

• Auto-rendering: a new PURE method takes your HTML and your JSON data and merges them automatically. The class attribute is used to map the HTML and the data. (Read more about autoRender and its jQuery version on our Wiki).

• Recursive Template Call

• Functions as directive are called by reference and not serialized

• Attach events to your HTML (Read more)

• Change the id of the template root node (as any other attribute)

• Better string value handling

• Use of named properties in iteration “obj.prop” as well as “obj['name']“

We also made some changes to the PURE environment:

• The Home page and the Getting Started page have been re-done, including more examples

• The source code moved from Google Code to GitHub

• You can find now a technical documentation on the GitHub Wiki

• You can report bugs on Lighthouse

• There is a dedicated jQuery Plugin project

• You can discuss about PURE in French on our French discussion group

We are also actively looking for help in order to port PURE to other JS libraries such as DomAssistant, Dojo, Mootools, Prototype, YUI, …

If you are ready to get your hands dirty, just pass by the discussion group and leave us a message.

Stay tuned

One of them is a poor phone law that makes consumers pay the full price for a phone, probably one of the highest in the world. This doesn’t bring any cheaper usage cost than our neighbours either.

So it came as a kind of consolation when I saw PURE running smoothly on my brand new iPhone 3G.

Ok, it’s an easy shot as Safari is running there. But that’s good news for web applications using PURE.

Even if we’ll have to build specific screens for the smaller devices, we’ll be able to use the same technology, back-end services and share some templates between the desktop and the smart phone versions.

Moreover, the rendering speed was really good. We will show some benchmarks soon.

I can’t wait on what Google/HTC will ship in a couple of months.

The idea behind it is to decentralize the power needed to run the application to the clients and also to lower the bandwidth needed (by sending just small pieces of JSON).

If this is good in our context (creation of a business application), some people might have good reasons to render the HTML on the server side.

For example, if you need to have the content of your application or website indexed by Google (for SEO).

We have planned to bring the logic of PURE to our Erlang back-end for our own needs (like sending tables to Excel for example) and there is nothing that should stop anybody from doing the same with any other back-end language.

But there is also the possibility to run the JavaScript on the server side.

While we have received comments about Spidermonkey or Rhino, we have never performed tests until now.

We have however received a message from Davey Waterson, JavaScript Architect from Aptana, telling us that:

PURE works unchanged out of the box with Jaxer running as serverside JS

Have a look at his example. You can also check out the Aptana website for more information about Jaxer

Davey will soon publish new examples of integration between PURE and Jaxer on the Aptana Forum

We’ll keep you updated.

On a more personal note, PURE has been entirely built on Aptana Studio and it was a great surprise to read that the same company was paying attention to our project.

Stay tuned