|When it gets bigger... Teamactivation or base when or nothing? [message #643650]
||Tue, 07 December 2010 13:22
| Jan Marc Hoffmann
Registered: July 2009
my project has reached quite a bit of complexity. SInce its an extension of the OT Tooling for another language there are many places where I had to do some adjustments. This results in a ton of roles and a few teams. (70 Roles, 10 Teams). Everything would be fine if my Tooling were alone in the eclipse workbench and the only files and projects open are of my language extension.
But sadly thats not the case. So it would be wise to activate my tooling only when it's needed. Otherwise I might break some working stuff ^^. The "when it's needed" is by far the most difficult thing when adapting a complex framework with OT.
So what should I do? There are several ways to handle the activation of my teams and roles. I could either use the "base when" or "team activation". Or a mix of both. But what should I use if I have the choice? Should one prefer the TeamActivation or the RoleActivation (I ll call it that way to make it easier..)?
Or could you generally say that it's best to do the activation on the highest level (control flow) possible? For example, Team, Role, Callin. In that order.
And a second question: Is there some tool which might help me get an overview over active teams and roles?
thanks and greetings
Powered by FUDForum
. Page generated in 0.02015 seconds