On 12/12/2013 9:18 PM, Largo84 wrote:
Advance apology if this has already been considered and discarded as
impractical, stupid or whatever (since I'm not a programmer)....,but I
work with raw image files in photography that have 'sidecar' files
(XMP) that carry the metadata and editing instructions (they're
nothing more than glorified XML files with a specific purpose). The
convention is that the file name is the same between the sidecar file
and the raw image file. Any image editor then knows to read the
instructions in the XMP file for whatever purpose. The raw image file
is never actually touched or written to, just the XMP file. Different
image editors can ignore any specific XMP commands it doesn't
understand. It's a widely used convention in that arena and well
documented.
All of the discussion recently about @shadow files and sharing
outlines and the structure made me wonder if a similar strategy might
work for Leo created external files. For example a Leo user opening
SomeFile.py would read the outline structure from SomeFile.xmp (or
whatever file extension makes sense) The non-Leo user opening
SomeFile.py would simply see the plain .py file with no sentinels.
Other Leo users would need both files to share the outline structure.
Just a thought......
Rob................
As far as I know, this is what @shadow currently does. There are a
number of reasons why this is untenable, but that's really Edward's
current line of thought.
-->Jake
--
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 http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.
