On Mon, Jul 7, 2008 at 7:39 AM, Edward K. Ream <[EMAIL PROTECTED]> wrote:
>
>
> On Sun, Jul 6, 2008 at 12:38 PM, Kent Tenney <[EMAIL PROTECTED]> wrote:
>>
>> > At present, a script button converts a non-shadowed file to a shadowed
>> > file.  We could make the process of shadowing files more automatic.
>> > For example, @shadow-thin and @shadow-file might create shadowed
>> > private files in @thin or @file formats respectively.
>>
>> Sort of like the freedesktop thumbnails standard.
>> http://people.freedesktop.org/~vuntz/thumbnail-spec-cache/index.html
>> http://people.freedesktop.org/~vuntz/thumbnail-spec-cache/thumbsave.html
>>
>> When an image file is opened (by compliant apps), a file is created
>> in the ~/.thumbnails tree. This convention of using 'companion' files
>> has been proven to be very effective.
>
> Something like that.  The details are different:
>
> 1. We have a place to put private shadow files: in the leo-shadow directory
> of whatever directory contains the public file.

Could the shadow directory location be configurable?
Then Leo wouldn't have to write it's private stuff to the public directory.

>
> 2. We needn't hash the file name: we can munge the name of the private file
> in a more readable way.

I was put off by the hash at first, but the reasoning behind it seems to be
that .thumbnail files are intended to be of interest only to the app, not much
interest in user space.

The hashes are easier for code to work with; fixed length, easily indexed,
removing ambiguity regarding whether or not the shadow is current.



>
> But indeed, the idea is essentially the same: associating a "helper" file
> with a "main" file.
>
> Edward
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to