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 user 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ón: 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/kdewininstaller.jpg Regards, Percy On Mon, Oct 11, 2010 at 12:54 AM, Ralf Habacker <[email protected]>wrote: > 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 > _______________________________________________ > Kde-windows mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/kde-windows >
_______________________________________________ Kde-windows mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-windows
