On Sun, 11 Dec 2011 21:29:03 +0100 Werner Joss werner@hoernerfranzracing.de wrote:
On Sunday 11 December 2011 20:33:36 Timothy Pearson wrote:
To the users here: please don't bash KDE4 itself when the discussion is revolving around kwin. ;-) Keep things on topic--if there are aspects of kwin4 you can't stand please bring them up politely and ask for them to be resolved. It is quite possible that upstream can be more responsive than TDE due to more developer resources; what we will need to gauge is upstream's openness to our suggestions.
correct. however, it is clear that there _are_ serious disagreements on how to best provide a 'kde 3.5 computing style' to users. martin, e.g., claims that all what is needed for that would be to port kicker
- kdesktop from kde 3.5 to kde4, but it is not:
- kde 4 performance/responsiveness on some older hardware is
absolutely poor, thats simply a fact
Did you look at https://wiki.archlinux.org/index.php/KDE#Troubleshooting ? It has solutions for bad performance of KDE4. Personally I make no trick of this kind and didn't find KDE4 slow with anything better than my 1,2 GHz Athlon box (except if KWin desktop effects are activated, but they're optional). And even with this Athlon system KDE4 remains usable, just a bit sluggish.
- the kde 3.5 experience does also consist of the
simplicity/robustness/maintainability (from user's perspective) of applications
- this means: no nepomuk, no local database server, no
akonadi, no virtuoso, just plain text data/config files (and no, I don't want to discuss the pros and cons of these components, its just the fact that they can no longer be disabeled without losing basic functionality)
Since KDE maintains binary and source compatibility within major releases nothing should stop you from using kdepim 4.4.10 with any KDE 4.(4+), which doesn't need Akonadi to work.
there is more, of course, but it should be clear that what trinity wants to provide (and is supposed to) just cannot be achieved by simply porting 2 applications.
werner
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting