[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Re: containing plasmoid crashes
From:       "Aaron J. Seigo" <aseigo () kde ! org>
Date:       2009-07-26 19:24:23
Message-ID: 200907261324.23759.aseigo () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Sunday 26 July 2009, David Baron wrote:
> A similar problem has seemingly been solved, by .... Google. Since google's
> browser is opensource, one might take a look.

chrome solves a completely different problem. it displays a completely 
_different_ canvas (in this case, an html one) in each tab.

we are showing a single canvas with items in it.

the semi-equivalent in chrome would be to make each html element in the page 
it's own process and then have them all paint to the same canvas. it's still 
only semi-equivalent because, while there is javascript interaction, the html-
paint-to-canvas mechanism is a lot less complex than what QGraphicsView 
offers.

now, if you think that it's still a sane idea, go map out on paper all the 
details including data synchronization and managing painting from multiple 
process, remembering that the desktop is supposed to be very responsive and 
take as little cpu as possible.

the real solution is to use scripting languages and make sure the c++ plugins 
are absolutely solid.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Software

["signature.asc" (application/pgp-signature)]

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


[prev in list] [next in list] [prev in thread] [next in thread]