On Sun, Aug 29, 2010 at 8:07 AM, Matt Rogers <ma...@kde.org> wrote:
> On Wed, Aug 25, 2010 at 10:04 AM, Amir Pakdel <pak...@gmail.com> wrote:
> > Hi
> >
> > I was reading the source code in order to get familiar with its structure
> > and find out how should I start implementing Nepomuk integration. I found
> > out that NoteEditor::autoSave and BasketView::save are using
> > BasketView::saveToFile; and BasketView::saveToFile itself uses
> > BasketView::safelySaveToFile for the actual work. Am I right?
>
> That sounds about right, based on the last time that I looked at that
> particular piece of code.
>
>
> > I would like to know you opinion about where the code for insertion of
> > metadata into Nepomuk should be added:
> > 1. Inside BasketView::saveToFile or BasketView::save
> > 2. In another separate function: something like
> > BasketView::updateNepomukMetadata which would be called after every
> > BasketView::save or BasketView::saveToFile
> >
> >
> >
> > Thanks
> >
> > Amir
> >
> >
>
> I like option 2, but I would call updateNepomukMetadata inside of
> BasketView::saveToFile instead, so it's seamless to the rest of the
> current API.
>
Good point.
Right now, I am trying to get the Nepomuk plugin of KRunner (KDE Run
Command) to open baskets (which I have added manually to Nepomuk) using the
Basket Note Pads. Afterwards, I would start coding a clean separate function
called updateNepomukMetadata.
> Thanks
> --
> Matt
>
Thanks,
Amir
------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users
worldwide. Take advantage of special opportunities to increase revenue and
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Basket-devel mailing list
Basket-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/basket-devel
