Steps to create a new application similar to SuperBrewer3000?

[glsp-bot]

Although I've alluded to this issue in other posts, please allow me to restate my primary confusion at this point. Let's say I modify the frontend and backend code in the demo to deal with a new model, completely different from that of the coffee editor, and I have generated the Java source code from the new model and placed it in the model plugin directory. Now I need to create a new application, completely discarding SuperBrewer3000 in the process. What really needs to be in this new application directory before I start the application? The only files that seem to be relevant were, in the SuperBrewer3000 example, superbrewer3000.coffee, superbrewer3000.coffeenotation, and superbrewer3000.wfconfig. I don't need the .wfconfig file because my new application doesn't have the analysis components. My specific question is when and how, in the context of creating a new application, are the .coffee and .coffeenotation files (with different names in my case) created? Is that something I need to do manually for a new application? And these are XMI files -- are they documented anywhere? While the .coffeenotation file appears to carry diagramming information that is only relevant to an existing diagram, I see lines like that suggest to me a linkage (via @workflows) to some other model-related file, but what file?

original thread by GaryKopp

[glsp-bot]

[Jonas Helming]

Hi,
.coffeentation is the diagram information, as you stated. .coffee file is the domain model instance data. These files can be directly created by EMF by putting initial content in a Resource and then save it. How you create this file in your application flow is completly up to you.

[glsp-bot]

[GaryKopp]

Thanks Jonas. Your response had me a little confused, almost sounding like in all cases I had to create and manage those files. But with a little experimentation with the original demo I came to realize this files are indeed maintained and persisted by the existing application, and the contents of the tree editor and diagram editor remain synchronized.