[
https://issues.apache.org/jira/browse/PIVOT-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768218#action_12768218
]
Greg Brown commented on PIVOT-331:
----------------------------------
>From the more complex mockup, it seems like this definition of "vertical
>spacing" would be nearly sufficient. What is currently missing is the concept
>of an "upper" baseline vs. a "lower" baseline. The fields all seem to be
>arranged such that the "upper" baseline of component B is 28 pixels below the
>"lower" baseline of component A.
> Form layout improvements
> ------------------------
>
> Key: PIVOT-331
> URL: https://issues.apache.org/jira/browse/PIVOT-331
> Project: Pivot
> Issue Type: Improvement
> Components: wtk
> Reporter: Todd Volkert
> Priority: Minor
> Fix For: 1.4.1
>
> Attachments: form-layout-mockup.png, screenshot-before-and-after.png
>
>
> Graphic designers often want to lay out forms such that the vertical spacing
> between the baselines of the form elements is predictable. Though Pivot's
> Form can now align the baselines of its fields with their labels, it provides
> no way to coordinate the vertical spacing of the baselines. Take, for
> example, the following WTKX:
> <Window maximized="true"
> xmlns:wtkx="http://pivot.apache.org/wtkx";
> xmlns="org.apache.pivot.wtk">
> <content>
> <CardPane styles="{padding:10}">
> <Form>
> <sections>
> <Form.Section>
> <Label Form.label="Field 1" text="Foo"/>
> <Label Form.label="Field 2" text="Bar"/>
> <TextInput Form.label="Field 3" text="Baz"/>
> <TextInput Form.label="Field 4" text="Something Else"/>
> </Form.Section>
> </sections>
> </Form>
> </CardPane>
> </content>
> </Window>
> It produces the attached screenshot, where the vertical spacing between the
> baselines is unpredictable, even though the form's "verticalSpacing" style is
> evenly applied. Contrast this with the attached mockup provided by a graphic
> designer, where they clearly specify the layout in terms of spacing between
> baselines.
> It's not clear how best to achieve this feature from an architectural point
> of view. Ideas are welcome in this ticket.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
