[gwt-contrib] TaskEngine sample patched for GWT 2.0 MS 2
All, [excuse the cross posting to gwt/appengine] The TaskEngine sample application (http://taskengine.googlecode.com) by jaimeyap is a Google Web Toolkit application that runs on App Engine (http://taskengine.appspot.com) but is especially designed for use on iPhone. TaskEngine depends on GWT Incubator (http://code.google.com/p/google- web-toolkit-incubator) for CssResource, which is now folded into the main GWT trunk with GWT 2.0 Milestone 2. (http://code.google.com/p/ google-web-toolkit/downloads/list?can=1&q=2.0+Milestone+2). I have patched the TaskEngine sample code to remove the dependency for the incubator jar, and use the updated annotations for CssResource and ClientBundle available in GWT 2.0 MS 2. The patch is located at: http://code.google.com/p/emcode/wiki/TaskEnginePatchGWT20MS2 I have posted a screencast of TaskEngine running in the iPhone SDK emulator at: http://www.youtube.com/watch?v=LuJi6nadVhU Stuart -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] GWT RC2 - Events are being hid by Layout layers in UIBinder
Env: GWTRC2 Safari Mac OS X.
UI binding:
{{{
}}}
These two custom widgets sit right on top of each other visually. The
reason is I want them to "replace" each other. Since MyLister is added
last, I can trigger events from it. When I fire a certain event from
MyLister, MyLister hides via setVisible(false) and MyEditor displays
via setVisible(true) However, because MyEditor is a layer "below"
MyLister, all events are hidden. E.g. onClick in widget in MyEditor
does not fire.
Is there any way (declaratively or programmatically) to swap the
positions of the layers so that the visible layer is "on top" and can
respond to events?
sfm
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] GWT RC2 - Events are being hid by Layout layers in UIBinder
Thanks Joel.
My current workaround is to use the "old" Horizontal/VerticalPanel widgets,
so "no harm, no foul". Looking forward to more examples!
Stuart
On Mon, Nov 30, 2009 at 12:20 PM, Joel Webber wrote:
> Stuart,
>
> Hiding/showing layers is slightly tricky (or at least non-obvious). I'm
> still working on examples in the documentation that should make it a lot
> clearer.
>
> In a nutshell, you need to actually show/hide the layer elements
> themselves. You can get the layer's element (referred to as a widget's
> "container" element) using *LayoutPanel.getWidgetContainerElement(Widget).
> Showing/hiding this element rather than the widget itself should get rid of
> any event problems. I'll make a point to add an example of this to the
> documentation.
>
> I didn't want to require the existence of the elements, but it proved
> impossible to support arbitrary CSS any other way (the existence of these
> elements makes it possible to efficiently account for margins, borders, and
> padding on the child widgets' elements).
>
> Cheers,
> joel.
>
> On Thu, Nov 26, 2009 at 2:33 AM, Stuart Moffatt
> wrote:
>
>>
>> Env: GWTRC2 Safari Mac OS X.
>>
>> UI binding:
>> {{{
>>
>>
>>
>>
>>
>>
>>
>>
>> }}}
>>
>> These two custom widgets sit right on top of each other visually. The
>> reason is I want them to "replace" each other. Since MyLister is added
>> last, I can trigger events from it. When I fire a certain event from
>> MyLister, MyLister hides via setVisible(false) and MyEditor displays
>> via setVisible(true) However, because MyEditor is a layer "below"
>> MyLister, all events are hidden. E.g. onClick in widget in MyEditor
>> does not fire.
>>
>> Is there any way (declaratively or programmatically) to swap the
>> positions of the layers so that the visible layer is "on top" and can
>> respond to events?
>>
>> sfm
>>
>> --
>> 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] GWT RC2: TabPanelLayout -- no supporting CSS?
All, I found myself needing band-aids (read: bleeding edge) while trying out TabLayoutPanel. 1) The javadocs and code for TabLayoutPanel suggest that the gwt- TabLayoutPanel(*) css selectors exist: http://code.google.com/p/google-web-toolkit/source/browse/releases/2.0/user/src/com/google/gwt/user/client/ui/TabLayoutPanel.java 2) And, poking around the trunk shows this tidy example: http://code.google.com/p/google-web-toolkit/source/browse/releases/2.0/user/javadoc/com/google/gwt/examples/TabLayoutPanelExample.java 3) When that example is implemented, there is no CSS on the TabLayoutPanel: http://tablayoutpanel.latest.emcode-dev.appspot.com/ While there is no CSS to dress it up, the layout and events are mostly correct on Safari 4.0.3 (Mac). But on FF 3.5.5 (Mac) only one tab shows (the third) sitting above the contents of the first tab. Yikes, not really cross-browser. 4) Of course, it seems that the main problem is that the new gwt- TabLayoutPanel(*) selectors don't yet exist, in here: http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/user/theme/standard/public/gwt/standard/standard.css or any other of the themes/css files. Is there someone sitting on a patch for gwt-TabLayoutPanel(*) selectors, or is the problem deeper? I came across a couple of TODOs and hints about css floats maybe not doing the trick under the TabLayoutPanel implementation. Any help on this? In the meantime, is there sample UIBinder xml to use the old TabPanel instead? -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] GWT RC2: TabPanelLayout -- no supporting CSS?
Joel,
Is there something "special" that I need to do in my ui.xml in order to get
these CSS rules applied to my TabLayoutPanel?
http://google-web-toolkit.googlecode.com/files/xhtml.ent";>
... ui style ... src? type? empty? do I add {style.*} styles to the XML
below?
First Tabfirst tab
content
Second Tabsecond tab
content
You'll notice my sample app which has no default CSS rules applied:
http://tablayoutpanel.latest.emcode-dev.appspot.com/
Stuart
On Wed, Dec 2, 2009 at 12:49 AM, Joel Webber wrote:
> The following CSS rules should work fine with the TabLayoutPanel as checked
> in:
>
> .gwt-TabLayoutPanel { }
> .gwt-TabLayoutPanelTabs { }
> .gwt-TabLayoutPanelTab { }
> .gwt-TabLayoutPanelTab .gwt-TabLayoutPanelTabInner { }
> .gwt-TabLayoutPanelTab-selected { }
> .gwt-TabLayoutPanelTab-selected .gwt-TabLayoutPanelTabInner { }
>
> While we haven't added rules to default.css, et al, these rules should be
> sufficient for most standard CSS tricks. There is indeed an issue that's
> causing the tabs to stack up on Firefox, for which I will be committing a
> patch momentarily (TabLayoutPanel.java:111 should be setting "cssFloat"
> rather than just "float").
>
> If you run into other problems with the structures that are there, please
> let me know.
>
> Thanks,
> joel.
>
> On Tue, Dec 1, 2009 at 11:12 PM, Stuart Moffatt
> wrote:
>
>> All,
>>
>> I found myself needing band-aids (read: bleeding edge) while trying
>> out TabLayoutPanel.
>>
>> 1) The javadocs and code for TabLayoutPanel suggest that the gwt-
>> TabLayoutPanel(*) css selectors exist:
>>
>>
>> http://code.google.com/p/google-web-toolkit/source/browse/releases/2.0/user/src/com/google/gwt/user/client/ui/TabLayoutPanel.java
>>
>> 2) And, poking around the trunk shows this tidy example:
>>
>>
>> http://code.google.com/p/google-web-toolkit/source/browse/releases/2.0/user/javadoc/com/google/gwt/examples/TabLayoutPanelExample.java
>>
>> 3) When that example is implemented, there is no CSS on the
>> TabLayoutPanel:
>>
>> http://tablayoutpanel.latest.emcode-dev.appspot.com/
>>
>> While there is no CSS to dress it up, the layout and events are mostly
>> correct on Safari 4.0.3 (Mac). But on FF 3.5.5 (Mac) only one tab
>> shows (the third) sitting above the contents of the first tab. Yikes,
>> not really cross-browser.
>>
>> 4) Of course, it seems that the main problem is that the new gwt-
>> TabLayoutPanel(*) selectors don't yet exist, in here:
>>
>>
>> http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/user/theme/standard/public/gwt/standard/standard.css
>>
>> or any other of the themes/css files.
>>
>> Is there someone sitting on a patch for gwt-TabLayoutPanel(*)
>> selectors, or is the problem deeper? I came across a couple of TODOs
>> and hints about css floats maybe not doing the trick under the
>> TabLayoutPanel implementation. Any help on this?
>>
>> In the meantime, is there sample UIBinder xml to use the old TabPanel
>> instead?
>>
>> --
>> 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
Re: [gwt-contrib] GWT RC2: TabPanelLayout -- no supporting CSS?
Thanks. Will give @external a try. Stuart On Wed, Dec 2, 2009 at 8:59 AM, BobV wrote: >> [...@rjrjr, bobv: Is there some easy way to put plain, unobfuscated CSS rules >> in a .ui.xml file?] > > Yes. Declare those class selectors to be @external in the CSS block. > > @external gwt-TabLayoutPanelTabs gwt-TabLayoutPanelTabInner; > > Now that ui:style allows users to specify a src attribute as well as > inline styles, we should provide a CSS file that has @external > declarations for all of the gwt- styles. Alternatively, the @external > syntax could be extended with something like "@external gwt-*;" > > -- > Bob Vawter > Google Web Toolkit Team > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] GWT RC2: TabPanelLayout -- no supporting CSS?
Yep. @external worked. Thanks everyone.
For the record:
= TabLayoutPanelTest =
Thisthis
Thatthat
The Otherthe other
=== TabLayoutPanel.css
@external gwt-TabLayoutPanelTabs;
@external gwt-TabLayoutPanelTabInner;
@external gwt-TabLayoutPanelTab;
@external gwt-TabLayoutPanelTab-selected;
.gwt-TabLayoutPanelTab, .gwt-TabLayoutPanelTab-selected {
position: relative;
height: 26px;
width: 9em;
margin-left: -16px;
}
.gwt-TabLayoutPanelTab .gwt-TabLayoutPanelTabInner,
.gwt-TabLayoutPanelTab-selected .gwt-TabLayoutPanelTabInner {
height: 26px;
padding-left: 15px;
}
.gwt-TabLayoutPanelTab {
background: url(tab-inactive-left.png) no-repeat bottom left;
cursor: default;
}
.gwt-TabLayoutPanelTab .gwt-TabLayoutPanelTabInner {
background: url(tab-inactive-right.png) no-repeat bottom right;
}
.gwt-TabLayoutPanelTab-selected {
background: url(tab-active-left.png) no-repeat bottom left;
z-index: 1;
}
.gwt-TabLayoutPanelTab-selected .gwt-TabLayoutPanelTabInner {
background: url(tab-active-right.png) no-repeat bottom right;
}
.gwt-TabLayoutPanelTabs {
background: url(tabs-bg.png) repeat-x bottom;
padding-left: 2em;
margin-left: 2px;
margin-right: 4px;
}
.gwt-TabLayoutPanelTabInner div {
color: #444;
padding-top: 6px;
font-weight: bold;
height: 26px;
text-align: center;
margin-right: 15px;
}
.gwt-TabLayoutPanelTab .gwt-TabLayoutPanelTabInner div {
background: url(tab-inactive-center.png) repeat-x top;
}
.gwt-TabLayoutPanelTab-selected .gwt-TabLayoutPanelTabInner div {
background: url(tab-active-center.png) repeat-x top;
}
=
Note that all of the CSS class names in the CSS file need to be
annotated @external at the top of the CSS file. This could have all
been on one line, but it also works one per line.
Where to put things:
- Since the CSS path is picked up from the ui.xml file, the parser
expects the CSS file to be in the same path as the ui.xml file.
- Since the image URLs are inline in the CSS, but the CSS is annotated
external, then the images are expected to be in the war root
directory, right beside the main .html file for the project. (Images
were in an attachment in a previous email in this thread.)
And here is what it should look like:
http://tablayoutpanel.latest.emcode-dev.appspot.com
Stuart
On Wed, Dec 2, 2009 at 10:22 AM, Ray Ryan wrote:
>
> I don't think we should thaw 2.0 for the externalized CSS file (though it's
> tempting), but it would be a good add for the downloads page. Or a tool that
> externalizes CSS files, similar to the one that generates java interfaces
> from them.
>
> On Dec 2, 2009 5:59 AM, "BobV" wrote:
>
> > [...@rjrjr, bobv: Is there some easy way to put plain, unobfuscated CSS
> > rules > in a .ui.xml file?]
>
> Yes. Declare those class selectors to be @external in the CSS block.
>
> @external gwt-TabLayoutPanelTabs gwt-TabLayoutPanelTabInner;
>
> Now that ui:style allows users to specify a src attribute as well as
> inline styles, we should provide a CSS file that has @external
> declarations for all of the gwt- styles. Alternatively, the @external
> syntax could be extended with something like "@external gwt-*;"
>
> --
> Bob Vawter
> Google Web Toolkit Team
>
> --
>
> 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
Re: [gwt-contrib] GWT RC2 - Events are being hid by Layout layers in UIBinder
@jgw,
Now that my TabLayoutPanel is working (thanks, btw), I want to go back
to using LayoutPanel and . The problem is, my UI requires a
few layers that nest nicely together like the old VerticalPanel (one
above the other as you go down the page). Using a LayoutPanel with
layers, my UI components now sit "one above the other" as in "right on
top of each other".
Now that VerticalPanel and HorizontalPanel are on the way out, do I
now I have to worry coding my own CSS to replicate the functionality
that VerticalPanel had built in? It is not apparent how I should make
layers gang up either vertically or horizontally without sitting right
on top of each other.
Stuart
On Tue, Dec 1, 2009 at 7:51 AM, Stuart Moffatt wrote:
> Thanks Joel.
> My current workaround is to use the "old" Horizontal/VerticalPanel widgets,
> so "no harm, no foul". Looking forward to more examples!
> Stuart
>
> On Mon, Nov 30, 2009 at 12:20 PM, Joel Webber wrote:
>>
>> Stuart,
>> Hiding/showing layers is slightly tricky (or at least non-obvious). I'm
>> still working on examples in the documentation that should make it a lot
>> clearer.
>> In a nutshell, you need to actually show/hide the layer elements
>> themselves. You can get the layer's element (referred to as a widget's
>> "container" element) using *LayoutPanel.getWidgetContainerElement(Widget).
>> Showing/hiding this element rather than the widget itself should get rid of
>> any event problems. I'll make a point to add an example of this to the
>> documentation.
>> I didn't want to require the existence of the elements, but it proved
>> impossible to support arbitrary CSS any other way (the existence of these
>> elements makes it possible to efficiently account for margins, borders, and
>> padding on the child widgets' elements).
>> Cheers,
>> joel.
>> On Thu, Nov 26, 2009 at 2:33 AM, Stuart Moffatt
>> wrote:
>>>
>>> Env: GWTRC2 Safari Mac OS X.
>>>
>>> UI binding:
>>> {{{
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> }}}
>>>
>>> These two custom widgets sit right on top of each other visually. The
>>> reason is I want them to "replace" each other. Since MyLister is added
>>> last, I can trigger events from it. When I fire a certain event from
>>> MyLister, MyLister hides via setVisible(false) and MyEditor displays
>>> via setVisible(true) However, because MyEditor is a layer "below"
>>> MyLister, all events are hidden. E.g. onClick in widget in MyEditor
>>> does not fire.
>>>
>>> Is there any way (declaratively or programmatically) to swap the
>>> positions of the layers so that the visible layer is "on top" and can
>>> respond to events?
>>>
>>> sfm
>>>
>>> --
>>> 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
Re: [gwt-contrib] GWT RC2 - Events are being hid by Layout layers in UIBinder
@jgw, rjrjr, > You can use all kinds of inline-block > hackery (since its cross-browser support is poor), but even that breaks down > under various circumstances. Which is what I was trying to avoid by going completely table-less. > VerticalPanel, on the other hand, is less useful (I find, anyway). You can > almost always just stack up block-level elements in a div (in other words, > just shove most any widget in a FlowPanel) and get the effect of a > VerticalPanel without all the table stuff. However, I hit a dead-end with nesting TabLayoutPanel in a FlowPanel. The dummy latin text in the following ui.xml never shows up (the tabs are there, and clickable, but none of their child content displays): NestedFlowTabLayoutPanel.ui.xml north east south west This Lorem ipsum dolor sit amet, consectetur adipiscing elit. That In consequat, odio non tincidunt ornare. The Other the other On the other hand, nesting a TabLayoutPanel in a LayoutPanel with layers seems to work better, except for the aforementioned rendering problem of layers sitting right on top of layers. I think I changed my question: Are we seeing a bug in TabLayoutPanel that makes it render improperly if nested in a table-based widget like VerticalPanel or HorizontalPanel? Stuart -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] GWT RC2 - Events are being hid by Layout layers in UIBinder
..ah, let me restate that. This ui.xml makes the tab panel layout in the center of the dock panel disappear: north east south west This Lorem ipsum dolor sit amet, consectetur adipiscing elit. That In consequat, odio non tincidunt ornare, metus diam cursus odio, eget venenatis nulla sapien non massa. The Otherthe other The same goes for VerticalPanel. But, if I switch to a FlowPanel wrapping the TabLayoutPanel, the tabs appear but the content under the tabs does not. sfm -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] GWT RC2 - Events are being hid by Layout layers in UIBinder
Caught it: the height of the TabLayoutPanel must be explicitly set,
either programmatically or via a {style.*} setting in the ui.xml, or
else the content in the tabs cannot be seen.
So V/H panels survive the day.
My apologies for the traffic.
sfm
On Thu, Dec 3, 2009 at 5:44 PM, Stuart Moffatt wrote:
> ..ah, let me restate that.
>
>
> This ui.xml makes the tab panel layout in the center of the dock panel
> disappear:
>
>
>
> north
>
>
> east
>
>
> south
>
>
> west
>
>
>
> barHeight="28">
> This
>
> Lorem ipsum dolor sit amet,
> consectetur adipiscing elit.
>
>
> That
>
> In consequat, odio non
> tincidunt ornare, metus diam cursus odio,
> eget venenatis nulla sapien non massa.
>
>
> The
> Otherthe other
>
>
>
>
>
> The same goes for VerticalPanel.
>
> But, if I switch to a FlowPanel wrapping the TabLayoutPanel, the tabs
> appear but the content under the tabs does not.
>
> sfm
>
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: GWT RC2: TabPanelLayout -- no supporting CSS?
@jgw, Morten makes a good observation (which I wasn't worrying about for now as I just chalked it up to pre-release fuzzies). Any ideas why the rendering in FF is so poor? It seems we might be heading back to the land where web developers need a PhD in browser quirks (albeit CSS instead of JS) sfm On Tue, Dec 8, 2009 at 4:10 PM, Morten Holm wrote: > On 3 Dec., 21:53, Stuart Moffatt wrote: > > And here is what it should look like: > > > > http://tablayoutpanel.latest.emcode-dev.appspot.com > > > > This looks great in Safari, but not so good in FireFox. Any idea why? > > Morten -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] Re: GWT RC2: TabPanelLayout -- no supporting CSS?
Figured something along those lines. Thanks Joel.
sfm
On Tue, Dec 8, 2009 at 4:22 PM, Joel Webber wrote:
> That should be fixed in the final release. Turns out I had made the mistake
> of writing style.setProperty("float", "left"), rather than
> style.setProperty("cssFloat", "left"). The latter is "correct", but WebKit
> accepts either.
>
> (Yes, there should be a style.setFloat() method, but that will have to come
> later, once I have time to write a script to generate the bazillion CSS
> property setters!)
>
> On Tue, Dec 8, 2009 at 4:17 PM, Stuart Moffatt wrote:
>
>> @jgw,
>>
>> Morten makes a good observation (which I wasn't worrying about for now as
>> I just chalked it up to pre-release fuzzies).
>>
>> Any ideas why the rendering in FF is so poor? It seems we might be heading
>> back to the land where web developers need a PhD in browser quirks (albeit
>> CSS instead of JS)
>>
>> sfm
>>
>> On Tue, Dec 8, 2009 at 4:10 PM, Morten Holm wrote:
>>
>>> On 3 Dec., 21:53, Stuart Moffatt wrote:
>>> > And here is what it should look like:
>>> >
>>> > http://tablayoutpanel.latest.emcode-dev.appspot.com
>>> >
>>>
>>> This looks great in Safari, but not so good in FireFox. Any idea why?
>>>
>>> Morten
>>
>>
>> --
>> 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] GWT 2.0 dead in IE7?
@bruce, @jwg, @rjrjr
(and any other gwt'ers listening)
I just posted about a fairly severe show-stopper for my application
(that is, the app doesn't even finish onModuleLoad() in IE7 (see
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/952cdae8b5efa1d3)
I thought it was likely due to my code. So I built a dead simple
EntryPoint using the UiBinder wizard with a few touch ups:
import com.google.gwt.core.client.EntryPoint;
import com.google.gwt.core.client.GWT;
import com.google.gwt.uibinder.client.UiBinder;
import com.google.gwt.uibinder.client.UiField;
import com.google.gwt.user.client.ui.Button;
import com.google.gwt.user.client.ui.HTMLPanel;
import com.google.gwt.user.client.ui.RootLayoutPanel;
import com.google.gwt.user.client.ui.Widget;
public class UiBinderTestForIE implements EntryPoint {
private static UiBinderTestForIEBinder uiBinder = GWT.create
(UiBinderTestForIEBinder.class);
interface UiBinderTestForIEBinder extends UiBinder {}
@UiField Button button;
@UiField HTMLPanel htmlPanel;
public void onModuleLoad() {
Widget w = uiBinder.createAndBindUi(this);
RootLayoutPanel root = RootLayoutPanel.get();
root.add(w);
}
}
And here is the ui.xml
http://dl.google.com/gwt/DTD/xhtml.ent";>
.important {
font-weight: bold;
}
Hello,
User
When I launch this in Chrome / FF, I get what I expect. When launched
in IE7, there is nothing on the page. Yet, the console reports that
the module has been loaded.
At first I thought it was a problem with the developer plugin in IE,
so I compiled it and put it up on my App Engine sandbox:
http://uibindertestforie.latest.emcode-dev.appspot.com and tested from
two different machines. Works in FF/Chrome on both machines. Nothing
in IE7 on either machine.
What's the deal?
Again, it could be my code. But, really? GWT 2.0 is dead in IE7? I
can't actually believe it, so someone please tell me what I am doing
wrong.
Stuart
[cross-posting to gwt, gwt-contrib]
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] Re: GWT 2.0 dead in IE7?
@jgw,
Thanks for the rescue. I thought I was going crazy. Totally forgot about the
effects of doctype.
Nice to have: when the eclipse project wizard (or the app creator tool) is
updated to create a UiBinder-style Greeting template, it would be nice if
the doctype in the template html page was switched to standards-mode. Less
heart attacks for sleepy coders ;)
sfm
On Thu, Dec 10, 2009 at 9:18 AM, Joel Webber wrote:
> [duplicating my last message because it failed to post to groups/gwt last
> time]
>
>
> On Thu, Dec 10, 2009 at 9:11 AM, Joel Webber wrote:
>
>> The problem here is that you're using RootLayoutPanel explicitly, which
>> requires the use of a standards-mode doctype.
>>
>> * This widget will only work in standards mode, which requires
>> that
>> * the HTML page in which it is run have an explicit
>> * declaration.
>>
>> The good news is that these days you can just throw a
>> declaration at the top of the page to get there -- no need to dig through
>> the 37 different versions of [x]html doctypes. IE is particularly strange in
>> quirks mode, which is why you're seeing such a large difference.
>>
>> Hope that helps,
>> joel.
>>
>> On Wed, Dec 9, 2009 at 9:36 PM, Stuart wrote:
>>
>>> @bruce, @jwg, @rjrjr
>>>
>>> (and any other gwt'ers listening)
>>>
>>> I just posted about a fairly severe show-stopper for my application
>>> (that is, the app doesn't even finish onModuleLoad() in IE7 (see
>>>
>>> http://groups.google.com/group/google-web-toolkit/browse_thread/thread/952cdae8b5efa1d3
>>> )
>>>
>>> I thought it was likely due to my code. So I built a dead simple
>>> EntryPoint using the UiBinder wizard with a few touch ups:
>>>
>>> import com.google.gwt.core.client.EntryPoint;
>>> import com.google.gwt.core.client.GWT;
>>> import com.google.gwt.uibinder.client.UiBinder;
>>> import com.google.gwt.uibinder.client.UiField;
>>> import com.google.gwt.user.client.ui.Button;
>>> import com.google.gwt.user.client.ui.HTMLPanel;
>>> import com.google.gwt.user.client.ui.RootLayoutPanel;
>>> import com.google.gwt.user.client.ui.Widget;
>>>
>>> public class UiBinderTestForIE implements EntryPoint {
>>>
>>>private static UiBinderTestForIEBinder uiBinder = GWT.create
>>> (UiBinderTestForIEBinder.class);
>>>interface UiBinderTestForIEBinder extends UiBinder>> UiBinderTestForIE> {}
>>>
>>>@UiField Button button;
>>>@UiField HTMLPanel htmlPanel;
>>>
>>>public void onModuleLoad() {
>>>
>>>Widget w = uiBinder.createAndBindUi(this);
>>>RootLayoutPanel root = RootLayoutPanel.get();
>>>root.add(w);
>>>}
>>>
>>> }
>>>
>>> And here is the ui.xml
>>>
>>> http://dl.google.com/gwt/DTD/xhtml.ent";>
>>> >>xmlns:g="urn:import:com.google.gwt.user.client.ui">
>>>
>>>.important {
>>>font-weight: bold;
>>>}
>>>
>>>
>>>Hello,
>>>>> ui:field="button">User>> g:Button>
>>>
>>>
>>>
>>> When I launch this in Chrome / FF, I get what I expect. When launched
>>> in IE7, there is nothing on the page. Yet, the console reports that
>>> the module has been loaded.
>>>
>>> At first I thought it was a problem with the developer plugin in IE,
>>> so I compiled it and put it up on my App Engine sandbox:
>>> http://uibindertestforie.latest.emcode-dev.appspot.com and tested from
>>> two different machines. Works in FF/Chrome on both machines. Nothing
>>> in IE7 on either machine.
>>>
>>> What's the deal?
>>>
>>> Again, it could be my code. But, really? GWT 2.0 is dead in IE7? I
>>> can't actually believe it, so someone please tell me what I am doing
>>> wrong.
>>>
>>> Stuart
>>>
>>> [cross-posting to gwt, gwt-contrib]
>>>
>>> --
>>>
>>> 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.
>>>
>>>
>>>
>>
> --
> http://groups.google.com/group/Google-Web-Toolkit-Contributors
>
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: GWT 2.0 dead in IE7?
Logged as issue 4331
http://code.google.com/p/google-web-toolkit/issues/detail?id=4331
On Dec 10, 9:54 am, Stuart Moffatt wrote:
> @jgw,
>
> Thanks for the rescue. I thought I was going crazy. Totally forgot about the
> effects of doctype.
>
> Nice to have: when the eclipse project wizard (or the app creator tool) is
> updated to create a UiBinder-style Greeting template, it would be nice if
> the doctype in the template html page was switched to standards-mode. Less
> heart attacks for sleepy coders ;)
>
> sfm
>
>
>
> On Thu, Dec 10, 2009 at 9:18 AM, Joel Webber wrote:
> > [duplicating my last message because it failed to post to groups/gwt last
> > time]
>
> > On Thu, Dec 10, 2009 at 9:11 AM, Joel Webber wrote:
>
> >> The problem here is that you're using RootLayoutPanel explicitly, which
> >> requires the use of a standards-mode doctype.
>
> >> * This widget will only work in standards mode, which requires
> >> that
> >> * the HTML page in which it is run have an explicit <!DOCTYPE>
> >> * declaration.
>
> >> The good news is that these days you can just throw a
> >> declaration at the top of the page to get there -- no need to dig through
> >> the 37 different versions of [x]html doctypes. IE is particularly strange
> >> in
> >> quirks mode, which is why you're seeing such a large difference.
>
> >> Hope that helps,
> >> joel.
>
> >> On Wed, Dec 9, 2009 at 9:36 PM, Stuart wrote:
>
> >>> @bruce, @jwg, @rjrjr
>
> >>> (and any other gwt'ers listening)
>
> >>> I just posted about a fairly severe show-stopper for my application
> >>> (that is, the app doesn't even finish onModuleLoad() in IE7 (see
>
> >>>http://groups.google.com/group/google-web-toolkit/browse_thread/threa...
> >>> )
>
> >>> I thought it was likely due to my code. So I built a dead simple
> >>> EntryPoint using the UiBinder wizard with a few touch ups:
>
> >>> import com.google.gwt.core.client.EntryPoint;
> >>> import com.google.gwt.core.client.GWT;
> >>> import com.google.gwt.uibinder.client.UiBinder;
> >>> import com.google.gwt.uibinder.client.UiField;
> >>> import com.google.gwt.user.client.ui.Button;
> >>> import com.google.gwt.user.client.ui.HTMLPanel;
> >>> import com.google.gwt.user.client.ui.RootLayoutPanel;
> >>> import com.google.gwt.user.client.ui.Widget;
>
> >>> public class UiBinderTestForIE implements EntryPoint {
>
> >>> private static UiBinderTestForIEBinder uiBinder = GWT.create
> >>> (UiBinderTestForIEBinder.class);
> >>> interface UiBinderTestForIEBinder extends UiBinder >>> UiBinderTestForIE> {}
>
> >>> �...@uifield Button button;
> >>> �...@uifield HTMLPanel htmlPanel;
>
> >>> public void onModuleLoad() {
>
> >>> Widget w = uiBinder.createAndBindUi(this);
> >>> RootLayoutPanel root = RootLayoutPanel.get();
> >>> root.add(w);
> >>> }
>
> >>> }
>
> >>> And here is the ui.xml
>
> >>> http://dl.google.com/gwt/DTD/xhtml.ent";>
> >>> >>> xmlns:g="urn:import:com.google.gwt.user.client.ui">
> >>>
> >>> .important {
> >>> font-weight: bold;
> >>> }
> >>>
> >>>
> >>> Hello,
> >>> >>> ui:field="button">User >>> g:Button>
> >>>
> >>>
>
> >>> When I launch this in Chrome / FF, I get what I expect. When launched
> >>> in IE7, there is nothing on the page. Yet, the console reports that
> >>> the module has been loaded.
>
> >>> At first I thought it was a problem with the developer plugin in IE,
> >>> so I compiled it and put it up on my App Engine sandbox:
> >>>http://uibindertestforie.latest.emcode-dev.appspot.comand tested from
> >>> two different machines. Works in FF/Chrome on both machines. Nothing
> >>> in IE7 on either machine.
>
> >>> What's the deal?
>
> >>> Again, it could be my code. But, really? GWT 2.0 is dead in IE7? I
> >>> can't actually believe it, so someone please tell me what I am doing
> >>> wrong.
>
> >>> Stuart
>
> >>> [cross-posting to gwt, gwt-contrib]
>
> >>> --
>
> >>> 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 >>> cr...@googlegroups.com>
> >>> .
> >>> For more options, visit this group at
> >>>http://groups.google.com/group/google-web-toolkit?hl=en.
>
> > --
> >http://groups.google.com/group/Google-Web-Toolkit-Contributors
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] Re: GWT 2.0 dead in IE7?
Just to be clear: Issue 4331 is not about the doctype declaration. My posts
on doctype and another (very troublesome) defect regarding IE got crossed.
Sorry for the confusion.
Stuart
On Thu, Dec 10, 2009 at 3:34 PM, Joel Webber wrote:
> Lex's idea as well. I'll do that.
>
>
> On Thu, Dec 10, 2009 at 2:39 PM, Ray Ryan wrote:
>
>> Joel, shouldn't we put an assert to that effect somewhere in
>> RootLayoutPanel? Perhaps even something more garrish, tied to asserts being
>> enabled: replace its body with text saying "This panel will only work in
>> standards mode, set your doctype like so: "
>>
>>
>> On Fri, Dec 11, 2009 at 2:35 AM, Stuart Moffatt
>> wrote:
>>
>>> Logged as issue 4331
>>>
>>> http://code.google.com/p/google-web-toolkit/issues/detail?id=4331
>>>
>>> On Dec 10, 9:54 am, Stuart Moffatt wrote:
>>> > @jgw,
>>> >
>>> > Thanks for the rescue. I thought I was going crazy. Totally forgot
>>> about the
>>> > effects of doctype.
>>> >
>>> > Nice to have: when the eclipse project wizard (or the app creator tool)
>>> is
>>> > updated to create a UiBinder-style Greeting template, it would be nice
>>> if
>>> > the doctype in the template html page was switched to standards-mode.
>>> Less
>>> > heart attacks for sleepy coders ;)
>>> >
>>> > sfm
>>> >
>>> >
>>> >
>>> > On Thu, Dec 10, 2009 at 9:18 AM, Joel Webber wrote:
>>> > > [duplicating my last message because it failed to post to groups/gwt
>>> last
>>> > > time]
>>> >
>>> > > On Thu, Dec 10, 2009 at 9:11 AM, Joel Webber
>>> wrote:
>>> >
>>> > >> The problem here is that you're using RootLayoutPanel explicitly,
>>> which
>>> > >> requires the use of a standards-mode doctype.
>>> >
>>> > >> * This widget will only work in standards mode, which
>>> requires
>>> > >> that
>>> > >> * the HTML page in which it is run have an explicit
>>> <!DOCTYPE>
>>> > >> * declaration.
>>> >
>>> > >> The good news is that these days you can just throw a >> html>
>>> > >> declaration at the top of the page to get there -- no need to dig
>>> through
>>> > >> the 37 different versions of [x]html doctypes. IE is particularly
>>> strange in
>>> > >> quirks mode, which is why you're seeing such a large difference.
>>> >
>>> > >> Hope that helps,
>>> > >> joel.
>>> >
>>> > >> On Wed, Dec 9, 2009 at 9:36 PM, Stuart
>>> wrote:
>>> >
>>> > >>> @bruce, @jwg, @rjrjr
>>> >
>>> > >>> (and any other gwt'ers listening)
>>> >
>>> > >>> I just posted about a fairly severe show-stopper for my application
>>> > >>> (that is, the app doesn't even finish onModuleLoad() in IE7 (see
>>> >
>>> > >>>
>>> http://groups.google.com/group/google-web-toolkit/browse_thread/threa...
>>> > >>> )
>>> >
>>> > >>> I thought it was likely due to my code. So I built a dead simple
>>> > >>> EntryPoint using the UiBinder wizard with a few touch ups:
>>> >
>>> > >>> import com.google.gwt.core.client.EntryPoint;
>>> > >>> import com.google.gwt.core.client.GWT;
>>> > >>> import com.google.gwt.uibinder.client.UiBinder;
>>> > >>> import com.google.gwt.uibinder.client.UiField;
>>> > >>> import com.google.gwt.user.client.ui.Button;
>>> > >>> import com.google.gwt.user.client.ui.HTMLPanel;
>>> > >>> import com.google.gwt.user.client.ui.RootLayoutPanel;
>>> > >>> import com.google.gwt.user.client.ui.Widget;
>>> >
>>> > >>> public class UiBinderTestForIE implements EntryPoint {
>>> >
>>> > >>>private static UiBinderTestForIEBinder uiBinder = GWT.create
>>> > >>> (UiBinderTestForIEBinder.class);
>>> > >>>interface UiBinderTestForIEBinder extends UiBinder>> > >>> UiBinderTestForIE> {}
>>> >
>>> > >>>@UiField Button button
