| Summary: | Evaluation of umbrello-ng2 effort | ||
|---|---|---|---|
| Product: | [Applications] umbrello | Reporter: | Ralf Habacker <ralf.habacker> |
| Component: | general | Assignee: | Umbrello Development Group <umbrello-devel> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | emmanuel.lepage |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Other | ||
| URL: | https://github.com/Elv13/Umbrello-ng2 | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: |
class diagram showing the mentioned model classes
Overview ofthe doc system |
||
|
Description
Ralf Habacker
2015-03-10 22:19:12 UTC
Emmanuel wrote in a private email: It basically create some Qt Models for each class diagram entity types then feed that to the UI. Created attachment 91525 [details]
class diagram showing the mentioned model classes
I will write a proper overview later today. There is a bunch of branches merged there. A very brief summary: * Add model for most Class and Entity list/tables you find in right click -> property of elements/classifiers * Add GUI to create class and entity diagram using the keyboard only, inspired by Oracle MySQL Workbench. It vastly improve usability * Make the project tree more contextual and pretty (unfinished, good enough for light use) * Fix a few usability issues in the import dialog (could be merged as is, it is an external contribution, I didn't wrote that) * Add a nice auto completion framework with XML file to load various documentation format (only Doxygen was fully implemented). It could be merged in KDE4, but the KTextEditor API changed in KF5. I will try to dig up the design documents, email and IRC conversations about this. @ralf: I will be on #umbrello (irc) tomorrow if you want to drop by to discuss this Created attachment 91530 [details]
Overview ofthe doc system
Here is the doc system explanation I wrote 4 years ago. The code may need to be modernized to the current code standards and may or may not have aged well.
If I recall, it was quite isolated, so it should not require much porting efforts beside the KTextEdit KF5 API changes for the documentation widget. QTextEdit + popup completion could also be used, but is less flexible than the KTextEdit one
|