[rekonq] Re : One process per tab: TODO list for 0.3

Ivan Čukić ivan.cukic at gmail.com
Sat Aug 15 20:57:17 CEST 2009


> On my repository I created a branch isolateWebView.

1. Don't use QProcess, use KRun::runCommand (and don't use the relative path 
"./rekonqtab"
2. rekonqtab doesn't get installed

> But there is no communication between rekonq and rekonqtab. I don't have
> the knowledge to create the dbus interface. So, I turn to you to help me
> to continue this work.
There are three approaches:
 - the main application is d-bus /server/* and tabs are clients
 - the main application is d-bus client and tabs are /servers/
 - both are at the same time servers and clients

The first thing to do is to see what messages (methods and signals) you need 
to pass from one to another.

For example, the tab needs to notify the main application about the progress, 
statusbar text etc. The application needs to request reloading, stopping etc.

When you have all the messages, you can see what of the above can be the 
solution. The only way to send a /message/ from server to client is by using 
signals.

I've attached the Webbie code (the XEmbed demo browser) so that you can see 
how it is done.

The thing that made Webbie's D-Bus interface much smaller than it will be in 
rekonq is the fact that the tab handles all browsing stuff - it contains back 
and forward buttons etc.

Cheerio

* the term /server/ or /service/ is very unfortunate because those are already 
terms used by d-bus for different things, but I hope you get the meaning 
behind it in this case.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Webbie.tar.bz2
Type: application/x-bzip-compressed-tar
Size: 249730 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/rekonq/attachments/20090815/ef1ef489/attachment-0001.tbz2 


More information about the rekonq mailing list