Reading new Atlassian notes - anchors

[Varsuuk]

I see in one of the UI Standards docs it says:


Design Notes
When designing templates for this standardization effort, the goal is that templates should be self-contained for defined the anchoring offsets needed to support their frame offsets, and to prevent overlap with other controls. The end result should be that controls should be able to be stacked on top of each other as simple blocks, instead of trying to guess offsets that look good.

Other notes:

Lists and formatted text fields should indent extra 10 for scrollbars

Top anchor should be named “contentanchor”; and bottom anchor named “bottomanchor”
(for limited backward compatibility)

Provide options primarily for vertical layout (top down, bottom up, fill, split fill)

(Emphasis mine ;) )

And

OK - the following won't prob look right (check the "Window Layout Templates" section of https://fantasygroundsunity.atlassian.net/wiki/spaces/FGCP/pages/2172420127/UI+Standards+-+Rulesets+and+Extensions - there I wonder how to interpret.

For a window: charsheet_main.xml, do I create a name="contentanchor" or name="anchor_content_top" or "anchor_content_charsheet_main_top" or ?


For each of the top-level and panel window frames, there are a number of standard templates that should be used in order to ensure that content is displayed within the correct space with window frame assets using different sizes for borders, edges, gutters, shadows, etc.

The templates to be used are specified below, where “framename” should be replaced by the top level frame used:

Template Name

Notes

anchor_content_framename_top

Top/left/right edges of content area

anchor_content_framename_bottom

Bottom edge of content area;
Requires top anchor

close_framename

Location of window close button (upper-right)

help_framename

Location of window help button (upper-right)

resize_framename

Location of window resize graphic (lower-right);
Just a graphic; window resizing still requires frame asset insideoffset tag to be set to matching offsets.

Top and bottom anchors should be used as the place where content should be anchored to using relative anchoring. See that CoreRPG ruleset in the template_windows.xml for the templates of CoreRPG provided top-level and panel window frames.

When replacing top-level frames in layered rulesets or theme extensions, make sure to update all the associated templates to ensure that content is correctly placed in the new frames.

[Moon Wizard]

The overall layout helpers have not been worked on for the character sheets yet; and the character sheet layout code is fragmented across the various rulesets.

As noted in the UI document, we are starting the process with the tool/setting/utility and asset view windows. Next up are the record list windows, then the individual record windows (other than character sheet), then character sheet.

I'll add more information in the Laboratory forum as the project advances.

Regards,
JPG

[Varsuuk]

Gotcha. I just wanted to understand what it says whether it is implemented or not. The top I understood to telling me to use contentanchor and below I thought it was telling me to name them one of the three guesses I made, but I have no idea which if any of the 4 is (or will be) right.

If I knew what names will be used I’ll start using them as a proxy meanwhile or if in the case of windows I create that would not be in CoreRPG, if I am supposed to use one of the latter ones filling in my frame name, I could do that on the one I am just starting in vs having to fix all the errors ai create with search and replace (especially cos atm I am using RW to help me with planning looks - I suspect since it didn’t help me much with the windows where I made extensive use of anchors and relative options that I won’t stick with it for the long run)

[Moon Wizard]

Once I get to that location, they will be named:
anchor_content_charsheet_top
anchor_content_charsheet_bottom

I'm basically working through the top-level frames in the order of least to most impactful. (referencelist is next; with retirement to referencepage->recordsheet)

Regards,
JPG