Principles on what KDE for Windows includes?

[Ralf Habacker]

  Am 11.10.2010 01:00, schrieb Percy Camilo Triveño Aucahuasi:
> Hi Elias,
>
> >>1) Krita for historical reasons is a part of KOffice. This might be
> >>the reason why Krita cannot be used successfully as a search
> >>term in the KDE 4 Windows Installer.
> >>2) The end user does not know which of the KDE packages are
> >>stable and which are not. As Andrius wrote that KOffice
> >>packages are not stable so I searched the unstable releases.
> >>(But as Percy now confirmed - this is
> >>not a good search strategy as the wanted package is not there.)
> >Perhaps extending search to 'lookup by application name' could solve 
> the issue.
>
> Is true, also I think the main issue here isn't the searching of the 
> package name, but the availability of the packgages in self (or, as 
> Gilles Caulier said: the maintenability of huge packages)
>
> From my personal point of view: is hard to create *KDE* packages on 
> windows, it should be easy, but even betwen xp, vista and 7 exists 
> some factors that make it dificult (eg. permissions) Emerge is a great 
> tool and aims to achieve
> to make more easy the life *for developers*, but I think is time to 
> improve the windows user experience too.
>
> The windows installer paradigm is confusing users and even some get 
> scary of using it, however the paradigm in self isn't bad, is just 
> matters of enhance communication of what is aviable in each release 
> and what is not. Also, some improvements in the UI would be welcome: 
> maybe change the wizard style to something like a welcome dashboard or 
> simply (as Jaroslaw suggested) improve searching ... and hidding the 
> progress of installing => why the users have to see all the list of 
> files during the instalation proccess? ;)
Do you think about something like the single package installer approach 
like available at http://www.winkde.org/pub/kde/ports/win32/setup/stable/

Regards
Ralf