Tom Morris wrote:
I think the model is the ideal place to hold the read-only attribute.
The project can load the model read-only (such as for profiles) or
this can happen implicitly (for external references), but then the
model subsystem should keep track and be able to be queried whether
something is editable.
(...)
Tom
+1
For 0.26, if we consider the currently supported use cases, we have the
models being loaded by XmiReader, which has 2 types of models: normal
and profiles. It would be simple to mark the profiles' models as read
only and all the rest as not read only.
Then something like isEditable would work, but, here I also agree that
the models should be marked as read only on the model sub-system, maybe
by the project or even, as I propose, implicitly by a model being a
profile. This is an attribute of a model, not something persistent, but
contextual.
Also, for the long term we might think of the multi-model project, where
you could mark a model as read-only within ArgoUML. This is user
explicit and even if something that goes through the project, it should
be explicitly managed and enforced by the model - IMO of course.
Regards,
Luis
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
