GWT Cross Site Iframe Linker and Script Tags
Hi, can someone please explain to me the technical details why the xsiframe Link can not compile GWT apps which load script tags in their .gwt.xml module? It gives the following error: [ERROR] The Cross-Site-Iframe linker does not support script tags in the gwt.xml files, but the gwt.xml file (or the gwt.xml files which it includes) contains the following script tags: . In order for your application to run correctly, you will need to include these tags in your host page directly. In order to avoid this error, you will need to remove the script tags from the gwt.xml file, or add this property to the gwt.xml file: set-configuration-property name='xsiframe.failIfScriptTag' value='FALSE'/ The error message already tells the workaround, so I know how to compile it. Still, I'm wondering about the reason why it can't compile with script tags? I understand the same origin policy problem with the regular Iframe Linker and XHR. But including a script tag doesn't require XHR. So whats the technical reason behind this? 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/-/vWhzpfWvWNgJ. 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: Suggestion: Why not including the GWT 2.5 - UIBinder Enhancements in the GWT Showcase ?
I added sample code to the MobieWebApp sample, but... Point taken. No promises, but I'll see about getting an example in to showcase. On Sat, Jul 21, 2012 at 12:05 PM, regnoult axel regno...@gmail.com wrote: Hello, I am trying to learn to use Cell widgets and the GWT Showcase was a good start to learn it copying the existing code and then modifying it. I have seen that GWT 2.5 has a new feature that should help (using UI Binder will give a more readable code and maybe reduce it): https://developers.google.com/web-toolkit/doc/latest/DevGuideUiBinder#Rendering_HTML_for_Cells So my question,* if I am not doing a mistake* (because I have not seen any change in the *.ui.xml files of the GWT Showcase), is : - Do you plan to modify the GWT Showcase to integrate this new feature ? Best regards, -- 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/-/0XG5qO35UyQJ. 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. -- Rodrigo Chandia | Software Engineer | rchan...@google.com | 678 7431725 -- 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 components/panels on an externally hosted web page
Brilliant! That did it. Thank you. -- 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/-/E2VWDvf3k6QJ. 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.
Upgrade from 2.2 to 2.4 Issues
Hi Everyone, I've been trying to upgrade a gwt 2.2 project to 2.4 and have been getting lots of number format exceptions similar to below. There seems to be a problem with i18n. My configuration is gwt + maven + spring. I use the eclipse plugin and gwt maven plugin. The maven plugin shares the same version number as gwt (2.4.0). Any ideas on what I might be doing incorrectly? All help would be greatly appreciated. I've put the chunks of the pom file that relate to gwt below: 10:12:17.788 [ERROR] [webclient] '=1' is not a valid integral value java.lang.NumberFormatException: For input string: quot;=1quot; at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Integer.parseInt(Integer.java:449) at java.lang.Integer.parseInt(Integer.java:499) at com.google.gwt.i18n.rebind.MessagesMethodCreator$GenericSelector.generateSelectMatchStart(MessagesMethodCreator.java:326) at com.google.gwt.i18n.rebind.MessagesMethodCreator.generateMessageSelectors(MessagesMethodCreator.java:1459) at com.google.gwt.i18n.rebind.MessagesMethodCreator.createMethodFor(MessagesMethodCreator.java:1202) at com.google.gwt.i18n.rebind.AbstractLocalizableImplCreator.delegateToCreator(AbstractLocalizableImplCreator.java:501) at com.google.gwt.i18n.rebind.MessagesImplCreator.emitMethodBody(MessagesImplCreator.java:92) at com.google.gwt.user.rebind.AbstractGeneratorClassCreator.genMethod(AbstractGeneratorClassCreator.java:276) at com.google.gwt.user.rebind.AbstractGeneratorClassCreator.emitMethods(AbstractGeneratorClassCreator.java:238) at com.google.gwt.user.rebind.AbstractGeneratorClassCreator.emitClass(AbstractGeneratorClassCreator.java:117) at com.google.gwt.i18n.rebind.AbstractLocalizableImplCreator.generateConstantOrMessageClass(AbstractLocalizableImplCreator.java:225) at com.google.gwt.i18n.rebind.LocalizableGenerator.generate(LocalizableGenerator.java:151) at com.google.gwt.i18n.rebind.LocalizableGenerator.generate(LocalizableGenerator.java:124) at com.google.gwt.core.ext.GeneratorExtWrapper.generate(GeneratorExtWrapper.java:48) at com.google.gwt.core.ext.GeneratorExtWrapper.generateIncrementally(GeneratorExtWrapper.java:60) at com.google.gwt.dev.javac.StandardGeneratorContext.runGeneratorIncrementally(StandardGeneratorContext.java:647) at com.google.gwt.dev.cfg.RuleGenerateWith.realize(RuleGenerateWith.java:41) at com.google.gwt.dev.shell.StandardRebindOracle$Rebinder.rebind(StandardRebindOracle.java:78) at com.google.gwt.dev.shell.StandardRebindOracle.rebind(StandardRebindOracle.java:268) at com.google.gwt.dev.shell.ShellModuleSpaceHost.rebind(ShellModuleSpaceHost.java:141) at com.google.gwt.dev.shell.ModuleSpace.rebind(ModuleSpace.java:585) at com.google.gwt.dev.shell.ModuleSpace.rebindAndCreate(ModuleSpace.java:455) at com.google.gwt.dev.shell.GWTBridgeImpl.create(GWTBridgeImpl.java:49) at com.google.gwt.core.client.GWT.create(GWT.java:97) at com.nterop.app.client.view.widget.AuditingWidget_AuditingWidgetUiBinderImpl.createAndBindUi(AuditingWidget_AuditingWidgetUiBinderImpl.java:26) at com.nterop.app.client.view.widget.AuditingWidget_AuditingWidgetUiBinderImpl.createAndBindUi(AuditingWidget_AuditingWidgetUiBinderImpl.java:1) at com.nterop.app.client.view.widget.AuditingWidget.lt;initgt;(AuditingWidget.java:38) at com.nterop.app.client.view.impl.ItemSummaryView.lt;initgt;(ItemSummaryView.java:93) at com.nterop.app.client.impl.ClientFactory.getBrowsePagePresenter(ClientFactory.java:213) at com.nterop.app.client.impl.PageUtility.createPagePresenter(PageUtility.java:268) at com.nterop.app.client.impl.AppController.onValueChange(AppController.java:115) at com.google.gwt.event.logical.shared.ValueChangeEvent.dispatch(ValueChangeEvent.java:128) at com.google.gwt.event.logical.shared.ValueChangeEvent.dispatch(ValueChangeEvent.java:1) at com.google.gwt.event.shared.GwtEvent.dispatch(GwtEvent.java:1) at com.google.web.bindery.event.shared.EventBus.dispatchEvent(EventBus.java:40) at com.google.web.bindery.event.shared.SimpleEventBus.doFire(SimpleEventBus.java:193) at com.google.web.bindery.event.shared.SimpleEventBus.fireEvent(SimpleEventBus.java:88) at com.google.gwt.event.shared.HandlerManager.fireEvent(HandlerManager.java:127) at com.google.gwt.user.client.impl.HistoryImpl.fireEvent(HistoryImpl.java:75) at com.google.gwt.event.logical.shared.ValueChangeEvent.fire(ValueChangeEvent.java:43) at com.google.gwt.user.client.impl.HistoryImpl.fireHistoryChangedImpl(HistoryImpl.java:82) at com.google.gwt.user.client.impl.HistoryImpl.newItem(HistoryImpl.java:126) at com.google.gwt.user.client.History.newItem(History.java:169) at com.google.gwt.user.client.History.newItem(History.java:154) at com.nterop.app.client.impl.AppController.gotoHome(AppController.java:94) at
RequestFactory
Hi , How can I list all the data existing in the database using RF and Hibernate ? -- 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: DevMode for Firefox 14
Many thanks to Allan! ALL: Please star this issue: https://code.google.com/p/chromium/issues/detail?id=138557thanks=138557ts=1343057729 it might help to have better support for GWT devmode development (GWT plugin) for Chrome, and we can forget about firefox. On Monday, July 23, 2012 8:02:49 AM UTC-4, P.G.Taboada wrote: Thank you for jumping in and building the plugins. Do you know if someone else from the team will jump in? Just curious... I know I am a slightly off-topic here, I just don't want to start another thread. It might be that OSX users, especially Safari users don't have a big end-user market share. I have no hard data, but I would not agree it's the same when it comes down to the developers. Since Safari 5.1 we can't use it anymore (Omniweb sucks) and Chrome is not an option (way too slow). We are stuck with Firefox. Is there any plan to get the situation on OSX any better? At least make Chome DevMode usable? brgds Papick On Wednesday, July 18, 2012 2:08:06 AM UTC+2, Alan Leung wrote: While I am technically no longer on the team, I got curious and started looking at the FF14 changes. There were some slight changes in the JS Object layout again but they seem easy enough to fix. I have built it for Linux 32 bit: http://acleung.com/ff14-linux32.xpi -Alan -- 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/-/TZKHRwf0G6EJ. 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: DevMode for Firefox 14
Better devmode for chrome will be super devmode. I think the current plugin issue is a chrome bug that they seem to have no interest in fixing. On Monday, July 23, 2012 11:37:42 AM UTC-4, El Mentecato Mayor wrote: Many thanks to Allan! ALL: Please star this issue: https://code.google.com/p/chromium/issues/detail?id=138557thanks=138557ts=1343057729 it might help to have better support for GWT devmode development (GWT plugin) for Chrome, and we can forget about firefox. On Monday, July 23, 2012 8:02:49 AM UTC-4, P.G.Taboada wrote: Thank you for jumping in and building the plugins. Do you know if someone else from the team will jump in? Just curious... I know I am a slightly off-topic here, I just don't want to start another thread. It might be that OSX users, especially Safari users don't have a big end-user market share. I have no hard data, but I would not agree it's the same when it comes down to the developers. Since Safari 5.1 we can't use it anymore (Omniweb sucks) and Chrome is not an option (way too slow). We are stuck with Firefox. Is there any plan to get the situation on OSX any better? At least make Chome DevMode usable? brgds Papick On Wednesday, July 18, 2012 2:08:06 AM UTC+2, Alan Leung wrote: While I am technically no longer on the team, I got curious and started looking at the FF14 changes. There were some slight changes in the JS Object layout again but they seem easy enough to fix. I have built it for Linux 32 bit: http://acleung.com/ff14-linux32.xpi -Alan -- 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/-/3Gb59ogcVbsJ. 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: Cannot compile from command line
Hi Joseph, thanks for your reply and sorry it took me so long! My batch file looks like this (with real paths this time). It is located in the project's main folder (one level above src folder). The module is renamed to testwiese in the .gwt.xml file using module rename-to java -cp C:\gwt-2.4.0\gwt-dev.jar;C:\gwt-2.4.0\gwt-user.jar;C:\gwt-2.4.0\validation-api-1.0.0.GA.jar;C:\gwt-2.4.0\validation-api-1.0.0.GA-sources.jar;.\lib\gwt-dnd-3.1.2.jar;.\lib\gwt-voices-2.0.0.jar;.\src\de\crizzi\testwiese;.\src com.google.gwt.dev.Compiler -logLevel DEBUG testwiese Am Mittwoch, 18. Juli 2012 03:22:39 UTC+2 schrieb Joseph Lust: Can you supply the commandline argument you're using to launch the GWT compile from in the batch file? Just a wild guess, since you've redacted your path, but on my GWT projects the argument passed in looks something like this: com.lustforge.testbed.TestBed * * Perhaps you need: main.package.client.entrypoint.EntryPoint Sincerely, Joseph -- 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/-/sKm2hfPweuwJ. 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: DevMode for Firefox 14
ALL: Please star this issue: https://code.google.com/p/chromium/issues/detail?id=138557thanks=138557ts=1343057729 it might help to have better support for GWT devmode development (GWT plugin) for Chrome, and we can forget about firefox. You better take a look at: http://code.google.com/p/google-web-toolkit/issues/detail?id=4493#c24 and the two referenced chromium issues. It seems like that the chromium issues do not have a high priority since NPAPI may become obsolete in the future in favor of PPAPI. Its well known that the Chrome Dev Mode plugin is slower compared to Firefox because it has to work around mentioned chromium issues. -- 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/-/x_LiifvyZoUJ. 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: RequestFactory
A good way to start is: https://developers.google.com/web-toolkit/doc/latest/DevGuideRequestFactory *AUS. Cristian Rinaldi Co-founder* Mobile: (+54) 9 (342) 5 238 083 Email: cristian.rina...@logikas.com Skype: csrinaldi Site: www.logikas.com Google Plus https://plus.google.com/u/0/ Logikas +Page https://plus.google.com/u/0/b/114838406697164582224/ __ [image: eco] No me imprimas si no es necesario. PROTEJAMOS EL MEDIO AMBIENTE AVISO LEGAL: Esta informacion es privada y confidencial y está dirigida únicamente a su destinatario. Si usted no es el destinatario original de este mensaje y por este medio pudo acceder a dicha información por favor elimine el mensaje. La distribución o copia de este mensaje está estrictamente prohibida. Excepto que se haya establecido de otra forma, esta comunicación es sólo para propósitos de información y no debe ser considerada como propuesta, aceptación ni como una declaración de voluntad oficial de Logikas Conectando Ideas . La transmisión de e-mails no garantiza que el correo electrónico sea seguro o libre de error. Por consiguiente, no manifestamos que esta información sea completa o precisa. Toda información está sujeta a alterarse sin previo aviso. 2012/7/23 nesrine doghri nesrine.dogh...@gmail.com Hi , How can I list all the data existing in the database using RF and Hibernate ? -- 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. image002.gif
Re: GWT 2.5-rc1 feature uirender is not working as expected.
Yea you are absolutely right. It worked when I removed type attribute
from ui:with tag. I was wondering it has to identify type to call
respective methods on the same and I realized that it tries to match the
variable name with that of name of the parameter to render method (which I
marked in blue color in below code).
--
interface MyUiRenderer extends UiRenderer {
void render(SafeHtmlBuilder sb, *Person person*);
}
--
So Finally working code looks like this.
PersonCell.java
--
public class PearsonCell extends AbstractCellPerson {
interface MyUiRenderer extends UiRenderer {
void render(SafeHtmlBuilder sb, Person person);
}
private static MyUiRendererrenderer=
GWT.create(MyUiRenderer.class);
@Override
public void render(com.google.gwt.cell.client.Cell.Context context,
Person value, SafeHtmlBuilder sb) {
renderer.render(sb, value);
}
}
--
PersonCell.ui.xml
--
ui:UiBinder xmlns:ui='urn:ui:com.google.gwt.uibinder'
ui:with field='person' /
div
First Name :
span
ui:text from='{person.getFname}' /
/span
p
Last Name :
span
ui:text from='{person.getLname}' /
/span
/p
p
Email :
span
ui:text from='{person.getEmailid}' /
/span
/p
/div
/ui:UiBinder
--
Thanks Thomas for your valuable inputs. Without that it would have been
painful to identify the issue.
Thanks,
-Pandurang.
On Thursday, 19 July 2012 13:34:11 UTC+5:30, Thomas Broyer wrote:
On Thursday, July 19, 2012 5:36:13 AM UTC+2, Vasu wrote:
Yes you were right, it is instantiating new Person object. But if I try
to set Type to empty string validation fails and I cannot run the
application.
I didn't mean to set it to the empty string, but to not use the attribute:
ui:with field=person /
--
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/-/K3xzMkkBptoJ.
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: DevMode for Firefox 14
Last but not least, http://acleung.com/ff14-mac.xpi Have fun! -Alan On Mon, Jul 23, 2012 at 11:42 AM, Jens jens.nehlme...@gmail.com wrote: ALL: Please star this issue: https://code.google.com/p/**chromium/issues/detail?id=** 138557thanks=138557ts=**1343057729https://code.google.com/p/chromium/issues/detail?id=138557thanks=138557ts=1343057729 it might help to have better support for GWT devmode development (GWT plugin) for Chrome, and we can forget about firefox. You better take a look at: http://code.google.com/p/google-web-toolkit/issues/detail?id=4493#c24 and the two referenced chromium issues. It seems like that the chromium issues do not have a high priority since NPAPI may become obsolete in the future in favor of PPAPI. Its well known that the Chrome Dev Mode plugin is slower compared to Firefox because it has to work around mentioned chromium issues. -- 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/-/x_LiifvyZoUJ. 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 RC1 increases mgwt showcase by 22%
Daniel mentioned that somehow the CSS for the blackberry permutation is ending up in the iPhone permutation. That can't just be a Cell Widget issue. On Mon, Jul 23, 2012 at 12:24 AM, Ray Cromwell cromwell...@google.comwrote: Are you using any Cell widgets by any chance? I've seen that the Mail sample and ShowCase sample both shrunk, but the MobileWebApp sample increased in size. This leads me to believe it's not a compilation issue, but something in the user library pulling in a lot of extra code. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: Added Aria roles and properties to the CellTree (issue1776803)
The code for CellTree is rather odd. There is a keyboard selection policy with three values: DISABLED, ENABLED, and BOUND_TO_SELECTION. If the policy is ENABLED or BOUND_TO_SELECTION then the CSS styles for keyboard selection get updated, but the SelectionModel is only updated when the policy is BOUND_TO_SELECTION. So the question is whether we want aria-selected to be consistent with the CSS styles (in which case we should update it in keyboardSelected) or whether it should be consistent with the SelectionModel? I think making it consistent with the SelectionModel would be harder, since the SelectionModel depends on the implementation of the NodeInfo interface and you can swap in your own. Also, I'm not sure if BOUND_TO_SELECTION is working right anyway. According to this bug, the synchronization only works one way: http://code.google.com/p/google-web-toolkit/issues/detail?id=7480 It would help if we knew why there is a keyboard selection policy (why does this need to be configurable)? http://gwt-code-reviews.appspot.com/1776803/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: Fixes issue 6653: Activity interface should use the new EventBus (issue1786804)
Agree, we should not introduce breaking changes. Actually people were forced in 2.4 to use both versions (gwt and bindering) unless they use deprecated methods (Places), and using mvp+gin is a pain. I have not introduced more changes like you suggest to avoid more breaks and just to fix the annoying problem, so let me know what the committee decides, and whether it is appropriate to add those changes here (I dont mind spend some time to do that). http://gwt-code-reviews.appspot.com/1786804/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: Make DagePicker.getMonthSelector public. (issue1790803)
It looks like if you subclass DatePicker, you will be able to call this method from your subclass. Will that work for you? For an arbitrary DatePicker, making this method public won't help much because the MonthSelector interface doesn't have any interesting methods. http://gwt-code-reviews.appspot.com/1790803/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: Adds directory listings for the source files served by Super Dev Mode. (issue1770804)
http://gwt-code-reviews.appspot.com/1770804/diff/1/dev/codeserver/java/com/google/gwt/dev/codeserver/SourceMap.java File dev/codeserver/java/com/google/gwt/dev/codeserver/SourceMap.java (right): http://gwt-code-reviews.appspot.com/1770804/diff/1/dev/codeserver/java/com/google/gwt/dev/codeserver/SourceMap.java#newcode40 dev/codeserver/java/com/google/gwt/dev/codeserver/SourceMap.java:40: private JsonObject json; On 2012/07/23 18:43:40, mdempsky wrote: Could be final? Done. http://gwt-code-reviews.appspot.com/1770804/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] GWT 2.5 RC1 increases mgwt showcase by 22%
We are not using any cell widgets (we wrote our own for mgwt, because the current ones don work for mobile). I already have a good guess where this might be coming from. I'll try to provide a decent test case for it (without mgwt dependencies). -Daniel 2012/7/23 Rajeev Dayal rda...@google.com Daniel mentioned that somehow the CSS for the blackberry permutation is ending up in the iPhone permutation. That can't just be a Cell Widget issue. On Mon, Jul 23, 2012 at 12:24 AM, Ray Cromwell cromwell...@google.comwrote: Are you using any Cell widgets by any chance? I've seen that the Mail sample and ShowCase sample both shrunk, but the MobileWebApp sample increased in size. This leads me to believe it's not a compilation issue, but something in the user library pulling in a lot of extra code. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: Added support for ConstraintFinder. (issue1789803)
http://gwt-code-reviews.appspot.com/1789803/diff/1/user/src/org/hibernate/validator/metadata/ConstraintOrigin.java File user/src/org/hibernate/validator/metadata/ConstraintOrigin.java (right): http://gwt-code-reviews.appspot.com/1789803/diff/1/user/src/org/hibernate/validator/metadata/ConstraintOrigin.java#newcode2 user/src/org/hibernate/validator/metadata/ConstraintOrigin.java:2: // $Id: ConstraintOrigin.java 17620 2009-10-04 19:19:28Z hardy.ferentschik $ I copied this here based on a suggestion by Ray after trying unsuccessfully to add it to a new module via super source. I avoided adding it to the HibernateValidator module you linked because I do not need any of those other classes/wanted to keep bloat down. http://gwt-code-reviews.appspot.com/1789803/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Super Dev Mode cleanup in preparation for doing more server-side HTML rendering (issue1791803)
Reviewers: mdempsky, Description: Super Dev Mode cleanup in preparation for doing more server-side HTML rendering (no user-visible changes) - introduce HtmlWriter class - change log file rendering to use it - Move some code for handling generated file paths from SourceHandler to ModuleState Please review this at http://gwt-code-reviews.appspot.com/1791803/ Affected files: A dev/codeserver/java/com/google/gwt/dev/codeserver/HtmlWriter.java M dev/codeserver/java/com/google/gwt/dev/codeserver/ModuleState.java M dev/codeserver/java/com/google/gwt/dev/codeserver/SourceHandler.java M dev/codeserver/java/com/google/gwt/dev/codeserver/WebServer.java -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: Added support for ConstraintFinder. (issue1789803)
http://gwt-code-reviews.appspot.com/1789803/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: Added support for ConstraintFinder. (issue1789803)
http://gwt-code-reviews.appspot.com/1789803/diff/4002/user/src/com/google/gwt/validation/client/GroupInheritanceMap.java
File user/src/com/google/gwt/validation/client/GroupInheritanceMap.java
(right):
http://gwt-code-reviews.appspot.com/1789803/diff/4002/user/src/com/google/gwt/validation/client/GroupInheritanceMap.java#newcode72
user/src/com/google/gwt/validation/client/GroupInheritanceMap.java:72:
protected MapClass?, SetClass? mapping;
this should be private final
http://gwt-code-reviews.appspot.com/1789803/diff/4002/user/src/com/google/gwt/validation/rebind/GwtSpecificValidatorCreator.java
File
user/src/com/google/gwt/validation/rebind/GwtSpecificValidatorCreator.java
(right):
http://gwt-code-reviews.appspot.com/1789803/diff/4002/user/src/com/google/gwt/validation/rebind/GwtSpecificValidatorCreator.java#newcode273
user/src/com/google/gwt/validation/rebind/GwtSpecificValidatorCreator.java:273:
if (definedOn ==
org.hibernate.validator.metadata.ConstraintOrigin.DEFINED_IN_HIERARCHY)
{
for safety it is best to use a switch statement here so the default case
will catch new unknown enums and throw an exception.
http://gwt-code-reviews.appspot.com/1789803/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
