Style SchemaEditor

[alistair3149]

Closes: #391, #388

Key changes:

• Implement styles to SchemaEditor according to Figma spec
• Refactor DialogFooter component into EditSummary to be more generic
• Use EditSummary component for edit summary in SchemaEditor
• Use CdxMenu for property list
• Use CdxToggleSwitch for boolean values instead of CdxCheckbox
• Drop unused Codex override styles from global.scss

Recording.2025-05-14.200126.mp4

[JeroenDeDauw]

Nice!

Two ideas for improvment, not nececerily in this PR:

• Scrollbar in the property list to avoid vertical scroll of the entire page
• Select first property on initialization to avoid just seeing the property list

[malberts]

Looks great. I'm still reviewing, but my first thought is we should add a max-width on the outer container (or on inputs). The UI feels a bit weird when it is wide (e.g. at 1920x1080 where full screen is still common, bigger screens get worse). The toggle switch in particular bothers me. I know clicking the label toggles it, but the visual element is all the way on the far right. This is not a problem with a checkbox where it's right next to the label.

In Vector 2022 it looks good, but in Vector, Chameleon and Medik the width can be problematic.

For example, compare Special:Search (max-width on container) and Special:Preferences (max-width on inputs).

[malberts]

This shows the wrong help message on SchemaEditor:

[malberts]

I'll follow up on this.

[malberts]

Minor thoughts:

• EditSummary does not sound like it's a component with actions.
• It's being used on SubjectEditorDialog, SchemaEditorDialog and EditSchemaPage. Right now it's probably fine since they all mostly look and act the same, but if we end up passing in a bunch of cusomtizations, then maybe there is only a superficial similarity that should not really be extracted.

[malberts]

If it's just a margin, can't we rather add a custom common class like attributes-editor? Or maybe even add it once in PropertyDefinitionEditor. It feels like a hack to repurpose a class meant for something else.

[malberts]

Initially I did not use CdxMenu because my understanding was that it's supposed to be used in a specific way - as part of something that triggers a dropdown.
For example: :expanded="true" and the drop shadow point to the intention of it being a floating and hideable component.

I guess it's fine if it works. But I'm not sure at what point repurposing components in unintented ways might be a problem.