archi-contribs / specialization-plugin

Plugin for Archi to specialize concepts (figure, icon...)
Other
29 stars 2 forks source link

Inconsistency in plugin installation #50

Closed evlibra closed 3 years ago

evlibra commented 3 years ago

The wiki documentation refers to using .jar, but the new versions (master branch) contains .arhiplugin only (it's renaming to zip and unzipping does not work). Or that is better to not touch latest, and we shall keep using what is in branch: 1.0.0.11 vs 1.0.0.12 ?

By the way, judging from the file-extension, are new versions assumed to be installed from the Help->Manage Plugins? -At the moment it is not recognized as a plugin from there.

herve91 commented 3 years ago

I know my wiki is not up to date, I lack time to update it but the file can be imported into Archi using Help->Manage Plugins.

You say it is not recognised as a plugin here, have you got an error message ?

evlibra commented 3 years ago

yes, it is not recognized. image

herve91 commented 3 years ago

It works on my Archi.

How did you download the file ? Please try to download it again. It should be 1 847 186 bytes.

Should you prefer, archiplugin files are ZIP files, so you may unzip it and you'll find the JAR file inside. But the Help->Manage Plugins is easier, that's why I now deliver the plugin under this format.

evlibra commented 3 years ago

You're right. Thanks! Initially I did download by clicking on file and clicking download (the same effect was from right-click save-as), the filesize was 101 Kb. image

Resolved by "Download Zip" image

evlibra commented 3 years ago

By the way, is 2.0.0.alpha2 worth/risky trying? What are the major changes / release notes ? org.archicontribs.specialization_2.0.0.alpha2.archiplugin

Thanks for this great plugin!

herve91 commented 3 years ago

You may try the version 2 without any risk on your model. The difference is that the plugin v2 allows to create a kind of template for components (label, icon, color, ...) and then to apply this template to Archimate Concepts. I stopped developing it because I'm obliged to store the images in a dedicated view that is visible in the model and the reports ... which is very bad.

but I'm not sure it is worth it ...

The plugin version 1 stores the label in the objects properties which implies that, as the properties are linked to the Archimate concept, so the label is applied in ALL views.

New version of Archi implements a label functionality but stores its information in new attributes (that did not exist when I developed the plugin) that are linked to the graphical objects rather than the Archimate concepts. So the labels are different across views.

Please be informed that Archi devs are working to add the ability to natively change the icons as well.

So from my point of view, my plugin is already deprecated from a label replacement point of view and will be quickly deprecated as well from an icon replacement point of view. I do not know if they will implement the drill down part of the plugin.