Re: Chrome 15, GWT DMP Plugin crashes
Thats exactly the version I have and it works for me on a mac. Make sure it is not being upgraded automatically. the old version has a wrench icon in the top right corner, the new version has a few horizontal black lines. On 22/10/2012, at 7:00 PM, Juanra Collado wrote: > Wich version exactly?? I'm with the 21.0.1180.89 m and still doesn't work > > thanks > > El domingo, 21 de octubre de 2012 08:28:11 UTC+2, John Patterson escribió: > BTW, just save it on your desktop and turn off auto-update or it will be > replaced with the broken new version as soon as you restart it. > > On Sunday, 21 October 2012 12:59:08 UTC+7, John Patterson wrote: > Download Chome 21 and use it instead until this bug is resolved. > > http://www.oldapps.com/google_chrome.php > > On Sunday, 21 October 2012 09:23:02 UTC+7, Cristobal Ramirez wrote: > same problem in chrome v22.0.1229.94 m > but works well in mozilla & IE.. > ..any idea to fix this problem?? > > -- > 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/-/VXFdaQmYgNkJ. > 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: Chrome 15, GWT DMP Plugin crashes
BTW, just save it on your desktop and turn off auto-update or it will be replaced with the broken new version as soon as you restart it. On Sunday, 21 October 2012 12:59:08 UTC+7, John Patterson wrote: > > Download Chome 21 and use it instead until this bug is resolved. > > http://www.oldapps.com/google_chrome.php > > On Sunday, 21 October 2012 09:23:02 UTC+7, Cristobal Ramirez wrote: >> >> same problem in chrome v22.0.1229.94 m >> but works well in mozilla & IE.. >> ..any idea to fix this problem?? >> > -- 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/-/AGPBRprM0lkJ. 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: Chrome 15, GWT DMP Plugin crashes
Download Chome 21 and use it instead until this bug is resolved. http://www.oldapps.com/google_chrome.php On Sunday, 21 October 2012 09:23:02 UTC+7, Cristobal Ramirez wrote: > > same problem in chrome v22.0.1229.94 m > but works well in mozilla & IE.. > ..any idea to fix this problem?? > -- 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/-/xhCPhmw-gl8J. 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: Chrome 15, GWT DMP Plugin crashes
Was this issue ever fixed? I'm getting it now after upgrading chrome to the dev channel and then reverting it back to the stable channel -- 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/-/_KUMVAXeM7EJ. 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: Splitting initial fragment
Actually I mean the *leftovers *fragment! It just keeps on growing -- 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/-/sV9aapBd078J. 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.
Splitting initial fragment
My app has many html pages that each load a base "loader" module that calls a set of "features" which are each split with a GWT.runAsync call. The idea is to share common code such as java.util classes and common gwt widgets. But the problem I have hit is that the initial fragment has become too large. Any code that is common between 2 features is placed in the initial fragment even though it is not used in any other features. It doesn't seem very clever to just throw everything in the same fragment. I want this initial fragment to be more fine grained. Is there any work happening to help with these non-"app in a single page" type websites? -- 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/-/I28XH349chkJ. 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: Multiple leftover fragments with a tree of code split points?
I'm having the same problem - the left overs fragment is growing and control should be more fine grained. This is particularly important with multi page apps (c.f. app in one page) where each page must load the initial fragment, its exclusive fragment and the leftovers fragment. I found this work that seems related: http://code.google.com/p/gwt-splitter/ but there is no activity on that project. @Google: any work happening on smarter leftover fragment splitting? -- 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/-/Pi6rPRBEl84J. 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: addWindowClosingHandler firing when frame loads in IE
On 8 Jan 2010, at 16:22, Thomas Broyer wrote: Use Hyperlink or InlineHyperlink widgets for "internal navigation" (unless you also want ClickHandlers, in which case Anchor is fine, calling History.newItem() in a ClickHandler, but do not forget to ClickEvent#preventDefault() // this is more or less what Hyperlink/InlineHyperlink widgets do). Using Anchors caused onWindowClosing() to be called in IE7/8 so I could not use them. Using Button has solved this so far although I have a lot of default CSS to override. I just tested with Hyperlink as you suggested and this also works fine. Perhaps the difference is that it uses "#" as the href rather than "javascript:;" so IE recognises this as an internal link. -- 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.
Frame load event
Hi, I want to detect when a frame has loaded but IE does not fire an ONLOAD event. I see in the issues list that "onreadystatechange" can be used to achieve this. http://code.google.com/p/google-web-toolkit/issues/detail?id=1328 Has anyone got this working and can share the code? -- 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: Attaching an event handler to existing element
2009/12/30 John Patterson
>
> How can the header then be added to the DockLayoutPanel?
>
OK, I have found that calling RootPanel.get("header") _after_ attaching
handlers to the links works without throwing the exception. But this seems
like a hack because exactly the same structure is being built... it just
side steps the `assert` statement. Is there something wrong with this
element hierarchy?
--
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: Attaching an event handler to existing element
2009/12/30 Thomas Broyer
>
> Use Document.get().getElementById("header") instead of RootPanel.get
> ("header").getElement() to avoid the RootPanel widget being created,
> which then prevents wrap()ing an inner element in another widget.
>
>
How can the header then be added to the DockLayoutPanel?
--
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: Anchor.wrap with GQuery
On 9 Dec 2009, at 16:59, Thomas Broyer wrote: > The element you're trying to wrap is a child of an element that's the > "root" element of a widget. A widget is supposed to control its > subtree, so wrapping a widget's child element in another widget is > prohibited, as the "parent" widget would be aware of it. My question is _why_ is this element already owned and what can be done about it. -- 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: RC2 and Eclipse Plugin
Actually, where do you define the start url in your configuration? I assume this must come from somewhere but I see no option. On 3 Dec 2009, at 23:23, Miguel Méndez wrote: > > Do you have a war folder as part of yo -- 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: RC2 and Eclipse Plugin
On 3 Dec 2009, at 23:23, Miguel Méndez wrote: > > Yes I see the dev mode view but there is no link. ie it says "For > you convenience" and there is an empty list. > > > Do you have a war folder as part of your project? Yes I do. Although its not a problem... the url just works. But, I have not defined a startUrl anywhere. Previously I put one in the launch dialogue but that is not there anymore -- 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: RC2 and Eclipse Plugin
On 3 Dec 2009, at 22:41, Jeff Chimene wrote: > > Eh? > > The Dev. Mode window should have a url that's the same as the one > you posted. Right-click, copy and paste into your browser. AFAIK, > Dev. Mode is now identical on all supported platforms. Do you see a > Dev. Mode View after launching development mode? Eh? Yes I see the dev mode view but there is no link. ie it says "For you convenience" and there is an empty list. -- 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: RC2 and Eclipse Plugin
Thanks for the confirmation. I now have it working - _possibly_ my problem was due to not having a fresh workspace. Just for others reference this is what I did: Installed fresh Eclipse 3.5 and chosen a new workspace I have installed WST and then only Google Plugin RC2. I configured the Google preferences with both GWT 1.2RC2 and GAE1.6 and then imported my single existing project. I have created a Google Web Application launch and it kicks off Jetty. The Development Mode window inside Eclipse shows no URL's to launch but I use http://localhost:/?gwt.codesvr=localhost:9997 And it works!! Thanks again 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-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
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>