Hi there,
for a client of mine we replaced Tapestry 5 with our own rendering engine becoming a very own web framework.
With this framework all my long term hates about Tapestry are gone but most of the I love is still there. Now we thought
about going open source since this piece of sofware drives the new version of a commercial site (60+ countries).
The question is whats the point? I really do not know if the server sie model of developing a web application is still valid.
To give you an impression what Tapestry (and also this framework) is all about:
The model is a component based rendering engine where you define pages and components using Objects. Pages and
components consist of parts and of cause can have templates describing the HTML to create. Within the templates (or what ever)
you can specify parameters and maintain a global model being composed on the go using ModelProvider, which gives this
a reactive feeling.
The JavaScript part is composed by using GWT. It is mostly a single front side script that annotates and enhances the elements.
We currently go with bootstrap 3 and JQuery.
But now the question, do we care for this or is the time for classic HTML centric web sites almost over?
For example we started to reduce the server load by do not create HTML Ajax parts on the server side but put the logic on the client
by using client side templates and use REST calles directly. But we still have a server side component to create complete HTML
pages for the search engines.
In the end we will make the Webpage dynamic bu the initial HTML will be full constructed to avoid the HTML snapshot problem:
(https://developers.google.com/webmasters/ajax-crawling/).
So the question is, is such a web framework of any use and how will GWT 3.0 fit the picture? What are the new mobile components
when compared to anything like it. Is GWT 3.0 using phonegap or something?
Does anyone being interested in discussing this?
Cheers,
Martin (Kersten),
Germany
-- for a client of mine we replaced Tapestry 5 with our own rendering engine becoming a very own web framework.
With this framework all my long term hates about Tapestry are gone but most of the I love is still there. Now we thought
about going open source since this piece of sofware drives the new version of a commercial site (60+ countries).
The question is whats the point? I really do not know if the server sie model of developing a web application is still valid.
To give you an impression what Tapestry (and also this framework) is all about:
The model is a component based rendering engine where you define pages and components using Objects. Pages and
components consist of parts and of cause can have templates describing the HTML to create. Within the templates (or what ever)
you can specify parameters and maintain a global model being composed on the go using ModelProvider, which gives this
a reactive feeling.
The JavaScript part is composed by using GWT. It is mostly a single front side script that annotates and enhances the elements.
We currently go with bootstrap 3 and JQuery.
But now the question, do we care for this or is the time for classic HTML centric web sites almost over?
For example we started to reduce the server load by do not create HTML Ajax parts on the server side but put the logic on the client
by using client side templates and use REST calles directly. But we still have a server side component to create complete HTML
pages for the search engines.
In the end we will make the Webpage dynamic bu the initial HTML will be full constructed to avoid the HTML snapshot problem:
(https://developers.google.com/webmasters/ajax-crawling/).
So the question is, is such a web framework of any use and how will GWT 3.0 fit the picture? What are the new mobile components
when compared to anything like it. Is GWT 3.0 using phonegap or something?
Does anyone being interested in discussing this?
Cheers,
Martin (Kersten),
Germany
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment