![]() |
Telelogic Rhapsody (steve huntington) | ![]() |
Topic Title: Rhapsody Properties system needs an overhaul Topic Summary: Created On: 26-Oct-2007 22:12 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi - We've been using Rhapsody for almost a year now, and a lot of our attempts at a nice clean setup have been foiled by the unnecessarily crippled Properties system. So, I'd like to start a dialogue on what can be done to improve it.
Some of our ideas: 1) All properties should support a large, common set of substitution variables for all code-insertion-type properties. Things like $(modelelementname), $(classname), $(operationname) should be available as widely and consistently as possible, instead of (in many cases) just in the ImplementationProlog. 2) Properties should be more flexible in overriding/appending/modifying their inherited value. For instance, I'd like to set up CG::Class::StandardOperation in a package (so far, so good) and then also set a specific class, set CG::Class::StandardOperation to "NewStandardOp,$(inherit from parent)" so that it will pick up the std ops from the package. This is a simple example, but I think it could be expanded to a nice generally useful system that fixes many maintenance limitations in the current system. Anyone else think these would be useful, or have suggestions for additional improvements that won't give backward compatibility fits? |
|
![]() |
|
![]() |
|
I do.
|
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.