Use of attatchments

[Nathan L.Walls]

On Dec 1, 2004, at 9:32 AM, Bart Rossmann wrote:

> Co-workers and I attach files to the outlines we share when we beta
> tested.
>
> Basically, we would outline a project (like requirements for software
> development or some possible changes in our server infrastructure) and
> attach Word and OG documents that we would also modify. Easier that
> zipping all the files up and then referring to such and such a document
> in the project outline and we never forget to include necessary
> documents since they are in the OO package.
>
> Groovy

Overall, I like how Omni handled this. foo.oo3 becomes a container 
directory, similar to .app. But, one thing I don't see is a way to keep 
the attached document and the original in sync? Is this correct? If so, 
was it not practical to include a link (raw file path or something 
similar to an alias) in the <attatchments /> block?

Something else I noticed -- and any insight would be appreciated -- it 
appears if an attachment is included multiple times. Don't ask me why 
you'd do it, but I tried it to see. OO3 creates a new copy of the 
attachment, preview .tiff and a new reference in the data structure. I 
know I'm (intentionally) glazing over some complexity, but why not id 
these as the same file and only include it in the .oo3 container once?

Aside from these questions, I like what I see so far and look forward 
to discovering more.

Regards,

Nathan
--
nathan l. walls
articles and such:          http://ismedia.org
          "It's the 'Lorum Ipsum' of our time!"