This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Integrate KHTML *properly*

Page 2 of 2 (17 posts)

Previous • 1, 2

3

Votes
17
14
Tags: khtml, e-mail, contacts, chat khtml, e-mail, contacts, chat khtml, e-mail, contacts, chat
(comma "," separated)
User avatar
Madman
Registered Member
Posts
593
Karma
1
OS

Integrate KHTML *properly*

Tue May 11, 2010 4:43 pm
airdrik wrote:KHTML would be the component that would be recognizing if you navigate to a web mail site and display the Open in Kmail bar.
Doing so in KHTML has advantages and disadvantages; namely: it will work across applications that use KHTML for rendering pages, but OTOH most of the other applications that use KHTML for rendering either won't be used for going to gmail, or wouldn't be appropriate locations to have such a notification. IMO, it is probably better to implement in Konqueror (or whatever other browser you would use to navigate to your web mail site) than KHTML.


Wouldn't we have to tie into KHTML in order to get the form information to use for creating Akonadi resources?

Madman, proud to be a member of KDE forums since 2008-Oct.
airdrik
Registered Member
Posts
1854
Karma
5
OS

Integrate KHTML *properly*

Wed May 12, 2010 3:37 pm
Madman wrote:
Wouldn't we have to tie into KHTML in order to get the form information to use for creating Akonadi resources?


I'm not sure - I'm not a KDE developer, but the In Konqueror vs. In KHTML issue seems mainly an implementation detail that is best decided by the developers who are familiar with how those components work together.
I would assume that as a browser using KHTML for rendering, Konqueror should be able to get the form information (from KHTML) to send to Akonadi.

airdrik, proud to be a member of KDE forums since 2008-Dec.

Page 2 of 2 (17 posts)

Previous • 1, 2

Bookmarks


Who is online

Registered users: Bing [Bot], Google [Bot], Sogou [Bot]