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

Katalin Rebhan <[email protected]> Thu, 23 Jul 2026 01:01:44 +0200
Newsgroups gmane.comp.lib.gnustep.general
Message-ID <[email protected]>
--Apple-Mail=_271A5B7E-F850-44BB-87B3-8FEB065244FA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On 22. Jul 2026, at 07:35, Gregory Casamento =
<[email protected]> wrote:
>=20
> As our team grows, the binary nature of .gorm files is becoming =
untenable. Because Git cannot merge binary files, concurrent changes =
result in merge conflicts where "the last person to merge wins."

> While we can easily read these formats, writing to them will always be =
imperfect. Therefore, I propose we design a custom, project-controlled =
serialization format that meets three criteria:
>     1. Compositional Structure: Nested objects should reflect the =
actual UI hierarchy (e.g., nesting an NSView inside an NSWindow tag).
>     2. Human-Readable & Editable: This will allow clean version =
control and manual merging.
>     3. Project-Controlled: We dictate the schema, protecting us from =
external breaking changes.

Hi,

This might be a bit out of left field, but is it perhaps feasible to
instead have a Gorm merge tool, keeping the format? I.e. you give it a
base/ours/theirs and it will merge the files with its specific
structural knowledge about Gorm files (maybe even built into Gorm
itself). Git already doesn=E2=80=99t have to use its built-in text =
merge, you can
use whatever tool you want.

I feel like generic text merge on a complex data format like UI layout
even if the format is theoretically suitable for it is always going to
be error-prone, especially if you aren=E2=80=99t an expert on reading =
the format
(and I feel like a merge tool would be more the NeXTSTEP approach :^) ).

Cheers,
Katalin


--Apple-Mail=_271A5B7E-F850-44BB-87B3-8FEB065244FA
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQRZnaWI8gLWxkaKIHnv4LcrvDUVFwUCamFL2AAKCRDv4LcrvDUV
F7M8AP9nY7jmXtjNx6C9o+VgMBG93Aa0b5CV9RLpDDYN4TUD8QEArPd4zEXmi4DQ
IWJZ38yjEiz8LaBxF6+5dZtxMqgIJAU=
=hcZO
-----END PGP SIGNATURE-----

--Apple-Mail=_271A5B7E-F850-44BB-87B3-8FEB065244FA--