Baseline support is needed on both ends. A given component needs to expose that it has a baseline (not all of them do) and where that baseline is.
A given container needs to know when it should line things up according to baselines, or just leave stuff alone. So yes, either the Skin or the Component subclass would need to have an API for retrieving baseline info. I would think that the baseline API would be defined on Component, but the Skin would set the value. (As is done for other layout attributes like preferredSize, etc). Greg Brown wrote: >> Note that this requires more than just a change to >> pivot.Form/pivot.TablePane, >> i.e. all pivot.wtk.Component would need to return their baseline, if they >> had one. >> > > If that's true, then we wouldn't need to create the new attributes. Is the > baseline something that the component's skin would define, or is it up to the > caller? If the former, then we'll need to modify the component API. If the > latter, then attributes would be more appropriate. > > > >
