At first: Thank you very much for the information, Volker! So the layout manager always has to know at least basic information about the boundaries. Well, I was playing around with really a LOT of combinations of size or design information but I cannot remember setting size values for the page itself. That's because I was convinced that the rendering system would always pack the contained components together as tight as possible (depending on their size and positioning) if there's no outer boundary assigned.
So I was fiddling about with various "columns" and "rows" attributes in gridLayout elements. With no sensible effect. Still, I have problems understanding the layout manager. How does the component positioning process work? As I understood it up to now, facets with gridLayout can define the sizes of the cells for (neighbour) components. But can't there be problems when gridLayouts a few levels lower define conflicting sizes? Well, maybe yes, and then an error is thrown and the site can't be built. But what's the case when several nested gridLayouts have lots of not exactly defined size values like rows="*"? Is there a precedence of some kind? I mean, Tobago doesn't have very much documentation, does it? To be serious, in my eyes tlddoc or javadoc are normally most important pieces of documentation, but I have a hard time even understanding some attribute descriptions in tlddoc... And of course, I can't derive very much layout management information from it ;) You see, I still have a very basic lack of knowledge about the rendering process. Of course I really don't expect from you to explain everything. On the other hand, I'd deeply appreciate a hint to some (online) documentation about that topic. Or some good (offline) books. My research until now didn't yield any valuable result at all. > or if you want a layout which reflects the actual size of your > browserwindow > [...] > <managed-property> > <property-name>clientWidth</property-name> > <value>800</value> > </managed-property> > <managed-property> > <property-name>clientHeight</property-name> > <value>600</value> > </managed-property> > </managed-bean> Er... so these clientX properties define the screen resolution and the browser window size is retrieved based on that information somehow? But so there's no way to generate a page _totally_ dynamically, independent of screen resolution as well? Have a nice Sunday! Bernd
