Re: GWT 2.6.1 is now available
Great On Saturday, May 10, 2014 5:54:20 AM UTC+8, Daniel Kurka wrote: Hi GWT community, We're excited to announce the GWT 2.6.1 release! Many of you noticed it was uploaded a few days ago, but if you missed it, you can download it here http://goo.gl/BLc6R8. This release has also been uploaded to Maven Central with the version string of 2.6.1”. GWT 2.6.1 is a bug fix release for GWT 2.6.0 containing 21 changes and fixes for GWT with almost 50% coming from outside of Google. Thanks so much to everyone who reported issues and/or submitted patches, with a special thanks to Thomas Broyer! For a summary of user-visible changes, please see the GWT release noteshttp://www.gwtproject.org/release-notes.html. And as always, please report any issues using the GWT issue trackerhttps://code.google.com/p/google-web-toolkit/issues/list . -Daniel, on behalf of the GWT open source project -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.6.1 is now available
Hi, My automated dependency resolving scripts (ant + ivy) are failing because there is no http://repo1.maven.org/maven2/com/google/gwt/gwt-user/2.6.1/gwt-user-2.6.1-sources.jar when it is clearly listed in http://repo1.maven.org/maven2/com/google/gwt/gwt-user/2.6.1/ Go figure... Maybe it will resolve itself. Time is the best healer after all... Vassilis Virvilis On 05/12/14 06:02, Rehmetjan Tursun wrote: Great On Saturday, May 10, 2014 5:54:20 AM UTC+8, Daniel Kurka wrote: Hi GWT community, We're excited to announce the GWT 2.6.1 release! Many of you noticed it was uploaded a few days ago, but if you missed it, you can download it here http://goo.gl/BLc6R8. This release has also been uploaded to Maven Central with the version string of 2.6.1”. GWT 2.6.1 is a bug fix release for GWT 2.6.0 containing 21 changes and fixes for GWT with almost 50% coming from outside of Google. Thanks so much to everyone who reported issues and/or submitted patches, with a special thanks to Thomas Broyer! For a summary of user-visible changes, please see the GWT release notes http://www.gwtproject.org/release-notes.html. And as always, please report any issues using the GWT issue tracker https://code.google.com/p/google-web-toolkit/issues/list. -Daniel, on behalf of the GWT open source project -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com mailto:google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com mailto:google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.6.1 is now available
There were some mirroring issues on Central (gwt-codeserver-2.6.1.jar being a 404 while listed at …/gwt-codeserver/2.6.1/, same symptom) and Sonatype told me it was now OK: https://twitter.com/sonatype_ops/status/465278441458114560 At least gwt-codeserver is now OK. Ping them if you have issues. On Monday, May 12, 2014 10:19:08 AM UTC+2, Vassilis Virvilis wrote: Hi, My automated dependency resolving scripts (ant + ivy) are failing because there is no http://repo1.maven.org/maven2/com/google/gwt/gwt-user/2.6.1/gwt-user-2.6.1-sources.jar when it is clearly listed in http://repo1.maven.org/maven2/com/google/gwt/gwt-user/2.6.1/ Go figure... Maybe it will resolve itself. Time is the best healer after all... Vassilis Virvilis On 05/12/14 06:02, Rehmetjan Tursun wrote: Great On Saturday, May 10, 2014 5:54:20 AM UTC+8, Daniel Kurka wrote: Hi GWT community, We're excited to announce the GWT 2.6.1 release! Many of you noticed it was uploaded a few days ago, but if you missed it, you can download it here http://goo.gl/BLc6R8. This release has also been uploaded to Maven Central with the version string of 2.6.1”. GWT 2.6.1 is a bug fix release for GWT 2.6.0 containing 21 changes and fixes for GWT with almost 50% coming from outside of Google. Thanks so much to everyone who reported issues and/or submitted patches, with a special thanks to Thomas Broyer! For a summary of user-visible changes, please see the GWT release notes http://www.gwtproject.org/release-notes.html. And as always, please report any issues using the GWT issue tracker https://code.google.com/p/google-web-toolkit/issues/list. -Daniel, on behalf of the GWT open source project -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com mailto:google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com mailto:google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.6.1 is now available
Hi Thomas, Thanks for the quick reply as always. Ping them where? I am not sure. To twitter? On Mon, May 12, 2014 at 11:25 AM, Thomas Broyer t.bro...@gmail.com wrote: There were some mirroring issues on Central (gwt-codeserver-2.6.1.jar being a 404 while listed at …/gwt-codeserver/2.6.1/, same symptom) and Sonatype told me it was now OK: https://twitter.com/sonatype_ops/status/465278441458114560 At least gwt-codeserver is now OK. Ping them if you have issues. On Monday, May 12, 2014 10:19:08 AM UTC+2, Vassilis Virvilis wrote: Hi, My automated dependency resolving scripts (ant + ivy) are failing because there is no http://repo1.maven.org/maven2/com/google/gwt/gwt-user/2.6.1/ gwt-user-2.6.1-sources.jar when it is clearly listed in http://repo1.maven.org/maven2/com/google/gwt/gwt-user/2.6.1/ Go figure... Maybe it will resolve itself. Time is the best healer after all... Vassilis Virvilis On 05/12/14 06:02, Rehmetjan Tursun wrote: Great On Saturday, May 10, 2014 5:54:20 AM UTC+8, Daniel Kurka wrote: Hi GWT community, We're excited to announce the GWT 2.6.1 release! Many of you noticed it was uploaded a few days ago, but if you missed it, you can download it here http://goo.gl/BLc6R8. This release has also been uploaded to Maven Central with the version string of 2.6.1”. GWT 2.6.1 is a bug fix release for GWT 2.6.0 containing 21 changes and fixes for GWT with almost 50% coming from outside of Google. Thanks so much to everyone who reported issues and/or submitted patches, with a special thanks to Thomas Broyer! For a summary of user-visible changes, please see the GWT release notes http://www.gwtproject.org/release-notes.html. And as always, please report any issues using the GWT issue tracker https://code.google.com/p/google-web-toolkit/issues/list. -Daniel, on behalf of the GWT open source project -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com mailto:google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com mailto:google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout. -- Vassilis Virvilis -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.6.1 is now available
On Monday, May 12, 2014 10:31:42 AM UTC+2, Vassilis Virvilis wrote: Hi Thomas, Thanks for the quick reply as always. Ping them where? I am not sure. To twitter? That's what I used (I was on http://central.sonatype.org/ and clicked on status on the top right), They were very reactive. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.6.1 is now available
This looks I have to create a twitter account. This is crazy. I suppose I will do it so I can as well stop whining anyway... On Mon, May 12, 2014 at 11:39 AM, Thomas Broyer t.bro...@gmail.com wrote: On Monday, May 12, 2014 10:31:42 AM UTC+2, Vassilis Virvilis wrote: Hi Thomas, Thanks for the quick reply as always. Ping them where? I am not sure. To twitter? That's what I used (I was on http://central.sonatype.org/ and clicked on status on the top right), They were very reactive. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout. -- Vassilis Virvilis -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.6.1 is now available
Ok I reported it. On Mon, May 12, 2014 at 12:13 PM, Vassilis Virvilis vasv...@gmail.comwrote: This looks I have to create a twitter account. This is crazy. I suppose I will do it so I can as well stop whining anyway... On Mon, May 12, 2014 at 11:39 AM, Thomas Broyer t.bro...@gmail.comwrote: On Monday, May 12, 2014 10:31:42 AM UTC+2, Vassilis Virvilis wrote: Hi Thomas, Thanks for the quick reply as always. Ping them where? I am not sure. To twitter? That's what I used (I was on http://central.sonatype.org/ and clicked on status on the top right), They were very reactive. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout. -- Vassilis Virvilis -- Vassilis Virvilis -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.6.1 is now available
Maybe you could also have raised an issue at https://issues.sonatype.org/browse/CENTRALSRV On Monday, May 12, 2014 11:13:39 AM UTC+2, Vassilis Virvilis wrote: This looks I have to create a twitter account. This is crazy. I suppose I will do it so I can as well stop whining anyway... On Mon, May 12, 2014 at 11:39 AM, Thomas Broyer t.bro...@gmail.comwrote: On Monday, May 12, 2014 10:31:42 AM UTC+2, Vassilis Virvilis wrote: Hi Thomas, Thanks for the quick reply as always. Ping them where? I am not sure. To twitter? That's what I used (I was on http://central.sonatype.org/ and clicked on status on the top right), They were very reactive. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout. -- Vassilis Virvilis -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Maven pom for gwt-servlet 2.6.1 looks broken on maven central
The pom on maven central for gwt 2.6.1 is broken. See http://repo1.maven.org/maven2/com/google/gwt/gwt-servlet/2.6.1/gwt-servlet-2.6.1.pom -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Maven pom for gwt-servlet 2.6.1 looks broken on maven central
Why? 2014-05-12 16:37 GMT-03:00 Michael Wiles michael.wi...@gmail.com: The pom on maven central for gwt 2.6.1 is broken. See http://repo1.maven.org/maven2/com/google/gwt/gwt-servlet/2.6.1/gwt-servlet-2.6.1.pom -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.6.1 is now available
Also got a problem with http://repo1.maven.org/maven2/com/google/gwt/gwt-servlet/2.6.1/gwt-servlet-2.6.1.pom On Monday, 12 May 2014 12:04:14 UTC+2, Thomas Broyer wrote: Maybe you could also have raised an issue at https://issues.sonatype.org/browse/CENTRALSRV On Monday, May 12, 2014 11:13:39 AM UTC+2, Vassilis Virvilis wrote: This looks I have to create a twitter account. This is crazy. I suppose I will do it so I can as well stop whining anyway... On Mon, May 12, 2014 at 11:39 AM, Thomas Broyer t.br...@gmail.comjavascript: wrote: On Monday, May 12, 2014 10:31:42 AM UTC+2, Vassilis Virvilis wrote: Hi Thomas, Thanks for the quick reply as always. Ping them where? I am not sure. To twitter? That's what I used (I was on http://central.sonatype.org/ and clicked on status on the top right), They were very reactive. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.comjavascript: . To post to this group, send email to google-we...@googlegroups.comjavascript: . Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout. -- Vassilis Virvilis -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: How to use JavaScript to customize both the client and server in a consistent way?
If you only one to expose the JS code to do expressions, you can define a
concrete and reduced context where the expression will be executed. For
example, if you want to evaluate the price, just add all the properties you
may need (probably all properties of the item bean) to the script execution
bindings. The creation of this bindings may not be shared between client
and server, but it's not complicated. Access random internal classes like
MyClass::getSomethingUseful it's a bad idea, it's better to expose explicit
binding, so if you want to expose MyClass::getSomethigUseful you may add a
util object with a getSomethigUseful method, this is safer, and also solves
your client/server problem. Although, the process to add this methods to
the context may also be a little different between client and server.
This reduced context also is a good idea to reduce your second big problem,
the security! Execute dangerous code through this script it's very easy,
and restrict the access it's difficult. There are a lot of articles and
discussions
like http://stackoverflow.com/questions/1399505/sandboxing-jsr-223. I try
to do something similar, but I end up using Groovy (only server) because
this
utility
http://groovy.codehaus.org/api/org/codehaus/groovy/control/customizers/SecureASTCustomizer.html
'solves' the security problem.
On Saturday, May 10, 2014 4:29:56 PM UTC+2, Phineas Gage wrote:
I am writing a GWT app that will be usable by multiple customers. I'd like
for my customers to be able to customize the app, both on the server side
and client side by writing JavaScript. In other words, they could do things
like:
- Set some configuration for their site, like its name, their web site
URL, address, items on their site, etc.
- Write a JavaScript function to, for example, calculate the price for
some item based on its properties. So the price calculation could be done
on both the client and server, and no recompiling would be needed to change
the price calculation.
The beauty of this is that they could write the JavaScript, and it could
be run using JSNI on the client and Rhino on the server, giving consistent
results. This could also get me out of the business of writing a bunch of
administrative UI code to handle the many possibilities for customization
that customers would want, and also give them much more flexibility,
particularly for price calculations, where the customers want endless
flexibility, and writing a rules engine to handle all of those cases would
be very complicated.
Obviously, the JavaScript they write has to be runnable on both the client
and server. And, if it's just a matter of returning primitives or the
customer writing functions that take and return primitives, it's easy.
Simple JavaScript code snippets like this:
var myname='Joe';
function getMyName() { return 'Joe' };
can be syntactically the same for both JSNI and Rhino.
But the fun soon ends. Let's say I want to allow them to call into methods
in Java classes that I've defined, so I can give them an API to do useful
things. The syntax for accessing Java objects from JavaScript is vastly
different between Rhino and JSNI:
// Rhino
com.abc.package.MyClass.getSomethingUseful();
// JSNI: first in Java
public static native String exportGetSomethingUseful() /*-{
getSomethingUseful =
$entry(@com.abc.package.MyClass::getSomethingUseful());
}-*/;
// JSNI: then in JavaScript
getSomethingUseful();
The situation gets more challenging if you want to pass instances of your
own Java classes into JavaScript for their use, or call from JavaScript
into APIs defined in Java. You've got to define host objects in Rhino, and
I'm not even sure how you do it in JSNI without writing glue code by hand
so that they wouldn't have to learn JSNI's arcane syntax,
My question is: I don't think it's possible for the JavaScript syntax to
be the same between JSNI and Rhino without writing some glue code on both
the client and server in JavaScript to insulate them from these syntactical
differences when working with APIs defined in Java. Am I right, or have I
missed anything?
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No startup URLs supplied and no plausible ones found -- use -startupUrl -- not true but why does development mode think it is
Hi, Every time I try to bring up an application in Development mode in Eclipse I get this message and that's as far as it goes: *[WARN] No startup URLs supplied and no plausible ones found -- use -startupUrl* My web.xml includes: welcome-file-list welcome-fileFERPASigningRequest.jsp/welcome-file /welcome-file-list Isn't that the startup URL. I'm confused. ~ Rob -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: No startup URLs supplied and no plausible ones found -- use -startupUrl -- not true but why does development mode think it is
And, BTW, I do have the -startupUrl set in the run configuration for the app in Eclipse. ?? ~ Rob On Monday, May 12, 2014 3:18:17 PM UTC-7, Rob Tanner wrote: Hi, Every time I try to bring up an application in Development mode in Eclipse I get this message and that's as far as it goes: *[WARN] No startup URLs supplied and no plausible ones found -- use -startupUrl* My web.xml includes: welcome-file-list welcome-fileFERPASigningRequest.jsp/welcome-file /welcome-file-list Isn't that the startup URL. I'm confused. ~ Rob -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.6.1 is now available
Hello, any chance to have this updated in Google Plugin for Eclipse - http://dl.google.com/eclipse/plugin/4.3 as well? It still lists 2.6.0 as latest. On Friday, 9 May 2014 23:54:20 UTC+2, Daniel Kurka wrote: Hi GWT community, We're excited to announce the GWT 2.6.1 release! Many of you noticed it was uploaded a few days ago, but if you missed it, you can download it here http://goo.gl/BLc6R8. This release has also been uploaded to Maven Central with the version string of 2.6.1”. GWT 2.6.1 is a bug fix release for GWT 2.6.0 containing 21 changes and fixes for GWT with almost 50% coming from outside of Google. Thanks so much to everyone who reported issues and/or submitted patches, with a special thanks to Thomas Broyer! For a summary of user-visible changes, please see the GWT release noteshttp://www.gwtproject.org/release-notes.html. And as always, please report any issues using the GWT issue trackerhttps://code.google.com/p/google-web-toolkit/issues/list . -Daniel, on behalf of the GWT open source project -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWTproject site menu
On Sat, May 10, 2014 at 8:02 AM, Manuel Carrasco Moñino man...@apache.orgwrote: On Sat, May 10, 2014 at 2:33 AM, 'Goktug Gokdogan' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: Pretty cool. Thanks for all the work. Also special kudos for fixing the styling for download page, it is much more elegant now! Footer: - We are now missing the extra space in the bottom of the pages (the one before the footer) done - The area for the footer is larger and the text is closer to the bottom - I think the original spacing was better. Also if you take a look at the overview page you will see the footer hides part of the image. fixed css Others: - Clicking images shows blank page - perhaps just a deployment issue Don't see this issue, what images do you mean? Click devmode screenshot in http://gwtproject.gquery.org/gettingstarted.html - There is a broken Advanced Topics menu item - I think it is mixed up with the Logging menu item. Fixed, the logging item was indented wrong - I would put Optimize to Advanced topics. Perhaps security and i18n as well. Done, I think i18n could be out. But anyway is difficult to put the edge about what are or not advanced topics - Perhaps move Community - Developer Spotlight under Resources? done - In Resources, we can move gwt surveys to the end of the list done Below are other issues that doesn't look like regressions. Perhaps we can have some other quick wins before publishing the final version? Menu: - Ideally the arrows shouldn't indent the menu items and instead menu items should be aligned by text (e.g. gmail). I'm not sure if you are reusing any widgets here; if you aren't reusing we might want to change that. done. We dont use any widget, just html+css. gquery enhances the list adding handlers using selectors. - We might want to change how menus behave. I actually like GWT Developer pages (e.g. https://developers.google.com/appengine/pricing) where menu items that are parents of the other menu items are not used as links to a content, instead they serve as a placeholder and collapses/expands based when clicked. Also it won't auto collapse existing items. I think all together that is more useable. I have changed parents with not content (href = #) to expand/collapse menu (See 'Advance topics' in docs). Having parent-items with content makes the menu shorter and easy to use, like 'side bars' in google code wikis https://code.google.com/p/support/wiki/WikiSyntax#Side_navigation I'd rather auto-collapse on, but I have set it off as you prefer. Even if you look at the menu in that wiki page, you will see that parent menu items are not acting as links to their own content instead they are just placeholders for grouping and will collapse/expand on click. I think that is the most intuitive and what we should do in the long run, however that might require some work to move the content to child pages. Nevertheless I think the last version is problematic: - Having menu item sometimes collapse sometimes not collapse when clicked is not user friendly as they will behave inconsistently. - As it is difficult and not easy to discover how to collapse a menu with content after it is expanded, it can become annoying for users to not have auto-collapse enabled on navigation. So I think we should either keep the old behavior (i.e. auto-collapse) or move the new behavior (no content association for ALL parent menus, expand and collapse on click, NO auto-collapse). Again the second option is ideal from my point of view but we may want to do it later for reducing the amount work. General: - We have smaller size font for links (probably regular text font is larger than it suppose to be). Fixed - Looks like you made the body wider which I think is good but making the whole page right aligned (i.e. all extra space goes to left) is not a good idea. It looks really bad in widescreen (which many developers has). We should probably follow a different approach for distributing the space (e.g. add the extra space to left until a max value is reached). I dont know if I understand correctly. The width is adjusted based on media sizes, and I have set 3 sizes: wide desktop, small desktop tablets and mobile. Also I have changed the font size (16 - 14px) so as there is more text in the same place, and text alignment (left - justify). I have adjusted content padding for big desktop, I see correctly the pages, let me know if that works for you. LGTM. It looks like it distributes the spacing evenly for left and right sight. I would use less padding before the leftnav but this is mostly ok. I'm not sure if this is a new problem or not but now when you switch through menu items, left nav sometimes jumps around. It looks this is related to scrollbar being shown on the right or not. Perhaps you can use the scrollbar only for the content bar to prevent
