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 - adepreter

Pages: [1] 2 3
1
Suggestions and Requests / Enable tooltips on HTML reports
« on: February 21, 2018, 11:54:48 pm »
We would like to see element notes when hovering on elements in generated HTML reports.

A.

Related post: http://sparxsystems.com/forums/smf/index.php/topic,29540.0.html

2
End users sometimes want to create several views of the same element on the same diagram.
They also want to tell which connector needs to be visible for each view on the element (diagram object).
They don't want to create a "virtual connector". How could they think about such terminology when searching the documentation?
=>

1) Bug: The documentation provides documentation on the implementation i.e. "virtual connector"
It should instead on the end user's feature i.e. getting several views on the same element on the same diagram.

2) Questioning the implementation
Why not creating virtual diagram objects instead of "virtual connectors". These virtual diagram objects would not visible in the project browser (like text, boundary etc...)??
Users would then explicitly hide the connectors they don't what to see for the virtual object.
So it would be also more flexible for the end-user.
And it would be a direct implementation of the requirement.

3
So that we can
- Export only changed elements (and import in other tools)
- Create reports on last changes

If we could also have the author that would be even better

4
Before importing elements from an Excel file, we would like to check whether the imported tagged values are compliant with the type defined in the element stereotype (part of a MDG).

Does anybody know how to validate the to-be-imported tagged values at runtime?

5
Prerequisite for reproducing the problems
- Create a package PV1 with 3 diagrams each showing same elements.

Scenario:
- Clone package PV1 as new version PV2

- In PV2...
- Open cloned diagram D1 and filter to version
- Create a new element ENEW
=> PROBLEM 1: ENEW is greyed out, though this is clearly a change.

- Clone an element ECHANGED. The element is properly cloned and it is no longer greyed out.
- Open cloned diagram D2 that shows same elements as D1
=> PROBLEM 2: ECHANGED is greyed out, though it has been clearly changed.

6
REQUEST
Get a variant of this syntax (http://mysite/?guid={xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx}) to get the url of the generated IMAGE.
I mean ONLY THE IMAGE (png). No frame and no project browser.

CONTEXT
HTML report of the Sparx model repository is generated every night

GOAL
Integrate html report page images into other web sites (SharePoint and WordPress) using some stable urls to these images.

7
CONTEXT
HTML report of the Sparx model repository is generated every night

GOAL
Integrate html report page images into other web sites (SharePoint and WordPress) using some stable urls to these page images.

MY QUESTION
Is there any existing variant of this syntax (http://mysite/?guid={xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx}) to get the url of a generated image?
Or is there any reusable Web Style template content/code that would do the trick?

Thanks

Alain

8
When a tag grouping is changed in an MDG the Synchronized Stereotype function does not update the grouping on existing elements.

(almost a) work around: Move existing elements to a diagram.
However when there are hundreds of elements than Sparx freezes when dragging the elements on the diagram. Equivalent to Sparx CRASHING.

This bug makes Sparx EA look like a toy. Users are very disappointed.

This is our third request since 2016 for a descent work around (program, script.. whatever).


9
Bugs and Issues / Virtual Connectors do not execute Shape Scripts
« on: December 13, 2017, 03:28:10 am »
When we create a virtual connector, only the original item is displayed as requested by the shape script.

The ghost is ill-mannered as it simply ignores the shape script. I mean the ghost doesn't bother and it shows as a UML element.

Is there a trick for taming the ghost in the shape script or is it simply a bug?

If it is a bug (ghosts can also have bugs), will this be fixed for version 14?

Cheers,
Alain

10
Users very often have to maintain several diagrams that share common elements including their layout.

When we drag a source diagram 1 into target diagrams 2 and 3, one additional option (besides "diagram frame" etc...) would be to
- drop the laid out source diagram objects from diagram 1 into the target diagrams 2 and 3 (not a picture)
- keep the target diagram layout synchronized with the source diagram layout
That way, in each target diagram 2 and 3 we can re-use the layout of the source diagram 1 and add specific elements and connectors.

In other words, in each specific target diagram, we should be able to re-use a source diagram as a "dynamic layer of connectable diagram objects".

Example 1:
- Shared/Common part of the diagram:  Business Function Landscape
- Specific diagrams: Information owned by functions, Organizations performing functions, Applications supporting functions, Domain architect in charge of function, functional heat map, roles that belong to functions...

Example 2:
- Shared/Common part of the diagram:  Organization structure
- Specific diagrams: Organization Managers, Organization Locations, Organization-owned Applications


11
Sparx shines thanks to its UML implementation. But the focus on UML and low levels abstractions is also an impediment.

We should be able to create languages without any UML profile.
The user experience, the architecture and the implementation of Sparx might be simplified if languages could be defined independently of UML.

We should be able to create elements, connectors, properties, shapes, metamodels and other consistency rules from scratch.

The language author would create
- Element and connector types (no stereotype)
- Properties (not tag)
- User-defined shapes (not derived from any UML type)
- Properties validation rules (including but not limited to enumerations)
- A metamodel (defining possible combinations of elements and connectors)

The end user of the language would enjoy a simplified user experience user i.e.
- Element and connectors types (no stereotype)
- Properties (not tag) which are editable either in shapes, in property windows and or in catalog sheets (result sets)
- Automatic validation of connectors based on the metamodel, and of properties based on properties validation rules

UML (and legacy UML profiles) would be languages as any other.

12
When we lock a package, and the locking gets propagated into the elements in the package, other individuals or groups shouldn’t be able to change or delete connectors connecting elements in the locked package.

In other word, when an element is locked, its connectors should be implicitly locked as well.

Note that this could also be an option, in which case you need different types of locking.
So this is for you an opportunity to use the field LockType in the table t_seclocks.
Today this field is always empty.

Alain

13
Automation Interface, Add-Ins and Tools / Paste diagram objects by code
« on: September 18, 2017, 07:46:57 pm »
Selecting diagram objects seems to be OK: The Diagram class has a collection property called SelectedObjects that we can read and write to.

But I can't find a way to paste the selected data objects into another diagram (by code).

Any idea?

14
When we mix different types of element... in some cases (it seems random), we are no longer able to move SOME elements (not all of them) up and down by using CTRL-Up or CTRL-DOWN or by using the menu option "Move up" or "Move down" on the element.
In addition, the option 'Content / Reset Sort Order" does not sort these elements.

Any idea how to resolve this?

Thank you in advance,
Alain

15
Automation Interface, Add-Ins and Tools / Protecting some MDG
« on: March 09, 2017, 08:47:32 pm »
If we want to make a product out of an MDG, what is the best way to protect it from reverse engineering?
- MDG as part of the database?
- MDG as part of an add-on?
- ...?
Thank you in advance
A.

Pages: [1] 2 3