Re: Proposal: create XML based .gorm format: .xorm

On 22/07/2026 06:35, Gregory Casamento wrote:
> # Compositional Structure: Nested objects should reflect the actual UI=
=20
> hierarchy (e.g., nesting an |NSView| inside an |NSWindow| tag).
> # Human-Readable & Editable: This will allow clean version control and=
=20
> manual merging.
> # Project-Controlled: We dictate the schema, protecting us from external=
=20
> breaking changes.

I get where you are coming from, but suspect that maybe the only person=20
with the background to happily manually edit archives would be you.

For that reason, I'd suggest that the primary objective should be a=20
format which is easily diffable: things are divided up by newlines and=20
there are stable groupings of lines between different versions of an=20
archive (no cases where a small change in the UI results in a huge=20
number of separate changes in the archive) so that changes produced by=20
diff are small/clean.

So yes, I agree that things need to be at least human readable enough=20
that we can make some sense of diffs when we need to.

I don't know if that acctually requires your 'compositional structure'=20
objective:=C2=A0 if not, I'd say that's nice to have, but secondary.

I think your third point is an obvious given: who elses schema would we=20
want to adopt anyway? I don't know of anything suitable.