On 5/7/07, Justin Haygood <jhaygood@spsu.edu> wrote:
After all of the package management discussion, I had an idea. Why not port Ubuntu's gnome-app-install to zypp for GNOME users? (Or create our own). This will provide an easy to use interface to install applications (not packages, not patterns, applications!). Why is this needed? Aunt Jill or Grandpa Bill or Cousin Fred who used Windows doesn't know or care what a package is, but knows very much what an application is.
Agreed.
What I forsee:
1. An easy to use Application Installer that prompts for root password only before installation 2. The Application Installer has a list of applications in various categories, with the icon, name, description, and potentially user reviews, screenshots, etc.. (similar to Linspire CNR) 3. Uses zypp sources to provide the package data, extra information can come from a web service. 4. Installation happens natively using zypp
Sounds good, but to be really successful this needs more metadata than is available in the package repositories already. For example we need ratings, tags, icons, screenshots, links to relevant documentation. It also needs to be read-write so users can contribute to improving these, and get recommendations "Other people who installed kopete also installed konversation". (Think last.fm but for software). See pascal's software portal mockup: http://linux01.gwdg.de/~pbleser/files/swportal/mockup/mockup.jpg (http://lists.opensuse.org/opensuse-project/2007-05/msg00084.html) We can easily make this web based with the single click install feature which hopefully should make its way into the distro before long. In addition we can expose all the features that are available through the web based portal through an web service to enable client side yast/kde/gnome interaction with it.
What do people think? I'm very willing to commit resources (programming abilities and free time) for this idea.
Great.
It would probably need to be broken down until 3 parts:
1. C++ Library to fetch application information from zypp and web services 2. GTK/GNOME front-end 3. KDE/Qt front-end
I would say 1: Backend to collect and organise metadata from repositories & user input. 2: Web Service frontend exposing all required features. 3: Web based portal - most flexible, and quickest to get off the ground, and enables anyone with a web browser to contribute the vital tagging, organisation, images, and statistics needed to make it a success. 4: Client side frontend - using YaST would give us GTK+ and Qt and ncurses and command line frontends for free. This might require some extension of yast's UI capabilities which would benefit all YaST modules. KDE/Gnome clients not based on yast would also be possible, but possibly a waste of time. All in all this is a lot of work, but by no means unachievable, a significant portion is already available in the automatic trawling and organising of repository metadata for http://benjiweber.co.uk:8080/webpin/ package search, which is exposed through a web service and can be used from clients (see http://benjiweber.co.uk/packagesearch-yast.png for screenshot of yast querying the pakcage search). "install now" links are available both for the web based version and the local client. (More on design http://en.opensuse.org/Package_Search) The biggest piece of work is combining user input with the above, storing user tagging, search statistics, links, and other metadata. Quite a few people have expressed an interest in contributing to this project in one form or another. I suggest we arrange a technical planning IRC meeting to enable some more interactive discussion on the matter. _ Benjamin Weber --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org