[gwt-contrib] Re: Fix error starting up in DevMode+GAE
I am experiencing the "Unable to find 'myapp.gwt.xml' on your classpath; could be a typo, or maybe you forgot to include a classpath entry for source?" after upgrading to RC1. The project does not use GAE. Is it possible that this could be same? On Nov 17, 2:03 pm, j...@google.com wrote: > As discussed FTF, I think a better plan is to pin the loaded modules in > memory until they have been referenced at least once from a browser. > > Letting them be immediately unloaded before they are used and then > reloading them seems inefficient and will annoy the user with duplicate > warnings/errors from the module load. > > The downside of this approach is that any modules which are loaded but > never referenced (such as from a launch config that is used for many > different modules) will pin those modules in memory indefinitely, but I > think that is the lesser evil. > > http://gwt-code-reviews.appspot.com/103801 -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: r6354 committed - Fixes IE bug in ScrollPanel at 100% width; Adds Requires/ProvidesResiz...
Thank you for pointing me in this direction. Changing from http://www.w3.org/TR/html4/
strict.dtd"> to seems to fix it. However now most of my other
styles look rather poor. I really do not understand the difference so
I guess I'll Google it and hopefully find a layman's explanation.
On Oct 28, 9:55 am, Ray Ryan wrote:
> Todd, can you send a sample that demonstrates the problem? Also, is your
> page in standards mode?
>
> On Oct 28, 2009 5:40 AM, "todd.sei...@gmail.com"
> wrote:
>
> This change appear to have broken all of my scrollable content in
> IE6/7. What I see now is the scroll panel with scrollbar and the
> content exceeding the bounds of the scrollpanel. Interaction with the
> scrollbar has no effect on the content.
>
> The use of the ScrollPanels and their child Widgets vary. So I do not
> know if this is an error in my implementation.
>
> Using IE Dev tools I remove the relative positioning from the
> containerElem and it displays correctly.
>
> On Oct 13, 8:53 am, codesite-nore...@google.com wrote:
>
> > Revision: 6354
> > Author: j...@google.com
> > Date: Tue Oct 13 05:52:22 2009
> > Log: Fixes IE bug inScrollPanelat 100% width; Adds
> > Requires/ProvidesResize.
> > Review:
>
> http://gwt-code-reviews.appspot.com/78810http://code.google.com/p/goo...
>
> > > Modified: >
>
> /trunk/user/src/com/google/gwt/user/client/ui/ScrollPanel.java > >
> ===...
>
> > public classScrollPanelextends SimplePanel implements
> > SourcesScrollEvents, > - HasScrollHandlers { > + HasScrollHandlers,
>
> RequiresResize, Provides...> + //
>
> http://stackoverflow.com/questions/139000/div-with-overflowauto-and-a...
>
> > + DOM.setStyleAttribute(getElement(), "zoom", "1"); > +
>
> DOM.setStyleAttribute(containerElem,...
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
[gwt-contrib] Re: r6354 committed - Fixes IE bug in ScrollPanel at 100% width; Adds Requires/ProvidesResiz...
This change appear to have broken all of my scrollable content in
IE6/7. What I see now is the scroll panel with scrollbar and the
content exceeding the bounds of the scrollpanel. Interaction with the
scrollbar has no effect on the content.
The use of the ScrollPanels and their child Widgets vary. So I do not
know if this is an error in my implementation.
Using IE Dev tools I remove the relative positioning from the
containerElem and it displays correctly.
On Oct 13, 8:53 am, codesite-nore...@google.com wrote:
> Revision: 6354
> Author: j...@google.com
> Date: Tue Oct 13 05:52:22 2009
> Log: Fixes IE bug inScrollPanelat 100% width; Adds
> Requires/ProvidesResize.
> Review:http://gwt-code-reviews.appspot.com/78810http://code.google.com/p/google-web-toolkit/source/detail?r=6354
>
> Modified:
> /trunk/user/src/com/google/gwt/user/client/ui/ScrollPanel.java
>
> ===
> --- /trunk/user/src/com/google/gwt/user/client/ui/ScrollPanel.java Tue
> May
> 12 11:20:32 2009
> +++ /trunk/user/src/com/google/gwt/user/client/ui/ScrollPanel.java Tue
> Oct
> 13 05:52:22 2009
> @@ -27,15 +27,26 @@
> */
> @SuppressWarnings("deprecation")
> public classScrollPanelextends SimplePanel implements
> SourcesScrollEvents,
> - HasScrollHandlers {
> + HasScrollHandlers, RequiresResize, ProvidesResize {
> +
> + private Element containerElem;
>
> /**
> * Creates an empty scroll panel.
> */
> publicScrollPanel() {
> setAlwaysShowScrollBars(false);
> +
> + containerElem = DOM.createDiv();
> + getElement().appendChild(containerElem);
> +
> // Prevent IE standard mode bug when a AbsolutePanel is contained.
> - DOM.setStyleAttribute(getElement(), "position", "relative");
> + DOM.setStyleAttribute(containerElem, "position", "relative");
> +
> + // Hack to account for the IE6/7 scrolling bug described here:
> + //
> http://stackoverflow.com/questions/139000/div-with-overflowauto-and-a...
> + DOM.setStyleAttribute(getElement(), "zoom", "1");
> + DOM.setStyleAttribute(containerElem, "zoom", "1");
> }
>
> /**
> @@ -89,6 +100,13 @@
> public int getScrollPosition() {
> return DOM.getElementPropertyInt(getElement(), "scrollTop");
> }
> +
> + public void onResize() {
> + Widget child = getWidget();
> + if ((child != null) && (child instanceof RequiresResize)) {
> + ((RequiresResize) child).onResize();
> + }
> + }
>
> /**
> * @deprecated Use the {...@link HandlerRegistration#removeHandler}
> @@ -194,6 +212,10 @@
> public void setWidth(String width) {
> super.setWidth(width);
> }
> +
> + protected Element getContainerElement() {
> + return containerElem;
> + }
>
> private native void ensureVisibleImpl(Element scroll, Element e) /*-{
> if (!e)
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
[gwt-contrib] IE "Access is denied" javascript exception
Many users with IE 6-8 experience trouble loading my site the first time they try to access it. The site either never tries to load or else they get an "access is denied" error. I have tracked the access is denied error to the maybeCreateGwtFrame method in .nocache.js. It is being throw on the line 204 ( var doc = win.document;). If the user refreshes the application will load perfectly. What I tried doing is wrapping those lines with a try block then redirecting however it doesn't appear to catch the exception thrown. I also have cut down my initial code from 700KB to 20KB with code splitting thinking that that might ease the situation. All it helped do is get to the exception quicker. (P.S. thank you for code spllitting) Does anyone have any suggestions for me to try? --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] StyleInjector/OOPHM
Running FireFox in OOPHM and GWT trunk (c. r5498) I am getting the
following error. It looks like it is trying to use the IE
implementation of StyleInjector instead of the default implementation.
Is the a bug in gwt-dnd or gwt trunk?
Exception
00:02:36.817 [ERROR] Unable to load module entry point class
com.allen_sauer.gwt.dnd.client.util.DragEntryPoint (see associated
exception for details) com.google.gwt.core.client.JavaScriptException:
(TypeError): $doc.createStyleSheet is not a function fileName:
http://localhost:8080 lineNumber: 20 stack: ()@http://localhost:
8080:20 connect("192.168.1.111:9997","main",[object
XPCCrossOriginWrapper])@:0 ((void 0),"main","http://localhost:8080/
main/")@http://localhost:8080/?gwt.hosted=192.168.1.111:9997:185
maybeStartModule()@http://localhost:8080/main/main.nocache.js:41 (5)
@http://localhost:8080/main/main.nocache.js:196 at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown
Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance
(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown
Source) at
com.google.gwt.dev.shell.ModuleSpace.createJavaScriptException
(ModuleSpace.java:62) at
com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript
(BrowserChannelServer.java:101) at
com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke
(ModuleSpaceOOPHM.java:121) at
com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:
501) at com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject
(ModuleSpace.java:273) at
com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject
(JavaScriptHost.java:91) at com.google.gwt.dom.client.StyleInjector
$StyleInjectorImplIE.createElement(StyleInjector.java) at
com.google.gwt.dom.client.StyleInjector
$StyleInjectorImplIE.injectStyleSheet(StyleInjector.java:100) at
com.google.gwt.dom.client.StyleInjector
$StyleInjectorImplIE.injectStyleSheetAtStart(StyleInjector.java:145)
at com.google.gwt.dom.client.StyleInjector.injectStylesheetAtStart
(StyleInjector.java:202) at
com.allen_sauer.gwt.dnd.client.util.DragEntryPoint.onModuleLoad
(DragEntryPoint.java:33) at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at
java.lang.reflect.Method.invoke(Unknown Source) at
com.google.gwt.dev.shell.ModuleSpace.onLoad(ModuleSpace.java:367) at
com.google.gwt.dev.shell.OophmSessionHandler.loadModule
(OophmSessionHandler.java:169) at
com.google.gwt.dev.shell.BrowserChannelServer.run
(BrowserChannelServer.java:149) at java.lang.Thread.run(Unknown Source)
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
[gwt-contrib] Re: HashMap keyset behavior
No, I'm sorry it appears as though this simple test does work. My real
code is more complex and does return different results in hosted mode
versus compiled. Perhaps it is a timing issue. I will repost if I find
the issue. Thanks.
On Dec 17, 12:38 pm, Scott Blum wrote:
> You're saying this works in web mode and fails in hosted mode?
>
> On Wed, Dec 17, 2008 at 10:14 AM, todd.sei...@gmail.com <
>
> todd.sei...@gmail.com> wrote:
>
> > In the following code web mode removes the object for key "foo1" but
> > hosted mode does not seem to remove it. What is the 'correct'
> > behavior? I am using GWT 1.5.3.
>
> > HashMap hm = new HashMap();
> > hm.put("foo1", new Foo());
> > Set keys = hm.keySet();
> > keys.remove("foo1");
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
[gwt-contrib] HashMap keyset behavior
In the following code web mode removes the object for key "foo1" but
hosted mode does not seem to remove it. What is the 'correct'
behavior? I am using GWT 1.5.3.
HashMap hm = new HashMap();
hm.put("foo1", new Foo());
Set keys = hm.keySet();
keys.remove("foo1");
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
