diff options
| author | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2013-01-26 13:17:21 -0600 |
|---|---|---|
| committer | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2013-01-26 13:17:21 -0600 |
| commit | dfe289850f068f19ba4a83ab4e7e22a7e09c13c9 (patch) | |
| tree | c297348a55df66c571de4525646e0b9762427353 /kutils/TODO | |
| parent | b7658a0d5eca24a9d37c6e04f88298ef02389db0 (diff) | |
| download | tdelibs-dfe289850f068f19ba4a83ab4e7e22a7e09c13c9.tar.gz tdelibs-dfe289850f068f19ba4a83ab4e7e22a7e09c13c9.zip | |
Rename a number of libraries and executables to avoid conflicts with KDE4
Diffstat (limited to 'kutils/TODO')
| -rw-r--r-- | kutils/TODO | 25 |
1 files changed, 0 insertions, 25 deletions
diff --git a/kutils/TODO b/kutils/TODO deleted file mode 100644 index 7d9f473ab..000000000 --- a/kutils/TODO +++ /dev/null @@ -1,25 +0,0 @@ - -This is a list of random changes to do in KDE 4 with the various KCM* classes. - -* TDECModuleinfo; - - Make it inherit KService; saves a lot of code, simplifies ctors/overloads in surrounding classes - - Implement docPath in KService - - Get rid of loadAll() and do lazy loading in each getter - -* Merge TDECModuleProxy and its DCOP Object class(MI) - -* Get rid of `QStringlist arguments` in TDECModule and all the helper classes(simplify API) - -* Move stuff to d pointers.. Too much hackish solutions otherwise - -* Get rid of bool fallback argument in helper classes(never fails, simplify API) - -* Re-implement the QScrollView(d->view) in TDECModuleProxy; the protection against violation of HIG-clause. It needs kde-core-devel approval. - -* The API in TDECModule, TDECModuleProxy, and the various desktop entries, concerning root loading are butt ugly. It needs cleaning and simplification. - -* There's big confusion regarding /when/ the changed(bool) signal should be emitted, abd by /whom/. This can't be fixed properly in 3.x since it means breaking behavior. In KDE 4 it must be made clear if TDECModuleProxy should take care of emitting appropriate signals for load()/save()/defaults, or if modules manually should handle it(is there a reason?). - -* Root modules in TDECModuleProxy doesn't support D&D, or it is perhaps implemented in QXEmbed? Anyway, this is what the XEmbed Protocol Specification says: - -Solving the drag-and-drop problem, however, is quite easy, since the XDND protocol was carefully designed in a way that makes it possible to support embedded windows. Basically, the embedder has to operate as drag-and-drop proxy for the client. Any XDND messages like XdndEnter, Xdnd,Leave, etc. simply have to be passed through. A toolkit's XDND implementation has to take this situation in consideration. |