Ohh I see. I was thinking because XML was so cluttered that the problem laid there and makes not only difficult to read it, but to diff it.... In the case of STON the serializer enumerates the objects and use pointers to them using ordinal numbers (like @1 or @20), so moving children is mostly indicated by changing such ordinals. I don't know if this is useful about the behind-the-scenes for Leo.
Cheers and thanks for the clarification, Offray On 09/07/17 11:29, Edward K. Ream wrote: > On Sun, Jul 9, 2017 at 11:10 AM, Offray Vladimir Luna Cárdenas > <[email protected] <mailto:[email protected]>> wrote: > > > Some fairly simple changes like sorting siblings can give > false impression of massive changes when in fact there is no > big difference in code. > > > Yes. This is truly annoying. > > That's why of us have proposed a more diff friendly format, like > YAML or JSON and that's why I use STON for Grafoscopio. > > > Imo, changing the format of .leo files will not make much > difference. The problem is idiosyncratic to Leo and will require a > lot of behind-the-scenes work. > > Edward > -- > You received this message because you are subscribed to the Google > Groups "leo-editor" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/leo-editor. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
