Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - g.makulik

Pages: [1] 2 3
Suggestions and Requests / Forum FAQ and policies
« on: January 31, 2013, 06:12:13 am »
Pro FAQ:

I've seen several discussion threads here that either end up with links to (for long term users) well known issues and discussions, or some generally applicable answers about usage of the forum (e.g. search strategies, 'official' bug reports, 'official' feature requests, when to contact Sparx support, etc.).

Pro policies:
Besides YABB's (sometimes strange) standard policies, there should be some points clarified for this particular forum, e.g. the role of Sparx employees/admins that participate here and what the OP of a question might expect for responses.

Both could be simply realized as e.g. "important" topics like done with RoyC's No English? †topic in the general board.
The FAQ topic may contain replies with question like titles (e.g. 'Will Sparx notice a post I made in the 'Bugs and Issues' board for doing a fix?'), which can be contributed by any forum user, but either be pre-discussed on this board, or be discussed with "Re:" prefix on the FAQ thread (suboptimal IMHO). Anyway replies there be rigorously removed by admins if not applicable.

Anyone else supporting this?

Best regards,

I'm willing to contribute to the FAQ of course, but answers there should be heavily moderated from Sparx admins side, so one or more maintainers should admit for this.

... element notations

EA should implement rendering constraints for textual element notations as e.g. attributes or operations in their compartments according UML 2.3 spec:

7.3.10 Constraint (from Kernel)
... For an element whose notation is a text string (such as an attribute, etc.), the constraint string may follow the element text
string in braces.

It should be possible to select the constraints to be rendered (shown) per (feature) element (/diagram).

See also this related forum thread:

Feature request submitted.

Suggestions and Requests / Preprocessor macros for C missing?!?
« on: November 27, 2012, 11:46:24 am »
Wouldn't it make sense to provide preprocessor macro setting also for C language?

There are surely a lot of compiler implementation or framework specific definitions, that should be ignored when C code is imported/synchronized.

Opinions anyone?

Best reagards,


I've recently sent a bug report to Sparx that the 'Advanced' settings set with the 'Generate Code' command for a selected (Class) element doesn't change anything for this particular element's generated code (I was particularly referring the 'C-Language->Object Oriented Support' option).
Their answer was that this behavior is intended and this(those) option(s) won't be considered on class level.

Well the options sections are titled 'Options for the current model/user', though your value changes will be saved and recalled on class level. I find this behavior pretty misleading, either changing such settings should be disabled or not accepted to be saved (at class level).

Most of those options I would find pretty useful to be configured on class level anyways.

Thoughts, experiences or workarounds anyone?



Suggestions and Requests / C OOP support option
« on: November 16, 2012, 05:44:58 am »
The C OOP support option should be revealed on package level, e.g. as a special tagged value supported by standard C code generation/reverse engineering features.

The current project global option gives conflicts with imported legacy C code.

Anyone else an opinion about this?


I'd like to propose that EA should provide an interface for reverse engineering and synchronizing code for custom defined (code generation) languages. At least I couldn't work out so far, how this could be done using the existing AddIn events.


It would be nice to have a feature to add custom compartments to non native drawn shapes, e.g using a special sub shape script.


Suggestions and Requests / Feature to add icons in custom compartments
« on: March 31, 2012, 12:53:30 am »
I like the new custom compartment feature for shape scripts, now its possible to list your child elements in the main shape.
It would be nice though to have a drawing method feature to add an icon/decoration to appear in the beginning of each child element text line.
Such you could achieve an appearance similar as in native package shapes.


General Board / Promotion of SO Enterprise-Architect tag
« on: October 08, 2014, 05:42:40 am »
Hi all,

I attended the EA User Group Europe meeting in Munich today, and noticed a number of complaints about the low quality of this forum:

  • Advanced search is too slow, limited.
  • Sorting of results by relevance is bad.
  • Obscure user voting system.
  • ...

Well, since the Sparx Experts and moderators are around here, this is what will keep up the usefulness and quality of this forum. Though the technical base (YaBB), probably isn't the best choice nowadays.

