Lot more data points now. Pattern is quite clear: everyone is either
migrated already or will migrate soon. Really increases my confidence
in 1.5.2 to see so many adopting it so quickly.
Until Google commissions a real scientific adoption rate survey
similar to the one Adobe did for Flash, this w
1) yes, for new projects
2) yes, for existing projects
3) yes
4) no
5) yes - unless 1.6 is ready and stable
6) no
7) 3 months
Moving off 1.4.62 depends on how fast I can re-implement/replace our
legacy use of MyGWT Widgets. I have replicated about
80% of our dependency with custom components that
Even though I'm still using this old version on production server, I'm
planning to switch soon; say in 2 weeks.
On 9/26/08, Ian Bambury <[EMAIL PROTECTED]> wrote:
> 1) Yes
> 2) No
> 3) N/A
> 4) No
> 5) Hope 1.6 is out
> 6) Already have
>
> I don't think I'll be using the present version of *anyth
1) Yes
2) No
3) N/A
4) No
5) Hope 1.6 is out
6) Already have
I don't think I'll be using the present version of *anything* in 4 years
time. My *marriage* didn't last that long.
Ian
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the G
1) yes - new and migrated projects
2) yes - but migrating as fast as possible
3) no - hope to be using 1.6+
4) no
5) no - unless the 1.6 dev cycle spins out of control
6) no
7) as soon as all of my current projects are migrated
-jason
On Sep 22, 2008, at 3:57 PM, John Gunther wrote:
>
> Trying
1. No
2. Yes
3. Yes
4. No
5. Hopefully not -- I'm hoping 1.6 will be released with OOPHM :-)
6. No
7. Depends how quickly we can rip out our usage of MyGWT :-(
On Sep 22, 2:57 pm, John Gunther <[EMAIL PROTECTED]> wrote:
> Trying to get a sense of how quickly the migration to GWT 1.5 from
> 1.4.62
Hi.
On Fri, Sep 26, 2008 at 07:40, reechard <[EMAIL PROTECTED]> wrote:
> Yes no yes no yes no now.
>
Same for me.
When I started to work with GWT at the beginning of this year, I
looked at version 1.4 and the trunk of 1.5. It was very quickly clear
to me, that I don't bother to start with 1.4, s
Yes no yes no yes no now.
--~--~-~--~~~---~--~~
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 ema
Thomas, walden, kozura
Since the official 1.5 was released only a few weeks back, I was
assuming most would not be using 1.5 yet. Kinda like IE6, I thought
1.4.62 would linger on for years. Seems I was very wrong.
A survey based on three data points isn't very significant, but it's
the best I've
Concur with Thomas, the ROI of generics and annotations with 1.5 made
switching a no-brainer even at M1, even for a fairly large project.
With a good IDE, coding productivity and bug rates are *vastly*
improved. 1.5 is quite stable now, but even when it wasn't, most
problems were point issues for
I just completed a "Big Bang" upgrade from 1.4.62 to 1.5. Since I
have exactly one GWT project, I'm done with 1.4 for good. I expect to
be using 1.5 exclusively for the next year (if I'm employed that
long).
My upgrade:
1. technical conversion (replacing libs and shaking out errors I
introduce
On 22 sep, 23:57, John Gunther <[EMAIL PROTECTED]> wrote:
> Trying to get a sense of how quickly the migration to GWT 1.5 from
> 1.4.62 will (or has already) occurred by asking:
>
> 1) Are you using GWT 1.5 right now?
Yes. We've been using 1.5 since M1 (with the hope that "1.5 GA" be out
before
Trying to get a sense of how quickly the migration to GWT 1.5 from
1.4.62 will (or has already) occurred by asking:
1) Are you using GWT 1.5 right now?
2) Are you using 1.4.62 right now?
3) Do you expect to be using GWT 1.5 six months from now?
4) Do you expect to be using GWT 1.4.62 six months f
13 matches
Mail list logo
