Re: [platform-core-dev] Re: pushing the shared metadata idea...

["John Arthorne" <John_Arthorne@xxxxxxxxxx>]

Largely because there is no facility
for sharing preferences or properties (at least yet). You'd want the encoding
information available (at folder granularity) as soon as you check a project
out from the repository, so you can start editing files without having
to manually set or load encodings from elsewhere.





I'm a little puzzled. Why can't encoding's
needs be met with preferences + resource properties?
 
Bob
----- Original Message ----- 
From: Rafael
Chaves 
To: platform-core-dev@xxxxxxxxxxx

Sent: Wednesday, June 18, 2003 10:06 AM
Subject: Re: [platform-core-dev] Re: pushing the
shared metadata idea...


No, so far it was a "single-message thread". I have been told
that there had been a discussion about this before, but I didn't know it
was in the list archive (thanks for pointing it out). It was also a good
idea to move it to platform-core-dev because, as you said, it is related
to the new proposal for shareable preferences (although this message was
written before the proposal was made available, and the proposal authors
never read this before). 

Rafael

John Arthorne/Ottawa/IBM@IBMCA Sent by: platform-core-dev-admin@xxxxxxxxxxx 18/06/2003 10:51 AM Please respond to platform-core-dev

To:        platform-core-dev@xxxxxxxxxxx        cc:                Subject:        [platform-core-dev] Re: pushing the shared metadata idea...

Hi Rafael, I don't know if you've had discussions about this while I was
away, I may have missed it since I went through my mail quite quickly.
 First I wanted to point you to the thread from our last discussion
about this idea: 

http://dev.eclipse.org/mhonarc/lists/platform-core-dev/msg00048.html

My only real concern about moving the .project file again is the backwards
compatibility nightmare.  We currently have to look for a .prj file
(which used to exist before .project), and team looks for a .vcm_meta file
(the old name for the shared project description file).  It's also
confusing for users because they don't know what's safe to delete and what
needs to be shared.  Another option is to just add the file encoding
information in the .project file.  This was the approach used for
linked resources.  Since it's XML it's fairly easy to add more elements
in a backwards and forwards compatible manner.  This would avoid creating
more files/folders that clutter the user's content area and doesn't introduce
any new concepts from the user's point of view. 

I've moved the discussion to the mailing list so we have a record of it
and so other interested parties can follow it.  I suspect this is
something that will also need to be discussed in the context of the shared
user preferences work. 

John