customizable icon set #32
Comments
This was referenced Dec 11, 2018
Closed
AlexanderZellober
added a commit
that referenced
this issue
Apr 11, 2019
AlexanderZellober
added a commit
that referenced
this issue
Apr 12, 2019
AlexanderZellober
added a commit
that referenced
this issue
Apr 14, 2019
…ist is empty renames files to more approriate names renames Registryto Dictionary where appropriate changes look of lower button row in configurationDialog adds Polyfill for tests
AlexanderZellober
added a commit
that referenced
this issue
Apr 15, 2019
…with the start-replay button #32
AlexanderZellober
added a commit
that referenced
this issue
Apr 16, 2019
AlexanderZellober
added a commit
that referenced
this issue
Apr 18, 2019
…ons and works with custom-icons #32
AlexanderZellober
added a commit
that referenced
this issue
Apr 18, 2019
…erent from the current domain #32
AlexanderZellober
added a commit
that referenced
this issue
Apr 25, 2019
AlexanderZellober
added a commit
that referenced
this issue
Apr 25, 2019
enables drag and drop between selected actor- and workObjectList
AlexanderZellober
added a commit
that referenced
this issue
May 31, 2019
dirtyFlag is now set when deleting objects or changing title / description #51 title will now be shown correctly in header-dialog title and description in header will now be upadtes correctly, if there was a previous title and a new domainStory is imported the name of the icon-customizationDomain is now saved in the config-file and in the exported domainStories Uploading a .dst file which has a domain specified now clears the previous domain and loads the new one. #32 fixes dialog for unsaved changes from sometimes firing when no changes were made #54
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
One of the ideas of domain storytelling's pictographic language is to use domain-specific icon. But so far, only a fixed icon set is available in the modeler.
Describe the solution you'd like
Ideally, the modeler provides a configurable icon set. The modeler ships with a few dozen icons. Which are available in the palette and context pad should be configurable by the user, without the need to deploy a new version of the modeler.
If even the new, configurable icon set does not meet the user's reqirements, it should be easy for programmers to add additional icons. That would require to download the source code, program some javascript and CSS and deploy the modeler.
To ensure compatibility between modeler instances with different icon sets, the current icon set should be used as a fallback. E.g. unknown actor icons could be mapped to "person" actors.
Describe alternatives you've considered
Additional context
We should keep the base icon set as is, allowing end users to grow it if needed. That will likely result in scenarios where the palette becomes too big or unmanageable, but I think that might be a desirable problem to have and one to solve once we have it.
The text was updated successfully, but these errors were encountered: