similarities with GWT.
Once difference is jar files will be downloaded instead of JavaScript
module. Ultimate jnlp app
runs in local jvm and makes some socket calls to server.
for sure, JNLP addressed issue of client deployment. Though JavaScript
runs on browser and makes ajax calls,
I am not seeing web concentric approach. All these efforts are leading
to P2P approach.
If I have to compare web with network models , I would say it works
like a "start network model" that way we can avoid
any initial downloads, cache issues, script engine version issues (we
got lot many jvm version issues with JNLP).
Just like web page build with pure HTML pages, user experience should
be same, no version issues, dll conflicts nothing.
I would even go one step forward and ask why "java to javascript"
compilation , why not
"java to 'html+javascript'" compilation ? ( javascript for ajax).
DOM api should be able to generate HTML directly, where there is no
dynamic refresh, we don't need JavaScript.
- venu
- http://schoolk12.appspot.com/
On Jul 30, 6:24 am, dreamer <venugopal.vasire...@gmail.com> wrote:
> Very good point. I have gone through same thought process.
> After using designer to build composites (html pages), I came to
> conclusion that this is what I want to build my web sites with.
>
> Just drag and drop widgets and build pages, Yes we got new world for
> page design and development, but web is
> highly distributed network, it can never become thick client
> application which just makes jdbc calls to server, or some thing like
> that.
>
> I was fascinated by JSF and its Idea, but it my fascination faded down
> slowly after struggling few weeks.
> But not with GWT and App engine.
>
> I found what I am looking for, thing is how to make these better, so
> that we can build more complex enterprise apps without much re-
> engineering.
>
> - venu
> - http://schoolk12.appspot.com/
>
> On Jul 30, 12:38 am, Alain Ekambi <jazzmatad...@googlemail.com> wrote:
>
>
>
>
>
>
>
> > Then what just you dont use JSP or JSF then ?
> > GWT follows a different paradigm then those technologies.
> > I just cant see the benefit of similutationg JSP with GWT
>
> > 2011/7/30 dreamer <venugopal.vasire...@gmail.com>
>
> > > What if we need to port very complex web app with 100's of jsp/html
> > > pages into GWT ?
>
> > > Yes. swing and gwt got lot of similarities. But loosing web advantages
> > > being on web may be not cool.
> > > yep Swing is Forms flow with thick client nature. There is a huge
> > > paradigm shift between these two worlds.
> > > as per my understanding GWT is trying to simulate thick client (yep
> > > swing) where all the forms/pages
> > > are at client and makes rpc to create Models thus MVP to refresh GUI.
>
> > > My thought is to preserve the thin client nature, when you are getting
> > > completely new page,
> > > just make URL / URI call to load javascript component. Server serves
> > > Model and View, on client presenter
> > > can update view, before rendering GUI. this way application stays very
> > > light weight , just like HTML pages,
> > > I beleive complex application with hundereds of jsp/html pages can be
> > > easily ported into GWT. sure AJAX reduces # of pages.
> > > but not down to one or two pages.
>
> > > Partial refreshes will will be done as usual.
>
> > > - venu
> > > - http://schoolk12.appspot.com/
>
> > > On Jul 29, 7:34 am, Juan Pablo Gardella <gardellajuanpa...@gmail.com>
> > > wrote:
> > > > Is swing applications pageflow? I think not. Perhaps you can look at
> > > > architecture proposed in ProGWT
> > > > book<
> > >http://books.google.com/books?id=OG816JSZYVcC&printsec=frontcover&dq=...>
> > > > .
> > > > In this architecture you don't need use a whole page.
>
> > > > 2011/7/29 dreamer <venugopal.vasire...@gmail.com>
>
> > > > > Hi,
>
> > > > > I want to start a new opensource project - "GWT page flows" - similar
> > > > > to struts.
>
> > > > > With my moderate GWT knowledge, I did not find any way to weave
> > > > > application with pages, though components are there.
>
> > > > > Not all ajax applications are single page apps.
>
> > > > > Here are my thoughts from very high level -
> > > > > ===================================================
> > > > > Use composites (widgets) as pages - build using designer.
> > > > > Weave all these pages with the help of something like "struts-
> > > > > config.xml".
> > > > > ======================================================
> > > > > It would have been great if GWT compilation is component by component
> > > > > more transparently. Some thing under the hood is happening on these
> > > > > lines. Even loading javascript into browser would have happened page
> > > > > by page, only when it is needed.
>
> > > > > Few questions:
>
> > > > > Is it possible to build page flow on the above lines using GWT as is?
> > > > > Are these features available in any other form, that I did not
> > > > > realize? (UiBinder seems slightly different than I want)
>
> > > > > Just I would like to brainstorm. Please share your thoughts.
> > > > > - venu
> > > > > - http://schoolk12.appspot.com/
>
> > > > > --
> > > > > You received this message because you are subscribed to the Google
> > > Groups
> > > > > "Google Web Toolkit" group.
> > > > > To post to this group, send email to
> > > google-web-toolkit@googlegroups.com.
> > > > > To unsubscribe from this group, send email to
> > > > > google-web-toolkit+unsubscribe@googlegroups.com.
> > > > > For more options, visit this group at
> > > > >http://groups.google.com/group/google-web-toolkit?hl=en.
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "Google Web Toolkit" group.
> > > To post to this group, send email to google-web-toolkit@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > google-web-toolkit+unsubscribe@googlegroups.com.
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-web-toolkit?hl=en.
>
> > --
>
> > GWT API for non Java based platformshttp://code.google.com/p/gwt4air/http://www.gwt4air.appspot.com/
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment