Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create draw.io diagram libraries #5

Open
Dr-Electron opened this issue Jun 21, 2022 · 6 comments
Open

Create draw.io diagram libraries #5

Dr-Electron opened this issue Jun 21, 2022 · 6 comments
Assignees

Comments

@Dr-Electron
Copy link
Member

We should create different diagram libraries so that most of the images In the build section can easily be updated.

Maybe the structure could be something like:

diagram-libraries/
├── README.md
├── flowchart.xml
└── misc.xml
@JSto91
Copy link
Collaborator

JSto91 commented Jun 23, 2022

yes - btw it's possible to load multiple libraries in draw.io.
So you would have multiple sections on the left menu to open and select elements. That would kinda fix the issue with subgroups.

I still think we should maybe separate identity - just to keep it clean.
diagram-libraries/
├── README.md
├──identity.xml #everything BPMN 2.0 Specification
├── flowchart.xml #Container/Arrows/Addresses etc
├── iota-libraries-nodes.xml #Icons etc
└── misc.xml #General elements like VM etc?

wdyt?

@Dr-Electron
Copy link
Member Author

Sounds good. Still not sure if we should separate identity, but let's try

@JSto91
Copy link
Collaborator

JSto91 commented Jun 24, 2022

Sounds good. Still not sure if we should separate identity, but let's try

Well we don't need to but I can already imagine the identity team searching through the flowchart library with some elements in it that have nothing to do with their specification/standard, ending in ragequit :trollface:

@JSto91 JSto91 moved this from Todo to In Progress in Wiki Overview Jun 25, 2022
@Dr-Electron
Copy link
Member Author

But don't you think all IF projects will/should use the same spec/standard?
Everything we need that isn't in this spec/standard should be part of the misc or another group

@JSto91
Copy link
Collaborator

JSto91 commented Jun 29, 2022

They should - but i don't know if every element definition for identity is the same as for smart contracts for example.
If it is then we can go with it.
If it isn't and they want to go that way they need to work with the specs (500+ pages).

If that isn't going to be the case - but will for example be in a year - we can just rename the identity lib to flowchart and delete/move the other libs into misc :)

@Dr-Electron
Copy link
Member Author

Ok. Sounds good to me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

2 participants