And here we go with another image!
Ok, as an instrument for making everything a little more clear, I made a class diagram (yes, UML…), which shows a high level view of how the dialog system may show up in a few weeks.
Now, I use UML in the Fowler’s way, so the final system may look completely different from this one, or the diagram may change accordingly, mainly because of two things:
- this is not completely integrated with the Qt/KDE dialog classes, essentially because I’d like to have some backend system working before planning that part deep;
- the SuggestionProvider and the integration with the Annotation Plugin already present in playground is still a work in progress: in particular, I still think that giving an abstract class to be subclassed by KDE developers is better than a pure function to be called, but anyway I may change my idea on that, we’ll see.
So, expect something to come up (soon?) under playground/base/nepomuk-kde/smartsave (nice name, uh?), waiting for the official GSoC start in 9 days…