RE: [Andromda-devel] ScriptHelper subtask

[<to...@am...>]

Hi,

I guess I will disagree back at you :-)

You are not restricted to a single helper with the current design, becaus=
e
you could add as many methods as you want to the one helper that would gi=
ve
you access to other helpers.  

Example:

 $transform.workflowHelper
 $transform.stateMachineHelper
 $transform.useCaseHelper


>-- Original Message --
>From: Mat...@gm...
>To: "Anthony Mowers" <to...@am...>
>Cc: and...@li...
>Subject: RE: [Andromda-devel] ScriptHelper subtask
>Date: Tue, 27 May 2003 10:26:20 +0200 (MEST)
>
>
>Hi Anthony,
>
>I don't agree with you. I know that andromda allows the definition of a
>single helper class on a per-template basis. But this still restricts an=
dromda
>to
>the single "$transform" helper.
>Why shouldn't I use different helper on one template? I think the existe=
nce
>of the StringUtilsHelper proofs that it can make sense to have different=

>helper classes for different purposes. Even within one template.
>Another problem with the current design is that I have to subclass the
>default helper SimpleOOHelper or UMLDefaultHelper if I want to use the
default
>helper methods AND my own helper methods within one template. In case my=

>own
>helper methods do not address the static behavior of the model the desig=
n
>results in a helper that mixes different aspects of the model in one cla=
ss.
>So in
>my opinion subclassing is not the proper design here.
>What do you think?
>
>Matthias.
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: ObjectStore.
>If flattening out C++ or Java code to make your application fit in a
>relational database is painful, don't do it! Check out ObjectStore.
>Now part of Progress Software. http://www.objectstore.net/sourceforge
>_______________________________________________
>Andromda-devel mailing list
>And...@li...
>https://lists.sourceforge.net/lists/listinfo/andromda-devel