Trucs et astuces pour optimiser vos applications HTML5

Les applications HTML5 sont réputées lentes. C’est effectivement souvent le cas. Pourtant ce n’est pas une fatalité. Avec quelques bons conseils et beaucoup de noeuds au cerveau, il est possible d’avoir des applications HTML5 réactives sur mobile.

Par « application réactive » on entend généralement que l’utilisateur doit avoir du feedback en moins d’une seconde :

Sauf que la plupart des applications utilisent des données provenant d’un serveur.

Et le réseau étant ce qu’il est, difficile d’avoir une application réactive. A vrai dire, si on enlève le temps réseau et serveur, vous n’avez que 200 millisecondes : Alors comment on fait?

Voici quelques conseils qui pourront peut-être vous aider…

Changez de framework pour un plus léger !

voir mon autre article à ce sujet si vous l’avez raté.

Méfiez vous de la hype !

Ah ! la magie de CSS3, c’est beau, on peut tout faire ! mais méfiez vous : les dégradés peuvent vous faire ramer, les box-shadow et les border-radius aussi, les flexbox aussi.

Malheureusement tout le monde n’a pas le dernier device à la mode.

Faites attention à vos modification du DOM

Chaque modification du DOM ou d’un style de votre page est couteuse. En effet, le navigateur « repeint » régulièrement votre page en fonction des modifications que vous y apportez. Pensez-y : parfois il vaut mieux par exemple construire une liste d’items en mémoire, hors du DOM, puis les injecter tous d’un coup.

Utilisez une sprite css pour toutes vos images

L’image une fois chargée sera en cache pour toute votre application, les icônes s’afficheront instantanément, ça donne un effet de vitesse indiscutable. Avec un peu de bidouille vous aurez une sprite pour chaque résolution de device.

Et puis il existe des générateurs de sprite.

Déchargez vos images

Sous iOS, les images ne sont pas déchargées de la mémoire du navigateur quand elles sont hors de la zone visible de l’écran. Si vous avez des tonnes d’images, vous pouvez remplacer les sources des images invisibles par un pixel vide, afin de soulager le navigateur. Voir l’article de linkedin sur son fil d’actu HTML5.

Utilisez vanillaJS

Non ce n’est pas un autre framework javascript ! C’est juste du vent. Pour nous rappeler que pour un petite application, rien de tel que le bon vieux javascript.

Utilisez des bouts de css inline

Dans ces slides, Patrick Hamann conseille cette technique pour afficher le début de la page, pendant que le reste se charge.

Après tout, pourquoi pas. Parfois, entre « application qui rame » et « application réactive » il n’y a pas grand chose. C’est aussi de sa présentation que viennent une partie des images plus haut.

Vérifez que vous utilisez bien vos frameworks

Dans ces vieux slides, Paul Irish nous rappelle à l’ordre à travers le temps. Car nous utilisons mal jQuery. Il est fort, Paul.

Tips and tricks for optimizing their HTML5 applications

HTML5 applications are considered slow. This is usually the case. However, This is not inevitable. With some good advice and lots of knots to the brain, it is possible to have reactive HTML5 applications on the mobile.

"Application of reactive" usually means that the user must have less than a second to feedback:

Except that most of the applications uses data from a server.

And the network is that it is difficult to have a sensible application. True, if we remove the time server and network, it has only 200 milliseconds : then like?

Here are some tips that can help you to...

Change the frame for a lighter!

If you missed it, see my other article on this subject.

Careful with exaggerations!

Ah! the magic of CSS3, is beautiful, you can do anything! But be careful : gradients can paddle, shadows and border radius also, flexbox also.

Unfortunately, not all are the last device in the mode.

Pay attention to the modification of the DOM

Each modification of the DOM or the style of your page is expensive. In fact, the "repainted" browser regularly your page depending of the changes that do. Think about this: sometimes the best thing is to build for example a list of items in memory, the DOM, then injected them suddenly.

Use a css sprite for all your images

The image once loaded is stored in cache for the entire application, the icons will be displayed instantly, gives an undisputed speed effect. With a bit of hacking a sprite for each device resolution.

And then there are the generators of sprite.

Download your images

IOS, images are not downloaded from the memory of the browser when they are outside the visible area of the screen. If you have tons of photos, you can replace an invisible pixel blank image sources, in order to relieve the browser. See the article on linkedin in grain of actu HTML5.

Use vanillaJS

