A quick update on GWT 1.4. We're wrapping up new features now and will soon enter a short bugfix phase. It seems like a good time to do a checkpoint and drop a binary distribution for your hacking and experimentation pleasure. If you can swing it, please grab a copy and try out your favorite feature from the 1.4 dev plan: http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4 .
First, the disclaimer:
- This is *not* a release candidate. It's just a snapshot build of the GWT 1.4 code in progress. - You definitely should not try to switch over to it for production. - There is a some chance of API changes on the new features between now and the release candidate for 1.4. - The new features may have introduced new bugs. - We still have bugfixes left before we do a GWT 1.4 release candidate; mostly what you'll see in this build is new features. - Release notes are absent, and doc is spotty; there will be more for the RC.
Now that all that's out of the way, grab the build for your platform here:
this is awesome :-) # RichTextArea - jgw, knorton # DisclosurePanel (formerly CollapsiblePanel) - knorton # Widgets in Tabs - knorton
are exactly the 3 features which I need the most at the moment. I hope 1.4 will be ready by april 23 since I start working on my diploma project as a software engineer. (will make a GWT application)
> A quick update on GWT 1.4. We're wrapping up new features now and will soon > enter a short bugfix phase. It seems like a good time to do a checkpoint and > drop a binary distribution for your hacking and experimentation pleasure. If > you can swing it, please grab a copy and try out your favorite feature from > the 1.4 dev plan:http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4.
> First, the disclaimer:
> - This is *not* a release candidate. It's just a snapshot build of the > GWT 1.4 code in progress. > - You definitely should not try to switch over to it for production. > - There is a some chance of API changes on the new features between > now and the release candidate for 1.4. > - The new features may have introduced new bugs. > - We still have bugfixes left before we do a GWT 1.4 release > candidate; mostly what you'll see in this build is new features. > - Release notes are absent, and doc is spotty; there will be more for > the RC.
> Now that all that's out of the way, grab the build for your platform here:
Dominik Erbsland wrote: > this is awesome :-) > # RichTextArea - jgw, knorton > # DisclosurePanel (formerly CollapsiblePanel) - knorton > # Widgets in Tabs - knorton
> are exactly the 3 features which I need the most at the moment. > I hope 1.4 will be ready by april 23 since I start working on my > diploma project as a software engineer. (will make a GWT application)
> On Apr 12, 10:29 am, "Bruce Johnson" <b...@google.com> wrote:
>> Hi Folks!
>> A quick update on GWT 1.4. We're wrapping up new features now and will soon >> enter a short bugfix phase. It seems like a good time to do a checkpoint and >> drop a binary distribution for your hacking and experimentation pleasure. If >> you can swing it, please grab a copy and try out your favorite feature from >> the 1.4 dev plan:http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4.
>> First, the disclaimer:
>> - This is *not* a release candidate. It's just a snapshot build of the >> GWT 1.4 code in progress. >> - You definitely should not try to switch over to it for production. >> - There is a some chance of API changes on the new features between >> now and the release candidate for 1.4. >> - The new features may have introduced new bugs. >> - We still have bugfixes left before we do a GWT 1.4 release >> candidate; mostly what you'll see in this build is new features. >> - Release notes are absent, and doc is spotty; there will be more for >> the RC.
>> Now that all that's out of the way, grab the build for your platform here:
I jumped right into trying to use the RichTextArea class but bumped into a couple problems. Maybe I'm not using it right and should wait for more docs, but I'll post the errors, although I'm not sure if this is the right spot to do that. Anyway, here they are:
For IE, the widget is looking for RichEditIE.html and fails. I can't find this file. For Firefox, it seems to load great for a blank RichTextArea but if I create a RichTextArea, add it to a panel, and then add text to it immediately using setText, I get a javascript error: "this.a.contentWindow has no properties"
I'll try to test more of these great new features out over the next few days. There's so much new stuff!!! :)
Ryan
On Apr 12, 4:29 am, "Bruce Johnson" <b...@google.com> wrote:
> A quick update on GWT 1.4. We're wrapping up new features now and will soon > enter a short bugfix phase. It seems like a good time to do a checkpoint and > drop a binary distribution for your hacking and experimentation pleasure. If > you can swing it, please grab a copy and try out your favorite feature from > the 1.4 dev plan:http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4.
> First, the disclaimer:
> - This is *not* a release candidate. It's just a snapshot build of the > GWT 1.4 code in progress. > - You definitely should not try to switch over to it for production. > - There is a some chance of API changes on the new features between > now and the release candidate for 1.4. > - The new features may have introduced new bugs. > - We still have bugfixes left before we do a GWT 1.4 release > candidate; mostly what you'll see in this build is new features. > - Release notes are absent, and doc is spotty; there will be more for > the RC.
> Now that all that's out of the way, grab the build for your platform here:
On 4/12/07, Joseph Ottinger <dreamr...@gmail.com> wrote:
> I was hoping that 1.4's compiler would be able to handle ignoring > annotations so I wouldn't have to code value objects for my domains. :(
Life sucks. Seriously, COME ON. I see so much complaining (quite apart from all the really weird questions that - if I wasn't so polite and Reiner so prolific, vast and seemlingy bottomless in his undying willingness to taunt people from all over the world - seem to be increasing in number daily) right now. "Why isn't this supported, why isn't that supported". Implement it. It's open. Just do it. Thanks to all the people who, through their hard work make all of this available to us. Thanks to Reiner and all the others here on the list who take the time to answer questions instead of (like me) dishing out non sequiteurs and ad hominems. There. I have said it.
----- Original Message ----- From: Niklas Derouche To: Google-Web-Toolkit@googlegroups.com Sent: Thursday, April 12, 2007 7:43 AM Subject: Re: GWT 1.4 Status Update
On 4/12/07, Joseph Ottinger <dreamr...@gmail.com> wrote:
I was hoping that 1.4's compiler would be able to handle ignoring annotations so I wouldn't have to code value objects for my domains. :(
Life sucks. Seriously, COME ON. I see so much complaining (quite apart from all the really weird questions that - if I wasn't so polite and Reiner so prolific, vast and seemlingy bottomless in his undying willingness to taunt people from all over the world - seem to be increasing in number daily) right now. "Why isn't this supported, why isn't that supported". Implement it. It's open. Just do it. Thanks to all the people who, through their hard work make all of this available to us. Thanks to Reiner and all the others here on the list who take the time to answer questions instead of (like me) dishing out non sequiteurs and ad hominems. There. I have said it.
n.
-- ---------------------------------------- I've had a wonderful time but this wasn't it. Groucho Marx
Oh, I know it's coming... but I'm too lazy to write VOs in the meantime. There are a lot of tiny issues to worry about with it, too - which is why I'd be happy to have the compiler - which is more complex than I want to dig into, thank you very much, just ignore annotations.
If *I* were to "fix" the compiler, I'm pretty sure it'd be rendered unusable. And who wants that? :)
Full java1.5 notational compatibility is plannen as one of the first features for GWT 1.5. With a bit of luck a beta with just GWT1.4 + java1.5 notations will be released. Or, better yet, you can just watch the completely open development process, grab the patches, and build such a beast yourself!
And as far as GWT1.4 is concerned: w000000t!
On Apr 12, 4:43 pm, "Niklas Derouche" <nik...@gmail.com> wrote:
> On 4/12/07, Joseph Ottinger <dreamr...@gmail.com> wrote:
> > I was hoping that 1.4's compiler would be able to handle ignoring > > annotations so I wouldn't have to code value objects for my domains. :(
> Life sucks. Seriously, COME ON. I see so much complaining (quite apart from > all the really weird questions that - if I wasn't so polite and Reiner so > prolific, vast and seemlingy bottomless in his undying willingness to taunt > people from all over the world - seem to be increasing in number daily) > right now. "Why isn't this supported, why isn't that supported". Implement > it. It's open. Just do it. Thanks to all the people who, through their hard > work make all of this available to us. Thanks to Reiner and all the others > here on the list who take the time to answer questions instead of (like me) > dishing out non sequiteurs and ad hominems. There. I have said it.
> n.
> --
> > ---------------------------------------- > > I've had a wonderful time but > > this wasn't it. > > Groucho Marx
Would it be hard to add some sort of gwt-compiler comment block, as a hack for the time being? Something like this: /* GWT-IGNORE-{ */ @Annotations /* }-*/
and gwt compiler could happily ignore those. Looks ugly but it just might work. :) Then I guess it'd be just as easy to just ignore annotations... Although I can see other applications of this comment block...
Joseph Ottinger wrote: > I was hoping that 1.4's compiler would be able to handle ignoring > annotations so I wouldn't have to code value objects for my domains. :(
> Dominik Erbsland wrote:
>> this is awesome :-) >> # RichTextArea - jgw, knorton >> # DisclosurePanel (formerly CollapsiblePanel) - knorton >> # Widgets in Tabs - knorton
>> are exactly the 3 features which I need the most at the moment. >> I hope 1.4 will be ready by april 23 since I start working on my >> diploma project as a software engineer. (will make a GWT application)
>> On Apr 12, 10:29 am, "Bruce Johnson" <b...@google.com> wrote:
>>> Hi Folks!
>>> A quick update on GWT 1.4. We're wrapping up new features now and will soon >>> enter a short bugfix phase. It seems like a good time to do a checkpoint and >>> drop a binary distribution for your hacking and experimentation pleasure. If >>> you can swing it, please grab a copy and try out your favorite feature from >>> the 1.4 dev plan:http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4.
>>> First, the disclaimer:
>>> - This is *not* a release candidate. It's just a snapshot build of the >>> GWT 1.4 code in progress. >>> - You definitely should not try to switch over to it for production. >>> - There is a some chance of API changes on the new features between >>> now and the release candidate for 1.4. >>> - The new features may have introduced new bugs. >>> - We still have bugfixes left before we do a GWT 1.4 release >>> candidate; mostly what you'll see in this build is new features. >>> - Release notes are absent, and doc is spotty; there will be more for >>> the RC.
>>> Now that all that's out of the way, grab the build for your platform here:
Looking forward to the 1.4 release, or a at least RC. Good job!
Just a couple of comments: - RichTextArea: are undo and redo going to be supported? AFAIK, they can be easily implemented with execCommand("undo", null) and execCommand("redo", null) which are supported by all browsers. - VerticalSplitPanel behaves weirdly in IE -- when I drag the bar it always appears with the width it was originally loaded with, not the current width (of the horizontal splitter's right widget), which causes the scroll bar across the whole panel if there is no sufficient space.
> A quick update on GWT 1.4. We're wrapping up new features now and will > soon enter a short bugfix phase. It seems like a good time to do a > checkpoint and drop a binary distribution for your hacking and > experimentation pleasure. If you can swing it, please grab a copy and > try out your favorite feature from the 1.4 dev plan: > http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4 .
> First, the disclaimer:
> * This is *not* a release candidate. It's just a snapshot build of > the GWT 1.4 code in progress. > * You definitely should not try to switch over to it for production. > * There is a some chance of API changes on the new features > between now and the release candidate for 1.4. > * The new features may have introduced new bugs. > * We still have bugfixes left before we do a GWT 1.4 release > candidate; mostly what you'll see in this build is new features. > * Release notes are absent, and doc is spotty; there will be more > for the RC.
> Now that all that's out of the way, grab the build for your platform here:
I think one can work around annotations with a little automated preprocessing such as an ant script that:
1. copies java files to a different directory 2. performs a find/replace with regular expressions and removes annotations 3. unleashes the gwt-compiler on the stripped files 4. cleans up
My only reservation is towards wether the altered source code counts as a different class signature, which would make this approach useless for RPC, but that should be easy to test.
On Apr 12, 7:03 pm, Pavel <pave...@gmail.com> wrote:
> Looking forward to the 1.4 release, or a at least RC. Good job!
> Just a couple of comments: > - RichTextArea: are undo and redo going to be supported? AFAIK, they > can be easily implemented with execCommand("undo", null) and > execCommand("redo", null) which are supported by all browsers. > - VerticalSplitPanel behaves weirdly in IE -- when I drag the bar it > always appears with the width it was originally loaded with, not the > current width (of the horizontal splitter's right widget), which causes > the scroll bar across the whole panel if there is no sufficient space.
> Thanks.
> Pavel
> Bruce Johnson wrote: > > Hi Folks!
> > A quick update on GWT 1.4. We're wrapping up new features now and will > > soon enter a short bugfix phase. It seems like a good time to do a > > checkpoint and drop a binary distribution for your hacking and > > experimentation pleasure. If you can swing it, please grab a copy and > > try out your favorite feature from the 1.4 dev plan: > >http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4.
> > First, the disclaimer:
> > * This is *not* a release candidate. It's just a snapshot build of > > the GWT 1.4 code in progress. > > * You definitely should not try to switch over to it for production. > > * There is a some chance of API changes on the new features > > between now and the release candidate for 1.4. > > * The new features may have introduced new bugs. > > * We still have bugfixes left before we do a GWT 1.4 release > > candidate; mostly what you'll see in this build is new features. > > * Release notes are absent, and doc is spotty; there will be more > > for the RC.
> > Now that all that's out of the way, grab the build for your platform here:
<g.georgovassi...@gmail.com> wrote: > I think one can work around annotations with a little automated > preprocessing such as an ant script that:
> 1. copies java files to a different directory > 2. performs a find/replace with regular expressions and removes > annotations > 3. unleashes the gwt-compiler on the stripped files > 4. cleans up
> My only reservation is towards wether the altered source code counts > as a different class signature, which would make this approach useless > for RPC, but that should be easy to test.
> On Apr 12, 7:03 pm, Pavel <pave...@gmail.com> wrote:
> > Looking forward to the 1.4 release, or a at least RC. Good job!
> > Just a couple of comments: > > - RichTextArea: are undo and redo going to be supported? AFAIK, they > > can be easily implemented with execCommand("undo", null) and > > execCommand("redo", null) which are supported by all browsers. > > - VerticalSplitPanel behaves weirdly in IE -- when I drag the bar it > > always appears with the width it was originally loaded with, not the > > current width (of the horizontal splitter's right widget), which causes > > the scroll bar across the whole panel if there is no sufficient space.
> > Thanks.
> > Pavel
> > Bruce Johnson wrote: > > > Hi Folks!
> > > A quick update on GWT 1.4. We're wrapping up new features now and will > > > soon enter a short bugfix phase. It seems like a good time to do a > > > checkpoint and drop a binary distribution for your hacking and > > > experimentation pleasure. If you can swing it, please grab a copy and > > > try out your favorite feature from the 1.4 dev plan: > > >http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4.
> > > First, the disclaimer:
> > > * This is *not* a release candidate. It's just a snapshot build of > > > the GWT 1.4 code in progress. > > > * You definitely should not try to switch over to it for production. > > > * There is a some chance of API changes on the new features > > > between now and the release candidate for 1.4. > > > * The new features may have introduced new bugs. > > > * We still have bugfixes left before we do a GWT 1.4 release > > > candidate; mostly what you'll see in this build is new features. > > > * Release notes are absent, and doc is spotty; there will be more > > > for the RC.
> > > Now that all that's out of the way, grab the build for your platform here:
You are right, that escaped me. It seems a simple task though since the number of namespaces of allowed import packages should be manageable. True enthusiasts would parse the module.gwt.xml to obtain them.
On Apr 13, 4:02 am, "wangzx" <wangzaixi...@gmail.com> wrote:
> Not so simply, but also you should process the import statement, > otherwise the java compiler will complain it cant find the annotation > source file.
> On Apr 13, 4:19 am, "George Georgovassilis"
> <g.georgovassi...@gmail.com> wrote: > > I think one can work around annotations with a little automated > > preprocessing such as an ant script that:
> > 1. copies java files to a different directory > > 2. performs a find/replace with regular expressions and removes > > annotations > > 3. unleashes the gwt-compiler on the stripped files > > 4. cleans up
> > My only reservation is towards wether the altered source code counts > > as a different class signature, which would make this approach useless > > for RPC, but that should be easy to test.
> > On Apr 12, 7:03 pm, Pavel <pave...@gmail.com> wrote:
> > > Looking forward to the 1.4 release, or a at least RC. Good job!
> > > Just a couple of comments: > > > - RichTextArea: are undo and redo going to be supported? AFAIK, they > > > can be easily implemented with execCommand("undo", null) and > > > execCommand("redo", null) which are supported by all browsers. > > > - VerticalSplitPanel behaves weirdly in IE -- when I drag the bar it > > > always appears with the width it was originally loaded with, not the > > > current width (of the horizontal splitter's right widget), which causes > > > the scroll bar across the whole panel if there is no sufficient space.
> > > Thanks.
> > > Pavel
> > > Bruce Johnson wrote: > > > > Hi Folks!
> > > > A quick update on GWT 1.4. We're wrapping up new features now and will > > > > soon enter a short bugfix phase. It seems like a good time to do a > > > > checkpoint and drop a binary distribution for your hacking and > > > > experimentation pleasure. If you can swing it, please grab a copy and > > > > try out your favorite feature from the 1.4 dev plan: > > > >http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4.
> > > > First, the disclaimer:
> > > > * This is *not* a release candidate. It's just a snapshot build of > > > > the GWT 1.4 code in progress. > > > > * You definitely should not try to switch over to it for production. > > > > * There is a some chance of API changes on the new features > > > > between now and the release candidate for 1.4. > > > > * The new features may have introduced new bugs. > > > > * We still have bugfixes left before we do a GWT 1.4 release > > > > candidate; mostly what you'll see in this build is new features. > > > > * Release notes are absent, and doc is spotty; there will be more > > > > for the RC.
> > > > Now that all that's out of the way, grab the build for your platform here:
@gwt team This is a very good idea!!! And try to kick out the IsSerializable interface, please. (I want to use my object domain in the client layer too)
Thanks to the gwt team their work! (I'm a big fan)
Hi Bruce, I am wounding, can I check-in my piece of code written for "Vertical Tab" bar and panels to be accommodate in this release?
P.S.: current build only support top- horizontally (left-to-right) TabBar/Tabpanel, vertical tabbar(top-to-bottom) is needed for example Document/e-book etc. like application.. and bottom tabbar is needed for example editor/Rich Text, switch code/ design like application.. etc.etc..
> A quick update on GWT 1.4. We're wrapping up new features now and will soon > enter a short bugfix phase. It seems like a good time to do a checkpoint and > drop a binary distribution for your hacking and experimentation pleasure. If > you can swing it, please grab a copy and try out your favorite feature from > the 1.4 dev plan: > http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4 .
> First, the disclaimer:
> - This is *not* a release candidate. It's just a snapshot build of the > GWT 1.4 code in progress. > - You definitely should not try to switch over to it for production. > - There is a some chance of API changes on the new features between > now and the release candidate for 1.4. > - The new features may have introduced new bugs. > - We still have bugfixes left before we do a GWT 1.4 release > candidate; mostly what you'll see in this build is new features. > - Release notes are absent, and doc is spotty; there will be more for > the RC.
> Now that all that's out of the way, grab the build for your platform here:
> Hi Folks!<br><br>A quick update on GWT 1.4. We're wrapping up new features now and will soon enter a short bugfix phase. It seems like a good time to do a checkpoint and drop a binary distribution for your hacking and experimentation pleasure. If you can swing it, please grab a copy and try out your favorite feature from the > 1.4 dev plan: <a href="http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4</a>
> . <br><br>First, the disclaimer:<br><ul><li> > This is *not* a release candidate. It's just a snapshot build of the GWT 1.4 code in progress. </li><li>You definitely should not try to switch over to it for production. </li>
> Hi Bruce, > I am wounding, can I check-in my piece of code written for "Vertical > Tab" bar and panels to be accommodate in this release?
> P.S.: current build only support top- horizontally (left-to-right) > TabBar/Tabpanel, vertical tabbar(top-to-bottom) is needed for example > Document/e-book etc. like application.. > and bottom tabbar is needed for example editor/Rich Text, switch code/ > design like application.. etc.etc..
> -- Ishtiaq
> Bruce Johnson wrote: > > Hi Folks!
> > A quick update on GWT 1.4. We're wrapping up new features now and will soon > > enter a short bugfix phase. It seems like a good time to do a checkpoint and > > drop a binary distribution for your hacking and experimentation pleasure. If > > you can swing it, please grab a copy and try out your favorite feature from > > the 1.4 dev plan: > >http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4.
> > First, the disclaimer:
> > - This is *not* a release candidate. It's just a snapshot build of the > > GWT 1.4 code in progress. > > - You definitely should not try to switch over to it for production. > > - There is a some chance of API changes on the new features between > > now and the release candidate for 1.4. > > - The new features may have introduced new bugs. > > - We still have bugfixes left before we do a GWT 1.4 release > > candidate; mostly what you'll see in this build is new features. > > - Release notes are absent, and doc is spotty; there will be more for > > the RC.
> > Now that all that's out of the way, grab the build for your platform here:
> > Hi Folks!<br><br>A quick update on GWT 1.4. We're wrapping up new features now and will soon enter a short bugfix phase. It seems like a good time to do a checkpoint and drop a binary distribution for your hacking and experimentation pleasure. If you can swing it, please grab a copy and try out your favorite feature from the > > 1.4 dev plan: <a href="http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4</a>
> > . <br><br>First, the disclaimer:<br><ul><li> > > This is *not* a release candidate. It's just a snapshot build of the GWT 1.4 code in progress. </li><li>You definitely should not try to switch over to it for production. </li>
Reinier Zwitserloot wrote: > Ishtiaq, you'd have to submit a patch to the tracker (follow the issue > tracker link from the google code GWT page) to get the ball rolling.
> Any bug fixes might make it, new features definitely won't, from what > I understand. If it's a feature, you should probably 'demo' it > somewhere.
> On Apr 16, 8:45 am, "ISHTIAQ" <ishtiaq.ah...@gmail.com> wrote: > > Hi Bruce, > > I am wounding, can I check-in my piece of code written for "Vertical > > Tab" bar and panels to be accommodate in this release?
> > P.S.: current build only support top- horizontally (left-to-right) > > TabBar/Tabpanel, vertical tabbar(top-to-bottom) is needed for example > > Document/e-book etc. like application.. > > and bottom tabbar is needed for example editor/Rich Text, switch code/ > > design like application.. etc.etc..
> > -- Ishtiaq
> > Bruce Johnson wrote: > > > Hi Folks!
> > > A quick update on GWT 1.4. We're wrapping up new features now and will soon > > > enter a short bugfix phase. It seems like a good time to do a checkpoint and > > > drop a binary distribution for your hacking and experimentation pleasure. If > > > you can swing it, please grab a copy and try out your favorite feature from > > > the 1.4 dev plan: > > >http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4.
> > > First, the disclaimer:
> > > - This is *not* a release candidate. It's just a snapshot build of the > > > GWT 1.4 code in progress. > > > - You definitely should not try to switch over to it for production. > > > - There is a some chance of API changes on the new features between > > > now and the release candidate for 1.4. > > > - The new features may have introduced new bugs. > > > - We still have bugfixes left before we do a GWT 1.4 release > > > candidate; mostly what you'll see in this build is new features. > > > - Release notes are absent, and doc is spotty; there will be more for > > > the RC.
> > > Now that all that's out of the way, grab the build for your platform here:
> > > Hi Folks!<br><br>A quick update on GWT 1.4. We're wrapping up new features now and will soon enter a short bugfix phase. It seems like a good time to do a checkpoint and drop a binary distribution for your hacking and experimentation pleasure. If you can swing it, please grab a copy and try out your favorite feature from the > > > 1.4 dev plan: <a href="http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4</a>
> > > . <br><br>First, the disclaimer:<br><ul><li> > > > This is *not* a release candidate. It's just a snapshot build of the GWT 1.4 code in progress. </li><li>You definitely should not try to switch over to it for production. </li>
> Hi Bruce, > I am wounding, can I check-in my piece of code written for "Vertical > Tab" bar and panels to be accommodate in this release?
> P.S.: current build only support top- horizontally (left-to-right) > TabBar/Tabpanel, vertical tabbar(top-to-bottom) is needed for example > Document/e-book etc. like application.. > and bottom tabbar is needed for example editor/Rich Text, switch code/ > design like application.. etc.etc..
> -- Ishtiaq
> Bruce Johnson wrote: > > Hi Folks!
> > A quick update on GWT 1.4. We're wrapping up new features now and will > soon > > enter a short bugfix phase. It seems like a good time to do a checkpoint > and > > drop a binary distribution for your hacking and experimentation > pleasure. If > > you can swing it, please grab a copy and try out your favorite feature > from > > the 1.4 dev plan: > > http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4 .
> > First, the disclaimer:
> > - This is *not* a release candidate. It's just a snapshot build of > the > > GWT 1.4 code in progress. > > - You definitely should not try to switch over to it for production. > > - There is a some chance of API changes on the new features between > > now and the release candidate for 1.4. > > - The new features may have introduced new bugs. > > - We still have bugfixes left before we do a GWT 1.4 release > > candidate; mostly what you'll see in this build is new features. > > - Release notes are absent, and doc is spotty; there will be more for > > the RC.
> > Now that all that's out of the way, grab the build for your platform > here:
> > Hi Folks!<br><br>A quick update on GWT 1.4. We're wrapping up new > features now and will soon enter a short bugfix phase. It seems like a good > time to do a checkpoint and drop a binary distribution for your hacking and > experimentation pleasure. If you can swing it, please grab a copy and try > out your favorite feature from the > > 1.4 dev plan: <a href=" > http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4" > target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> > http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4</a>
> > . <br><br>First, the disclaimer:<br><ul><li> > > This is *not* a release candidate. It's just a snapshot build of the > GWT 1.4 code in progress. </li><li>You definitely should not try to switch > over to it for production. </li>
I just tried GWT 1.4 on Linux because I was having serious problems running in hosted mode with Hotspot SIGSEGV crashes. The garbage collection problem ? It's a fairly large app with RPCs
Well the good news is it doesn't crash anymore, but I did get a few Java heap space errors until I bumped up Xmx and Xms in Eclipse to - Xms256m -Xmx512m. However, I did notice that it seemed quite a bit slower in hosted mode. I'm using the KitchenSink example to lazily instantiate my panels and first time they used to take about 1 to 2 secs to display, now they take about 20 secs to display. Occasionally it just hangs in hosted mode and I have to exit Eclipse.
I had problems deploying to Tomcat in that tomcat reported it could not find a ...nocache.html file. I changed MyApp.html to include com.test.MyApp.nocache.js from gwt.js and removed the meta tag for GWT. It now seems to work OK in tomcat. Not sure if that was the right thing to do but it got me going.
Thanks for the pre-release, it's removed quite a bit of pain running hosted for me. Hopefully there is still some debugging code causing the performance slowdown.
> I just tried GWT 1.4 on Linux because I was having serious problems > running in hosted mode with Hotspot SIGSEGV crashes. The garbage > collection problem ? It's a fairly large app with RPCs
> Well the good news is it doesn't crash anymore, but I did get a few > Java heap space errors until I bumped up Xmx and Xms in Eclipse to - > Xms256m -Xmx512m. However, I did notice that it seemed quite a bit > slower in hosted mode. I'm using the KitchenSink example to lazily > instantiate my panels and first time they used to take about 1 to 2 > secs to display, now they take about 20 secs to display. Occasionally > it just hangs in hosted mode and I have to exit Eclipse.
In the 1.4 milestone release, some debugging code was left enabled so if there was still a problem we would be able to get useful information from the error message. This debugging code creates a Throwable and fills in the stack trace for each JavaScript object created (to keep a stack trace of where it was created), then tracks it to make sure it is eventually freed exactly once and that no other Java object refers to the same JavaScript object. For applications like RPC where the code crosses into JSNI frequently, this can eat 60-75% of the app's time. These tracking objects also dramatically expand memory requirements for JavaScript values, which is why you had to increase the heap size and also contributes to performance decreases due to additional GC runs.
If you are comfortable building from source, you can checkout the current trunk which disables this. Alternatively, 1.4RC1 will have the debug code disabled when it is released.
Thanks for the pre-release, it's removed quite a bit of pain running
> hosted for me. Hopefully there is still some debugging code causing > the performance slowdown.
Yes, as described above, much of the slowdown is due to debugging code. However, our tests show that without the debugging code it is still slower than 1.3.3, since actually doing the GC correctly takes time and we are now creating many more Java objects than before (previously, it was just a primitive int referring to the underlying JavaScript value, now it is an object). We have some ideas about improving that (unifying much of the Safari and Mozilla code, reducing the number of GC roots kept in the JSVM), but that won't be in 1.4.
Just to be plain though, most of the slowdown you were experiencing is due to the debug code. I don't think we should have released default enabled debug code that was so slow and had such large memory requirements that it made some apps unsable.
> > I just tried GWT 1.4 on Linux because I was having serious problems > > running in hosted mode with Hotspot SIGSEGV crashes. The garbage > > collection problem ? It's a fairly large app with RPCs
> > Well the good news is it doesn't crash anymore, but I did get a few > > Java heap space errors until I bumped up Xmx and Xms in Eclipse to - > > Xms256m -Xmx512m. However, I did notice that it seemed quite a bit > > slower in hosted mode. I'm using the KitchenSink example to lazily > > instantiate my panels and first time they used to take about 1 to 2 > > secs to display, now they take about 20 secs to display. Occasionally > > it just hangs in hosted mode and I have to exit Eclipse.
> In the 1.4 milestone release, some debugging code was left enabled so if > there was still a problem we would be able to get useful information from > the error message. This debugging code creates a Throwable and fills in the > stack trace for each JavaScript object created (to keep a stack trace of > where it was created), then tracks it to make sure it is eventually freed > exactly once and that no other Java object refers to the same JavaScript > object. For applications like RPC where the code crosses into JSNI > frequently, this can eat 60-75% of the app's time. These tracking objects > also dramatically expand memory requirements for JavaScript values, which is > why you had to increase the heap size and also contributes to performance > decreases due to additional GC runs.
> If you are comfortable building from source, you can checkout the current > trunk which disables this. Alternatively, 1.4RC1 will have the debug code > disabled when it is released.
> Thanks for the pre-release, it's removed quite a bit of pain running > > hosted for me. Hopefully there is still some debugging code causing > > the performance slowdown.
> Yes, as described above, much of the slowdown is due to debugging code. > However, our tests show that without the debugging code it is still slower > than 1.3.3, since actually doing the GC correctly takes time and we are > now creating many more Java objects than before (previously, it was just a > primitive int referring to the underlying JavaScript value, now it is an > object). We have some ideas about improving that (unifying much of the > Safari and Mozilla code, reducing the number of GC roots kept in the JSVM), > but that won't be in 1.4.
> -- > John A. Tamplin > Software Engineer, Google
> A quick update on GWT 1.4. We're wrapping up new features now and will soon > enter a short bugfix phase. It seems like a good time to do a checkpoint and > drop a binary distribution for your hacking and experimentation pleasure. If > you can swing it, please grab a copy and try out your favorite feature from > the 1.4 dev plan:http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4.
> First, the disclaimer:
> - This is *not* a release candidate. It's just a snapshot build of the > GWT 1.4 code in progress. > - You definitely should not try to switch over to it for production. > - There is a some chance of API changes on the new features between > now and the release candidate for 1.4. > - The new features may have introduced new bugs. > - We still have bugfixes left before we do a GWT 1.4 release > candidate; mostly what you'll see in this build is new features. > - Release notes are absent, and doc is spotty; there will be more for > the RC.
> Now that all that's out of the way, grab the build for your platform here:
> A quick update on GWT 1.4. We're wrapping up new features now and will soon > enter a short bugfix phase. It seems like a good time to do a checkpoint and > drop a binary distribution for your hacking and experimentation pleasure. If > you can swing it, please grab a copy and try out your favorite feature from > the 1.4 dev plan:http://code.google.com/p/google-web-toolkit/wiki/DevPlan_1_4.
> First, the disclaimer:
> - This is *not* a release candidate. It's just a snapshot build of the > GWT 1.4 code in progress. > - You definitely should not try to switch over to it for production. > - There is a some chance of API changes on the new features between > now and the release candidate for 1.4. > - The new features may have introduced new bugs. > - We still have bugfixes left before we do a GWT 1.4 release > candidate; mostly what you'll see in this build is new features. > - Release notes are absent, and doc is spotty; there will be more for > the RC.
> Now that all that's out of the way, grab the build for your platform here:
