[prev in list] [next in list] [prev in thread] [next in thread] 

List:       raptor
Subject:    [Raptor-Menu] New Raptor Design
From:       Dario Freddi <drf54321 () gmail ! com>
Date:       2008-09-10 18:44:57
Message-ID: 200809102044.57716.drf54321 () gmail ! com
[Download RAW message or body]

Hey people,
I don't want to write the book, so I'll be quick as possible :D

The best way to go, in our opinion, is Plasma. And this means that Raptor will 
be nothing but a popup applet, interacting with a dataengine. The dataengine 
will mostly hold a model that the applet will use for generating the view.

Let's talk about tom quickly. Me and riccardo discussed right today that every 
bit we need for raptor has already been implemented in KDE. So, we think the 
best solution for TOM would be using nepomuk based storage, by creating a new 
ontology. This would grant us an optimized database we can use to update our 
model.

Riccardo has some other ideas about using some KRunners that I'll let him 
explain.

So in the end I think we should keep the code simple, we don't need plugins or 
anything, that would just add a whole level of complexity without giving any 
real advantage. I'd aim for code simplicity that would let us maintain it more 
easily.

I personally think this kind of approach (yes, it's just a very very short 
decscription) it's the best one, though I'd like to hear some other voices

Cheers
Dario
_______________________________________________
Raptor mailing list
Raptor@kde.org
https://mail.kde.org/mailman/listinfo/raptor
[prev in list] [next in list] [prev in thread] [next in thread]