No, this is not another javascript framework! It is the wind. To remind us that for a small application, nothing as good old javascript.

Inline css tips

In these slides, Patrick Hamann recommends this technique to show the top of the page, while the rest of loads.

After all, why not. Sometimes, between "application to rowing" and "test application" there isn't much. It is also his presentation which are part of the image above.

Verify that you are using your frames

In these old slides, Paul Irish reminds us on the agenda over time. Because we use jQuery badly. Is strong, Paul.

Trucs et astuces pour optimiser vos applications HTML5

Les applications HTML5 sont réputées lentes. C’est effectivement souvent le cas. Pourtant ce n’est pas une fatalité. Avec quelques bons conseils et beaucoup de noeuds au cerveau, il est possible d’avoir des applications HTML5 réactives sur mobile.

Par « application réactive » on entend généralement que l’utilisateur doit avoir du feedback en moins d’une seconde :

Sauf que la plupart des applications utilisent des données provenant d’un serveur.

Et le réseau étant ce qu’il est, difficile d’avoir une application réactive. A vrai dire, si on enlève le temps réseau et serveur, vous n’avez que 200 millisecondes : Alors comment on fait?

Voici quelques conseils qui pourront peut-être vous aider…

Changez de framework pour un plus léger !

voir mon autre article à ce sujet si vous l’avez raté.

Méfiez vous de la hype !

Ah ! la magie de CSS3, c’est beau, on peut tout faire ! mais méfiez vous : les dégradés peuvent vous faire ramer, les box-shadow et les border-radius aussi, les flexbox aussi.

Malheureusement tout le monde n’a pas le dernier device à la mode.

Faites attention à vos modification du DOM

Chaque modification du DOM ou d’un style de votre page est couteuse. En effet, le navigateur « repeint » régulièrement votre page en fonction des modifications que vous y apportez. Pensez-y : parfois il vaut mieux par exemple construire une liste d’items en mémoire, hors du DOM, puis les injecter tous d’un coup.

Utilisez une sprite css pour toutes vos images

L’image une fois chargée sera en cache pour toute votre application, les icônes s’afficheront instantanément, ça donne un effet de vitesse indiscutable. Avec un peu de bidouille vous aurez une sprite pour chaque résolution de device.

Et puis il existe des générateurs de sprite.

Déchargez vos images

Sous iOS, les images ne sont pas déchargées de la mémoire du navigateur quand elles sont hors de la zone visible de l’écran. Si vous avez des tonnes d’images, vous pouvez remplacer les sources des images invisibles par un pixel vide, afin de soulager le navigateur. Voir l’article de linkedin sur son fil d’actu HTML5.

Utilisez vanillaJS

Non ce n’est pas un autre framework javascript ! C’est juste du vent. Pour nous rappeler que pour un petite application, rien de tel que le bon vieux javascript.

Utilisez des bouts de css inline

Dans ces slides, Patrick Hamann conseille cette technique pour afficher le début de la page, pendant que le reste se charge.

Après tout, pourquoi pas. Parfois, entre « application qui rame » et « application réactive » il n’y a pas grand chose. C’est aussi de sa présentation que viennent une partie des images plus haut.

Vérifez que vous utilisez bien vos frameworks

Dans ces vieux slides, Paul Irish nous rappelle à l’ordre à travers le temps. Car nous utilisons mal jQuery. Il est fort, Paul.

HTML5, JavaScript to choose what framework applications?

Difficult to navigate JavaScript frameworks! Mobile is even worse: the technical limitations that we grow more and more to find the Pearl: the framework that will simplify us life, without wasting time and without slowing down the application.

We found it? Almost, but in any case we seek

First, when it starts in the development of web applications in fall of big fish, big frameworks that do everything. Forget them!

SenchaTouch kill you: this frame is so ' ios - like ' will have most of the time to break everything to rebuild when you go to the version of Android app. Lists of do everything to look native but not provide in comparison: displacement of lags and learn the ins and outs of the Dr. will take you all the time.

jQueryMobile is almost good, but if you're pointing old terminal application are all similarly to start paddling. The reason is simple:

jQueryMobile is great!

Do even after a compilation custom (in beta), still it is big enough, and then you have that they include jQuery - across the Court, it would be not a bit exaggerated?

Another jQueryMobile disadvantage is that he is managed rather the DOM when is ' improving ' the HTML code for the representation of the various components.»

Although they have recently reduced the amount of manipulation of this type, this operation is very expensive in performance on a smartphone!

