GWT is for apps — right? But what's about static pages? (GWT's Future Plans...)

2011-08-06 Thread Mikhail Marenov
Google for GWTP or GWT Platform. It has crawler support. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/4XErh3QYXD4J. To post to this group,

Re: GWT is for apps — right? But what's about static pages? (GWT's Future Plans...)

2011-08-05 Thread Alexander Orlov
On Fri, Aug 5, 2011 at 6:07 AM, Nick Hristov nick.hris...@gmail.com wrote: You are going to generate page content on the browser which you will post on the server so that it can be loaded by the browser. Please read what I wrote! I wrote during *compile time*. And compile time is the time

Re: GWT is for apps — right? But what's about static pages? (GWT's Future Plans...)

2011-08-04 Thread Alexander Orlov
On Thursday, August 4, 2011 5:57:23 AM UTC+2, Nick Hristov wrote: If I am understanding you correctly, you want to have the server generate some html page content and the the embedded gwt module will A server-side approach that generates static snapshots of every — in a certain way

Re: GWT is for apps — right? But what's about static pages? (GWT's Future Plans...)

2011-08-04 Thread Jambi
But there could be also a compile time approach. That is,* during compile time the appropriate static snapshots could be generated* to represent a certain state of the app pre-filled with certain default values. This would be even a more elegant solution as the server don't need to be bothered

Re: GWT is for apps — right? But what's about static pages? (GWT's Future Plans...)

2011-08-04 Thread Alexander Orlov
On Thu, Aug 4, 2011 at 11:27 AM, Jambi michael.lukaszc...@googlemail.comwrote: I don´t think this is a good idea. The dynamic content, that should be crawlable, doesn´t exist at compile time. What I mean is that you should be able to annotate static parts of your app that might be relevant

Re: GWT is for apps — right? But what's about static pages? (GWT's Future Plans...)

2011-08-04 Thread Juan Pablo Gardella
Any gwt team member? 2011/8/4 Alexander Orlov alexander.or...@loxal.net On Thu, Aug 4, 2011 at 11:27 AM, Jambi michael.lukaszc...@googlemail.comwrote: I don´t think this is a good idea. The dynamic content, that should be crawlable, doesn´t exist at compile time. What I mean is that you

Re: GWT is for apps — right? But what's about static pages? (GWT's Future Plans...)

2011-08-04 Thread Alex Dobjanschi
http://code.google.com/web/ajaxcrawling/docs/getting-started.html -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/eSyQbMFsHaQJ. To post to this

Re: GWT is for apps — right? But what's about static pages? (GWT's Future Plans...)

2011-08-04 Thread Alex Dobjanschi
I just saw you already posted this link, sorry for that. As far as it goes, you're basically running Javascript code, in a (simple-to-complex) app, inside client code (browser sandbox). I don't how crawling such an app would be straightforward. -- You received this message because you are

Re: GWT is for apps — right? But what's about static pages? (GWT's Future Plans...)

2011-08-04 Thread Alexander Orlov
On Thu, Aug 4, 2011 at 3:11 PM, Alex Dobjanschi alex.dobjans...@gmail.comwrote: As far as it goes, you're basically running Javascript code, in a (simple-to-complex) app, inside client code (browser sandbox). I don't how crawling such an app would be straightforward. The apps parts of an app

Re: GWT is for apps — right? But what's about static pages? (GWT's Future Plans...)

2011-08-04 Thread dreamer
= static pages I tried to develop a page uisng UIBinder (mix of html and widgets) and RPC calls where it makes sense and ultimately I wanted to post entire page to server and let server serve next page. Here are My roadblocks for now * Not sure how to post entire page to servlet, develop

Re: GWT is for apps — right? But what's about static pages? (GWT's Future Plans...)

2011-08-04 Thread Nick Hristov
I am sorry, but this sounds insane. You are going to generate page content on the browser which you will post on the server so that it can be loaded by the browser. I still stand by my original approach. Generate the simple html content on the server, and let the browser load a GWT module which

GWT is for apps — right? But what's about static pages? (GWT's Future Plans...)

2011-08-03 Thread Alexander Orlov
GWT is a framework for building Ajax apps that act as clients and (optionally) communicate with a kinda RESTful backend via RPC or using RequestFactory (both are JSON based). That's my to the point understanding of GWT. But what's about static pages? To deliver static content, especially for

Re: GWT is for apps — right? But what's about static pages? (GWT's Future Plans...)

2011-08-03 Thread Karthik Reddy
I would like to make a related observation although, only tangentially related to the initial poster's questions and grievances: Even though GWT started off as a toolkit for developing desktop-style applications for the web, I think it has slowly transformed beyond the said scope. As an

Re: GWT is for apps — right? But what's about static pages? (GWT's Future Plans...)

2011-08-03 Thread Gal Dolber
GWT isn't the problem, you can easily make a non-CEO-friendly apps with jquery, sencha, or any other js framework. The problem is that search engines do not crawl AJAX apps yet. The proposal to make ajax crawlable is a quick solution to make them work with old crawling infrastructure. I really

Re: GWT is for apps — right? But what's about static pages? (GWT's Future Plans...)

2011-08-03 Thread Nick Hristov
What exactly do you hope to accomplish? If I am understanding you correctly, you want to have the server generate some html page content and the the embedded gwt module will make the page dynamic (I.e apply filters, next page, etc.) You can already do much of this functionality, its just not the