Syvo3

A brief note, just because lots of things changed during this weekend (this long weekend, two days of holidays here in Italy): I have dropped the metadata model that I started last week, because the annotation plugin already had one, and a couple of hours ago I also dropped the SuggestionProvider plugin system.

Recent annotations will be implemented through an AnnotationPlugin subclass, and related annotations will be provided with an utility class, probably later on.

Still working on save dialog UI, though, and I’m trying to add views in a KFileDialog subclass: task which seems not so easy (any advice?), some functioning code will shortly come, I promise!

The first official SoC week is gone! A bit of a hard work, but good results obtained…

With the last smartsave commit, all the stubs are done and real code is coming out: all the base classes are being populated, and in a few days some UI may come up.

I’m especially working in the save part of the system, still from the backend point of view, with models and signals that come and go through the classes (test 2 already shows something of this), updating views when new annotations come up. A hard link to the annotation framework (in playground) is coming out, and probably one of the two exposed classes will be collapsed to that framework, when my experiments and my messing up the API will stabilize a little.

The most difficult part, I must admit, has been to adapt to Qt frameworks (signal-slot, model-view, d-pointers), which are pretty different from my last C++ works or from the Java approach, so a big thank goes to Sebastian Trueg for his advices on them.

Besides, I hope not to flame in any way, but I really have some difficulties in understanding why the d-pointer idea… for example, I see the model-view as some kind of a derivative of MVC, and signal-slot as an alternative to a callback system; I see why calling getter methods with the variable name (C# does something similar), but why can’t I put my private members directly in the class? I read about the binary compatibility, but those are still private members, so the outside world cannot see them. So why complicate the classes structure with all those private classes with public members?

So, C++/Qt masters, I’d really like to read your opinion on that, not for flaming (I repeat), just for deeply understanding this way of programming 🙂

And, stay tuned for UI updates in the next few days!

This week has seen my first (and second, by the way) commit into KDE SVN! Another milestone reached 🙂

There are mostly stubs into the new smartsave/ folder, and a bit of documentation for the interfaces; there also is a test program, taken from one of Techbase tutorials: a very simple notepad, which will be the very first application to use the new dialog system, and it will be useful for trying functionalities.

No, don’t try it now: it just falls back to the standard KFileDialog class; let me write some real implementations before toying with it!

For now, the idea is to have an abstract class, Nepomuk::SuggestionProvider, which may be subclassed by any application (there’s, for now, just a method to be implemented), and an instance of it will be passed to the dialog UI for getting personalized suggestions, in form of Nepomuk::Annotation objects. These objects need to be created by the developer in the way he wants, by hand or using any Nepomuk::AnnotationPlugin, but things may change later on.

The second important class is Nepomuk::KSmartDialog (I called it ‘K’ just to mimic KFileDialog, but if you don’t like it, I can drop that ‘K’), which is a subclass of the actual file dialog, and which will provide a couple of static methods for getting or setting document metadata; of course, each of these methods will use the SuggestionProvider subclass as stated before.

These are the two important exported classes, at least today; expect some working code in the next days!

Oh, by the way: tomorrow is the official GSoC start! Godspeed to any GSoCer around PlanetKDE!

System UML 2

I promise: this will be the last image!

The next post will discuss a bit about real code (which is coming, I just have to check the very first compilation cycle before throwing a new folder into playground); for now, here is an update of the previous UML diagram: it’s a little bit more into the “real virtual world” of KDE libraries, even if something could be changed any time.

I’m studying the model-view framework from Qt, and a few classes are now related to the abstractions offered by that system; as soon as the structure will be clear, I will write about it.

Next week, waiting for the GSoC official start (on saturday the 23rd), the first classes will come up and I will talk about something a little less into the air and a little more into the bits.