Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[mdt-papyrus.dev] RE: Papyrus: only one file

Hi all,

 

Here is the comment of Kenn.

According to Kenn, it is already possible to open archive file with EMF.

 


De : Kenn Hussey [mailto:kenn.hussey@xxxxxxxxx]
Envoyé : lundi 19 octobre 2009 15:05
À : GERARD Sebastien 166342
Objet : Re: Papyrus: only one file

 

Sébastien,

 

I think it's a bad idea to attempt to merge the content into a single resource. As I've suggested before, the archive (e.g. ZIP or JAR) approach is probably better, and EMF already has support for (de)serializing resources to/from archives. Another approach that would be better than having everything in one resource would be to have a single, top-level, "index" resource which essentially contains references to the other resources, which would in turn be stored in folders nested below; the names of the folders could start with "." to facilitate ease of filtering in the project/model explorer.

 

Cheers,

 

Kenn

On Sun, Oct 18, 2009 at 4:34 PM, GERARD Sebastien 166342 <Sebastien.GERARD@xxxxxx> wrote:

Hi Kenn,

 

We are discussing at the moment the solution to have only one file for the user. The first solution proposed by ATOS' boys is to merge in one single file all the the data. I think it would be better to use a kind of archive file that would gather all the files needed for a papyrus project. What do you thin in that issue? Do you know some existing facilities/plug-in that would implement my solution?

 

Thanks,

Cheers… Sébastien.

 

 

Dr. Sébastien Gérard

Head of MDD for DRES research project

CEA LIST/LISE

Boîte courrier 65, GIF SUR YVETTE

CEDEX, F-91191 France

Phone/fax : +33 1 69 08 58 24 / 83 95

Leader of the Eclipse Component Papyrus (The UML2 Graphical Modeler): www.papyrusuml.org

http://www.eclipse.org/modeling/mdt/?project=papyrus

 

Before printing, think about the environment

 

 


Back to the top