Archetype needed a real reference in order to clearly demonstrate its ability to work on huge Web 2.0 applications. Now it’s done!
Météo France, the official French meteorological Agency, uses Archetype on its brand new web site. www.meteofrance.com is one of the most visited French web sites with several millions of clients a day.
Florian, Loïc and I work for a French IT services company: Atos Worldline. The company provides us time to work on our framework as well - it’s good to remind it, thank you Atos Worldline. Actually, our company was chosen to realise this new Météo France web site. I’ve been working myself on this project for months; I proposed our framework for the client development sites, and it all started this way.
The use of the framework is a total success. JavaScript developments are well structured; using the framework was easy for developers, notably for developers new to JavaScript and the frameworks functionalities were indeed appreciated. Web performances are pretty good and compatibility is assured on a large portion of the browser marketplace.
It’s the current Mercurial “tip” version which is used on this project. As this is very stable, we will tag it very soon as of 0.8.0 final !
Hope this is only the first reference using so many Archetype features ;)
Yes, Archetype is ready for a heavy usage on large websites!
Note: The Geoportal API (http://api.ign.fr/geoportail/) and some parts of the Geoportal website itself (http://geoportail.fr), another institutional French web site, receiving several millions hits a day, both use Archetype as their JS loader ;D
jeudi 11 septembre 2008
samedi 6 septembre 2008
"La rentrée" !
Libellés :
0.8.0,
0.9.0,
announce,
Archetype,
Archetype Javascript Framework,
archetypejs,
Atos Worldline,
bookmark,
final,
JQuery,
opensearch,
prototype,
Release,
Solr
We have passed some busy summer holidays, and some announcement will come in the next few days. No comment, the content is a surprise :)
As 0.8.0 beta was based upon the (quite deprecated now) Prototype 1.5, the current "tip" works perfectly using now Prototype 1.6.
We originally made a branch in order to implement Prototype 1.6 compatibility as an experiment for the 0.9.0... But I've "mis-committed" (I've stupidly clicked on the bad repository when pushing the main changes) it on the current tip and continued with it.
The 0.8.0 was at this moment quite ready for a release, but we wanted to document a lot more the use of the framework itself. However, my job is to read and correct the documentation and I prefer a lor more coding than correcting a documentation, so... We did not release during the summer.
However a release is yet ready to go out, but based on Prototype 1.6. It has been quite heavily tested, even on the brand new Chrome, and we are hapopy with the result yet. But yet again we lack of documentation for this new release.
So, I think we will release the 0.9.0 before the 0.8.0 final(!!), because getting the 0.8.0 back from the history, test it, etc. will just be a pain compared to the 0.9.0 release.
Between the 2 releases, the main change is jumping from Prototype 1.5 to Prototype 1.6, we have added some handy tools in the 0.9.0, notably for playing easily with URLs.
Now what do we plan for 1.0 ? It depends. We have purposed an internship in our company focused on working on Archetype, in order to give it some cool tools to help for high trafic website, notably to minify the number of hits for loading the page (so mostly helping for bundling JavaScripts, and maybe help for CSS Sprites).
We have started in 0.8.0, the ability to choose what you want for specific part as a backend. We would like in the future version not to rely just on Prototype, but on any good framework we can use as a backend. We have just started a "secret" JQuery branch in order to see what is possible.
Other good news : a cool new open source project about social bookmarks relying only on Archetype to render the application should be there in some months. We've got a cool working beta version of it at Atos Worldline, but we have to do some work in order to release it as a free software ( we mainly have to avoid the use of our SSO for login). The main author of this project has written a very cool JS Code and I hope to convince him joining the Archetype Team :)
Again using Archetype, I've made a "plug&play" (call it widget if you want, but it's not exactly a widget) system in order to use a Solr ( http://lucene.apache.org/solr/ ) as a cross-domain search tool, that you can use on any web page that has a little form with an input and a submit event. I am working now on integrating Opensearch with it if it's possible.
We are very happy with Archetype can do yet, and we hope it's the same for you!
As 0.8.0 beta was based upon the (quite deprecated now) Prototype 1.5, the current "tip" works perfectly using now Prototype 1.6.
We originally made a branch in order to implement Prototype 1.6 compatibility as an experiment for the 0.9.0... But I've "mis-committed" (I've stupidly clicked on the bad repository when pushing the main changes) it on the current tip and continued with it.
The 0.8.0 was at this moment quite ready for a release, but we wanted to document a lot more the use of the framework itself. However, my job is to read and correct the documentation and I prefer a lor more coding than correcting a documentation, so... We did not release during the summer.
However a release is yet ready to go out, but based on Prototype 1.6. It has been quite heavily tested, even on the brand new Chrome, and we are hapopy with the result yet. But yet again we lack of documentation for this new release.
So, I think we will release the 0.9.0 before the 0.8.0 final(!!), because getting the 0.8.0 back from the history, test it, etc. will just be a pain compared to the 0.9.0 release.
Between the 2 releases, the main change is jumping from Prototype 1.5 to Prototype 1.6, we have added some handy tools in the 0.9.0, notably for playing easily with URLs.
Now what do we plan for 1.0 ? It depends. We have purposed an internship in our company focused on working on Archetype, in order to give it some cool tools to help for high trafic website, notably to minify the number of hits for loading the page (so mostly helping for bundling JavaScripts, and maybe help for CSS Sprites).
We have started in 0.8.0, the ability to choose what you want for specific part as a backend. We would like in the future version not to rely just on Prototype, but on any good framework we can use as a backend. We have just started a "secret" JQuery branch in order to see what is possible.
Other good news : a cool new open source project about social bookmarks relying only on Archetype to render the application should be there in some months. We've got a cool working beta version of it at Atos Worldline, but we have to do some work in order to release it as a free software ( we mainly have to avoid the use of our SSO for login). The main author of this project has written a very cool JS Code and I hope to convince him joining the Archetype Team :)
Again using Archetype, I've made a "plug&play" (call it widget if you want, but it's not exactly a widget) system in order to use a Solr ( http://lucene.apache.org/solr/ ) as a cross-domain search tool, that you can use on any web page that has a little form with an input and a submit event. I am working now on integrating Opensearch with it if it's possible.
We are very happy with Archetype can do yet, and we hope it's the same for you!
Archetype, "promising" ? :)
If you particularly follow the JS/Ajax world, you must (or should!) follow Ajaxian ( http://ajaxian.com ).
So let's check some news from Ajaxian today... Hey, but what's new? An article on 10 promising JS frameworks. And you know what? Archetype is here ! :)
The article : http://sixrevisions.com/javascript/promising_javascript_frameworks/
So let's check some news from Ajaxian today... Hey, but what's new? An article on 10 promising JS frameworks. And you know what? Archetype is here ! :)
The article : http://sixrevisions.com/javascript/promising_javascript_frameworks/
Inscription à :
Messages (Atom)