[Kde-imaging] [Bug 199848] turn facebook import/export plugin into a virtual folder ressource

Johannes Wienke languitar at semipol.de
Thu Oct 1 15:24:23 CEST 2009


https://bugs.kde.org/show_bug.cgi?id=199848


Johannes Wienke <languitar at semipol.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |languitar at semipol.de




--- Comment #9 from Johannes Wienke <languitar semipol de>  2009-10-01 15:24:17 ---
This looks cool!

But I think if we do it like this for facebook, we should do it for all export
tools. That's one thing I already noticed while browsing through the code of
the export / import plugins: there is a high potential for some generalization
in the gui work that's currently not used and that is - to my mind - something
that's very important for users. Because having the same feeling for all export
tools makes using them much easier.

My suggestion would be to create a base class (eg. AbstractExportTool) for all
export dialogs that creates the basic GUI with the image list (or whatever
solution is preferred) and all properties that can generalized over all export
services (eg. resizing before uploading). For all capabilities that are unique
to some services I would suggest a kind of strategy pattern. Every subclass for
a special service like flickr implements a template method that returns a list
of capabilites. These capabilities consist of two parts: 1. a QWidget that is
filled into the gui by the AbstractExportTool class and 2. a handler class.
This handler processes the options provided by the QWidget. With this structure
the Capability classes can still be used by different services without the need
to reimplement them (at least the gui, eg. most of the services provide a way
to create albums. The gui can be reused for a convieniet user experience while
the handler code maybe needs to be reimplemented).

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the Kde-imaging mailing list