[gwt-contrib] Re: GWT 2 Roadmap as it applies to future deprecations

I'd welcome a separate discussion about a backward compatibility contract, but clearly we have to contrast the "technically Java 8 is supported" with "realistically, any project that uses standard up-to-date tools can't use Java 8 by the end of 2023". We support _end users_ to the extreme, as

[gwt-contrib] Re: GWT 2 Roadmap as it applies to future deprecations

My 2 cents: We also have quite a few projects here based on GWT, still running DevMode on Java 1.8 I am afraid. Like everyone else sharing the same fate, we are struggling to upgrade to Java 11 which seems to be the next sensible move. Yet, the world is being indirectly and inevitably forced to

[gwt-contrib] Re: GWT 2 Roadmap as it applies to future deprecations

We have a project here that uses GWT for all its web UI and is still running Java 1.8. The SAP JVM 8 will be supported at least until 2030. According to https://newrelic.com/resources/report/2022-state-of-java-ecosystem in April 2022 still close to half of the projects (46%) were using Java

Re: [gwt-contrib] GWT 2 Roadmap as it applies to future deprecations

On Thu, Aug 4, 2022 at 5:05 AM Colin Alworth wrote: > > > If there’s one thing that GWT has tried to be consistent about, it is > retaining support for technologies past their “best by” dates. This is a > sore point from time to time, as it makes the tooling feel dated even right > after a

Re: [gwt-contrib] GWT 2 Roadmap as it applies to future deprecations

My 2¢ worth  is that it would be good to have a split path with both a branch (GWT 2.10.x) for only security updates and misc fixes as a bug fix only *LTS* and also a current *Stable* branch (GWT 3.x)  that implements new language features and tracks with most recent Java LTS. This is

Re: [gwt-contrib] GWT 2 Roadmap as it applies to future deprecations

