Polishing store plugins

3 views
Skip to first unread message

Roberto Alsina

unread,
Feb 7, 2011, 4:08:32 PM2/7/11
to aranduka...@googlegroups.com
I have started work on branch issue47, caused of course by Issue 47 ;-)

Basically, I am doing UI work on the feedbooks store plugin to make it
work as well as possible.

I have adopted some of the CSS tricks from the guesser dialog (which
should probably be factored into a CSS stylesheet we provide to plugins
to use).

There are still lots of rough edges, but I think there is some serious
*easy* improvements that can be done.

Also: that plugin works in a different way from the others, in that it
uses Qt's infrastructure to load the network resources so they are
multithreaded, nonblocking and all kind of nice stuff.

That should also be adopted later by the other plugins (I'll do it!)

Finally, then I need to port all the other store plugins on the other
branches to work the same way.

I think this can take a week, but feel free to try the branch and give
me feedback!

Andrés Gattinoni

unread,
Feb 7, 2011, 4:33:51 PM2/7/11
to aranduka...@googlegroups.com
On Mon, Feb 7, 2011 at 6:08 PM, Roberto Alsina
<ral...@netmanagers.com.ar> wrote:
> I have started work on branch issue47, caused of course by Issue 47 ;-)

Cool.
Would it make sense to do something like what we did with guessers? I
mean moving the GUI to Aranduka's core and have the store plugins work
as a sort of proxy that translate generic operations into specific
calls to the different catalogs?

Roberto Alsina

unread,
Feb 7, 2011, 4:52:47 PM2/7/11
to aranduka...@googlegroups.com
Could be. At least for stores that follow the current pattern.

For others it may make more sense to just open the website on a HTML view.

Reply all
Reply to author
Forward
0 new messages