On Mon, Jun 30, 2008 at 09:06:29PM +0300, Marius Vollmer wrote: > "ext Marius Gedminas" <marius@xxxxxx> writes: > > > Speaking of non-UI programs listed in the Application Manager, how can > > we solve the current problem of having tens of pidgin/canola/gcompris > > plugins/themes/translations cluttering up the list? > > Good question. We have been pondering this a bit. > > > I think a collapsible tree (with two levels only) would work. If there > > is a package $foo, and several packages named $foo-$bar, group them > > under $foo. > > What about using the Recommends and Suggests fields of a package for > this? I don't think that would work. It puts too much on the shoulders of the packagers, and has nonintuitive consequences when porting Debian packages that already have Recommends/Suggests. E.g. if a random package just happens to have Recommends: wget, I wouldn't want wget to be hidden from the top-level installable package list. > When installing a package, the user could get a dialog where s/he can > select which additional packages to install. The dialog would list all > recommended and suggested packages, and the recommended ones would be > pre-selected. I think currently when a user selects a package to install, she already gets too many extra dialogs. > One open questions with this is: how can the user get back to this > dialog after installing a package? E.g., you might want to change the > set of Pidgin plugins later on. Hm. Show the top-level package (say, canola) iff there are any subpackages that aren't yet installed. The 'Install' button would then be disabled if you select the already-installed package. Marius Gedminas -- Seen on a button at an SF Convention: Veteran of the Bermuda Triangle Expeditionary Force. 1990-1951.
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ maemo-users mailing list maemo-users@xxxxxxxxx https://lists.maemo.org/mailman/listinfo/maemo-users
