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

List:       kde-commits
Subject:    kdenonbeta/kdmthemes (silent)
From:       Enrico Ros <rosenric () dei ! unipd ! it>
Date:       2004-04-05 22:18:18
Message-ID: 20040405221818.1C2E899F4 () office ! kde ! org
[Download RAW message or body]

CVS commit by eros: 

CVS_SILENT Added a little architectural note that will be useful for
developers. Thanks to uga.


  M +22 -8     README   1.2


--- kdenonbeta/kdmthemes/README  #1.1:1.2
@@ -15,10 +15,24 @@
  - Start kdmthemes, the theme should be displayed
 
-TODO:
-
- - Fix the layout for box elements. It's similar to QVBox/QHbox, but custom made.
- - SVG support
-
-then integrate it into kdm and kdm's contol centre module sometime before KDE 4
-
-
+Architecture: (some chat lines with uga)
+<uga> uhm.. the architecture will have to wait. Sorry, but I have no much
+      time during the week for that... I did some file before, but it's too
+      much changed since then...
+<uga> The basic Idea is simple
+<uga> there's only one visible widget: KdmTHemer
+<uga> which arranges the widgets in position, and calls every widget to draw
+      themselves when needed
+<uga> all widgets are invisible, so Qt won't care about painting those
+<uga> so basically we paint on KdmThemer. this helps to implement the
+      translucency of boxes and highlighting (blending)
+<eros> so..there is no hieracy in widgets? And the widget tree is hold inside
+      the main widget?
+<eros> why don't you do real widgets placement using qt's hieracy?
+<uga> because Qt doesn't layout widgets when they're invisible
+<uga> so it's not of much use
+<uga> we needed to implement layouting ourselves
+<uga> which has delayed the project a lot
+<uga> eros: and they need to be invisible
+<uga> Qt can't blend one translucent widget over another one
+<uga> so we had to paint it all in a single widget (KdmThemer)
+<uga> which is like a Canvas


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