Re: GWT Advice

2013-02-15 Thread Lehel
That is a good solution...
And you will have one webserver that runs your server side application, for 
different type of devices? Clients using laptop, mobile, desktop or I do 
not know what(application written in other languages), will achieve the 
same server side implementation? In this case, a webservice could be an 
elegant answer. I do not entered in details in such cases, but I think if 
you have database operation, and you have a webservice that communicates 
with your db, you should find a solution for connection persistence, like 
using DAO design pattern, or in case of servlets using connection pool...

Anyway, MySql database supports, as I know, stored procedures too For 
me it means, that I can have all the database operations, queries on sql 
server, and all the transaction handlings written in stored 
procedures...And the server side implementation just call these functions 
and serves the answers to client.Thinking in a multi tier arhitecture is 
always a good point...What do you think?

thx,
Lehel Sipos


2013. február 14., csütörtök 13:39:14 UTC+1 időpontban Tim Hill a 
következőt írta:

 Wow - thanks for all the pointers guys! :)

 Regarding the offline/online/syncing, I was hoping to implement a solution 
 using a PHP 'bridge' on the server side between the webapp and a mysql 
 backend - I have read that this is possible (restygwt?).

 I have also come to the conclusion that I will need three different UI 
 formats (desktop, tablet and mobile) that reference a single logic 
 implementation.

 I will have a shift at the links provided and see how I get on - thanks 
 for the offers of further help also!

 Cheers

 Tim

 On Tuesday, 12 February 2013 11:40:13 UTC, Tim Hill wrote:

 Hi,

 A friend and I are about to embark on developing and web application and 
 from what we have read/seen, GWT appears to be the most versatile. The 
 requirements for the project are as follows:

- Platform agnostic
- Both server and client side storage (database) with syncing
- Mobile support
- Write it once (very nice to have)

 Before beginning however, I want to make sure that we are choosing the 
 correct development platform. I have also come across things like phonegap, 
 GWT-mobile and MGWT and it is these that I am slightly confused about - 
 which one(s) should we use, for example. What is the best way to integrate 
 them into the main GWT application?

 If somebody would be kind enough to take the time to guide us in the 
 right direction, it would be greatly appreciated!

 Cheers

 Tim



-- 
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+unsubscr...@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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: GWT Advice

2013-02-14 Thread Lehel
Hi

  I think GWT is a  good choice, you can have both client and server side 
programming with it, and runs on any platform.
But my oppinion is that for mobile you should choose other technology like 
Codename one, especially if you would like to have true native 
applicationsI think a whole web site, that runs in a desktop browser, 
can be very hard navigating in a mobile phone, with same UI. I mean you 
should plan anyway at least 2 UI-interface, one for desktop, and one for 
mobiles, indifferent what technology you use.

1. Having MGWT is a good choice for mobile, but:
-if you have server side communication(gwt-rpc), you must use Phonegap too 
with mgwt(becuase GWT version compatibiliy). It is not a problem, but it 
means your server side arhitecture is also will have 2 implementations, one 
for desktop and one for mobiles...kind of.
-you will have anyway 2 UI-interface (gwt for desktop, mgwt for moible)

2. You could have SmartGwt (mobile) to implement your proiect, because it 
says:
-their cilent side widgets is compatibile with desktop and mobile and yout 
don't have to write twice the UI-interface, also they a SmartGWT.mobile 
widgetset too
-also you can use the server side programming in SmartGWT, writing just 
once and runnig also in desktop and mobile (even gwt-rpc, but they does not 
recommend, instead using their datasource soulution which is not free)
-a small problem with SmartGWT what you will face, that though you will 
have one UI interface, does not look so good in mobiles as in desktops, and 
the functionlaity should be tested. And of course native access you don't 
have, like Camera, File, Contacts, Geolocation...in smartgwt.

So my oppinion is in short, for web pages, web applications on desktop use, 
GWT, SmartGwt or Gxt, or even JavaFx...but for mobiles don't write a whole 
website or webapplication, they have smaller screen, smaller memory, cpu, 
and whatever. There are a plenty of technologies in other languages too, 
which are better to use for mobile, they are sharp-edged to every problem 
what you face in case of mobiles. For example Codename one has the write 
once and run at any mobile platofrm concept, programming in java. Codename 
one has a WebBrowser component what you can use to navigate to a web page, 
if you want. But I think when you deal with server side data, your moubile 
UI.interface should be simple, easly handling and good looking...
For desktop applications, use java swing

With regards,
Lehel Sipos

2013. február 12., kedd 12:40:13 UTC+1 időpontban Tim Hill a következőt 
írta:

 Hi,

 A friend and I are about to embark on developing and web application and 
 from what we have read/seen, GWT appears to be the most versatile. The 
 requirements for the project are as follows:

- Platform agnostic
- Both server and client side storage (database) with syncing
- Mobile support
- Write it once (very nice to have)

 Before beginning however, I want to make sure that we are choosing the 
 correct development platform. I have also come across things like phonegap, 
 GWT-mobile and MGWT and it is these that I am slightly confused about - 
 which one(s) should we use, for example. What is the best way to integrate 
 them into the main GWT application?

 If somebody would be kind enough to take the time to guide us in the right 
 direction, it would be greatly appreciated!

 Cheers

 Tim


-- 
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+unsubscr...@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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: GWT Advice

2013-02-14 Thread Lehel
Sorry, I forget about SmartGWT

SmartGWT.mobile supports packaging with PhoneGap to create installable 
native applications that have access to on-device resources such as the 
user's address book or photos. 


