quicksilver-project / quicksilver Goto Github PK

Quicksilver will use UML2 for diagramming. It must generate output to popular formats like EMF to export. Adding bitmaps and generating diagrams from scratch is in the roadmap. All functionality related to external tools will be a plugin and not part of quicksilver package. For future reference, please do not submit issues related to proprietary diagramming frameworks.

With some lessons learned with the XMI component, the module should best be written with only the specification document as a blueprint. This will enable CMOF/EMOF support. Development will start after XMI support is acceptable.

The project that influenced me to start this project was written in Java targeted at OpenJDK version 1.8. I propose we should be able to profile applications written in Python 2, and 3 and OpenJDK 1.7, and 1.8 as a proof of concept. They will be primitive to avoid bias of software development opinions. Future development of context-based models based on programming language will not be part of the Quicksilver package and utilized in the form of a plugin. For future reference, please do not submit issues related to proprietary languages/frameworks, e.g. Costs money to obtain or is only distributed in a binary format.

Main reason I started making this, to reduce time crawling though giant projects.

xmiparser1-5 looks abandoned and not as extensible as I'd like it to be. It needs to take account for vanilla OMG specifications and have ability to modify/extend beyond that specification to be a genuine 'agnostic' and reliable tool.
link to current development effort.
Will eventually be a submodule.

I will consider a CoC, this is a hobby project at heart so at time or writing see no point. Will be implemented after v0.2.0 passes acceptance testing.

Roadmap has a framework like Sphinx auto-generating developer documentation. Once v0.2.0 has passed acceptance testing I will publish package and the whole nine yards.

Will implement after v0.2.0 candidate passes acceptance.