Microblog port to Akonadi pushed into a branch

[Martin Klapetek]

On Mon, Oct 29, 2012 at 10:09 AM, Marco Martin <notmart at gmail.com> wrote:

> On Saturday 27 October 2012, Martin Klapetek wrote:
> > Hey all,
> >
> > I've just pushed my port of Microblog declarative plasmoid in a branch -
> > mklapetek/akonadi_port (kde:declarative-plasmoids). Setting this up needs
>
> sounds great :D
>
> i've still not checked at it, hope will find time those next days
>
> > try microblog too, you can get the new microblog resource from
> > kde:scratch/mklapetek/akonadi-microblog-ng - I'm not aiming to have the
> > microblog-ng resource in 4.10 though, but it might be finished by then
> and
> > just released separately.
>
> one thing i didn't understand from this email (din't look at the code) are
> both facebook and microblog migrated to proper models?
> (hope so ;)
>

Yes (the microblog resource works fine btw)! And not just that, you can put
ANY data in there as long as there is an Akonadi resource for it :) All you
have to do is store the data as SocialFeedItem with the proper mimetype and
you can have your upcoming calendar events there (careful here to not flood
it, the resource should be intelligent enough to show max 3-5 events as
they will be on top of the list because they are in the future), or emails,
or just about anything, it's generic enough :)


>
> > It's not yet finished, but it's fairly usable already. Here is what
> works:
> >  * listing stuff
> >     * facebook goes 3 days back (limit 400 posts) with number of likes
> and
> > comments
> >     * microblog for now goes 20 posts only
> >  * displaying facebook comments by clicking on the status (probably needs
> > better discoverability)
> >  * posting to networks
> >
> > Issues:
> >  * the scrollbar is baaad, unusable even (because of the non-uniform
> > delegate height), not sure what to do about it
>
> there is really not much that can be done.
> ie is really not possible to know how much the content will be long is the
> delegates are of different size.
>
> there are 2 pseudo solutions:
> 1) enlarging the offscreen cache of the listview high rnough to have all or
> almost all delegates created (but memory usage skyrockets)
> 2) have all delegates the same (eliding long text or somethig like that)
> and
> enlarge the delegate enough only when clicking on it
>

I was thinking about the 2nd, won't be as cool but oh well...


>
> >  * when using mouse wheel to scroll, sometimes it just stops scrolling
> and
> > you have to either scroll the wheel /really/ fast or drag the list, I'm
> > unsure why that happens, I suspect it's the item snapping to the list
> edge,
> > but I don't understand qml that deeply to see how it works exactly
>
> tried with different snap modes?
>

Yeah, only the NoSnap works fine :/


>
> >  * sometimes the plasmoid can get really really slow or even freeze when
> > scrolling very fast as it tries to fetch all the avatars and post images,
> > this might need some optimizations
>
> one thing that one should pay attention is to make delegates as little as
> possible so there isn't much to create. if more informations are needed,
> eventually create them dynamically later on mouse click or something like
> that
>

Right, for example facebook comments are displayed only after clicking the
status, so this can use the conditional loader.

Cheers
-- 
Martin Klapetek | KDE Developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20121029/60225047/attachment.html>