Thanks to everyone for their insights. By my count, 25% of the replies have at least some use for Java 8 yet, so as the example that all responders latched on to, it seems unlikely that the time has come to drop support for it, at least in production deployments (a useful distinction that Jens

Re: [gwt-contrib] GWT 2 Roadmap as it applies to future deprecations

In my case we have different codebases that overlap with reusable components. Not all projects are willing to invest in a newer jdk since they are basically in maintenance mode. If GWT would drop Java 8 it would be a problem. On the other hand, maybe it will finally force people to move on

Re: [gwt-contrib] GWT 2 Roadmap as it applies to future deprecations

Same here. It's time to move forward. Java 8 and IE 11 should be dropped. In case someone will stay with Java 8 he can use GWT 2.10.0. I'll expect new versions of GWT will - in many cases - bring new language features. So, someone staying with Java 8 is not interested in updating. stockiNail

Re: [gwt-contrib] GWT 2 Roadmap as it applies to future deprecations

In my opinion, my 2 cents, the support of JAVA 8 and IE11 should be dropped because very close to be obsoleted. Whoever is using these platforms could stay on current version of GWT where they are supported. I still have some applications based on Java 8 but they will remain with GWT 2.8.2 and

Re: [gwt-contrib] GWT 2 Roadmap as it applies to future deprecations

My company is also migrating everything to JDK 17. The less opportunity for bitrot in future versions, the better. On Sat, Aug 6, 2022 at 11:06 AM Manfred Tremmel wrote: > In my company Java 8 was dropped long ago, at the moment the migration > from > Java 11 to 17 is in progress. So from my

Re: [gwt-contrib] GWT 2 Roadmap as it applies to future deprecations

We have been using Java 17 for some time now. But I think a policy of supporting the two most recent LTS (11, 17) would be fair. In September 23 that would become (17, 21). On Sat, Aug 6, 2022 at 11:14 AM eliasbala...@gmail.com < eliasbala...@gmail.com> wrote: > My 2 cents. > > I am afraid some

Re: [gwt-contrib] GWT 2 Roadmap as it applies to future deprecations

My 2 cents. I am afraid some teams, like ours, are still using Java8 looking for the next opportunity to move to Java11. Perhaps, Java8 shouldn't be dropped yet. On Saturday, 6 August 2022 at 16:06:28 UTC+1 ManfredTremmel wrote: > In my company Java 8 was dropped long ago, at the moment the

Re: [gwt-contrib] GWT 2 Roadmap as it applies to future deprecations

In my company Java 8 was dropped long ago, at the moment the migration from Java 11 to 17 is in progress. So from my side, let's cut off the old stuff. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and

[gwt-contrib] Re: GWT 2 Roadmap as it applies to future deprecations

I think first we should put a good Java version policy into place. Personally I would split this policy into two policies. One for client code (Compiler) and one for shared/server code. For client code GWT has two main dependencies: Eclipse JDT and Jetty. So I would define the minimum required

[gwt-contrib] GWT 2 Roadmap as it applies to future deprecations

If there’s one thing that GWT has tried to be consistent about, it is retaining support for technologies past their “best by” dates. This is a sore point from time to time, as it makes the tooling feel dated even right after a release, but it has some specific advantages with regards to

Re: GWTReact Release and Roadmap

Yes, I think you would need a good immutable collection library to make Redux work well from Java. In our application we are just using React State. This works fine because we are replacing relatively small isolated parts of our application currently (1 or 2 connected screens at the most).

Re: GWTReact Release and Roadmap

Side question: I can imagine that the lack of object spread probably makes Redux a bit annoying to use from Java. Yet, if you are not using neither Redux nor MobX, how are you managing your state? On Monday, May 1, 2017 at 3:48:51 PM UTC+3, Paul Stockley wrote: > > I agree both Redux and MobX

Re: GWTReact Release and Roadmap

I agree both Redux and MobX are both pretty stable. The decision was more a reflection on the current state of the GTWReact projects. I would say both are really proof of concepts at this stage. Redux in particular would really need interfaces building to the common middleware to be really

Re: GWTReact Release and Roadmap

Great work. We are just starting down the path of React+GWT and glad to see the project moving forward On Sun, Apr 30, 2017 at 10:27 PM, Paul Stockley wrote: > I have just released a new version of the GWTReact > projects to support GWT 2.8.1

Re: GWTReact Release and Roadmap

For what it's worth, as a Redux maintainer I can assure you that Redux is very stable and not going to meaningfully change (at least at the API level) from here on out :) On Sunday, April 30, 2017 at 8:27:10 AM UTC-4, Paul Stockley wrote: > > I have just released a new version of the GWTReact

GWTReact Release and Roadmap

I have just released a new version of the GWTReact projects to support GWT 2.8.1 As of this release, I will no longer be maintaining the MobX and Redux projects. Our company is not using them currently and I don't have the time to keep them updated. In the future,

Re: Roadmap Question for GWT 3.0

+1: RPC is one of GWT's strong suits. Haven't seen another web-oriented (de-)serialization mechanism that handles polymophism, generics and bidi relations without config or pain. Doesn't litter your domain classes with non-standard annotations or dependencies. AnyGWT 3.0 alternative should be

Re: Roadmap Question for GWT 3.0

Maybe there is effectively going to be a fork? So if the interest was there could be GWT 2.9 - GWT 2.123 I think that might represent the truth that there is one user base that wants to build Java apps that happen to run in a browser vs users who are working on products that need to squeeze

Re: Roadmap Question for GWT 3.0

I'm puzzled as to what the disadvantages could be of GWT Widgets. They are, after all, translated to efficient JavaScript and allow full use of the browser. I can see that some developers might want to integrate with JavaScript frameworks, but others, like me, start writing applications in pure

Re: Roadmap Question for GWT 3.0

I can see the logic of GWT 3.0. The browser has evolved a lot since GWT was first designed. Back in those days every browser had significant quirks and the lowest common denominator was very low. In 2015 there is less reason for a big layer between domain code and the browser. I think the same

Re: Roadmap Question for GWT 3.0

+1 I think the division of GWT-compiler and GWT-widgets is the right thing to do. The web-platform is moving fast and to GWT has to adopt to stay relevant. Webcomponents have the potential to become the new widgets and the new JSInterops will make it quite easy to consume webcomponents that are

Re: Roadmap Question for GWT 3.0

If you just want to run java apps in the browser there are solutions out thtere Free: http://www.webswing.org Paying: http://www.creamtec.com/products/ajaxswing/overview.html Now if you want to run create webapps then it is another matter. For me the web stack is a crazy platform. But still since

Re: Roadmap Question for GWT 3.0

On Monday, October 19, 2015 at 12:22:19 PM UTC+2, Jens wrote: > > >> * Stick with 2.x and risk being left behind and the project becoming >> neglected due to split effort. >> > > You are not behind when using 2.x: > > GWT 2 = GWT 2.x Compiler + JsInterop + Elemental 1 + Elemental 2 when >

Re: Roadmap Question for GWT 3.0

Somehow people seem to forget that they don't have to migrate at all if its not profitable. Just stay on GWT 2.8.x and only start new projects with new technology. There will be plenty of companies that have huge apps that will not be rewritten anytime soon (if at all) so IMHO GWT 2.8.x will

Re: Roadmap Question for GWT 3.0

I'm trying to understand my options. * Stick with 2.x and risk being left behind and the project becoming neglected due to split effort. * Try to migrate to 3.x and possibly throw away a big investment. * Look to move to something other than GWT. Obviously we will also be taking action to

Re: Roadmap Question for GWT 3.0

> > > * Stick with 2.x and risk being left behind and the project becoming > neglected due to split effort. > You are not behind when using 2.x: GWT 2 = GWT 2.x Compiler + JsInterop + Elemental 1 + Elemental 2 when released + all current GWT SDK code + all GWT libraries. GWT 3 = J2CL +

Re: Roadmap Question for GWT 3.0

Actually what makes sense for me in an after split era is * compile with the newest GWT 3.5, 4, 5 to pick up new features * link with legacy but compatible gwt-widgets until I can gradually get rid of them - or not. This way I can migrate step by step my application (widget per widget) and stay

Re: Roadmap Question for GWT 3.0

I'm eager for GWT 2.8 because of Lambda support, but I can't see that my company will ever use GWT 3.0 if what you write is true. We have products that make substantial use of GWT Widgets, and there is no prospect of re-writing to some other system. GWT without the Widgets just isn't GWT -

Re: Roadmap Question for GWT 3.0

Thanks Thomas, For my own use I'm going to keep a list of what I think I know http://salk31.blogspot.co.uk/2015/10/gwt-30-migration.html corrections welcome. I can see why they want to reduce the scope of GWT and integrate (not build) but is such a high quality complete package in 2.7 it is a

Re: Roadmap Question for GWT 3.0

Is there a guide somewhere of migration path to 3.0 per feature? I've been trying to follow these threads but I'm still not sure on the future of things like RequestFactory and Editor. They heavily depend on GWT.create and the latter depends on Widgets, are they really going away? We have a

Re: Roadmap Question for GWT 3.0

I think nobody has such information yet; not even Google who are pushing for the change. They do have many apps that use widgets and RPC today (example: Google Groups, the exact app I'm typing this message into) and will need to come up with a migration path for those apps too. On Friday,

Re: Roadmap Question for GWT 3.0

It was process but we ported everything to the low level RequestBuildner.and json. Now we have just one timer in the UI a huge reduction from the async nature of RPC. In our situation we render everything out of a DataDictionary on the server side and use a Frame for the results, The GUI is

Roadmap Question for GWT 3.0

Where can I read that GWT RPC and widget system will be dropped with GWT 3.0? Is there a presentation / doc online? And what does it mean that GWT.create will be dropped? And: really dropped or set as deprecated? -- You received this message because you are subscribed to the Google Groups

Re: Roadmap Question for GWT 3.0

Where can I read that GWT RPC and widget system will be dropped with GWT 3.0? Is there a presentation / doc online? And what does it mean that GWT.create will be dropped? And: really dropped or set as deprecated? GWT 3.0 drops support for JSNI and GWT.create(). JSNI will be replaced

Re: Roadmap Question for GWT 3.0

Thank you for your answer Jens. So much GWT solutions build on widget system so I think there will be a port/solution (thinking about the new GWT Material Project which was startend a view months ago...). @Ed: so you use a REST service on backend? Seems also for us a good solution but

Re: Roadmap Question for GWT 3.0

Both gwt-jackson (https://github.com/nmorel/gwt-jackson/wiki/Type-support) and restygwt (resty-gwt.github.io/documentation/restygwt-user-guide.html) supports polymorphism (and gwt-jackson in addition generics)! gwt-rpc is nice at the beginning (fast learning curve), but hurts later on -

Re: Roadmap Question for GWT 3.0

is dagger + ... an alternative to gwt-rpc? Dagger is an injection library like google-gin with the difference that it uses annotation processors instead of GWT.create(). It has nothing to do with gwt-rpc. -- You received this message because you are subscribed to the Google Groups

Re: Roadmap Question for GWT 3.0

I cannot disagree more. Restful, as far as I understand, does not replace gwt-rpc as it does not provide polymorphism. It might be an issue with the current implementations I had a look - can someone tell me some implementation that can handle object graphs and polymorphism as gwt-rpc does?

Re: Roadmap Question for GWT 3.0

Is there any downside to Request Builder? Possible deprecation in GWT 3.0? Well the internally used XMLHttpRequest / Timer classes would need to be ported to JsInterop of course because they use JSNI. There are some general to consider with RequestBuilder as well: - It is quite low level -

Re: Roadmap Question for GWT 3.0

@jens Is there any downside to Request Builder? Possible deprecation in GWT 3.0? Best Regards Ed On Mon, Jun 29, 2015 at 1:43 PM, Ed ej19...@gmail.com wrote: Thanks Jens, Great response, gives our devs something to learn. On Mon, Jun 29, 2015 at 12:55 PM, Jens jens.nehlme...@gmail.com

Re: Roadmap Question for GWT 3.0

In addition to what Jens said: If possible, go Restful. it makes it much easier to later add non-GWT clients and also forces you to think about your domain model as resources (might lead to a clean API). I guess once Elemental 2.0 is released (AFAIK along the lines with GWT 3.0) you could

Re: Roadmap Question for GWT 3.0

@jens @umit Thank you very much for this insight. Best Regards Ed On Tue, Jun 30, 2015 at 9:44 AM, Ümit Seren uemit.se...@gmail.com wrote: In addition to what Jens said: If possible, go Restful. it makes it much easier to later add non-GWT clients and also forces you to think about your

Roadmap Question for GWT 3.0

If I wanted to start now for the the GWT 3.0 release, what would be the best mechanism to replace: 1. GWT.create 2. RPC We starting a refactor of existing code, and would like some foresight into this matter. Thanks Ed -- You received this message because you are subscribed to the Google

Re: Roadmap Question for GWT 3.0

1. GWT.create generate-with: Annotation processors replace-with: Dagger 2.x + AutoFactory (assisted inject) for injection and System.getProperty() to build the Dagger dependency graph based on your deferred binding properties. For Dagger I created a pull request that generates a dagger-gwt

Re: Roadmap Question for GWT 3.0

Thanks Jens, Great response, gives our devs something to learn. On Mon, Jun 29, 2015 at 12:55 PM, Jens jens.nehlme...@gmail.com wrote: 1. GWT.create generate-with: Annotation processors replace-with: Dagger 2.x + AutoFactory (assisted inject) for injection and System.getProperty() to

Re: GWT 3.0 Roadmap?

I believe 2.8 will be first: http://gwtcreate.com/videos/index.html#keynote /Brian Den onsdag den 17. september 2014 kl. 16.07.14 UTC+2 skrev Martin Kersten: Hi There, I am wondering what the current status of GWT 3.0 is. Is it already in the making? Are there any release dates for GWT

Re: GWT 3.0 Roadmap?

Next release will be called 2.8. Meeting minutes of the Steering group regarding the release: https://docs.google.com/document/d/1g6Ro3RbrOlD4RxqtWUv86wwXVSyD0uSFOO3-LnR9mGc/edit -- J. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To

Re: GWT 3.0 Roadmap?

Uh, the year is not soo early any more. Any news on GWT 3.0 release plans? On Monday, September 22, 2014 at 10:34:26 AM UTC+2, Jens wrote: GWT 3.0 will be early next year with Java8 language support. Before that GWT 2.7 RC1 is planed to be release at the end of this month...but could also

Re: 2.7.0 Release Roadmap

Excellent JS Interop is such a big step forward. On Sunday, October 26, 2014 7:56:02 PM UTC, Oleg Cohen wrote: Greetings, Now that GWT 2.7.0-beta1 is out, I was wondering if there is a roadmap for the 2.7.0 GA Release? Thank you! Oleg -- You received this message because you

Re: 2.7.0 Release Roadmap

On Sunday, October 26, 2014 8:56:02 PM UTC+1, Oleg Cohen wrote: Greetings, Now that GWT 2.7.0-beta1 is out, I was wondering if there is a roadmap for the 2.7.0 GA Release? It'll be ready when it's ready You can find a list of remaining actions before release: https://docs.google.com

Re: 2.7.0 Release Roadmap

Thank you very much for the info! Looking forward to trying out RC1. On Monday, October 27, 2014 5:34:39 AM UTC-4, Thomas Broyer wrote: On Sunday, October 26, 2014 8:56:02 PM UTC+1, Oleg Cohen wrote: Greetings, Now that GWT 2.7.0-beta1 is out, I was wondering if there is a roadmap

2.7.0 Release Roadmap

Greetings, Now that GWT 2.7.0-beta1 is out, I was wondering if there is a roadmap for the 2.7.0 GA Release? Thank you! Oleg -- 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

Re: GWT 3.0 Roadmap?

No comment noone knows? Any idea how I can optain this information? Am Mittwoch, 17. September 2014 16:07:14 UTC+2 schrieb Martin Kersten: Hi There, I am wondering what the current status of GWT 3.0 is. Is it already in the making? Are there any release dates for GWT 3.0 - Beta, Mx or

Re: GWT 3.0 Roadmap?

GWT 3.0 will be early next year with Java8 language support. Before that GWT 2.7 RC1 is planed to be release at the end of this month...but could also be next month. GWT 2.7 will have CSS3 support, an experimental version of JsInterop and a faster, easier to set up SuperDevMode (and bug fixes

GWT 3.0 Roadmap?

Hi There, I am wondering what the current status of GWT 3.0 is. Is it already in the making? Are there any release dates for GWT 3.0 - Beta, Mx or RC1? Cheers, Martin (Kersten) -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To

Re: GWT Runtime Plugins - Is it on the Roadmap?

On Wednesday, April 2, 2014 6:07:53 PM UTC+2, Thanos wrote: I just read this: The goal for 2.7 is to have incremental compilation (that will tremendously speed up Super Dev Mode) and a beta of JsInterop (and remove support for IE6/7, and maybe deprecate support for IE8). Would it be

Re: GWT Runtime Plugins - Is it on the Roadmap?

was wondering if GWT Runtime Plugins are on the roadmap yet? We have GWT compile time plugins working quite nicely, each plugin is a maven module. After the number of plugins gets large, this really starts to bog down the compiler. So it would be great if plugins where pre-compiled and linked

GWT Runtime Plugins - Is it on the Roadmap?

I was wondering if GWT Runtime Plugins are on the roadmap yet? We have GWT compile time plugins working quite nicely, each plugin is a maven module. After the number of plugins gets large, this really starts to bog down the compiler. So it would be great if plugins where pre-compiled

Re: Roadmap

On Monday, August 26, 2013 10:58:11 PM UTC+2, Michael Prentice wrote: *GWT-Ext has been superseded by Smart GWT. Smart GWT is an open source (LGPL), GWT-based framework that allows you to not only utilize its comprehensive widget library for your application UI, but also tie these

Re: Roadmap

/sessions/327833110 ? On Thursday, August 22, 2013 6:17:53 PM UTC+2, Marcos wrote: Hi, Is there any roadmap / plan to the next versions of GWT ? Thanks Mussi -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from

Re: Roadmap

decided to use GWT pure. Em quinta-feira, 22 de agosto de 2013 13h17min53s UTC-3, Marcos escreveu: Hi, Is there any roadmap / plan to the next versions of GWT ? Thanks Mussi -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group

Re: Roadmap

. Consistently displayed the message Do you want to stop running the script? So I decided to use GWT pure. Em quinta-feira, 22 de agosto de 2013 13h17min53s UTC-3, Marcos escreveu: Hi, Is there any roadmap / plan to the next versions of GWT ? Thanks Mussi -- You received

Roadmap

I strongly recommend https://vaadin.com/ They are also extending GWT -- 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

Roadmap

Hi, Is there any roadmap / plan to the next versions of GWT ? Thanks Mussi -- 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

Re: Roadmap

https://developers.google.com/events/io/sessions/327833110 ? On Thursday, August 22, 2013 6:17:53 PM UTC+2, Marcos wrote: Hi, Is there any roadmap / plan to the next versions of GWT ? Thanks Mussi -- You received this message because you are subscribed to the Google Groups Google Web

Re: Roadmap GWT?

On Friday, November 9, 2012 2:56:00 AM UTC+1, Joseph Lust wrote: Are the calls/meetings still regular? I had thought they were going to be Hangouts and recorded, but there is little mention of anything on the forum. There hasn't been any other meeting. Several SC members were touring the

Re: Roadmap GWT?

On 09/11/12 10:01, Thomas Broyer wrote: no decision were made, except for welcoming JetBrains as a new SC member. That's a good example of something that should have been posted to the SC group. Paul -- You received this message because you are subscribed to the Google Groups Google Web

Re: Roadmap GWT?

Thanks Thomas, that's a start. I was hoping for something more than that, but I guess I'll be patient. When is the next SC meeting / decision point? On Friday, November 9, 2012 4:01:32 AM UTC-6, Thomas Broyer wrote: On Friday, November 9, 2012 2:56:00 AM UTC+1, Joseph Lust wrote: Are the

Re: Roadmap GWT?

On Monday, November 5, 2012 6:56:29 AM UTC-8, Thomas Broyer wrote: On Monday, November 5, 2012 3:41:26 PM UTC+1, Ryan Shillington wrote: To be a little more blunt than Christian - I would like to see some results from the Steering committee. I don't care about timelines as much as I

Re: Roadmap GWT?

For the record, I am still touring the world. =) I'm speaking at the Silicon Valley JUG (http://www.meetup.com/sv-jug/events/87379262/), the Vancouver JUG two days later (http://www.vanjug.com/events/90557972/?eventId=90557972action=detail), Beijing 5 days later, Seoul 3 days after that, and

Re: Roadmap GWT?

I also have been touring around talking about mgwt and phonegap. You should definitely take a look at the gerrit and git setup that Matthew has already managed. I just patched a small issue using it and it works like a charm. -Daniel On Friday, November 9, 2012 9:22:00 PM UTC+1, Mike Brock

Re: Roadmap GWT?

Any chance you could post that to the Steering Committee forum? Joe -- 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/-/1W8tvJ66LFcJ. To post to

Re: Roadmap GWT?

On Thursday, November 8, 2012 7:51:08 PM UTC+1, Joseph Lust wrote: Any chance you could post that to the Steering Committee forum? Assuming you're asking me to do it, for the record; it's no news: see https://groups.google.com/d/topic/gwt-steering/AfMwY3nzcps/discussion and

Re: Roadmap GWT?

Thanks Thomas. My apologies, I thought that might have been newer news than July. Are the calls/meetings still regular? I had thought they were going to be Hangouts and recorded, but there is little mention of anything on the forum. Sincerely, Joseph -- You received this message because you

Re: Roadmap GWT?

We are starting a new project and GWT is a possible candidate for the implementation. So I would also be interested to see a road map. Road maps generate trust (if you see a plan for the next year ahead and if you can watch the team reaching the planned milestones in time). I know the steering

Re: Roadmap GWT?

To be a little more blunt than Christian - I would like to see some results from the Steering committee. I don't care about timelines as much as I care about direction. What direction are you taking GWT for vNext? Ryan On Monday, November 5, 2012 4:07:28 AM UTC-6, ChrLipp wrote: We are

Re: Roadmap GWT?

On Monday, November 5, 2012 3:41:26 PM UTC+1, Ryan Shillington wrote: To be a little more blunt than Christian - I would like to see some results from the Steering committee. I don't care about timelines as much as I care about direction. What direction are you taking GWT for vNext?

Re: Roadmap GWT?

Stay tuned to the Steering Committeehttps://groups.google.com/forum/#!forum/gwt-steeringif you want to know where they are steering towards. Sincerely, Joseph -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on

Roadmap GWT?

When we have a roadmap GWT? -- 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/-/ZnMVnoiO3AUJ. To post to this group, send email to google-web-toolkit

Re: Roadmap GWT?

On Thu, Nov 1, 2012 at 11:47 AM, Marcos muss...@gmail.com wrote: When we have a roadmap GWT? What do you want a roadmap for? -- 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

Re: GWT Chrome dev OOPHM is Slow. What is the roadmap?

@jchimene -- thanks for that...hugely helpful as I dev on Ubuntu and the constant Firefox updates are a pain. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit

Re: GWT Chrome dev OOPHM is Slow. What is the roadmap?

I am a linux dev, my ubuntu distro updates firefox along with the OS updates soon after a new firefox release. Mozilla has adopted an aggressive release schedule and the gwt plugin for it has lagged several weeks behind. So when a new firefox is released, i have to change from firefox dev to

Re: GWT Chrome dev OOPHM is Slow. What is the roadmap?

On 11/28/2011 09:47 AM, Williame wrote: I am a linux dev, my ubuntu distro updates firefox along with the OS updates soon after a new firefox release. Mozilla has adopted an aggressive release schedule and the gwt plugin for it has lagged several weeks behind. So when a new firefox is

Re: GWT Chrome dev OOPHM is Slow. What is the roadmap?

While I can't speak for the OP, I'll add my two cents on why it would be a major plus for our development team. We are developing an offline feature using Web SQL and the only way to test it is to go through Chrome, since Firefox does not support it. On Monday, November 28, 2011 2:42:44 AM

Re: GWT Chrome dev OOPHM is Slow. What is the roadmap?

If you haven't already starred the issue, please star it. http://code.google.com/p/google-web-toolkit/issues/detail?id=6813 They have begun working on it too. I agree Firefox is faster as of now. On Nov 27, 2011 6:39 PM, Strelok roman.ro...@gmail.com wrote: Latest ChromeDev (17.0.942.0 dev-m) is

Re: GWT Chrome dev OOPHM is Slow. What is the roadmap?

I'm curious to know why this is a priority for you? I use Firefox for development and it's a perfectly workable solution for me. What does Chrome give you that you need for GWT development? Tom On Mon, Nov 28, 2011 at 5:53 AM, Brandon Donnelson branflake2...@gmail.comwrote: If you haven't

Re: GWT Chrome dev OOPHM is Slow. What is the roadmap?

I would say the dev channel release is, maybe slightly faster. Not even close to as fast as safari dev plugin is. Just to make sure, I'm not talking about load time of the dev (translating). Once its up in running, its the widget init and iteration rendering that is slow in chrome compared to

Re: GWT Chrome dev OOPHM is Slow. What is the roadmap?

Chrome canary is the same. -- 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/-/UCLDbl8tNBQJ. To post to this group, send email to

GWT Chrome dev OOPHM is Slow. What is the roadmap?

Please focus on the development plugin for Chrome. What is the future roadmap for the Chrome dev plugin? Thanks, Brandon Donnelson -- 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

Re: GWT Chrome dev OOPHM is Slow. What is the roadmap?

I filed a specific issue related to this - http://code.google.com/p/google-web-toolkit/issues/detail?id=6813 -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit

Re: GWT Chrome dev OOPHM is Slow. What is the roadmap?

I suspect this wont change anytime soon because of all the sandboxing chrome does. -- 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/-/C6cxePpbficJ.

Re: GWT Chrome dev OOPHM is Slow. What is the roadmap?

Using the development build of Chrome (Chrome Dev Channel, currently version 15.0.874.15) I found its already a good portion faster than it was some time ago. Maybe you can try and update your version. -- J. -- You received this message because you are subscribed to the Google Groups Google

Re: GWT Chrome dev OOPHM is Slow. What is the roadmap?

Thanks for that note. I'll check that out. I also added to the issue for reference. Brandon -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit

Re: GWT Chrome dev OOPHM is Slow. What is the roadmap?

Also if you are using Mac you can still use Safari 5.0.5 (or OmniWeb) beside Safari 5.1. Firefox 6 is also supported (search for Firefox 6 in this group and you will find an updated dev mode plugin). -- You received this message because you are subscribed to the Google Groups Google Web

GWT 2.3 and roadmap

Hi, As already known, 2.3-Beta is out. Does anyone know when the 2.3 will be released? btw; i couldn't find a global roadmap page. anyone know of a link to, or info about, the roadmap? Regards, Hasan. -- You received this message because you are subscribed to the Google Groups Google Web

  1   2   >