| Re: [mdt-papyrus.dev] Cross-reference index in di-files? |
Hi, Philip, We had, in early releases, editor window layout information in the *.di file that caused headaches of constant churn and conflicts in that file in team source control (note that it is still an option to do this, which is useful when sending models to others with diagrams already open to show them). This was a problem because the editor layout is a manifestly personal thing, user-specific information that normally should not be shared. What you propose is not like this, so that is good. However, I think I would prefer not to see this index in the *.di file mostly because it is derived information. It is like the compiled *.class files and other resources that the Eclipse workspace treats specially: it is computed from the information already in source control and so keeping it there is redundant. But also this *.di resource can contain non-derived user data, so it cannot be excluded from source control (some users may like to) and it cannot be somehow treated as partially derived. And what are the potential pitfalls for team scenarios? I can imagine cases where merge accidents corrupt these indices, for example, if done without the EMF Compare tooling to manage it carefully. I would prefer to keep the index in the workspace metadata. I don’t think that the start-up cost for a new workspace of indexing the models is so onerous, but I must admit that I haven’t ever had the opportunity to observe it on real-world models of very large scale, only with naïvely generated models. Will your alternative solution require adding to the workspace metadata an index of all of the model files in remote branches that the user has fetched? Would this be so different to discovering an index that is stored within those same files? I hope that mine is not the only opinion on this subject. Cheers, Christian On 25 November, 2016 at 12:57:11, Philip Langer (planger@xxxxxxxxxxxxxxxxx) wrote:
|