Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Famix Milestone-4.3
New issue 539 by tudor.gi...@gmail.com: Introduce SourceLanguage as an explicit entity http://code.google.com/p/moose-technology/issues/detail?id=539
Currently, sourceLanguage is modeled with a symbol stored in the Model. This is suboptimal due to at least two things: - the only way to decide strategies of what highlighting to use when displaying text is with an if - there is no possibility of having multiple languages in the same model
I would like to introduce FAMIXSourceLanguage as an explicit entity that can be linked to any FAMIXEntity.
If an entity does not have a FAMIXEntity, it will fallback to the mooseModel sourceLanguage.
The overall MooseModel sourceLanguage will be decided based on the FAMIXSourceLanguage object that has no attached entities.
Updates: Status: Fixed
Comment #1 on issue 539 by tudor.gi...@gmail.com: Introduce SourceLanguage as an explicit entity http://code.google.com/p/moose-technology/issues/detail?id=539
I did the followings:
- introduced FAMIXSourceLanguage - FAMIXSourcedEntities have potentially declaredSourceLanguage - if there is none, we fall back to the source language of the MooseModel - the MooseModel checks to see if there is a FAMIXSourceLanguage that is not attached to an entity, and if there is it means this is the language for the entire model - refactored the implementation of MooseModel>>isSmalltalk
-
moose-technology＠googlecode.com