On Fri, Dec 9, 2011 at 8:00 AM, Jesse Vander Does <[email protected]> wrote: > I finally got a chance to wade into this mess. After reading the responses > a few times and messing around in my code I'm sure I have no freaking clue > what I'm doing. . . Ugh, layout. It feels crazy how difficult it is to > get my able to fill out the page. My intuitive response is to come up with > some sort of expanding content, or deal with it using callbacks.
there is another way, which you have access to thanks to pyjamas in a convenient manner: see the Mail example with its proliferation of onWindowResize. in this way, you can simply bypass absolutely everything, set everything manually to fixed pixel distances, calculate absolutely everything yourself and you will then _know_ that it is going to be correct.... ... but you have to actually do that. now the thing is: it *does not matter* what "system" you use, whether it be pyjamas, straight HTML/CSS or some god-awful random bit of javascript downloaded off the internet, you *have* to understand how CSS works. even i don't quite get how CSS works, so i just experiment until it works reasonably well, because i go copying other bits of code from places in the examples where a particular widget works and does the job. but yes: scrollpanels are a bitch. you cannot just "go make one", you *do* have to look very very closely at the examples. what i recommend that you do is copy *entirely* an example that contains a scrollpanel, then "adapt" it - even if that's one line of code at a time. then, if it breaks (because you made only one character change) you know not to do that again. remember to commit to a source control repsitory every single time - even if it's just one character change in one single line. l.

