If it is useful to some users, then I don't see any harm in including such a Container. It sounds like it wouldn't require much internal logic, so there wouldn't be much to go wrong or maintain.
Ages ago, I wrote a couple of simple extensions of TablePane to reduce the amount of BXML markup needed to achieve the sort of things that you have described. (Back in the dark days before the @DefaultProperty annotation). They allowed me to specify the same TablePane as I might otherwise have done in BXML, but using custom markup. One class was named StripPane as it would create either a vertical or horizontal 'strip' of Components. I added a custom Orientation property which allowed me to switch its layout direction (even at runtime, although I haven't needed that so far). It behaves like a slightly more flexible version of BoxPane, and was also useful for simple toolbar functionality. Another class sounds exactly like the 'FullSizePane' you describe, but I didn't end up using it nearly as much as I had expected. YMMV obviously. I have since rewritten both classes as 'builder' classes, made possible by a version of this idea I wrote up a while back. http://apache-pivot-developers.417237.n3.nabble.com/Idea-for-a-useful-change-to-BXMLSerializer-tp3133361p3133361.html So for instance, the 'FullSizePane' builder class just takes a single Component as input and then outputs a TablePane containing that Component in a 'maximized' cell. It allows for much simpler BXML while still creating org.apache.pivot.wtk.* Components. An additional benefit is that if I want to change the implementation, all I have to do is update the builder class and reload the BXML. On 20 August 2011 00:56, Roger L. Whitcomb <roger.whitc...@ingres.com> wrote: > In some places right now I'm using a simple BoxPane to wrap a bunch of > other components as children of CardPane that itself is being used to > populate "pages" of a bigger dialog template. But, although BoxPane is > simple, it sizes itself to its children's sizes except that if "fill" is > true it will expand in the orthogonal direction to fill the space. In > order to fill the space I know I can use TablePane or GridPane, but the > extra "stuff" required in my BXML files makes it awkward to do a simple > replacement. We're talking hundreds of places now in the code.... > > > > So, what I was thinking of was a "FullSizePane" (name is negotiable) > that does the equivalent of a one-row, one-column TablePane with width > and height of "1*" to just be a simple wrapper of other components. > That way, an embedded ScrollPane would fill up the space without having > to be given preferred sizes (that might or might not match the > container's size). This would be a simple name change in my BXML files > (from "BoxPane" to "FullSizePane") so the replacement would be easy. > > > > Am I thinking correctly? Do you think this would be useful enough to > include in Pivot? Or is there some other (simple) way to achieve this > effect without a new component? > > > > Thanks. > > > > Roger Whitcomb > > Architect, Engineering > > Ingres Corporation > > roger.whitc...@ingres.com <mailto:roger.whitc...@ingres.com> > > > > PHONE +1 650.587.5596 > > FAX +1 650.587.5550 > > > > www.ingres.com <http://www.ingres.com/> > > > > This transmission is confidential and intended solely for the use of the > recipient named above. It may contain confidential, proprietary, or > legally privileged information. If you are not the intended recipient, > you are hereby notified that any unauthorized review, use, disclosure or > distribution is strictly prohibited. If you have received this > transmission in error, please contact the sender by reply e-mail and > delete the original transmission and all copies from your system. > > > >
