GWT 1.4 Status Update
Bruce Johnson
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.
Windows - http://google-web-toolkit.googlecode.com/files/gwt-windows-0.0.858.zip
Mac OS X - http://google-web-toolkit.googlecode.com/files/gwt-mac-0.0.858.tar.gz
Linux - http://google-web-toolkit.googlecode.com/files/gwt-linux-0.0.858.tar.gz
We're looking forward to your feedback.
-- Bruce
Dominik Erbsland
# 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)
will be the shell-crashing bug be fixed in 1.4, too? (see:
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/8027fc677e3e10fa)
dominik
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:
>
> Windows -http://google-web-toolkit.googlecode.com/files/gwt-windows-0.0.858.zip
> Mac OS X -http://google-web-toolkit.googlecode.com/files/gwt-mac-0.0.858.tar.gz
> Linux -http://google-web-toolkit.googlecode.com/files/gwt-linux-0.0.858.tar.gz
Joseph Ottinger
annotations so I wouldn't have to code value objects for my domains. :(
Ryan Dewsbury
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:
> 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:
>
> Windows -http://google-web-toolkit.googlecode.com/files/gwt-windows-0.0.858.zip
> Mac OS X -http://google-web-toolkit.googlecode.com/files/gwt-mac-0.0.858.tar.gz
> Linux -http://google-web-toolkit.googlecode.com/files/gwt-linux-0.0.858.tar.gz
Niklas Derouche
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. :(
--
----------------------------------------
I've had a wonderful time but
this wasn't it.
Groucho Marx
L Frohman
Jason Essington
1.4 release.
The GWT team didn't want to make a half ass hack, then just rip it
out (change its behavior) when the java 1.5 feature set was supported.
-jason
Joseph Ottinger
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? :)
Reinier Zwitserloot
And just to try and live up to the praise:
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:
Pavel
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...
Just my two cents.
Pavel
Pavel
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
George Georgovassilis
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.
wangzx
otherwise the java compiler will complain it cant find the annotation
source file.
On Apr 13, 4:19 am, "George Georgovassilis"
George Georgovassilis
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.
kro...@googlemail.com
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)
Greetings
Marc
ISHTIAQ
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:
>
> Windows -
> http://google-web-toolkit.googlecode.com/files/gwt-windows-0.0.858.zip
> Mac OS X -
> http://google-web-toolkit.googlecode.com/files/gwt-mac-0.0.858.tar.gz
> Linux -
> http://google-web-toolkit.googlecode.com/files/gwt-linux-0.0.858.tar.gz
>
> We're looking forward to your feedback.
>
> -- Bruce
>
> ------=_Part_29040_22079172.1176366543569
> Content-Type: text/html; charset=ISO-8859-1
> X-Google-AttachSize: 1900
>
> 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>
>
> <li>There is a some chance of API changes on the new features between now and the release candidate for
> 1.4.</li><li>The new features may have introduced new bugs.</li><li>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.<br></li><li>Release notes are absent, and doc is spotty; there will be more for the RC.
> </li></ul>Now that all that's out of the way, grab the build for your platform here:<br> <br> Windows - <a href="http://google-web-toolkit.googlecode.com/files/gwt-windows-0.0.858.zip">http://google-web-toolkit.googlecode.com/files/gwt-windows-0.0.858.zip
> </a><br> Mac OS X - <a href="http://google-web-toolkit.googlecode.com/files/gwt-mac-0.0.858.tar.gz">http://google-web-toolkit.googlecode.com/files/gwt-mac-0.0.858.tar.gz</a><br> Linux - <a href="http://google-web-toolkit.googlecode.com/files/gwt-linux-0.0.858.tar.gz">
> http://google-web-toolkit.googlecode.com/files/gwt-linux-0.0.858.tar.gz</a><br><br>We're looking forward to your feedback.<br><span class="sg"><br>-- Bruce<br><br>
> </span>
>
> ------=_Part_29040_22079172.1176366543569--
Reinier Zwitserloot
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.
ISHTIAQ
its a new feature that I have implemented... providing a demo is
pretty nice advise...
I will get back after hosting it somewhere.
does google provide some space for "demo"?
--
Thanks,
ISHTIAQ AHMAD
European Organization for Nuclear Research (CERN)
Bruce Johnson
Is there any particular reason you want Vertical Tab to be in GWT itself so urgently? Why not just keep it as part of your own library for now?
-- Bruce
ianH
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.
Ian.
John Tamplin
From: ianH < ian.h...@gmail.com>
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
Toby Reyelts
nseb
On 12 avr, 10:29, "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:
>
> Windows -http://google-web-toolkit.googlecode.com/files/gwt-windows-0.0.858.zip
> Mac OS X -http://google-web-toolkit.googlecode.com/files/gwt-mac-0.0.858.tar.gz
> Linux -http://google-web-toolkit.googlecode.com/files/gwt-linux-0.0.858.tar.gz
Berzehk
syaskin
or will it be there in the final release?
Thanks!
Looking forward to trying 1.4 out!
On Apr 12, 4: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:
>
> Windows -http://google-web-toolkit.googlecode.com/files/gwt-windows-0.0.858.zip
> Mac OS X -http://google-web-toolkit.googlecode.com/files/gwt-mac-0.0.858.tar.gz
> Linux -http://google-web-toolkit.googlecode.com/files/gwt-linux-0.0.858.tar.gz
Reinier Zwitserloot
found, the RC will be renamed to 'final release' after a while. If
between an RC and that same version's "Final" release, differences in
features exists, the company or entity that is in charge of naming
failed it. RC = Release Candidate. It's a Candidate to release (which
is the same as 'final', which is after all: the final edition of a
given version number. In other words: The release of that version
number.)
If the nightlies have it now, likely the RC will have it, which
automatically means the final will have it, unless there is an
unsolvable bug that leads to the decision to eject the code entirely
and shove it to 1.5. That's extremely unlikely.
pram
RichTextArea .Every thing is fine but when I am trying to capture
keyboard event in IE I am not able to catch it.But working wonderfully
in Mozilla.
Code snippet :
RichTextArea area = new RichTextArea();
area.addKeyboardListener(new KeyboardListenerAdapter() {
public void onKeyDown(Widget sender, char keyCode, int modifiers)
{
Window.alert("key down "+keyCode);
}
public void onKeyPress(Widget sender, char keyCode, int
modifiers) {
Window.alert("key pressed "+keyCode);
}
public void onKeyUp(Widget sender, char keyCode, int modifiers)
{
Window.alert("key up "+keyCode);
}
});