--===============1746844634== Content-Type: multipart/alternative; boundary=0016e659f4a81aefe00492531090 --0016e659f4a81aefe00492531090 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Ralf >Do you think about something like the single package installer approach >like available at http://www.winkde.org/pub/kde/ports/win32/setup/stable/ Yes, in some way, that is a cool approach, the ui is very plain and the use= r only have to wait. It could be better: the ui can have a simple progress control and a gif embedded (but is only my opinion ;)) ... but yep that is the idea. However, the fact of provide individual installers for every app/module could be still confusing (even if is the same versi=F3n: stable, testing, 4.5,3, ...) Also, this kills the concept of the windows installer: have a common place to install (update) KDE software on windows. Perhaps the best way to join both approach would be let the user to chooses the KDE-version installer (kde-stable.exe, kde-testing.exe ...) instead of the module/app-version one.The ui of the installer will omit the idea of choose the version (and even omit the idea of searching and replaced by choosing) and will have a UI very similar to your packages plus some searching (or choosing) system, this is a mockup to show the concept: http://lh4.ggpht.com/_DsEzMwoRlb4/TLLF_ibv6LI/AAAAAAAAAcI/0kEn49CkN5U/kdewi= ninstaller.jpg Regards, Percy On Mon, Oct 11, 2010 at 12:54 AM, Ralf Habacker w= rote: > Am 11.10.2010 01:00, schrieb Percy Camilo Trive=F1o 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 =3D> 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 > _______________________________________________ > Kde-windows mailing list > Kde-windows@kde.org > https://mail.kde.org/mailman/listinfo/kde-windows > --0016e659f4a81aefe00492531090 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Ralf

>Do you think about something like the single package ins= taller approach
>like available at http://www.winkde.org/pub/kde/ports/win32/= setup/stable/

Yes, in some way, that is a cool approach, the ui = is very plain and the user only have to wait. It could be better: the ui ca= n have a simple progress control and a gif embedded (but is only my opinion= ;)) ... but yep that is the idea.

However, the fact of provide individual installers for every app/module= could be still confusing (even if is the same versi=F3n: stable, testing, = 4.5,3, ...) Also, this kills the concept of the windows installer: have a c= ommon place to install (update) KDE software on windows.

Perhaps the best way to join both approach would be let the user to cho= oses the KDE-version installer (kde-stable.exe, kde-testing.exe ...) instea= d of the module/app-version one.The ui of the installer will omit the idea = of choose the version (and even omit the idea of searching and replaced by = choosing) and will have a UI very similar to your packages plus some search= ing (or choosing) system, this is a mockup to show the concept:

http://lh4.ggpht.com/_DsEzMwoRlb4/TLLF_ibv6L= I/AAAAAAAAAcI/0kEn49CkN5U/kdewininstaller.jpg

Regards,
Percy<= br>











= On Mon, Oct 11, 2010 at 12:54 AM, Ralf Habacker <ralf.habacker@freenet.de> wrote:
=A0Am 11.10.2010= 01:00, schrieb Percy Camilo Trive=F1o Aucahuasi:
> Hi Elias,
>
> >>1) Krita for historical reasons is a part of KOffice. This mig= ht 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' c= ould solve
> the issue.
>
> Is true, also I think the main issue here isn't the searching of t= he
> 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 =3D> 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/setu= p/stable/

Regards
Ralf
__________________________________= _____________
Kde-windows mailing list
Kde-windows@kde.org
https://mail.kde.org/mailman/listinfo/kde-windows

--0016e659f4a81aefe00492531090-- --===============1746844634== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kde-windows mailing list Kde-windows@kde.org https://mail.kde.org/mailman/listinfo/kde-windows --===============1746844634==--