ariel-bentu / tam-drawio Goto Github PK

I am a new user of draw.io. After following the installation steps (added at #11), I am still not sure whether the plugin works.

After installation, the dialog for new diagrams does not show anything related to "Block Diagrams"

However, the plugin is listed in "Plugins"

The current README.md guides well through the installation steps. I wish it had a "checkup" to show whether the plugin was installed well...

Hi folks,

I am using this plugin with Draw.io desktop (19.0.1) on MacOS.
I noticed a visual glitch with the connectors (communication channels and read/write requests): After moving connectors, they are still shown at their initial positions, but in blue.
I think the attached image explained it better:

.

In the TAM / Block section, I can find request-response channels but I am missing bi-directional (no R ▶) and unidirectional (→○→) channels.

Hello Ariel, I could not find a License file on this repo, would you consider adding one?

Best Regards,
Guilherme.

I have installed the latest tam diagram plugin in Drawio. I am using version 19.0.3 which has plugins disabled by default and I have managed to enable the TAM plugin. Now I see the elements but when I try to add an element to the canvas I get the same error for each element:

When I close the dialog everything is fine, but still it happens each time I add

When zooming in, the stroke gets doubled and scaled

It seems that there is a syntax error in the tam-drawio.js plugin for the desktop app. When restarting the app with the plugin added, one what receive the following console log.

Message: Uncaught SyntaxError: Invalid or unexpected token 
URL: draw.io/plugins/tam-drawio.js
Line: 1 
Column: 13884 
Error: SyntaxError: Invalid or unexpected token

Hi!

It seems like the latest release of draw.io desktop (20.3.0) disabled support for the plugins array of the configuration object

Here is how i got it the plugin working:

1. Launch with plugin support enabled (/path/to/draw.io --enable-plugins)
2. Add tam-plugin via Extras -> Plugins... -> Add l External Plugins
3. Relaunch (with --enable-plugins)

Hi,

Access arcs should use rounded corners as explained at http://www.fmc-modeling.org/visualization_guidelines. Currently, only channels have rounded corners.

(By the way, the documentation uses "using-edge" do describe channels. Is there a reason for that? In TAM, the edges between agents are called channels.

Best regards,
Martin