[Marble-devel] Network handling

[Pino Toscano]

Alle sabato 30 agosto 2008, tackat at t-online.de ha scritto:
> > Second step would be creating a plugin structure, and decouple HttpJob in
> > two: the abstract HttpJob and the QHttpHttpJob plugin (of course, still
> > making things working after this).
> > Then, it comes writing plugins for QNetworkAccessManager and KIO.
>
> For that part you'd also need to take the proxy setting into account
> that is
> currently located in the settings dialog. I guess the job-plugin would
> then
> offer a property which tells whether displaying the proxy setting inside
> the
> settings dialog is needed, right?

Correct, and about that I just had an idea.
Something like this:

| class AbstractProxyWidget : public QWidget
| {
|   virtual QNetworkProxy settings() const = 0;
|   virtual void setSettings(QNetworkProxy np) = 0;
| };

and extending the network plugin interface with:

|   virtual QNetworkProxy settings() const = 0;
|   virtual void setSettings(QNetworkProxy np) = 0;
|   AbstractProxyWidget *proxyWidget() const = 0;

This way the plugin can optionally return its proxy configuration widget (if 
supported), and provide the current configuration, and have a new one 
applied.

-- 
Pino Toscano
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/marble-devel/attachments/20080831/7cf98675/attachment.sig