Hi Ümit,
thanks for your reply. It is a content centric site and seo is very important. What mades me curious is the creation of static html pages for SPAs. I experiment with using server side and client side similarities in composing the different versions of the very same application. SEO is quite important and SPAs we use for the admin application.
In the end I do not know how far one can go with the parallel aspect once GWT on the client side become almost as capable as the server side. It is a nice idea but I guess it is only suitable for default components driven by REST data, Issuing an asynchronous REST request on the server or client side should be quite similar including the simple display logic. Therefore a dynamic table, text elements and alike should be easeable doable. I have no idea if this makes actually sense but should reduce responsiveness by creating the html representation on the fly and saving a roundtrip to the server depending whether the REST call leaves the server or not. And maybe the rest result can be embedded within the HTML (script tag) to actually allow interactions with multi level data.
Does anyone have any experience with it?
Cheers,
Martin (Kersten),
Germany.
Am Montag, 20. Oktober 2014 16:28:49 UTC+2 schrieb Ümit Seren:
-- thanks for your reply. It is a content centric site and seo is very important. What mades me curious is the creation of static html pages for SPAs. I experiment with using server side and client side similarities in composing the different versions of the very same application. SEO is quite important and SPAs we use for the admin application.
In the end I do not know how far one can go with the parallel aspect once GWT on the client side become almost as capable as the server side. It is a nice idea but I guess it is only suitable for default components driven by REST data, Issuing an asynchronous REST request on the server or client side should be quite similar including the simple display logic. Therefore a dynamic table, text elements and alike should be easeable doable. I have no idea if this makes actually sense but should reduce responsiveness by creating the html representation on the fly and saving a roundtrip to the server depending whether the REST call leaves the server or not. And maybe the rest result can be embedded within the HTML (script tag) to actually allow interactions with multi level data.
Does anyone have any experience with it?
Cheers,
Martin (Kersten),
Germany.
Am Montag, 20. Oktober 2014 16:28:49 UTC+2 schrieb Ümit Seren:
Well there is definately an increasing trend to SPA (single page applications) and frameworks and fewer server side frameworks/apps.There is also a trend to encapsulated and interoperable components based on HTML itself (web-components).GWT is designed specifically to solve the problem of creating complex SPAs. It can also be used to enhance server side frameworks/rendering like jQuery but I think for that jQuery is the better fit.It also depends what kind of app you are going to develop. Is it a interactive web-application that SPA is probably the way to got. If it is more a conent centrict web-site (wordpress, CMS, blog, etc) where SEO is important, then probably a traditional server side framework (Tapestry, Spring MVC, etc) with some web 2.0ish jQuery enhancements is better.However also with SPA server side rendering is not totally out. React.js is a framework that allows you to combe the benefits of SPAs and server side rendering.
On Sunday, October 19, 2014 7:25:14 PM UTC+2, Martin Kersten wrote: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
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