This is what you should ask whenever you add a JavaScript library to your project.

Zepto.js, for example, is a JavaScript library that incorporates the main features of jQuery, but with what is needed for mobile: is not optimized for the old Firefox or IE. It has the huge advantage of being small (25 KB) and not get if you just jQuery.

However you will find difficult to be efficient with an application complete-JavaScript if not filled Zepto a JavaScript templating system. For this we recommend mustache.js or better as well:

 

Handlebar, fuller mustache.js is a scalable system templates based on reinforcement. It allows to generate HTML for the data. You can manage lists, conditions and even allows to define your own tags.

Therefore, with this pair of bookcases, Zepto, and handlebars, 30 KB in total, that I'm more like. But the competition is tough, and other frameworks are talking with them.

The new advertising is the MV frameworks *, not fully MVC frameworks, but are inspired. She was found among them the famous Google AngularJS, Backbone.js and Ember.js

AngularJs and EmberJs are trying to improve the HTML components through the incorporation of a template as well - like system. They also simplify update views in real time, is the famous " two way data binding«.»" Spinal column puts everything to avoid this, bearing in mind that it is for a demo but it is not necessary in the 'real world', you choose!

 

Don't miss this topic organized whole AngularJS presentation soon by CodeDarmor on 22 October next in Lannion.

Tips and tricks for optimizing their HTML5 applications

HTML5 applications are considered slow. This is usually the case. However, This is not inevitable. With some good advice and lots of knots to the brain, it is possible to have reactive HTML5 applications on the mobile.

"Application of reactive" usually means that the user must have less than a second to feedback:

Except that most of the applications uses data from a server.

And the network is that it is difficult to have a sensible application. True, if we remove the time server and network, it has only 200 milliseconds : then like?

Here are some tips that can help you to...

Change the frame for a lighter!

If you missed it, see my other article on this subject.

Careful with exaggerations!

Ah! the magic of CSS3, is beautiful, you can do anything! But be careful : gradients can paddle, shadows and border radius also, flexbox also.

Unfortunately, not all are the last device in the mode.

Pay attention to the modification of the DOM

Each modification of the DOM or the style of your page is expensive. In fact, the "repainted" browser regularly your page depending of the changes that do. Think about this: sometimes the best thing is to build for example a list of items in memory, the DOM, then injected them suddenly.

Use a css sprite for all your images

The image once loaded is stored in cache for the entire application, the icons will be displayed instantly, gives an undisputed speed effect. With a bit of hacking a sprite for each device resolution.

And then there are the generators of sprite.

Download your images

IOS, images are not downloaded from the memory of the browser when they are outside the visible area of the screen. If you have tons of photos, you can replace an invisible pixel blank image sources, in order to relieve the browser. See the article on linkedin in grain of actu HTML5.

Use vanillaJS

No, this is not another javascript framework! It is the wind. To remind us that for a small application, nothing as good old javascript.

Inline css tips

In these slides, Patrick Hamann recommends this technique to show the top of the page, while the rest of loads.

 

After all, why not. Sometimes, between "application to rowing" and "test application" there isn't much. It is also his presentation which are part of the image above.

Verify that you are using your frames

In these old slides, Paul Irish reminds us on the agenda over time. Because we use jQuery badly. Is strong, Paul.

Tips and tricks for optimizing their HTML5 applications

HTML5 applications are considered slow. This is usually the case. However, This is not inevitable. With some good advice and lots of knots to the brain, it is possible to have reactive HTML5 applications on the mobile.

"Application of reactive" usually means that the user must have less than a second to feedback:

Except that most of the applications uses data from a server.

And the network is that it is difficult to have a sensible application. True, if we remove the time server and network, it has only 200 milliseconds : then like?

Here are some tips that can help you to...

Change the frame for a lighter!

If you missed it, see my other article on this subject.

Careful with exaggerations!

Ah! the magic of CSS3, is beautiful, you can do anything! But be careful : gradients can paddle, shadows and border radius also, flexbox also.

Unfortunately, not all are the last device in the mode.

Pay attention to the modification of the DOM

Each modification of the DOM or the style of your page is expensive. In fact, the "repainted" browser regularly your page depending of the changes that do. Think about this: sometimes the best thing is to build for example a list of items in memory, the DOM, then injected them suddenly.

Use a css sprite for all your images

The image once loaded is stored in cache for the entire application, the icons will be displayed instantly, gives an undisputed speed effect. With a bit of hacking a sprite for each device resolution.

And then there are the generators of sprite.

Download your images

IOS, images are not downloaded from the memory of the browser when they are outside the visible area of the screen. If you have tons of photos, you can replace an invisible pixel blank image sources, in order to relieve the browser. See the article on linkedin in grain of actu HTML5.

Use vanillaJS

No, this is not another javascript framework! It is the wind. To remind us that for a small application, nothing as good old javascript.

Inline css tips

In these slides, Patrick Hamann recommends this technique to show the top of the page, while the rest of loads.

After all, why not. Sometimes, between "application to rowing" and "test application" there isn't much. It is also his presentation which are part of the image above.

Verify that you are using your frames

In these old slides, Paul Irish reminds us on the agenda over time. Because we use jQuery badly. Is strong, Paul.

HTML5, JavaScript to choose what framework applications?

Difficult to navigate JavaScript frameworks! Mobile is even worse: the technical limitations that we grow more and more to find the Pearl: the framework that will simplify us life, without wasting time and without slowing down the application.

We found it? Almost, but in any case we seek

First, when it starts in the development of web applications in fall of big fish, big frameworks that do everything. Forget them!

SenchaTouch kill you: this frame is so ' ios - like ' will have most of the time to break everything to rebuild when you go to the version of Android app. Lists of do everything to look native but not provide in comparison: displacement of lags and learn the ins and outs of the Dr. will take you all the time.

jQueryMobile is almost good, but if you're pointing old terminal application are all similarly to start paddling. The reason is simple:

jQueryMobile is great!

Do even after a compilation custom (in beta), still it is big enough, and then you have that they include jQuery - across the Court, it would be not a bit exaggerated?

Another jQueryMobile disadvantage is that he is managed rather the DOM when is ' improving ' the HTML code for the representation of the various components.»

Although they have recently reduced the amount of manipulation of this type, this operation is very expensive in performance on a smartphone!

This is what you should ask whenever you add a JavaScript library to your project.

Zepto.js, for example, is a JavaScript library that incorporates the main features of jQuery, but with what is needed for mobile: is not optimized for the old Firefox or IE. It has the huge advantage of being small (25 KB) and not get if you just jQuery.

However you will find difficult to be efficient with an application complete-JavaScript if not filled Zepto a JavaScript templating system. For this we recommend mustache.js or better as well:

Handlebar, fuller mustache.js is a scalable system templates based on reinforcement. It allows to generate HTML for the data. You can manage lists, conditions and even allows to define your own tags.

Therefore, with this pair of bookcases, Zepto, and handlebars, 30 KB in total, that I'm more like. But the competition is tough, and other frameworks are talking with them.

The new advertising is the MV frameworks *, not fully MVC frameworks, but are inspired. She was found among them the famous Google AngularJS, Backbone.js and Ember.js

AngularJs and EmberJs are trying to improve the HTML components through the incorporation of a template as well - like system. They also simplify update views in real time, is the famous " two way data binding«.»" Spinal column puts everything to avoid this, bearing in mind that it is for a demo but it is not necessary in the 'real world', you choose!

Don't miss this topic organized whole AngularJS presentation soon by CodeDarmor on 22 October next in Lannion.

HTML5, JavaScript to choose what framework applications?

Difficult to navigate JavaScript frameworks! Mobile is even worse: the technical limitations that we grow more and more to find the Pearl: the framework that will simplify us life, without wasting time and without slowing down the application.

We found it? Almost, but in any case we seek

First, when it starts in the development of web applications in fall of big fish, big frameworks that do everything. Forget them!

SenchaTouch kill you: this frame is so ' ios - like ' will have most of the time to break everything to rebuild when you go to the version of Android app. Lists of do everything to look native but not provide in comparison: displacement of lags and learn the ins and outs of the Dr. will take you all the time.

jQueryMobile is almost good, but if you're pointing old terminal application are all similarly to start paddling. The reason is simple:

jQueryMobile is great!

Do even after a compilation custom (in beta), still it is big enough, and then you have that they include jQuery - across the Court, it would be not a bit exaggerated?

Another jQueryMobile disadvantage is that he is managed rather the DOM when is ' improving ' the HTML code for the representation of the various components.»

Although they have recently reduced the amount of manipulation of this type, this operation is very expensive in performance on a smartphone!

This is what you should ask whenever you add a JavaScript library to your project.

