> Luke said:
>the SimplePanel is excessive. its purpose is to help turn widgets
> that don't have certain kinds of DOM characteristics (can't accept
> focus for example) to compensate for that lack. you don't need it.
>
> ...
>
> .panelname {
> margin: 15px;
> }
>
> that should do the trick. the alternative is to use the "Spacing"
> parameter or "Padding" parameter.
when I read this my thoughts were at first like a 5-year-old-kid's
"well duh I know what padding is, duh. I'm gonna show why just using
those isn't working, and for that very same reason, it's not going to
work without a div, cause there's no way its the div causing the
problem" and so then I made a simple HTML mockup of the situation with
two divs, and then one with only one div.
And for the second one the CSS worked as it was supposd to work....
groan. oh man... i'm such an idiot sometimes. That was what I was
doing wrong this whole time. Removing those excess panels actually
solved most of the incredibly messy problems I was having (and made
redundant the crazy selector I was using to get to an Hbox cell). The
only problems that remained were ones which required trial-and-error
on my hobbyist part. Thanks.
> actually i use it all the time. the only thing you have to remember
> with DockPanel is that you must use *both* setWidth (on the widget)
> *and* setCellWidth (passing in the widget and the exact same width
> value). or... yeah, if you want things to sit in the middle a bit,
> set the horizontal and vertical alignment to CENTER on each cell and
> then set the width of the widget to a bit less.
oh... did not know that. That could come in handy in the future.
>Rich said:
>I can feel your pain. Our app has a LOT of very specific layouts on
>multiple pages, and I struggled mightily to find a technique that I
>could use to get consistently good results on all browsers. The problem
>ISN'T Pyjamas (or Python) it's simply life in the Browser (i.e. HTML+CSS)
>world. You get tangled up deciding things like tables vs. divs, inline
>styles vs. sheets, etc.etc..
I know, right? I get straight-up confused sometimes when it comes to
screen resolution and scaling in CSS. What's worse, with ie6 more or
less gone, I no longer have an excuse. :D
Anyway, I finished up the rest of the layout (so I could find any
other problems before I e-mailed). But after some wrangling with
tabpanels, the UI is all working now, even if my color schemes are
awful.
I'll probably send in a nice link to the app next week after some
debugging (though there'll still be plenty of development to be done,
maybe be at version 0.3 or 0.2.5, still far from any release)
Nick.
