Re: Can't get correct DOMImpl when chromeframe installed but turned off

2011-09-09 Thread Paul Smith
After taking 2.4 I got caught by this issue also. If chrome frame is 
installed but not enabled for the page, then gwt uses deferred binding stuff 
meant for chrome and not the ones meant for ie. It breaks all over the 
place! Please fix this!

You might say just add the meta tag to make it use chrome frame, but I 
have two issues with that:
 - chrome frame could be installed and disabled - this still affects 
navigator.userAgent
 - my application doesn't even support chrome (yet)

-- 
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/-/UmdJiSphAHwJ.
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.



Putting bootstrap js in host page

2011-02-10 Thread Paul Smith
I was just wondering if anyone has tried to put the bootstrap js straight 
into the host page. It seems like it would reduce the number of http 
requests in a typical GWT app.

Typical GWT apps have a host page (probably not set to cache forever), which 
includes the boostrap js (which typically isn't set to cache forever), and 
the bootstrap page includes your app js (possible multiple js if you use 
code splitting, and they should cache forever).

So, if your cache isn't primed, you have at least 3 requests (host, 
bootstrap, app). If your cache is primed you get two (304 for host and 304 
for bootstrap). If you were to put the boostrap js in the host page, then 
you'd reduce each of these by 1. Because the bootstrap js is pretty small 
(6KB for me), it sounds like a good way to reduce requests.

Any thoughts? Anyone ever try this? I admit that I haven't tried it yet, but 
I suspect that copy and paste won't work unless perhaps your host page is 
sitting in the same directory as your boostrap and app js.

-- 
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: IE 7 bug? LayoutPanels cease resizing after first time displayed

2010-09-09 Thread Paul Smith
When you navigate between the screens are you removing the prior
panel? If so then you're probably encountering a bug that I found:
http://code.google.com/p/google-web-toolkit/issues/detail?id=5245

You could workaround it by hiding the previous panel instead of
removing it. Or you can call forcelayout recursively...

On Sep 8, 3:42 pm, mjeffw mjeffwil...@gmail.com wrote:
 I have an application that contains two screens, both of which are
 using DockLayoutPanel as their outermost container.

 The app is using Standards mode, and I am adding the panels to the
 RootLayoutPanel with code that looks like this:

       // container is my RootLayoutPanel
       container.clear();
       container.add(dockLayoutPanel);

 dockLayoutPanel is an instance of a Composite created via the
 UIBinder; it's topmost element is a DockLayoutPanel:

 ui:UiBinder xmlns:ui=urn:ui:com.google.gwt.uibinder
         xmlns:g=urn:import:com.google.gwt.user.client.ui

         g:DockLayoutPanel unit='EM'
                 g:west size='20'

 ... (remainder elided)

 Both screens are defined in this same way, but with different
 contents.

 I am also using History to manage navigation between the two screens.

 When the user starts the app, the first screen appears and correctly
 resizes with the browser window. Then the user click a button that
 leads him to the second page. At this point, that screen is also
 resizing properly.

 Then the user goes back to the first screen using the browser back
 button. The screen comes up but no longer resizes with the browser
 window. If the user then navigates back to the second screen, it too
 is no longer resizing properly.

 To reproduce this error, I am using IE 7.

 If I use Safari or Chrome, it seems to work fine.

-- 
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: how to call forcelayout() in a tablayout panel

2010-08-31 Thread Paul Smith
I had a need for this recently - this is what I used:

  private native void forceTabLayoutPanelToLayout(TabLayoutPanel
tabLayoutPanel) /*-{
var layoutPanel =
tablayoutpan...@com.google.gwt.user.client.ui.composite::getWidget()
();
 
layoutpan...@com.google.gwt.user.client.ui.layoutpanel::forceLayout()
();
  }-*/;

-- 
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: Changing CSS on the fly

2010-06-02 Thread Paul Smith
It is possible in straight javascript, but I don't think there's
anything in GWT to help out. See 
http://developer.apple.com/internet/webcontent/styles.html
for an example.

I used it a few years back for something really similar - changing the
style of a bunch of elements by modifying a css rule. Definitely much
faster than changing the styles on all those dom elements. If I
recall, finding the right stylesheet and css rule is kind of a pain
because there's no efficient lookup. I think I put the style that I
wanted to modify right on the html page to make finding it easier. I
bet GWT could do something to make referencing css rules in a
CssResource efficient.

On May 28, 11:39 am, fmod francisco.mode...@gdsoft.eu wrote:
 Hi, is there a way to change a CSS Property inside a Rule definition
 on the fly.

 I have defined a rule

 .myRule {
   height: 22px;
   width: 100px;
   overflow: hidden

 }

 I have hundreds of DIV elements with that rule.
 I will like to change the width property directly on the rule. Without
 iterating all the elements and
 inlining the new width.

 Is that possible?

 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.