[gwt-contrib] Compiling an application with current master
Hi, I was trying out the latest changes in the master branch. Is there something special I have take into account when using the gwt-maven-plugin? When doing a gwt:compile I get this error. [INFO] Loading inherited module 'GwtPlayground' [INFO]Loading inherited module 'com.google.gwt.user.User' [INFO] Loading inherited module 'com.google.gwt.media.Media' [INFO] Loading inherited module 'com.google.gwt.user.UI' [INFO] Loading inherited module 'com.google.gwt.uibinder.UiBinder' [INFO][ERROR] Line 20: Unexpected element 'resource' [INFO][ERROR] Failure while parsing XML It works with (S)DM. Any suggestions? Cheers, Johannes -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/52a73975-7c39-4b21-8bab-7f8708dfaa31%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: Compiling an application with current master
Thanks. That solved the issue! Am Montag, 18. August 2014 16:12:24 UTC+2 schrieb Thomas Broyer: On Monday, August 18, 2014 3:31:35 PM UTC+2, Johannes Barop wrote: Hi, I was trying out the latest changes in the master branch. Is there something special I have take into account when using the gwt-maven-plugin? When doing a gwt:compile I get this error. [INFO] Loading inherited module 'GwtPlayground' [INFO]Loading inherited module 'com.google.gwt.user.User' [INFO] Loading inherited module 'com.google.gwt.media.Media' [INFO] Loading inherited module 'com.google.gwt.user.UI' [INFO] Loading inherited module 'com.google.gwt.uibinder.UiBinder' [INFO][ERROR] Line 20: Unexpected element 'resource' [INFO][ERROR] Failure while parsing XML It works with (S)DM. Any suggestions? The error would mean you still have an older gwt-dev in the classpath. Could it be that you forgot to override the GWT dependencies of the gwt-maven-plugin itself? http://mojo.codehaus.org/gwt-maven-plugin/user-guide/using-different-gwt-sdk-version.html or maybe a dependency that transitively depends on gwt-dev? -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/0e523536-d2fb-4ca0-b379-8edd3eb8e8a6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Publish nighly snapshots of GWT builds to Maven
Hi, what do you think of publishing nightly builds of GWT to a Maven repository? This would save users which want to try/work with latest/unreleased features of building it on their own. A repository exists already. But I don't know who has write access to it https://oss.sonatype.org/content/repositories/google-snapshots/com/google/gwt/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
GWT-RPC: Passing a reference to another serializable type
Hello. I have a RPC service which needs to reference another serializable class in it's result. Since it's impossible to serialize `Class` we just pass the full name. The client then has to lookup the Class instance by the given class name. A generator does index the needed class names during compilation. I was wondering if there is a better way to do this because GWT RPC has already a mechanism to lookup classes by name interally I thought I could reuse this. Thanks in advance, Johannes -- 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/groups/opt_out.
Re: Use SuggestBox suggestions in another widget
Hi, the best code to refer is the source code of SuggestBox itself. Having a look at this constructor you'll notice an interface SuggestionDisplay. The default implementation uses a MenuBar to display a list of text items. You can easily implement any custom rendering by implementing this interface and passing it to the SuggestBox's constructor. Cheers, Johannes Am 02.07.2013 um 23:49 schrieb rahul neekhra rahul.n...@gmail.com: Thanks Kartik... with Customized Display u mean a simple panel right? or its diff widget. And also i donnot need the suggestion which we usually(like google search) show in suggest box instead i need to show it in seprate panel. how can I refresh my suggestion all the time in another panel when we type in suggest box? please refer some code if you can. Thanks Rahul On Tuesday, 2 July 2013 15:49:13 UTC-4, Kartik Suba wrote: Hey you can easily make Customized Suggestion box and also a Customized Display associated with it that will show the suggestions in the panel where ever it is. I have already implemented a Custom Suggest box as I wanted the SuggestionList to be displayed even when nothing is entered. So that I can easily extend and incorporate your functionality. Do try making customized one altogether. Do let me know if you needa code for reference. Kartik... On Tuesday, 2 July 2013 03:26:50 UTC+5:30, rahul neekhra wrote: I need similar thing, but in my case i want to hide the suggestion from text box and need to list them in seprate Panel with additional info. How we have achieve it? Regards Rahul On Tuesday, 16 June 2009 13:56:08 UTC-4, Josh wrote: Hi, I have been trying to think of a good way to add a specific feature to my application to search through a list of data, but can't figure anything out. Here is what I would like: The interface would be a suggest box, and a vertical panel, or grid of some sort with data. Initially all of the options are shown, as links, in the vertical panel/grid. When the user starts to type in the SuggestBox, not only does the normal SuggestBox functioanlity occur, but also the panel/ grid of all data updates as well to only have entries that match the users input. Is this possible? Thanks, Josh -- 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/groups/opt_out. -- 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/groups/opt_out.
Automatic reloading of the web application context in GWT's internal Jetty
Hi, I regularly work with server side code in the Development Mode and GWT's internal Jetty. I was always annoyed by the need to manually reload/deploythe application when I did change something on the server side. Especially when I forgot it. To be super productive I want to see my code changes in client and server side in the browser immediately. JRebel works out fine but it's rather expensive and for my usecases it was just overblown. Instead I use Jetty to poll for added, removed and changed class files and just reload the web application context. This work out fine for my applications because they boot up in miliseconds. However this cannot be configured straight because the boot process of the Jetty instance is hard-wired in GWT. I'm using a small helper class which extends GWT's JettyLauncher and adds the needed configuration. Today I released it as OpenSource: https://github.com/jbarop/gwt-hotdeployment It's available from the Central Maven Repository. To use it you only have to add it as dependency and set de.barop.gwt.HotDeploymentJettyLauncher as Server launcher for the Development Mode. See the project's README and/or demo application for details. Cheers, Johannes -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Overuse of AssumedStale Issue Tag
Hi, after reading this thread I have to write that I'm absolutely shocked about the expectations that some here have. It seems that you've forgotten that GWT is an open source project which does not imply that some team is going to implement your wishes for free. Back to topic: An issue which has not seen any real contribution for some time should be assumed dead and not clog the other ones. And hey, this doesn't mean that your issue is never being addressed. It means that YOU have to put some work in it. This hasn't to be the ultimate fix but may be some ideas how to fix it or some convincing why it's important. I had some free time lately where I wanted to work on some random issue. It turned out that it is very hard to find one because all of junk floating around in the tracker. Cheers, Johannes Am 08.06.2013 um 21:23 schrieb Jeff Schnitzer j...@infohazard.org: Hi Thomas. I have two comments that I hope you will find helpful: * I think most of the blowback from this could have been prevented with a little more communication. Yes, it's common for big projects to clean out stale bug databases by closing everything and re-opening issues when stakeholders speak up - but it's a good idea to folks know the procedure. Just putting speak up if you think this issue is still appropriate in the closing comment would have been enough. * It appears that you're using NotPlanned as a polite form of WontFix. This is a bad idea because it looks like a priority setting; there is already a Priority tag. WontFix is an appropriate response to issues which are considered to be outside the scope of GWT core, but NotPlanned is being misused for issues which are clearly within the scope of GWT core but simply not prioritized. For example, consider this issue: https://code.google.com/p/google-web-toolkit/issues/detail?id=3303 This is clearly within the perview of GWT core; it can't be implemented as a plugin, it would bring value to GWT, and there are some nonzero number of people who would like to see it addressed. I totally understand that it is not a priority for the GWT development team... so why not leave it open and deprioritize it? I fear that using NotPlanned instead of WontFix confuses low-priority issues with shouldn't be planned issues. It's very important to maintain a distinction between the two. Thanks, Jeff On Tue, Jun 4, 2013 at 2:11 AM, Thomas Broyer t.bro...@gmail.com wrote: On Tuesday, June 4, 2013 10:19:27 AM UTC+2, Davide Cavestro wrote: @Ed I really hope you are right... but so far I've had the same feelings of Mauro and David I guess some discouragement/vexation could be avoided adding an explanatory comment before or contextually tagging an issue as AssumedStale, and especially avoid stating I spent more than half an hour reading the code and the specs and doing tests. We can't realistically spend as many time on each and every opened issue. That really makes me wonder... The quote above is out of context: it was a reply to Mauro's This is the kind of feedback I would have appreciated before setting the AssumedStale keyword. So let's try again: the issue tracker has been neglected for years, leading to many issues open and never triaged; we need to clean that up we can't realistically spend half an hour for each and every of these issues: 1500 issues or so would take 750 man×hour, and nobody works full-time just on this (that'd be 100 workdays, i.e. 5 months, if one person were dedicated full-time verifying issues before closing them; surely we can spend everyone's time better) so as Ray Cromwell says, the only viable option is to crowd source: when in doubt, close the issue and see if someone complains, and then only spend time on that issue. Then we have to set priorities, because we're not paid to work on GWT (some Google employees are, but their priorities are the ones of Google; this is the reason why the issue tracker had been neglected for so long and why Google chose to make GWT more open by forming the Steering Committee). On the issue Mauro points out and many others where Daniel replies with feel free to provide patch, we can reopen it but if nobody spends the time to fix it, in a year from now we'll have the same mess in the issue tracker. On that specific issue, I could change the status to NotPlanned (so it's still closed, but removes the word stale) but would it change anything to the way the issue is handled after that? No. (though if you think NotPlanned would be better than AssumedStale, I can make that change). I've had issues open for years, patches pending review for months. I've been there. Daniel also closes some of the issues I reported some time ago [1], and my response is to post patches: e.g. https://code.google.com/p/google-web-toolkit/issues/detail?id=6227 I understand that everyone does not have the GWT sources setup to
Re: Overuse of AssumedStale Issue Tag
The problem is that you don't know in the beginning which issues are important. Most issues are not even bugs or hard to reproduce because it's so damn outdated. If I want to hack on GWT I don't want to spend ages in finding relevant issues. If you find an important bug/issue marked as AssumedStale then talk about it. Am 09.06.2013 um 17:14 schrieb Mauro Molinari mauro...@tiscali.it: Il 09/06/2013 14:48, Johannes Barop ha scritto: I had some free time lately where I wanted to work on some random issue. It turned out that it is very hard to find one because all of junk floating around in the tracker. I still don't understand (and never will) why old non-fixed bug reports should be considered junk. I won't bother to open a new issue again if this is the case. Mauro. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Add History.getUrl(String token) which returns the correspon...
Johannes Barop has uploaded a new patch set (#2). Change subject: Add History.getUrl(String token) which returns the corresponding URL for a history token. .. Add History.getUrl(String token) which returns the corresponding URL for a history token. This enables custom History implementations (for example a implementation with pushstate) to modify the display of URLs in widgets (for example Hyperlink). Change-Id: I9f9b261547b539489d9cee8a72f660264d64e9f2 --- M user/src/com/google/gwt/user/client/History.java M user/src/com/google/gwt/user/client/impl/HistoryImpl.java M user/src/com/google/gwt/user/client/ui/Hyperlink.java 3 files changed, 17 insertions(+), 2 deletions(-) -- To view, visit https://gwt-review.googlesource.com/2960 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: newpatchset Gerrit-Change-Id: I9f9b261547b539489d9cee8a72f660264d64e9f2 Gerrit-PatchSet: 2 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: Johannes Barop j...@barop.de -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Add History.getUrl(String token) which returns the correspon...
Johannes Barop has posted comments on this change. Change subject: Add History.getUrl(String token) which returns the corresponding URL for a history token. .. Patch Set 2: The first alternative is HyperlinkImpl. But this would introduce spaghetti inheritance because of the existing HyperlinkImpl's. And it clutters the History stuff across multiple classes. Other alternative: Add it only to HistoryImpl and let Hyperlink use HistoryImpl directly. But this is not optimal because then we have to duplicate the HistoryImpl.init() error handling and it feels hacky to me. I think a new method to generate a link for a given history token is the best way in the end because generating URLs is a part of implementing History mechanisms. This change makes the code of gwt-pushstate simpler. However I have already a workaround for it. So it's not critical and we can take time to think over it. -- To view, visit https://gwt-review.googlesource.com/2960 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: comment Gerrit-Change-Id: I9f9b261547b539489d9cee8a72f660264d64e9f2 Gerrit-PatchSet: 2 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: Johannes Barop j...@barop.de Gerrit-Reviewer: Goktug Gokdogan gok...@google.com Gerrit-Reviewer: Jens Nehlmeier jens.nehlme...@gmail.com Gerrit-Reviewer: Johannes Barop j...@barop.de Gerrit-HasComments: No -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Add History.getUrl(String token) which returns the correspon...
Johannes Barop has uploaded a new patch set (#3). Change subject: Add History.getUrl(String token) which returns the corresponding URL for a history token. .. Add History.getUrl(String token) which returns the corresponding URL for a history token. This enables custom History implementations (for example a implementation with pushstate) to modify the display of URLs in widgets (for example Hyperlink). Change-Id: I9f9b261547b539489d9cee8a72f660264d64e9f2 --- M user/src/com/google/gwt/user/client/History.java M user/src/com/google/gwt/user/client/impl/HistoryImpl.java M user/src/com/google/gwt/user/client/ui/Hyperlink.java 3 files changed, 16 insertions(+), 2 deletions(-) -- To view, visit https://gwt-review.googlesource.com/2960 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: newpatchset Gerrit-Change-Id: I9f9b261547b539489d9cee8a72f660264d64e9f2 Gerrit-PatchSet: 3 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: Johannes Barop j...@barop.de Gerrit-Reviewer: Goktug Gokdogan gok...@google.com Gerrit-Reviewer: Jens Nehlmeier jens.nehlme...@gmail.com Gerrit-Reviewer: Johannes Barop j...@barop.de -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Add History.getUrl(String token) which returns the correspon...
Johannes Barop has uploaded a new change for review.
https://gwt-review.googlesource.com/2960
Change subject: Add History.getUrl(String token) which returns the
corresponding URL for a history token.
..
Add History.getUrl(String token) which returns the corresponding URL for a
history token.
This enables custom History implementations (for example a implementation
with pushstate) to modify the display of URLs in widgets (for example
Hyperlink).
Change-Id: I9f9b261547b539489d9cee8a72f660264d64e9f2
---
M user/src/com/google/gwt/user/client/History.java
M user/src/com/google/gwt/user/client/impl/HistoryImpl.java
M user/src/com/google/gwt/user/client/ui/Hyperlink.java
3 files changed, 20 insertions(+), 2 deletions(-)
diff --git a/user/src/com/google/gwt/user/client/History.java
b/user/src/com/google/gwt/user/client/History.java
index 285ffee..03a29e8 100644
--- a/user/src/com/google/gwt/user/client/History.java
+++ b/user/src/com/google/gwt/user/client/History.java
@@ -18,6 +18,7 @@
import com.google.gwt.core.client.GWT;
import com.google.gwt.core.client.impl.Disposable;
import com.google.gwt.core.client.impl.Impl;
+import com.google.gwt.dom.client.AnchorElement;
import com.google.gwt.event.logical.shared.ValueChangeEvent;
import com.google.gwt.event.logical.shared.ValueChangeHandler;
import com.google.gwt.event.shared.HandlerManager;
@@ -240,4 +241,14 @@
WrapHistory.remove(impl.getHandlers(), listener);
}
}
+
+ /**
+ * Gets the corresponding URL for the given history token.
+ *
+ * @param historyToken History token to generate the URL for.
+ */
+ public static String getUrl(String historyToken) {
+return impl.getUrl(historyToken);
+ }
+
}
diff --git a/user/src/com/google/gwt/user/client/impl/HistoryImpl.java
b/user/src/com/google/gwt/user/client/impl/HistoryImpl.java
index af675cd..d960111 100644
--- a/user/src/com/google/gwt/user/client/impl/HistoryImpl.java
+++ b/user/src/com/google/gwt/user/client/impl/HistoryImpl.java
@@ -16,12 +16,16 @@
package com.google.gwt.user.client.impl;
import com.google.gwt.core.client.JavaScriptObject;
+import com.google.gwt.dom.client.AnchorElement;
import com.google.gwt.event.logical.shared.HasValueChangeHandlers;
import com.google.gwt.event.logical.shared.ValueChangeEvent;
import com.google.gwt.event.logical.shared.ValueChangeHandler;
import com.google.gwt.event.shared.GwtEvent;
import com.google.gwt.event.shared.HandlerManager;
import com.google.gwt.event.shared.HandlerRegistration;
+import com.google.gwt.user.client.DOM;
+import com.google.gwt.user.client.Element;
+import com.google.gwt.user.client.History;
/**
* Native implementation associated with
@@ -149,6 +153,10 @@
}
}
+ public String getUrl(String historyToken) {
+return # + History.encodeHistoryToken(historyToken);
+ }
+
protected native String decodeFragment(String encodedFragment) /*-{
// decodeURI() does *not* decode the '#' character.
return decodeURI(encodedFragment.replace(%23, #));
diff --git a/user/src/com/google/gwt/user/client/ui/Hyperlink.java
b/user/src/com/google/gwt/user/client/ui/Hyperlink.java
index 61b9821..3366aa4 100644
--- a/user/src/com/google/gwt/user/client/ui/Hyperlink.java
+++ b/user/src/com/google/gwt/user/client/ui/Hyperlink.java
@@ -342,8 +342,7 @@
assert targetHistoryToken != null
: targetHistoryToken must not be null, consider using Anchor
instead;
this.targetHistoryToken = targetHistoryToken;
-String hash = History.encodeHistoryToken(targetHistoryToken);
-DOM.setElementProperty(anchorElem, href, # + hash);
+DOM.setElementProperty(anchorElem, href,
History.getUrl(targetHistoryToken));
}
public void setText(String text) {
--
To view, visit https://gwt-review.googlesource.com/2960
To unsubscribe, visit https://gwt-review.googlesource.com/settings
Gerrit-MessageType: newchange
Gerrit-Change-Id: I9f9b261547b539489d9cee8a72f660264d64e9f2
Gerrit-PatchSet: 1
Gerrit-Project: gwt
Gerrit-Branch: master
Gerrit-Owner: Johannes Barop j...@barop.de
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are subscribed to the Google Groups GWT Contributors group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Add History.getUrl(String token) which returns the correspon...
Johannes Barop has posted comments on this change. Change subject: Add History.getUrl(String token) which returns the corresponding URL for a history token. .. Patch Set 1: Please note the missing test for History.getUrl as I unsure how to write a good test case for it. I'm open for suggestions -- To view, visit https://gwt-review.googlesource.com/2960 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: comment Gerrit-Change-Id: I9f9b261547b539489d9cee8a72f660264d64e9f2 Gerrit-PatchSet: 1 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: Johannes Barop j...@barop.de Gerrit-Reviewer: Johannes Barop j...@barop.de Gerrit-HasComments: No -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Re: GWT does not normalize IE mangling from http 204 code to 1223 (Issue 5031) (issue1875803)
My last commit caused a new Change-Id which caused a new issue to be created: https://gwt-review.googlesource.com/1460 Is this correct? Did I something wrong? Am 14.12.2012 um 15:29 schrieb j...@barop.de: New version in gerrit: https://gwt-review.googlesource.com/#/c/1440/ http://gwt-code-reviews.appspot.com/1875803/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: gwt-pushstate: Easy to use HTML5 pushState support for GWT
Hey, thanks for your feedback! 'gwt.codesvr' is only filtered. Other query-string parameters should not be altered. However I've decided to add the query-string to the historyToken. It turned out that this is a bad idea because then place is not the same place as place?some=foo. This may cause the effect of removing the complete query string. http://gwt-pushstate-examples.appspot.com/!homePage?foo=bar; The place !homePage?foo=bar is not found and the user get's redirected to http://gwt-pushstate-examples.appspot.com/!homePage; I'm going to fix that soon. BTW: If you have changes I would appreciate it if you push the changes back. Cheers, Johannes Am 12.12.2012 um 13:07 schrieb ChrisK: Great work! As far as I can see it will remove query parameters when using pushState? I may extend it to support passing through all query parameters rather than just gwt.codesvr. On Wednesday, 21 November 2012 17:17:25 UTC, Johannes Barop wrote: Hello GWT community, I've just released gwt-pushstate. It implements HTML5 pushState with GWTs standard History API and should work with existing applications fairly well. It also makes sure that the development mode doesn't break and provides a transparent fallback for non-pushState browsers. It's open source (Apache2) and uploaded to the Maven central repository. You can find the source here: https://github.com/jbarop/gwt-pushstate A running sample application is uploaded here: http://gwt-pushstate-examples.appspot.com The sample is basicly GWTP-0.7's gwtp-sample-hplace with little modifications to add the pushState support: https://github.com/jbarop/gwt-pushstate/commit/a3d278b2fae71adc4ea7fb22c5eb121ada36b644 Any feedback heavily appreciated. Johannes -- 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/-/34cywFthT2YJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: gwt-pushstate: Easy to use HTML5 pushState support for GWT
Thanks for pointing this problem out! I digged a bit and found out that History.init() is called before the HistoryAsserter because LoggingConfiguration does use History. Now I see that having a separate EntryPoint for the History is a semi productive idea! I'll fix this tomorrow! Cheers, Johannes Am 12.12.2012 um 15:16 schrieb ChrisK cknow...@gmail.com: No problem. It seems to stem from how pushState expects the query string to also be pushed in as well I think? As long as query parameters on links are maintained I think it should be fine. I'm having trouble getting HistoryAsserter to run before HistoryImplPushState.init() which means on pushState supported browser, any query string param apart from 'gwt.codesvr gets removed by the first line in HistoryImplPushState.init() before the HistoryConverter has a chance to kick in. Perhaps I've missing something. It means hitting a URL like this: http://127.0.0.1:/?gwt.codesvr=127.0.0.1:9997logLevel=FINE#someHistoryToken Actually goes to: http://127.0.0.1:/someHistoryToken?gwt.codesvr=127.0.0.1:9997 i.e. it loses the initial query parameters by the time the app loads On Wednesday, 12 December 2012 13:39:47 UTC, Johannes Barop wrote: Hey, thanks for your feedback! 'gwt.codesvr' is only filtered. Other query-string parameters should not be altered. However I've decided to add the query-string to the historyToken. It turned out that this is a bad idea because then place is not the same place as place?some=foo. This may cause the effect of removing the complete query string. http://gwt-pushstate-examples.appspot.com/!homePage?foo=bar; The place !homePage?foo=bar is not found and the user get's redirected to http://gwt-pushstate-examples.appspot.com/!homePage; I'm going to fix that soon. BTW: If you have changes I would appreciate it if you push the changes back. Cheers, Johannes Am 12.12.2012 um 13:07 schrieb ChrisK: Great work! As far as I can see it will remove query parameters when using pushState? I may extend it to support passing through all query parameters rather than just gwt.codesvr. On Wednesday, 21 November 2012 17:17:25 UTC, Johannes Barop wrote: Hello GWT community, I've just released gwt-pushstate. It implements HTML5 pushState with GWTs standard History API and should work with existing applications fairly well. It also makes sure that the development mode doesn't break and provides a transparent fallback for non-pushState browsers. It's open source (Apache2) and uploaded to the Maven central repository. You can find the source here: https://github.com/jbarop/gwt-pushstate A running sample application is uploaded here: http://gwt-pushstate-examples.appspot.com The sample is basicly GWTP-0.7's gwtp-sample-hplace with little modifications to add the pushState support: https://github.com/jbarop/gwt-pushstate/commit/a3d278b2fae71adc4ea7fb22c5eb121ada36b644 Any feedback heavily appreciated. Johannes -- 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/-/34cywFthT2YJ. To post to this group, send email to google-we...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- 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/-/OYrwtnfjXJwJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Firefox 17 dev plugin
ongoing http://gwt-code-reviews.appspot.com/1870803/ Am 22.11.2012 um 13:31 schrieb Karl: So here we go again, any idea when the dev mode plugin for firefox 17 will be available? -- 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/-/uKVStHR8CyoJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: gwt-pushstate: Easy to use HTML5 pushState support for GWT
Thanks for pointing that out. Am 21.11.2012 um 18:38 schrieb Thomas Broyer: Just a small note: why are you inheriting c.g.g.logging.Logging? You don't need to inherit anything if you just use java.util.logging, and if you need to use classes from c.g.g.logging.client then you should rather inherit LoggingDisabled. On Wednesday, November 21, 2012 6:17:25 PM UTC+1, Johannes Barop wrote: Hello GWT community, I've just released gwt-pushstate. It implements HTML5 pushState with GWTs standard History API and should work with existing applications fairly well. It also makes sure that the development mode doesn't break and provides a transparent fallback for non-pushState browsers. It's open source (Apache2) and uploaded to the Maven central repository. You can find the source here: https://github.com/jbarop/gwt-pushstate A running sample application is uploaded here: http://gwt-pushstate-examples.appspot.com The sample is basicly GWTP-0.7's gwtp-sample-hplace with little modifications to add the pushState support: https://github.com/jbarop/gwt-pushstate/commit/a3d278b2fae71adc4ea7fb22c5eb121ada36b644 Any feedback heavily appreciated. Johannes -- 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/-/NyulPSwagEIJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: [gwt-contrib] GWT 2.5 Final - Next Week
I'm still having this issue: http://code.google.com/p/google-web-toolkit/issues/detail?id=7475 Am 18.10.2012 um 17:56 schrieb unnurg unn...@google.com: Hi Guys - We are going to be pushing the 2.5 RC2 (plus 1-2 minor cherrypicks) to Final next week - if there are any problems, please let me (unn...@google.com) know before Monday morning. Note that problems includes only regressions - so stuff that worked in 2.4 and is now broken in 2.5. Thanks everyone! - Unnur -- http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: New version not being detected by browser
Hello, you have to configure your server to tell the clients to never cache .nocache.html files. See: https://developers.google.com/web-toolkit/doc/latest/FAQ_DebuggingAndCompiling#What%27s_with_all_the_cache/nocache_stuff_and_weird_filenames J. Am 29.07.2012 um 04:55 schrieb ERS: Hello all. I'm facing an issue almost everytime I upload a new version of my app to tomcat. The browser does not detect that there is a new app ... and the RPC calls fail. Then I have to click refresh a few times (or CTRL+F5) ... then the browser gets the new version. But end-users dont know that and may quit early... Is it normal? What should I do during deployment? Thanks -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 2.5, -compileReport and closure compiler
http://code.google.com/p/google-web-toolkit/issues/detail?id=7475 Am 02.07.2012 um 16:25 schrieb Stefano Ciccarelli: I've noticed that if I enable the closure compiler the -compileReport flag is totaly ignored and the soycReport in the extra folder is missing. Someone has a workaround? -- Nel mondo esistono 10 categorie di persone, quelle che capiscono il binario e quelle che non lo capiscono. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: A good book to understand GWT 2.4
Hi, This is hard to answer because I don't know which version of GWT you reference. But try this one: http://www.manning.com/tacy/ Cheers, Johannes Am 25.06.2012 um 15:04 schrieb Qrunk: Hi , Please let me know any good book with all updated features of GWT (i.e. till 2.4) this will make a great help. Thanks -- 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/-/d_II_WLmLC4J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
How to use Super Dev Mode
Hi, I'm trying to get a simple Application with the Super Dev Mode from trunk running. While I can get the CodeServer to run, I'm unsure how to start my Application with it. My first problem is that the CodeServer doesn't seem not to serve any static files from the war directory. This might be just the bootstrap HTML file but may be other needed external dependencies. Is this a bug or should I use another web server for static dependencies (jetty) which proxies to the CodeServer when it comes to loading the module? For now I've placed a bootstrap HTML file in the module's public folder in order to being able to start the application. I can load my module and the Dev Mode on works but if I change the source code and recompile the module with the Dev Mode On I'm not getting any changes. I dunno if I'm doing something completely wrong and would appreciate some help :-) Cheers, Johannes -- 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/-/eAvgSPAZQncJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: How to use Super Dev Mode
I'm still having troubles to see any changes. 1.) The App is loaded through the CodeServer 2.) I change something in the code. 3.) I recompile the module by hitting Dev Mode on 4.) I reload the page -- I do not see the changes I did to the source. Am 23.06.2012 um 13:30 schrieb Jens: I think currently the codeserver only serves the compiled JavaScript of your app. So you still have to use a server that serves your server side code. Thats what I do: 1.) create a new module.gwt.xml that inherits your main app and adds the xsiframe linker and sets the devModeRedirectEnabled property (see: http://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/hello/src/com/google/gwt/sample/hello/Hello.gwt.xml?spec=svn11016r=11016) 2.) Start code server with that new module 3.) copy your apps host html page and modify it to point to the bootstrap file provided by the code server. So instead of script src=app/app.nocache.js you now have script src=http://host:port/app/app.nocache.js;. Thats why you need a different linker in your module.gwt.xml. 4.) Deploy your gwt app like always, e.g. starting the normal dev mode to use embedded jetty or deploy it using an external server. 5.) Open your deployed host html page in the browser and it should load the compiled app from the SuperDevMode code server. If you have started the normal dev mode to use embedded jetty as server you would omit the gwt.codeserver GET parameter when loading the host html page. -- J. -- 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/-/9oYq7mW0Er8J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: where to download gwt 2.4.0 source code?
Hi, in case you have an Eclipse project: Right click on the project, Maven - Download Sources. J. Am 02.06.2012 um 18:19 schrieb tong123123: sorry, where is the checkbox download sources? Joseph Lust於 2012年6月2日星期六UTC+8下午10時48分32秒寫道： Are you familiar with Maven? It makes this very simple. Just check the box for download sources. 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/-/-gCedW9Pd1oJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
