2007/7/12, Michiel van der Wulp <[EMAIL PROTECTED]>:
Hi Marcos, (...) One more point: Suppose I create a profile, and use it on a project. Then I want my colleague to work on the project, so I send him the zargo file. This scenario shows, that it would be best, if the loaded profiles are stored in the zargo file.
1) You mean also adding the models provided by the profiles provided by plugins to the zargo files? 2) If the your colleague doesn't have all the required profiles (plug-ins or user defined) the project is still loadable (but the not found profiles are removed). My point is: I think this just makes sense when dealing with user defined profiles, with profiles defined by plug-ins I don't think this is worth doing. On machines that actually have the plug-in, we would have at least two (potentially) different profiles: the one inside the zargo file, and the one provided by the plugin. If the one provided by the plugin is used, the zargo would be carrying information that is not used at all, if all your machines have the plugin. If the one coming from the zargo file is used, the plugin would need to be "turned off". If the models differ, the plugin can rely on model elements that do not exist on the model. maas
