Microblog port to Akonadi pushed into a branch

[Marco Martin]

On Monday 29 October 2012, Martin Klapetek wrote:
> 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 :)

awesome sauce

> > 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...
> 

well, from a design perspective having a regular grid may have its advantages

another possibility is to play with canFetchMore of the model, so the data 
will be taken in chunks.
in that case tough, you'll see the scrollbar that goes to the end, then new 
data fetched, then the scrollbar gets smaller. is a behavior that is becoming 
common on websites tough.
in this case just few delegates will be created at the beginning but then 
would start to pile up almost forever, so solves only half of the problem

Cheers,
Marco Martin