Zepto.js, for example, is a JavaScript library that incorporates the main features of jQuery, but with what is needed for mobile: is not optimized for the old Firefox or IE. It has the huge advantage of being small (25 KB) and not get if you just jQuery.

However you will find difficult to be efficient with an application complete-JavaScript if not filled Zepto a JavaScript templating system. For this we recommend mustache.js or better as well:

 

Handlebar, fuller mustache.js is a scalable system templates based on reinforcement. It allows to generate HTML for the data. You can manage lists, conditions and even allows to define your own tags.

Therefore, with this pair of bookcases, Zepto, and handlebars, 30 KB in total, that I'm more like. But the competition is tough, and other frameworks are talking with them.

The new advertising is the MV frameworks *, not fully MVC frameworks, but are inspired. She was found among them the famous Google AngularJS, Backbone.js and Ember.js

AngularJs and EmberJs are trying to improve the HTML components through the incorporation of a template as well - like system. They also simplify update views in real time, is the famous " two way data binding«.»" Spinal column puts everything to avoid this, bearing in mind that it is for a demo but it is not necessary in the 'real world', you choose!

 

Don't miss this topic organized whole AngularJS presentation soon by CodeDarmor on 22 October next in Lannion.

Tips and tricks for optimizing their HTML5 applications

HTML5 applications are considered slow. This is usually the case. However, This is not inevitable. With some good advice and lots of knots to the brain, it is possible to have reactive HTML5 applications on the mobile.

"Application of reactive" usually means that the user must have less than a second to feedback:

 

Except that most of the applications uses data from a server.

And the network is that it is difficult to have a sensible application. True, if we remove the time server and network, it has only 200 milliseconds :  then like?

Here are some tips that can help you to...

Change the frame for a lighter!

If you missed it, see my other article on this subject.

Careful with exaggerations!

Ah! the magic of CSS3, is beautiful, you can do anything! But be careful : gradients can paddle, shadows and border radius also, flexbox also.

Unfortunately, not all are the last device in the mode.

Pay attention to the modification of the DOM

Each modification of the DOM or the style of your page is expensive. In fact, the "repainted" browser regularly your page depending of the changes that do. Think about this: sometimes the best thing is to build for example a list of items in memory, the DOM, then injected them suddenly.

Use a css sprite for all your images

The image once loaded is stored in cache for the entire application, the icons will be displayed instantly, gives an undisputed speed effect. With a bit of hacking a sprite for each device resolution.

And then there are the generators of sprite.

Download your images

IOS, images are not downloaded from the memory of the browser when they are outside the visible area of the screen. If you have tons of photos, you can replace an invisible pixel blank image sources, in order to relieve the browser. See the article on linkedin in grain of actu HTML5.

Use vanillaJS

No, this is not another javascript framework! It is the wind. To remind us that for a small application, nothing as good old javascript.

Inline css tips

In these slides, Patrick Hamann recommends this technique to show the top of the page, while the rest of loads.

 

After all, why not. Sometimes, between "application to rowing" and "test application" there isn't much. It is also his presentation which are part of the image above.

Verify that you are using your frames

In these old slides, Paul Irish reminds us on the agenda over time. Because we use jQuery badly. Is strong, Paul.

HTML5, JavaScript to choose what framework applications?

Difficult to navigate JavaScript frameworks! Mobile is even worse: the technical limitations that we grow more and more to find the Pearl: the framework that will simplify us life, without wasting time and without slowing down the application.

We found it? Almost, but in any case we seek

First, when it starts in the development of web applications in fall of big fish, big frameworks that do everything. Forget them!

SenchaTouch kill you: this frame is so ' ios - like ' will have most of the time to break everything to rebuild when you go to the version of Android app. Lists of do everything to look native but not provide in comparison: displacement of lags and learn the ins and outs of the Dr. will take you all the time.

jQueryMobile is almost good, but if you're pointing old terminal application are all similarly to start paddling. The reason is simple:

jQueryMobile is great!

Do even after a compilation custom (in beta), still it is big enough, and then you have that they include jQuery - across the Court, it would be not a bit exaggerated?

Another jQueryMobile disadvantage is that he is managed rather the DOM when is ' improving ' the HTML code for the representation of the various components.»

Although they have recently reduced the amount of manipulation of this type, this operation is very expensive in performance on a smartphone!

This is what you should ask whenever you add a JavaScript library to your project.