I'd like to invite everyone, who's frustrated by this forum, to have a look at the

StackExchange SO [enterprise-architect tag]

The community there is growing well, and you'll recognize a number of members who are around here also.

Best regards,

General Board / Questions on EA tagged value 'typeSynonyms'
« on: December 10, 2012, 01:47:03 am »
Does anyone know details about how the typeSynonyms tagged value works and what are it's effects regarding code generation and reverse engineering (C/C++ in particular).

I've made at least some interesting observations in project browser behavior selecting elements having this tagged value set.


Bugs and Issues / C Gode Generation, handling private class elements
« on: November 23, 2012, 08:05:38 am »
Hi all,

IMHO the way EA renders certain UML elements to C-code representation (without using the OOP support option) is wrong:

  • private (static) attributes/operations:
    private features should be really private, that means for C that they should have the 'static' keyword applied on compilation unit level. Otherwise the C compiler will warn about usage of an element defined without static but linking isn't prohibited. May be there's an intend with this implementation for enabling protected elements, but it should still be distinguished.

  • public static attributes (and initialization):
    public (static) attributes should render an 'extern' declaration in the header file and a (non static!) definition including initialization arguments (from initial value) in the source.
I've tried to provide remedy on these flaws changing the standard C code generation templates, but failed so far.

Thoughts, opinions or workarounds anyone?

Best regards,

Bugs and Issues / C code function pointer typedef import fails
« on: November 30, 2012, 08:04:45 am »
Am I right that importing function pointer typedefs like the following aren't supported for C rev. engineering?

Code: [Select]
typedef void (*FuncSig1)(int, char*);
typedef int (*FuncSig2)(int);

For C++ this is the recommended approach following the User Guide.

How is it possible to make use of function pointer definitions for C code generation/synchronization?

Best regards,

Bugs and Issues / CTF 'Import' and 'Import Impl' templates
« on: November 25, 2012, 08:28:55 am »

Can someone tell me how these templates apply exactly, I cannot find any general documentation for these.

I can see though these have code for languages like Java or C#. I just guess you can use these to have more fine grained control over single import statements (e.g. realized by #include or extern statements in C/C++).

1. Is there a possibility to use these from C/C++ code generation?

2. Is there further possibility to control the contents produced by the %fileImports% CTF macro anyhow?

I'd like to have #include statements generated for standard framework classes like std::string or std::vector<int>
The include statements for such classes always look like this:
Code: [Select]
#include "string.h"
#include "vector.h"
These #include statements should rather render as
Code: [Select]
#include <string>
#include <vector>

Does anyone know a solution how to achieve this for C/C++ code generation (without using class level code generation Import(s)/Header(s) settings)?

Best regards,

Bugs and Issues / Interface operation properties not reflected
« on: October 31, 2012, 09:05:23 am »
Can someone explain this strange difference of the operation properties from an interface with the properties showing up in the corresponding Method element from the EA object API:

Of course these properties are implicit for operations appearing in interface elements, though it's pretty strange that this isn't reflected in the EA.Method interface †:o ...

I think this is worth a bug report, anyone else came over this??


Bugs and Issues / Code Templates not updated using MDG tech
« on: April 02, 2012, 12:03:34 am »

I have a number of code templates for a new language stored in a profile project. When I export my (main) profile the checkbox 'Export Code Templates' is checked, afterwards I bundle everything using the 'Generate MDG Technology' wizard. The 'Code Templates' option is checked in the 'Code Modules' wizard page as well.
In newly created projects using this MDG technology, the Code Templates aren't changed though. We always need to import these as separate reference data. I guess this is a bug, or I completely misunderstood about that 'Export Code Templates' checkbox.
To be honest, I doubt what should relate a profile to the code template reference data anyway †:-?. Shouldn't this be just the option in the 'Generate MDG Technology - Code Modules' wizard page (I'll give that another try also)?


Pages: [1] 2 3