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

List:       kde-commits
Subject:    kdelibs
From:       Matt Rogers <mattr () kde ! org>
Date:       2005-02-14 3:52:36
Message-ID: 20050214035236.0D8AE1BAEF () office ! kde ! org
[Download RAW message or body]

CVS commit by mattr: 

Add an item about KDEDesktopMimeType::pixmap and the parameteres to it.
Fix some typos and limit line length to about 110 chars which is what the
rest of the file seems to do.


  M +14 -6     TODO   1.54
  M +3 -1      kdecore/kdebug.areas   1.329


--- kdelibs/TODO  #1.53:1.54
@@ -7,7 +7,10 @@
 
 - Change all FooPrivate *d; -> Private * const d; and place initialization
-in constructor (for classes that would benefit this).  To help catch silly \
mistakes since d should never change. Also concider changing to use \
KStaticDeleter to help prvent mistakes where developers forget to delete \
the pointer. Maybe make use of Qt4 helper Macros?  +  in the constructor \
(for classes that would benefit from this).  To help catch silly +  \
mistakes since d should never change. Also consider changing to use \
KStaticDeleter to +  help prevent mistakes where developers forget to \
delete the pointer. Maybe make use of +  Qt4 helper macros? 
 
-- Move all utility functions away from KApplication. TDB: Make \
KApplication  +- Move all utility functions away from KApplication. TBD: \
Make KApplication   a very thin wrapper around QApplication. Ideally, \
KApplication should go   away completely. The kapp pointer references \
everywhere must die. Find a  @@ -23,5 +26,5 @@
 
 - Remove all KSocket, KServerSocket, KSocks and KExtendedSocket references
-  throughout KDE in favour of KNetwork's socket implementations.
+  throughout KDE in favor of KNetwork's socket implementations.
   Also, revise the namespace usage.
         thiago.macieira@kdemail.net
@@ -103,5 +106,5 @@
   Use KConfigXT instead! /FransE
 
-- Is it really necessary to bother people using the KCM API:s with \
withFallback? I have +- Is it really necessary to bother people using the \
KCM APIs with withFallback? I have  never heard of it failing and when \
would you not like to have that fallback? I think  a default of 'true' \
would be fine(and remove the argument in the APIs). @@ -183,6 +186,7 @@
 - Merge KPIM::ClickLineEdit with KLineEdit
 
-- Merge all K*Label classes into one that offers all the features such as \
ellipsis (this time for center, middle and right in order to allow for \
                sqeezing the text), 
-links and selectable text with a consistant API.
+- Merge all K*Label classes into one that offers all the features such as \
ellipsis (this time for  +  center, middle and right in order to allow for \
sqeezing the text), links and selectable text  +  with a consistant API.
 
 - Make sure all GUI classes adopt well to palette changes.
@@ -207,2 +211,6 @@
 - Refactor the kio/bookmarks code so we don't need to use the static \
d-pointer trick anymore.  
+- Rename the parameters to KDEDesktopMimeType::pixmap so that they use \
meaningful names rather than +  just a, b, c, and d. Probably not something \
that has to wait for KDE 4, but seems like a good idea +  to have here for \
later doing. +

--- kdelibs/kdecore/kdebug.areas  #1.328:1.329
@@ -403,5 +403,5 @@
 14304       kopete (importer)
 14305       kopete (motionautoaway)
-14306       kopete (msginfo)
+14306       kopete (smpppdcs)
 14307       kopete (nowlistening)
 14308       kopete (translator)
@@ -568,2 +568,4 @@
 
 
+300000       kmdi - excessive
+


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