Re: GWT Cross Site Iframe Linker and Script Tags
This sucks great time, now that devmode plugins have been abandoned (surprise!), and Super Dev Mode was forced onto us, xsiframe became a must, and all the GWT libraries and apps that use script tags are not working anymore. What's wrong with document.write anyway? I'm really angry now with Google, and we're going to rewrite the app with JS, Backbone, jQuery, who knows. At least stuff won't break because of ridiculous developer decisions. Thanks Google -- 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/-/dLk5b77VnZIJ. 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.
Editor framework and interfaces
Hi All, I really see big potential in new and shiny editor framework. Works
pretty well so far, but I noticed, that it doesn't work when I use
interfaces for my views. Typical example: you describe your view as an
interface:
interface FooView extends EditorFoo { ... }
then instance of this get injected into presenter's constructor, where you
want initialize your Driver with this view. That's it, doesn't seem to work.
interface Driver extends SimpleBeanEditorDriverFoo, FooView { }
...doesn't work. While following does:
interface Driver extends SimpleBeanEditorDriverFoo, SimpleFooView { }
where SimpleFooView implements FooView. Is it a bug or a feature? Does it
have something to do with crippled reflection in GWT?
--
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-tool...@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: Casting JavaScriptObject with GWT 2.1
Julio, I think your last response was a bit aggresive. Watch it. As of your problem with overlay types, what you describe should work flawlessly, and it does, I'm using JavaScriptObject daily in my GWT projects, and never seen such behavior. Please try something like $wnd.console.log(this) in your BeanData getters, to see what objects is there, then use Firebug or WebKit inspector to watch those logged objects. That should work in both devmode and compiled version. Good luck -- 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-tool...@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: Multiple Activity Mappers and Gin
I think you're looking for annotated bindings: http://stackoverflow.com/questions/1221920/getting-multiple-guice-singletons-of-the-same-type I guess toInstance() doesn't work in GWT, but you can still use regular to() -- 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-tool...@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: Http Headers
There is already support for HTTP headers in XHR in GWT, it's the method I posted. And it works with all major browsers. The problem I guess is that you probably have issues with using RequestBuilder class from your Spring Roo app. -- 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-tool...@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: Casting JavaScriptObject with GWT 2.1
You can't, what you do here is that you create new (and empty) JavaScriptObject, and cast it to your type. It seems that you think you're copying the object, but that's certainly not true. I'm not sure what the problem is, if you need to pass that instance to another class, you can do it without any tranformation. On Dec 10, 11:08 am, julio antongiuli...@gmail.com wrote: Hi, In my application I get some data via JSONP, and it's perfectly transformed in a bean composed by String, JsArray, JsArrayJsArrayString, etc. At some point this bean is saved with something like this: private static JavaScriptObject data; ... BeanData b; MyClass.data = b; in another point of the application this value is passed to another class (to display some other page) with something like this: BeanData bd = data.createObject().cast(); String name = bd.getName(); but name is empty. After debugging the bd variable, it's still a JavaScriptObject. How can I cast it back? Thanks, Julio -- 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-tool...@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: Using Google Closure Library within GWT JSNI .....
There aren't any performance implications, it only can get faster I guess. You would need to wrap these Closure objects into JavaScriptObject, which is very tedious and time consuming thing to do, and not really rewarding, because those widgets are realy simple. IMHO, there is great overlap between GWT and Closure, there is a widget library, and there is a compiler. I think you should decide to either use GWT or Closure. With GWT, you benefit from rich language semantics of Java, while Closure is the lightweight approach. To make a wise decision you would have to sum your expectations on the library, compare Closure's and GWT's, consider language differences etc. Closure lacks MVP framework, in GWT you have several to choose from. On Dec 10, 8:23 am, karthik reddy karthik.ele...@gmail.com wrote: Given than closure library has a plethora of UI elements(all the nice UI elements one could see across various google products like Google docs, maps, gmail etc), would it not be worthwhile to use them in GWT using JSNI. Has anyone tried this ?? Any performance implications ??? 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-tool...@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: Http Headers
http://google-web-toolkit.googlecode.com/svn/javadoc/2.1/com/google/gwt/http/client/RequestBuilder.html#setHeader(java.lang.String, java.lang.String) -- 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-tool...@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: Http Headers
I assume you mean Spring Roo + GWT? In that case I can't help you, heard of it before but never used it, quickly checked it out, seems like lots of scaffolding is going on there, so you will have to customize. RequestBuilder class can make requests of any method btw (as long as browser supports that). -- 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-tool...@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: Internal compiler error when upgrading vom 2.0.4 to 2.1.0.RC1
Awesome! Saved my ass too, thanks a ton On Oct 20, 3:45 pm, wolfgang wor@gmail.com wrote: solved the problem. I changed the order in java build path (order and export), so that GWT SDK is now on Top. everything compiles without exception. On 15 Okt., 12:02, wolfgang wor@gmail.com wrote: Sorry for posting this twice - haven't found the first post so I assumed it got lost somewhere. On 15 Okt., 11:58, wolfgang wor@gmail.com wrote: I got thiserrormessage from thecompilerwhen I tried an upgrade from 2.0.4 to 2.1.0.RC1: [ERROR] Internalcompilererror java.lang.NoSuchMethodError: com.google.gwt.uibinder.rebind.UiBinderWriter.init(Lcom/google/gwt/ core/ext/typeinfo/JClassType;Ljava/lang/String;Ljava/lang/String;Lcom/ google/gwt/core/ext/typeinfo/TypeOracle;Lcom/google/gwt/uibinder/ rebind/MortalLogger;Lcom/google/gwt/uibinder/rebind/FieldManager;Lcom/ google/gwt/uibinder/rebind/messages/MessagesWriter;Lcom/google/gwt/ uibinder/rebind/DesignTimeUtils;Lcom/google/gwt/uibinder/rebind/ UiBinderContext;)V at com.google.gwt.uibinder.rebind.UiBinderGenerator.generateOnce(UiBinderGener ator.java: 135) at com.google.gwt.uibinder.rebind.UiBinderGenerator.generate(UiBinderGenerator .java: 119) at com.google.gwt.dev.javac.StandardGeneratorContext.runGenerator(StandardGene ratorContext.java: 427) at com.google.gwt.dev.cfg.RuleGenerateWith.realize(RuleGenerateWith.java: 39) at com.google.gwt.dev.shell.StandardRebindOracle $Rebinder.tryRebind(StandardRebindOracle.java:115) at com.google.gwt.dev.shell.StandardRebindOracle $Rebinder.rebind(StandardRebindOracle.java:58) at com.google.gwt.dev.shell.StandardRebindOracle.rebind(StandardRebindOracle.j ava: 161) at com.google.gwt.dev.shell.StandardRebindOracle.rebind(StandardRebindOracle.j ava: 150) at com.google.gwt.dev.Precompile $DistillerRebindPermutationOracle.getAllPossibleRebindAnswers(Precompile.ja va: 345) at com.google.gwt.dev.jdt.WebModeCompilerFrontEnd.doFindAdditionalTypesUsingRe binds(WebModeCompilerFrontEnd.java: 106) at com.google.gwt.dev.jdt.AbstractCompiler$Sandbox $CompilerImpl.process(AbstractCompiler.java:254) at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java: 444) at com.google.gwt.dev.jdt.AbstractCompiler$Sandbox $CompilerImpl.compile(AbstractCompiler.java:175) at com.google.gwt.dev.jdt.AbstractCompiler$Sandbox $CompilerImpl.compile(AbstractCompiler.java:288) at com.google.gwt.dev.jdt.AbstractCompiler$Sandbox$CompilerImpl.access $400(AbstractCompiler.java:145) at com.google.gwt.dev.jdt.AbstractCompiler.compile(AbstractCompiler.java: 632) at com.google.gwt.dev.jdt.BasicWebModeCompiler.getCompilationUnitDeclarations( BasicWebModeCompiler.java: 124) at com.google.gwt.dev.jdt.WebModeCompilerFrontEnd.getCompilationUnitDeclaratio ns(WebModeCompilerFrontEnd.java: 54) at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.precompile(JavaToJavaScript Compiler.java: 484) at com.google.gwt.dev.jjs.JavaScriptCompiler.precompile(JavaScriptCompiler.jav a: 32) at com.google.gwt.dev.Precompile.precompile(Precompile.java:544) at com.google.gwt.dev.Precompile.precompile(Precompile.java:465) at com.google.gwt.dev.Compiler.run(Compiler.java:205) at com.google.gwt.dev.Compiler.run(Compiler.java:177) at com.google.gwt.dev.Compiler$1.run(Compiler.java:149) at com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java: 87) at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRu nner.java: 81) at com.google.gwt.dev.Compiler.main(Compiler.java:156) [ERROR] Unexpected java.lang.NoSuchMethodError: com.google.gwt.uibinder.rebind.UiBinderWriter.init(Lcom/google/gwt/ core/ext/typeinfo/JClassType;Ljava/lang/String;Ljava/lang/String;Lcom/ google/gwt/core/ext/typeinfo/TypeOracle;Lcom/google/gwt/uibinder/ rebind/MortalLogger;Lcom/google/gwt/uibinder/rebind/FieldManager;Lcom/ google/gwt/uibinder/rebind/messages/MessagesWriter;Lcom/google/gwt/ uibinder/rebind/DesignTimeUtils;Lcom/google/gwt/uibinder/rebind/ UiBinderContext;)V at com.google.gwt.uibinder.rebind.UiBinderGenerator.generateOnce(UiBinderGener ator.java: 135) at com.google.gwt.uibinder.rebind.UiBinderGenerator.generate(UiBinderGenerator .java: 119) at com.google.gwt.dev.javac.StandardGeneratorContext.runGenerator(StandardGene ratorContext.java: 427) at com.google.gwt.dev.cfg.RuleGenerateWith.realize(RuleGenerateWith.java: 39) at
Re: Dev plugin for firefox 3.7
There is a big demand for this plugin. And unsatisfied :( On Nov 9, 11:34 am, csillag csillag.kris...@gmail.com wrote: On okt. 26, 00:54, slowpoison slowpoi...@slowpoison.net wrote: On Sep 14, 8:21 am, John Tamplin j...@google.com wrote: I am working on it right now. I have it working on FF40, but I am still trying to get it where one XPI will work on both FF3 and FF4. Any update about this, John? Hi, I am still waiting for this. Could you please at least give us some info about what's happening? Thank you: Kristof -- 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-tool...@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: Dev plugin for firefox 3.7
Are these first signs of GWT being forgotten? That there is less resources being allocated for GWT team?? On Sep 14, 4:44 pm, a...@mechnicality.com a...@mechnicality.com wrote: John, Chris Its now 09/14/2010. Please could you update us on the status of this work? The plugin still doesn't seem to work with FF 4.06 beta. Regards Alan Chaney On 08/11/2010 09:06 AM, John Tamplin wrote: On Wed, Aug 11, 2010 at 10:46 AM, Chris Conroy con...@google.com mailto:con...@google.com wrote: The short answer is that after preliminary support went in, the supporting libraries changed upstream. Also, when the prelim support went in Windows dev libraries weren't even available. I think John has a change in the works to get this updated but is blocked on something. Just being on vacation much of the last two weeks and having other things in front of it. I intend to update all the platforms for 4.0b2 this week. -- John A. Tamplin Software Engineer (GWT), Google -- 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-tool...@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: Dev plugin for firefox 3.7
Hi all, is there any progress on this issue? FF4 is almost done and we're stuck with developing on FF3.6 which is slow as hell on MacOS, and there's no Chromium plugin. On Sep 8, 1:07 am, csillag csillag.kris...@gmail.com wrote: Hi John, On aug. 11, 18:06, John Tamplin j...@google.com wrote: On Wed, Aug 11, 2010 at 10:46 AM, Chris Conroy con...@google.com wrote: The short answer is that after preliminary support went in, the supporting libraries changed upstream. Also, when the prelim support went in Windows dev libraries weren't even available. I think John has a change in the works to get this updated but is blocked on something. Just being on vacation much of the last two weeks and having other things in front of it. I intend to update all the platforms for 4.0b2 this week. Could you please give us some update on the current status? I have just downloaded the 64-bit version of FF4.0 B5 from mozilla, installed it (on my Debian system), updated my plugin svn dirs, built the plugin (w. BROWSER=ff40), installed it (shows up registered as 1.0.8725M.20100908004741), and tried to run a GWT app (running in Eclipse, GWT 2.0.4)... ...but I only got a warning about not supporting anythin above 3.5. Could you please help me finding out what am I doing wrong? Thank you for your help! Kristof Csillag -- 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-tool...@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.
[gwt-contrib] Re: now.. afetr GWT 2.0?
Allow UiBinder to use any ClientBundle in embedded ui:style CSS, so I can reuse my images actually, can't believe it's not working. On Dec 17 2009, 3:25 pm, FDG fdigiuse...@gmail.com wrote: - remove actual UiBinder limitations - supports printing using css media (so wrap themes around a @media screen) -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
CssResource in IE
Hi all, I got a problem using CssResource, after laborious convert from legacy CSS, everything works perfectly in gecko/webkit. However, IE loads/ sees only a couple of my CSS rules, like 5% of the whole stylesheet, which effectively destroys whole application. Debuggin from ensureInjected() call doesn't seem to bring any light into this issue. I refuse to believe that this is a bug of GWT, I guess the CssResource feature wouldn't be released in 2.0 if not working in all supported browsers. Any ideas what could be causing this? Thank you -- 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-tool...@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: Saving form inputs for browser autocomplete
It's the very basic browser feature, without any extensions. Just click twice on input, or start typing in a field you have had already submitted before, and previous values will be offered for you. This is standard feature of FF, Chrome, and I guess some more browsers. On Dec 23, 5:59 pm, Michael W mwang_2...@yahoo.com wrote: Skrat, Are you talking about the Google Autofill, Roboform Autofill feature? Which means browser remembers your form entry and next time once you click Autofill from browser, the form is refilled. Or just want to prepopulate your form processed by your program. On Dec 22, 9:22 am, skrat dusan.malia...@gmail.com wrote: Hmm, that script inserted forms problem, might be fatal. I guess security should be handled by browsers, and all non-XHR forms are leveraging this feature. please On Dec 22, 3:07 pm, Thomas Broyer t.bro...@gmail.com wrote: On Dec 22, 2:53 pm, skrat dusan.malia...@gmail.com wrote: Hi all, I am curious about, how can one enable, or force a browser to remember value inside text inputs (TextBox) values. In browsers it basically works when you submit a form, then all values are remembered, and next time you open that form, you will be provided with autocomplete box. All major browsers works like this. Since in apps, that decides to use XML, JSON or GWT RPC, values in forms are actually not submitted, and thus not remebered. We just read those values and don't do any submit, we do XHR instead. Any ideas how to get back this very useful browser feature? This is a hack but if you really want it: - use a form - expose a GWT method as a JS 'global' function (e.g., myExportedGwtMethod) - set the form's action to call the exported method (javascript:myExportedGwtMethod()) - do your XHR/RPC call from within your exported GWT method Note that (I'm almost sure this isn't the case, for any form except login forms, but just in case) this might only work if the form is actually part of the original HTML markup of the page (i.e. not inserted by script). It's not worth it IMO; except for login forms eventually, even if it goes against the most basic security rules, just because of the enhanced UX. -- 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-tool...@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.
Saving form inputs for browser autocomplete
Hi all, I am curious about, how can one enable, or force a browser to remember value inside text inputs (TextBox) values. In browsers it basically works when you submit a form, then all values are remembered, and next time you open that form, you will be provided with autocomplete box. All major browsers works like this. Since in apps, that decides to use XML, JSON or GWT RPC, values in forms are actually not submitted, and thus not remebered. We just read those values and don't do any submit, we do XHR instead. Any ideas how to get back this very useful browser feature? -- 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-tool...@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: Saving form inputs for browser autocomplete
Hmm, that script inserted forms problem, might be fatal. I guess security should be handled by browsers, and all non-XHR forms are leveraging this feature. please On Dec 22, 3:07 pm, Thomas Broyer t.bro...@gmail.com wrote: On Dec 22, 2:53 pm, skrat dusan.malia...@gmail.com wrote: Hi all, I am curious about, how can one enable, or force a browser to remember value inside text inputs (TextBox) values. In browsers it basically works when you submit a form, then all values are remembered, and next time you open that form, you will be provided with autocomplete box. All major browsers works like this. Since in apps, that decides to use XML, JSON or GWT RPC, values in forms are actually not submitted, and thus not remebered. We just read those values and don't do any submit, we do XHR instead. Any ideas how to get back this very useful browser feature? This is a hack but if you really want it: - use a form - expose a GWT method as a JS 'global' function (e.g., myExportedGwtMethod) - set the form's action to call the exported method (javascript:myExportedGwtMethod()) - do your XHR/RPC call from within your exported GWT method Note that (I'm almost sure this isn't the case, for any form except login forms, but just in case) this might only work if the form is actually part of the original HTML markup of the page (i.e. not inserted by script). It's not worth it IMO; except for login forms eventually, even if it goes against the most basic security rules, just because of the enhanced UX. -- 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-tool...@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: DockLayoutPanel and YUI
I also got trouble with DockLayoutPanel and IE6, and it doesn't have
anything with Unit.EM. I use Unit.PX, and in FF/Safari I got proper
styles on child widgets, that is
right: 0px; bottom: 0px; position: absolute; left: 0px; top: 0px;
and in IE6
there is something containing width:32px , how's that even possible,
where's that 32 coming from? Bulgaria?
On Oct 5, 9:01 pm, John Patterson jdpatter...@gmail.com wrote:
Right, I have reverted my code to use EM's and can see the problem
again. The code below also shows the problem. It uses a map in the
centre panel and I am not sure if this is where the problem arises.
!DOCTYPE HTML
html
head
meta http-equiv=content-type content=text/html; charset=UTF-8
script src=http://maps.google.com/maps?gwt=1file=apiv=2sensor=false
/script
script type=text/javascript language=javascript
src=search.nocache.js/script
/head
body
/body
/html
public void onModuleLoad()
{
DockLayoutPanel p = new DockLayoutPanel(Unit.EM);
p.addNorth(new HTML(north), 3);
p.addSouth(new HTML(south), 3);
p.addEast(new HTML(east), 10);
p.addWest(new HTML(west), 10);
MapWidget map = new MapWidget(LatLng.newInstance(-41.1,
174.8), 5);
p.add(map);
p.layout();
RootLayoutPanel rp = RootLayoutPanel.get();
rp.add(p);
rp.layout();
map.checkResizeAndCenter();
}
Not sure if this image will make it into my reply:
it shows the word East is partly obscured by the map. Possibly only
by 5px
My IE6 is 6.0.2900.2180.xpsp running on XP professional SP2 on Parallels
Hope this helps!
John
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[gwt-contrib] SubmitCompleteEvent.getResults() and text/plain
Hi all, before reporting a bug I would like to know whether this happens intentionally, and if so, what is the use case? Common use case: one needs to async. upload a file through hidden iframe, and she also wants to check what's the result of that submission. The only way is to check the content of that iframe. Since only text/plain and text/html are being loaded in iframes, we have to use these content types. Usually it just contains JSON string with server errors if something goes wrong. If not, then we issue an empty response. We use text/plain. When I call SubmitCompleteEvent.getResults() , and my iframe is loaded with empty response, I'll get pre /pre with firefox, and so my isEmpty() check fails. Shouldn't this be already sanitized when calling getResults() ? Now I'm forced to sanitize myself by creating hidden HTML widget, setHTML() getText().trim() isEmpty() --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
Re: RunAsyncCallback
Okay, that's kind of clear. Async Package (gateway class) looks nice,
but how does it fit within Gin and DI?
On Oct 26, 4:24 am, Sripathi Krishnan sripathi.krish...@gmail.com
wrote:
Maybe somebody from google will confirm this, but I doubt you are going to
achieve code splitting by using proxies or interfaces, or by using any
generic parameterized approach.
A piece of code will end up in split-point-1.js *only if* it is always being
used from within GWT.runAsync(). If a class can be used from two separate
GWT.runAsync() method blocks, it is going to end up in the left-overs block.
Now here is my understanding of the situation (of course I may be wrong) -
- You have two instances of the class AsyncLoader, say LoaderA and
LoaderB, with two unique providers - say ProviderA and ProviderB
- GWTC recognizes that there will be two GWT.runAsync() blocks, which is
why it creates two split points
- But it cannot guarantee that LoaderA will always get ProviderA, and so
it should put the code for ProviderA in split-point1.js
- So, it knows that the entry point is not using ProviderA or ProviderB -
which is why it is not in the initial download fragment. But it cannot
guarantee it will always be used from a unique code fragment, which is why
it ends up in the left-over fragment.
- When you use the inline implementation, you will hard-code the actual
provider - and hence things will work.
The only pattern that works well is Googles recommended Async Package
Patter. See this
presentationhttp://dl.google.com/io/2009/pres/Th_1045_TheStoryofyourCompile-Readi
--Sri
2009/10/25 skrat dusan.malia...@gmail.com
I'm trying to split my code using sort of proxies, where I reuse
parametrized RunAsyncCallback class. This class has basically just
reference to Gin Provider of the real module class. When I use this
for loading one module, it works perfectly, and I'm getting nice and
correct location of split point in report. When I use this second
time, loading different module proxy which uses the same
RunAsyncCallback class, both split points happen to be in Leftovers
code. Yet, split point on my proxies are still listed in report, but
with the same minimal (386) size.
I tried to use inline implementation of RunAsyncCallback instead, and
surprise! Split points worked correctly again.
Here is my parametrized RunAsyncCallback class:
class AsyncLoader implements RunAsyncCallback {
private ProjectPresenter parent;
private PlaceManager placeManager;
private Provider? extends AbstractLabeledPresenter real;
AsyncLoader( ProjectPresenter parent,
Provider? extends AbstractLabeledPresenter real,
PlaceManager placeManager ) {
this.placeManager = placeManager;
this.parent = parent;
this.real = real;
}
�...@override
public void onFailure(Throwable reason) {
// TODO Auto-generated method stub
}
�...@override
public void onSuccess() {
AbstractLabeledPresenter mod = real.get();
parent.addModule( mod );
if ( mod.hasToken( History.getToken() ) ) {
mod.revealDisplay();
parent.show(mod);
placeManager.fireCurrentPlace();
}
}
}
This is inner class defined in AbstractLabeledPresenter, that's the
same one I'm proxying and loading with GWT.runAsync. @Inject
annotation is not present because injection is done on proxy class
which in turn instatiates AbstractLabeledPresenter$AsyncLoader.
Not sure whether this is bug, but I can't see any linking or any other
rason why that code should end up in Leftovers and have empty, zero
size split points.
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[gwt-contrib] OOPHM extension for Linux Chromium
Hi all, as the subject says, is this doable? Can I somehow build myself that extension? --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
RunAsyncCallback
I'm trying to split my code using sort of proxies, where I reuse
parametrized RunAsyncCallback class. This class has basically just
reference to Gin Provider of the real module class. When I use this
for loading one module, it works perfectly, and I'm getting nice and
correct location of split point in report. When I use this second
time, loading different module proxy which uses the same
RunAsyncCallback class, both split points happen to be in Leftovers
code. Yet, split point on my proxies are still listed in report, but
with the same minimal (386) size.
I tried to use inline implementation of RunAsyncCallback instead, and
surprise! Split points worked correctly again.
Here is my parametrized RunAsyncCallback class:
class AsyncLoader implements RunAsyncCallback {
private ProjectPresenter parent;
private PlaceManager placeManager;
private Provider? extends AbstractLabeledPresenter real;
AsyncLoader( ProjectPresenter parent,
Provider? extends AbstractLabeledPresenter real,
PlaceManager placeManager ) {
this.placeManager = placeManager;
this.parent = parent;
this.real = real;
}
@Override
public void onFailure(Throwable reason) {
// TODO Auto-generated method stub
}
@Override
public void onSuccess() {
AbstractLabeledPresenter mod = real.get();
parent.addModule( mod );
if ( mod.hasToken( History.getToken() ) ) {
mod.revealDisplay();
parent.show(mod);
placeManager.fireCurrentPlace();
}
}
}
This is inner class defined in AbstractLabeledPresenter, that's the
same one I'm proxying and loading with GWT.runAsync. @Inject
annotation is not present because injection is done on proxy class
which in turn instatiates AbstractLabeledPresenter$AsyncLoader.
Not sure whether this is bug, but I can't see any linking or any other
rason why that code should end up in Leftovers and have empty, zero
size split points.
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[gwt-contrib] Re: Extending FocusWidget
Hi, thanks, that helped. I now check for both FocusWidget and HasState
On Oct 19, 10:31 pm, Thoka thobias.karls...@gmail.com wrote:
Hi,
Create an interface, like:
public interface HasState {
void setEnabled(boolean enabled);
boolean isEnabled();
}
...and then implement this with your composite widget. And don't try
to cast objects, GWT supports 'instanceof'. :-)
I hope this was to any help.
P.s. I'm actually confused that such an interface doesn't already
exist within the GWT API since many widgets have exactly those two
methods.
On 19 Okt, 16:07, skrat dusan.malia...@gmail.com wrote:
Hi all,
all the stuff that FocusWidget does is maybe too much for my case. I
only need to cast to something that has setEnabled(boolean) method. In
other words I want to create a widget that would act similar to
TextBox and similar input widgets. Then I want to checkout Widgets out
of my container, try to cast (FocusWidget), and if successful, call
setEnabled().
I tried to extend FocusWidget instead of Composite, but my widget
stopped working (event handler were not triggered) after that. Any
ideas how to overcome this?
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
[gwt-contrib] Extending FocusWidget
Hi all, all the stuff that FocusWidget does is maybe too much for my case. I only need to cast to something that has setEnabled(boolean) method. In other words I want to create a widget that would act similar to TextBox and similar input widgets. Then I want to checkout Widgets out of my container, try to cast (FocusWidget), and if successful, call setEnabled(). I tried to extend FocusWidget instead of Composite, but my widget stopped working (event handler were not triggered) after that. Any ideas how to overcome this? --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
