So given that CSS is used for the "flesh" what to you anchor it to?
The layout panels? With images as backgrounds (so you'd need 4
different anchors for 4 rounded corners?)? Or do you use something
like an HTMLPanel with several "divs" to outline around layout panels?
I feel more and more like my code is becoming a "hodge-podge" of
different markups and losing some of the "benefits" of the simplicity
of UIBinder. It seems like I'm missing a more elegant solution.
Anyone?
On Apr 15, 8:36 pm, dparish <dpar...@gmail.com> wrote:
> If gwt has a failing it's making the app look well rounded. Ok bad
> pun. The uibinder makes you think you are sculpting a ui. You really
> aren't. You are writing a skeleton that needs CSS for the flesh.
>
> The client side generated HTML is complex which makes the task harder.
> It's worth it considering the power and flexibility gwt gives you
>
> -Dave
>
> On Apr 15, 7:14 pm, Jonny <jonny.bren...@gmail.com> wrote:
>
>
>
>
>
> > Despite all my searching (and mostly because of the limited
> > information available regarding proper use of UIBinder) I cannot find
> > a simple, elegant way to use UIBinder with rounded corners. The
> > Google I have a vary simple, one page business card site with the with
> > the outline of the page as a rounded corner pod. There are a few pods
> > within that, one of which I want to use as the new TabLayoutPanel
> > (requiring strict browser support). I considered using the "older"
> > DecoratorPanel but that requires quirks mode. Is there an equivalent
> > for the new "layout" structures? My original code just laid out css
> > in the default html page and I anchored all my widgets using the
> > RootPanel.get('id') operation but that does not work with
> > RootLayoutPanel.get(), thereby limiting my ability to use the new
> > TabLayoutPanel.
>
> > I'm considering avoiding the new UIBinder features altogether, at
> > least until more tutorials are available but I have to say I'm am very
> > tempted
> > I hope this all makes some sense. I'd be happy to clarify as this
> > "simple" webpage project in GWT has turned into much more of a design
> > barrier than anything else.
>
> > --
> > 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
> > athttp://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-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group
> athttp://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-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.
