1
General Board / Re: HTML report filter
« on: May 30, 2021, 02:44:55 am »
As Geert says, you cannot filter the HTML output other than through packages. I have used two workarounds to get round this.
Option 1: Add Exception Text
Add some exception text, so the page doesn't look broken or out-of-date. As an example, see: http://www.kybernetica.co.uk/KyberneticaSparx/index.htm?guid={7746EFCB-934E-46b6-ADB6-018C10BAB72C}
The exception text is in dark red and says "There is no description for this element". Obviously, you can use any text you like – or even reference a graphic file or write-in a feedback form or some other feature.
This option depends on use of Jquery and custom CSS code – if you want to pursue this, I can post sample some code that works (this code is split between three Web Template Fragments).
Option 2: Move elements to a non-published package
If you want to exclude a specific element – or collection of elements – then you will need to put them in a separate package that will not be published. For example, in the example below, I have excluded all "Model View" elements. On the diagram, they are now unclickable: http://www.kybernetica.co.uk/KyberneticaSparx/index.htm?guid={CE46B582-5727-45aa-BEB5-125B1D77EF0C}
The same principle could be applied for individual elements, though that of course requires an additional maintenance overhead (e.g. a pre-publication routine whereby you (a) use a SQL query to find all elements that have a description AND are outside the publication package; then, (b) move them to the publication package).
Notes
Option 1: Add Exception Text
Add some exception text, so the page doesn't look broken or out-of-date. As an example, see: http://www.kybernetica.co.uk/KyberneticaSparx/index.htm?guid={7746EFCB-934E-46b6-ADB6-018C10BAB72C}
The exception text is in dark red and says "There is no description for this element". Obviously, you can use any text you like – or even reference a graphic file or write-in a feedback form or some other feature.
This option depends on use of Jquery and custom CSS code – if you want to pursue this, I can post sample some code that works (this code is split between three Web Template Fragments).
Option 2: Move elements to a non-published package
If you want to exclude a specific element – or collection of elements – then you will need to put them in a separate package that will not be published. For example, in the example below, I have excluded all "Model View" elements. On the diagram, they are now unclickable: http://www.kybernetica.co.uk/KyberneticaSparx/index.htm?guid={CE46B582-5727-45aa-BEB5-125B1D77EF0C}
The same principle could be applied for individual elements, though that of course requires an additional maintenance overhead (e.g. a pre-publication routine whereby you (a) use a SQL query to find all elements that have a description AND are outside the publication package; then, (b) move them to the publication package).
Notes
- The links above are to my own Sparx demo model (which models what I think is necessary - both in terms of functionality and competencies - for any "enterprise class" modelling tool and how Sparx potentially realizes these requirements). As you can see, this web output uses extensive customization: you can reverse engineer as you see fit, but clearly, it won't be possible to post here everything that is going on (the actual code used for example is tightly-coupled with the underlying meta-model, which essentially defines the information architecture of the web output).
- And finally, you cannot even hope to make Sparx's utterly primitive and amateurish "dog's dinner" of a design credible and useful without resorting to Jquery – see https://jquery.com/ and for specific coding problems, stackoverflow is your best friend.