Zepto.js, for example, is a JavaScript library that incorporates the main features of jQuery, but with what is needed for mobile: is not optimized for the old Firefox or IE. It has the huge advantage of being small (25 KB) and not get if you just jQuery.

However you will find difficult to be efficient with an application complete-JavaScript if not filled Zepto a JavaScript templating system. For this we recommend mustache.js or better as well:

Handlebar, fuller mustache.js is a scalable system templates based on reinforcement. It allows to generate HTML for the data. You can manage lists, conditions and even allows to define your own tags.

Therefore, with this pair of bookcases, Zepto, and handlebars, 30 KB in total, that I'm more like. But the competition is tough, and other frameworks are talking with them.

The new advertising is the MV frameworks *, not fully MVC frameworks, but are inspired. She was found among them the famous Google AngularJS, Backbone.js and Ember.js

AngularJs and EmberJs are trying to improve the HTML components through the incorporation of a template as well - like system. They also simplify update views in real time, is the famous " two way data binding«.»" Spinal column puts everything to avoid this, bearing in mind that it is for a demo but it is not necessary in the 'real world', you choose!

Don't miss this topic organized whole AngularJS presentation soon by CodeDarmor on 22 October next in Lannion.

HTML5 APPLIS, quel frame JavaScript choisir?

Difficile de similar retrouver dans les Marcos JavaScript! Mobile South c ' est encore pire: les contraintes technical nous poussent plus à trouver plus perle it: le framework goes simplifier nous the vie, sans nous faire perdre temps et sans ralentir l'application du.

Trouvé de savoir? Presque, mais tout nous cherchons cas

Tout d'abord, quand on website of lance dans le développement d'application of is of tombe sur les gros poissons, les gros Marcos font tout. Les Oubliez!

SenchaTouch va vous tuer: EC framework est tellement «ios - like ' than vous have plupart du temps tout casser pour tout reconstruire lorsque vous passerez votre application to the Android version. Listes Les font tout pour ressembler à du natif mais n'assurent juste pas in comparaison: le sliding rame, apprendre et les subtilites of the doc va vous prendre tout votre temps.

jQueryMobile est presque mais well, if vous votre application present vieux visez risque tout de même de commencer à ramer. The reason is simple:

jQueryMobile est gros!

Même après a custom build (at beta), il est encore assez gros, et puis il vous faut include court jQuery-tout aussi, ça ne ferait pas a peu "beaucoup".

D'un autre inconvénient jQueryMobile est qu'il handle pas mal le DOM when «improves» votre HTML pour le rendu des différents composants.

Well qu perpetrated recently Réduit la quantité of manipulations of EC type, cette operation est couteuse sur representations at a smartphone!

C'est ce qu il faut vous demander à chaque fois vous adds une librairie JavaScript à votre projet.

Zepto.js, for example, est une librairie JavaScript reprend les main fonctionnalités jQuery mais avec juste ce qu'il faut pour les mobile: il n ' est optimized pas pour les vieux Firefox ou IE. Il to l ' huge avantage d' être tout petit (25ko) et ne pas vous depayser if vous venez of jQuery.

Par contre vous aurez du mal à être efficace avec une application complete-JavaScript if vous ne pas complete templates them Zepto par un système de JavaScript. Cela je recommande mustache.js ou pour mieux handlebar:

Handlebar, more complete than mustache.js est un système de templates evolutif à base d'accolade. Il permet de Générer du code HTML à partir de données. Il peut Gérer listes les, conditions les et permet meme de ses propres define labels.

C ' est donc avec par ce libraries, Zepto et handlebars, 30ko au total, je suis le plus à l'aise. The concurrence est rude et d'autres mais Marcos source parler d'eux.

The nouvelle hype c ' est les Marcos MV *, pas des frames tout à fait MVC, mais s ' in inspirent. On trouve parmi ceux-ci les fameux Google AngularJS, Backbone.js et Ember.js

AngularJs et EmberJs relier d' améliorer le HTML avec des composants en and intégral d'un système template ressemblant of handlebar. ILS simplifient également la mise à jour des vues in temps reel, c ' est le fameux « two way data binding"."» De son Côté Backbone fait tout pour éviter cela, Considérant c ' est well pour le nécessaire dans de une demo mais pas «monde Réel», à vous de choisir.

NE ratez pas à ce sujet la AngularJS présentation organisée par CodeDarmor bientot tout le 22 Octobre prochain à Lannion.