[rekonq] An idea for GSoC

Andrea Diamantini adjam7 at gmail.com
Thu Apr 12 00:53:09 UTC 2012


On Monday 02 April 2012 10:54:13 Arjun Basu wrote:

Hello, 



I am Arjun, an undergraduate student from India. I know this is kind of late 
but I had an idea for GSoC 2012. 


The current private browsing currently saves the current session and starts a 
new session and when the private browsing is over , it restores the earlier 
session. I think this can be made of more utility to the user if he/she can 
create "private tabs" in that session only. Private browsing would be enabled 
on that tab only. If this feature is implemented then he would have all his 
open tabs and use the private browsing tab to access some sensitive 
information say in a multi user system where he doesn't want others to see his 
activities. This kind of private tab is available in opera.
I want to implement an app tab like utility present in chromium, firefox and 
opera in rekonq.


I don't know whether these ideas are enough for GSoC but I would like opinions 
on these ideas.



I have good knowledge of C++/Qt and Qt libraries like QGraphicsView. I have 
build rekonq from source and have read the source a bit



Hi Arjun,
I'm sorry to say your idea is very hard to be implemented actually. Let's 
start saying that the proposed implementation is surely the best and more used 
option to "private browse". Unfortunately, we have a big problem with this: 
cookies.
In fact, to really private browse the net we have to use session cookies 
(cookies lasting a browsing session). But KDE cookiejar has been implemented 
considering sessions as "apps sessions" (cookies are deleted when app has been 
closed) or worse as "kde sessions" (session cookies are deleted when the kde 
environment closes).
This block us to divide our tabs in two categories (the ones cleanly browsing 
and the one privately doing it).
kdewebkit maintainer probably just implemented a solution to this problem. 
Unfortunately this has been discarded as part of kdelibs due to its current 
freeze for kde5 development.
So, we are in the need to wait for kde5 release or, on the other hand, in the 
need to "reinvent the wheel" tracking two times the cookies to be deleted on 
tab close.
This is the motivation because I decided to leave private browsing "as is" in 
the current situation postponing further development to when I'll have a 
working solution to the problem.

About the "app tab" utility, I'm not sure I clearly understood what you'd like 
to implement exactly. Can you be a bit more precise with i.e. links, examples, 
images and so on?

Regards,

-- 
Andrea Diamantini, adjam
GPG Fingerprint: 57DE 8E32 7D1A 0E16 AA52 59D8 84F9 3ECD DBF9 730F

rekonq project
WEB: http://rekonq.kde.org
IRC: rekonq at freenode
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/rekonq/attachments/20120412/52154f60/attachment.html>


More information about the rekonq mailing list