2013. február 12., kedd 12:40:13 UTC+1 időpontban Tim Hill a következőt 
írta:

 Hi,

 A friend and I are about to embark on developing and web application and 
 from what we have read/seen, GWT appears to be the most versatile. The 
 requirements for the project are as follows:

- Platform agnostic
- Both server and client side storage (database) with syncing
- Mobile support
- Write it once (very nice to have)

 Before beginning however, I want to make sure that we are choosing the 
 correct development platform. I have also come across things like phonegap, 
 GWT-mobile and MGWT and it is these that I am slightly confused about - 
 which one(s) should we use, for example. What is the best way to integrate 
 them into the main GWT application?

 If somebody would be kind enough to take the time to guide us in the right 
 direction, it would be greatly appreciated!

 Cheers

 Tim


-- 
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+unsubscr...@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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: GWT Advice

2013-02-14 Thread Tim Hill
Wow - thanks for all the pointers guys! :)

Regarding the offline/online/syncing, I was hoping to implement a solution 
using a PHP 'bridge' on the server side between the webapp and a mysql 
backend - I have read that this is possible (restygwt?).

I have also come to the conclusion that I will need three different UI 
formats (desktop, tablet and mobile) that reference a single logic 
implementation.

I will have a shift at the links provided and see how I get on - thanks for 
the offers of further help also!

Cheers

Tim

On Tuesday, 12 February 2013 11:40:13 UTC, Tim Hill wrote:

 Hi,

 A friend and I are about to embark on developing and web application and 
 from what we have read/seen, GWT appears to be the most versatile. The 
 requirements for the project are as follows:

- Platform agnostic
- Both server and client side storage (database) with syncing
- Mobile support
- Write it once (very nice to have)

 Before beginning however, I want to make sure that we are choosing the 
 correct development platform. I have also come across things like phonegap, 
 GWT-mobile and MGWT and it is these that I am slightly confused about - 
 which one(s) should we use, for example. What is the best way to integrate 
 them into the main GWT application?

 If somebody would be kind enough to take the time to guide us in the right 
 direction, it would be greatly appreciated!

 Cheers

 Tim


-- 
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+unsubscr...@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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: GWT Advice

2013-02-13 Thread Ashton Thomas
At a very high-level I think you need to start with the offline data issue 
and define exactly what your requirements are for supporting offline.
- I haven't had a chance to go through all of this but may help
+ http://www.youtube.com/watch?v=Oic22dQMRXQ
- Also, I think we are in a critical time for finalizing flexible/powerful 
standards for supporting offline via the web
+ You will have to do a bit more research here

Since you want to be platform agnostic, GWT is great (GWT is awesome 
regardless)
- The GWT community needs to do a better job of providing great resources 
for getting up and running
+ there are many challenges but it's still a huge drawback (having a big 
learning curve)
+ I am trying to do my part and put together some resources for getting up 
and running (so feel free to reach out to me and I can provide my resources)
++ Although there is never a one size fits all or standard convention for 
doing everything - many technologies and different solutions
++ GWT is a toolkit so you have to build up your solutions completely 
dependent on our app's needs

GWT is awesome for mobile
- I have built my own app specific framework for mobile and I love it (but 
it took a lot of thought and effort)
- MGWT is referenced a lot (close tie to PhoneGap)
- http://www.netmagazine.com/features/app-cloud-vs-phonegap-web-developer-s-view

Overall, there are some significant start-up costs. If you have the time 
and will power it will be worth it.

I would highly recommend going the GWT route but caution that it is not 
easy (but it's awesome) 


On Tuesday, February 12, 2013 6:40:13 AM UTC-5, Tim Hill wrote:

 Hi,

 A friend and I are about to embark on developing and web application and 
 from what we have read/seen, GWT appears to be the most versatile. The 
 requirements for the project are as follows:

- Platform agnostic
- Both server and client side storage (database) with syncing
- Mobile support
- Write it once (very nice to have)

 Before beginning however, I want to make sure that we are choosing the 
 correct development platform. I have also come across things like phonegap, 
 GWT-mobile and MGWT and it is these that I am slightly confused about - 
 which one(s) should we use, for example. What is the best way to integrate 
 them into the main GWT application?

 If somebody would be kind enough to take the time to guide us in the right 
 direction, it would be greatly appreciated!

 Cheers

 Tim


-- 
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+unsubscr...@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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: GWT Advice

2013-02-13 Thread Rob
Hi,

- GWT (e.g. deferred binding, declarative UI, ...)
- GWTP (MVP, form-factor support), Gin and Guice (dependency injection)
- UI, you have several options: GWT, mgwt (mobile/tablet form-factors), GXT 
(desktop form-factor), smart GWT, ...
- Restlet: it has GWT support (as does RestyGWT)

GWT + mgwt = web application
GWT + mgwt + gwt-phonegap = mobile application 

- http://gwt-cx.com/mgwt-basic-project/index.html - mgwt Showcase (that 
uses gwt-platform)

If you need to support different UI toolkits (e.g. mgwt for mobile/tablet 
and GXT for desktop) then I would suggest you take a look at this post re 
UiHandlers:
- http://uptick.com.au/content/working-gwt-platforms-mvp-and-uihandlers

Some interesting posts:
- http://uptick.com.au/content/gwt-and-smartgwt-best-practices (with lots 
of good links to related posts)
- http://uptick.com.au/content/getting-started-gwt-maven-and-eclipse

Some good GWT books:
- http://www.manning.com/tacy/ - GWT in Action - Second Edition
- 
https://www.packtpub.com/google-app-engine-java-and-gwt-application-development/book
 
- GWT, GAE
- http://www.manning.com/louvel/ - Restlet in Action

Cheers
Rob

Kiahu.com

-- 
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+unsubscr...@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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.