Quite good to know.
Some questions about it:
a) Could you provide both, 64bit and 32bit versions?
b) Is there anything planned to get the code body window for an
operation to a reasonable size?
c) Why is it so complicated to add an operation to a class, and add e.g.
some C code to it?
I have to add an operation to a class, then I have to click the
method-'+' button in the operations properties view. Then, another
dialog pops up, where I have to also click on the '+' Button to add
an "OpaqueExpression" (or a "FunctionBehaviour?!?), which pops up
another Dialog, where I first have to select, which parent element
should contain that new "OpaqueExpression". Then "Ok", then another
Dialog pops up, where I have to give that one again a name, and
select, in which language it should be, and also again, I have to
specify which of which type. I guess that type is again the same, as the
operation I
actually just wanted to add!?!?!?!
The Body editor part has a visible space of 19 characters and 2
lines!! So, I wonder, who the hell is ever entering code in there?!
This is ridiculous! Who designed that and is even using it?!?
d) There was a UML2C code generator, and there is UMLEC. What state will
they be, and what kind of code are they able to generate?
Will they also generate code from Activity/StateMachine/Sequence
Diagrams? or just the basic structure stuff, and what someone might be
able to enter
in the above mentioned editor window?
How will I be able to adapt that generator, e.g. how would I let it
create Macros, type mapping, prolog/epilog of elements?
How would I setup a usage dependency to be either in
"Implementation" (.c file) or "Specification" (.h file)
How would I be able to set such stuff for each generation setting?
e.g.
${AttributeComment}
${AttributeProlog} ${type} ${name} [= ${InitializerList};${AttributeEpilog}
${FunctionComment}
${FunctionProlog}
${returntype} ${functionname}(${arglist})
{
}
${FunctionEpilog}
I wonder, how your "customers"/sponsors are using TOPCASED and for what?
Just to paint some class diagrams?
Do they make lots of adaptions to TOPCASED? Which code generators do
they use (and based on what)?
Do they also have reverse engineering tools for e.g. C or C++ (based on
what)?
Is it meant, that an operation which is not mapped to operation
behaviour, but e.g. an Activity Diagram or a State Machine, that ther
code for the function is directly generated from these diagrams into
this function?
In the current state of TOPCASED, I would regret to work in production
with it .. sorry to say that, but it is cumbersome to use in the state
you provide it.
Regards,
kessel
Am 01.11.2012 18:53, schrieb Topcased user list where issues are discussed:
TOPCASED 5.3 alpha exists but we first need to get a complete
validation campaign in order to deliver a final 5.3.0 release. As
there was no sponsor for that until recently, the delivery is
postponed (we have updated the roadmap on topcased.org to precise
that) . We expect to get the 5.3 validation campaign performed on the
second half of november or beginning of december. So there is a
reasonnable chance that the 5.3.0 can be out for christmas ;-)
In parallel, we will probably deliver an experimental TOPCASED-JUNO
release for mid december. For such a release, there is no need to get
a full validation campaign so it is just a matter of integration.
Best regards
TOPCASED delivery team
------------------------------------------------------------------------
_______________________________________________
Topcased-users mailing list
[email protected]
http://lists.gforge.enseeiht.fr/cgi-bin/mailman/listinfo/topcased-users
