Pandora Wiki - User contributions [en]

QEMU

2012-03-18T01:16:21Z

Caine: /* Downloading the PND */

This is a page about the qemu port by IngoReis and mcobit (forum thread [http://boards.openpandora.org/index.php?/topic/7004-qemu-for-pandora-for-rebirth-competition/ here]).

=Documentation=

==PND download and installation==
===Downloading the PND===
Use your favorite browser to navigate to the following url: [repo...](Will be available after release)
and click the Download button.
Save the File somewhere on your PC. If you use your Pandora to download, you can save it to the directory mentioned in the next chapter directly.

===Installing the PND===
Put the downloaded file onto your sdcard into one of the following folders:
For Desktop: YOURSDCARD/pandora/desktop
For Menu: YOURSDCARD/pandora/menu
For both: YOURSDCARD/pandora/apps

If you do this on your PC, insert the sdcard into your Pandora afterwards.

If you use pndstore or some other tool to download and install pnds, please see their documentation for how to use them.
===Running the PND===
If the above steps worked properly, you should see the Qemu for Pandora icon in the above mentioned place(s) now.
(Double)click it to startup the GUI.
==Using the UI==
===Main===
====Mounting HDD images====
Click on the icon with the folder next to "Load image..." to browse your filesystem. Navigate to the imagefile you want to load and select it by doubleclicking it or mark it with a single click and press "open".
The help-button will provide some hints on how to do that as well.
It is also possible to enter the fullpath including the imagename into the box directly. (e.g. /media/PATHTOYOURSD/qemuimages/freedos.qcow2)
====Mounting CD/DVD images====
Click on the icon with the folder next to "Load iso.." to browse your filesystem. Navigate to the iso (cdrom image) you want to load and select it by doubleclicking it or mark it with a single click and press "open".
The help-button will provide some hints on how to do that as well.
It is also possible to enter the fullpath including the isoname into the box directly. (e.g. /media/PATHTOYOURSD/qemuimages/freedos.iso)
====Assigning RAM to the machine====
Click on the textfield next to "RAM in MB" and enter the amount of RAM in MegaBytes, that the machine should use.
If you leave this field blank, the standard value of 128MB will be used.
====Launch the machine====
When you are happy with all options, you can click the "Launch" button to start the virtual machine.
====Exit the UI====
If you want to quit the gui, click on the "Cancel" button in the Main tab.
===Image Tools===
====Creating HDD images using the UI====
*On the "Image Tools" tab, type in the name of your image in the first textfield without a fileextension. (e.g. test-image)
*Type the desired size of the new image into the second textfield. The size is in MegaBytes. So for a 1GB image type 1024.
*Click on the "Create Image" button.
Your new image will be created in the following directory: appdata/qemu/images/
===Other options===
====Video options====
*Use Bochs vga card instead of Cirrus Logic
Simulate a standard VGA card with Bochs VBE extensions instead of the default Cirrus Logic GD5446 PCI VGA
*Fullscreen
Start the virtual machine in fullscreenmode rather than in a window. You can switch between the modes by pressing alt+ctrl+f.
====Sound options====
*Disable sound
Disable sound by selection this option. (Qemu doesn't support to disable the sound completely, but with this option you will choose a soundcard, that is not supported by most operating systems)
*Adlib card emulation
Emulate an additional Adlib synthesizer card.
====CPU options====
*486 CPU instead of pentium
Check this option, if you want qemu to emulate a 486 PC instead of the default pentium PC.
====Network options====
*Disable Network
Check this, if you do not want qemu to emulate a networkcard.
==Installing an OS into an image==
===Creating HDD images using your Desktop PC (Linux)===
===Creating HDD images using your Desktop PC (Windows)===

*Download Qemu Manager 7 for Windows.

*Install into Windows and run Qemu Manager as Admin.

*go to the Option Qemu Version Management and install Qemu 0.14.1
(You must do this,otherwise QemuManager will use Version0.11 by itself and this Version isnt Compatible)

*Now you can Use the "File/Create new Virtual Disk" Option

*Choose the max Image Size and i recommend the qcow2 Image Format.

Your new empty Image ist now in your QemuManager Folder named "Images"

===Installing Microsoft DOS===
====On your Desktop PC====
====On the Pandora====
===Installing Microsoft Windows 3.1 / 3.11===
====On your Desktop PC====
====On the Pandora====
===Installing Microsoft Windows 95 on PC===

*start Qemu Manager

*create new VM

*Name it what you like(example win95)

*Choose x86PC , Operating system Windows58 and very very Important choose Qemu Version 0.14.1 the standart 0.11.1 will not work

*select Ram 128MB(the max what Pandora Qemu can use) and choose the size of your Harddisk

*Virtual Machine Output is important to set it to "QemuWindow"(not QemuManager)

*now you should use this Hardware Settings: Soundcard=Yes

SoundHW=Soundblaster16

Networking=none (the Networking is not testet now with Win98,but it could work)

VideoCard=Cirrus GD5446

*and under the Menu Advanced some Performance Tweaks:

Disable Hpet=YES

Disable ACPI Support=YES

*NOW WE CAN INSTALL Win95:

*Switch to Drives and Choose as CDROM your CDROM Drive or your own Win95Iso

*use one Win95 Bootdisk (.ima and .img Diskformats shoud work)

*start from Bootfloppydisk(or Image)and start install (THE MSDOS CDROM DRIVER HANGS A LITTLE BUT AFTER 1-2MINUTES WILL IT LOAD FINE)

*Setup Should start well(when it hangs in installation Progress,theres a alternativly way to install Win95/98)

*AFTER INTALLATION CHANGE IN HARDWAREMANAGER THE PLUG&PLAY BIOS MANUALY TO PCI-BUS.

(HARDWARE AUTODETECTION WILL NOT WORK FULL THEN YOU MUST MAKE THIS AFTER INSTALLATION)

Happy installing/experimenting :)

===Installing Microsoft Windows 98===
====On your Desktop PC====
*start Qemu Manager

*create new VM

*Name it what you like(example win98)

*Choose x86PC , Operating system Windows98 and very very Important
choose Qemu Version 0.14.1 the standart 0.11.1 will not work

*select Ram 128MB(the max what Pandora Qemu can use)
and choose the size of your Harddisk

*Virtual Machine Output is important to set it to "QemuWindow"(not QemuManager)

*now you should use this Hardware Settings:
Soundcard=Yes

SoundHW=Soundblaster16

Networking=none (the Networking is not testet now with Win98,but it could work)

VideoCard=Cirrus GD5446

USBSupport=Yes

USBDevices=add USB Tablet with the + Symbol(this is for Pandora Touchscreen support)

*and under the Menu Advanced some Performance Tweaks:

Disable Hpet=YES

Disable ACPI Support=YES

*NOW WE CAN INSTALL WIN98 or WIN98SE:

*Switch to Drives and Choose as CDROM your CDROM Drive or your own Win98Iso

*start Qemu with the green Play Button

*start from CDROM and start install
(THE MSDOS CDROM DRIVER HANGS A LITTLE BUT AFTER 1-2MINUTES WILL IT LOAD FINE)

*THE TOUCHSCREEN SUPPORT WILL ONLY WORK WHEN YOU AFTER INTALLATION CHANGE IN HARDWAREMANAGER THE PLUG&PLAY BIOS MANUALY TO PCI-BUS.

*(HARDWARE AUTODETECTION WILL NOT WORK FULL THEN YOU MUST MAKE THIS AFTER INSTALLATION)

*Happy installing/experimenting :)

===alternativly Way to install Win95/98===

====On the PC====

*Break the installation Progress with F3 and you will be in MSDOS

*switch to a: and make your HD Image bootable with

sys c:

*switch to HDD and make a setup Directory with

md c:\setup

cd c:\setup

*now switch to your CD Drive

d:

cd win95 (or when you want to install win98,then "cd win98")

*and copy your Setup Files to your HDDImage

copy . c:.

*your setup Files should now copy to c:\setup

*after this boot your HDD Image without Floppy Image and without your Windows Iso

*you must be now in Dos and must type

cd setup

xmsmmgr

setup

*Now this is the Way who must install Windows perfectly

*happy experimenting/installing

====On the Pandora====

*same like PC

===Installing Microsoft Windows XP===
====On your Desktop PC====
same like Windows98 but not testet yet.

====On the Pandora====

===Installing Linux===
====On your Desktop PC====
====On the Pandora====
===Downloading and using ready-made FreeDOS and ReactOS images===

==Troubleshooting==
===Known problems===
We are working on them. If you have found a solution or can provide a patch, please pm mcobit at [http://boards.openpandora.org boards.openpandora.org]
* Paths to image or isofiles as well, as imagenames specified in the "Image Tool" MUST NOT contain any whitespaces.
* EMS Memory under Dos is a little Tricky to get work but it work. You must use in Config.sys the Entry "EMM386 M9" and behind Himem.sys must stand nothing,only Himem.sys
* Shared Folders: don't use shared folders as an "active" source: write support for shared folders is buggy, so don't run applications/games from shared folder, just copy its content on the virtual systems drive. A lot of games have problems writing to the shared folder

*under Windows,when a Game set 320x240 the Screen will stretched,but work,then try another Resolutions.

===Report a bug===
===What to do, if…===
* Windows cannot find the mounted CD Image??

Solution=Install a MS-Dos CD-Rom Treiber in your Image and let it load before Windows starting.

* EMS Memory isnt working??

Solution=It works when you have in Config.sys:

Device=Himem.sys

Device=Emm386.exe M9

(or Devicehigh=)

* A Game/or System breaks and you are in PanQemu Startwindow again??

Its a Fullscreen Bug from Qemu

(Qemu for Pandora cannot handle Resolutions over 640x480 in Fullscreen Mode)

Solution=use Qemu in Windowed Mode(not in Fullscreen)and switch to 640x480,

then you can press ctrl+alt+f to switch to Fullscreen again(works well).
===Tipps, Tricks & Hints===
====General====
* If you happen to miss the [alt] and [strg] keys, look between the nubs
====MS-DOS 6 and above / alike====
* Keyboard
** if you can't enter ":" and/or "\" one solution is to use the italien keyboard layout. just type "keyb it" on the commandline and press [enter] after that you can enter ":" with [Shift] + [.] and "\" with [Fn] + [H]
* CD-ROM Support
** To use cd images as CD-ROMS under MS-DOS 6 and above you need to do the following
** Get the Ms CD extension (mscdex.exe) from [http://support.microsoft.com/kb/123408/en here]
** You need a CD-ROM driver, there are several available, one that is known to work is "oakcdrom.sys"
** Copy the both on your virtual disk, the following bulletpoints assumes that you put them both into "c:\dos", if not change the pathnames according to your choice
** Put the following line in your config.sys : "DEVICEHIGH= C:\DOS\OAKCDROM.SYS /D:MSCD001"
** Put the following line in your autoexec.bat: "LH C:\DOS\MSCDEX.EXE /D:MSCD001 /L:E"
** Some explanation to the above: the character string "MSCD001" is just id you can choose as you like, but it has to be identical in both files. The Parameter "L:E" associates the CD-ROM with the drive letter "E", this is optional.
* Mouse support
** Mouse needs a driver under MS-DOS environments.
** There are several around, a - memory wise - light alternative could be [http://cutemouse.sourceforge.net/ CuteMouse]
** There are several executable files in the archive you download (inside the bin folder). You need a file that begins with "ctm-", choose the file according to the language you prefer (e.g. "ctm-en.exe" who wan't it in english)
** If you choose the english version and put it directly into the root of your main virtual drive, simply put the line "LH C:\ctm-en.exe" in your autoexec.bat to load it on startup.
* Two pane file manager
** As using the commandline to move data from one point to another can be very cumbersome (at least if no xcopy is available) have a look at [http://www.ritlabs.com/en/products/dn/ DOS Navigator] an open source Norton Commander clone

==Credits==

=Compatibility lists=

==Operating Systems==
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Name
! Version
! Runs?
! Useable?
! Loadingtime
! Comments
|-
|GParted
|0.12.0-2
|Yes
|No
|??
|Very long to run. Graphical mode crash.
|-
|Haiku
|r1 alpha 3
|No
|No
|??
|Converted official vmware image.
|-
|Microsoft DOS
|6.22
|Yes
|Yes
|??
|
|-
|Microsoft DOS
|7.10
|Yes
|Yes
|??
|
|-
|Microsoft Windows
|3.1
|??
|??
|??
|
|-
|Microsoft Windows
|3.11
|Yes
|Yes
|??
|
|-
|Microsoft Windows
|95
|Yes
|Yes
|??
|
|-
|Microsoft Windows
|98
|Yes
|Yes
|??
|IO - Access seems slow
|-
|Microsoft Windows
|ME
|??
|??
|??
|
|-
|Microsoft Windows
|2000
|Yes
|??
|??
|Should only install with activated Win2k hack for qemu. Runs very slow but usable. Tweaking guide [http://www.nexle.dk/win2000-32mb/ here].
|-
|Microsoft Windows
|XP
|Yes
|Not quite
|??
|
|-
|Microsoft Windows
|VISTA
|??
|??
|??
|
|-
|Microsoft Windows
|7
|??
|??
|??
|
|-
|Freedos
|1.1
|Yes
|Yes
|??
|Need a bit of work to get it installed
|-
|ReactOS
|??
|Yes
|Yes
|??
|[http://sourceforge.net/projects/reactos/files/ReactOS/0.3.14/ReactOS-0.3.14-REL-qemu.zip/download Downloadable image from website]
|-
|Ubuntu Linux
|??
|??
|??
|??
|
|-
|TinyCore Linux
|??
|Yes
|Yes
|??
|
|-
|}

==Office/Desktop programs==
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Name
! Version
! Runs?
! Useable?
! Loadingtime
! Comments
|-
|Notepad
|Windows 95
|Yes
|Yes
|
|-
|-
|CasCADe
|Windows 95
|Yes
|Yes
|
|-
|}

==Games==
Office/Desktop programs:
{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Name
! Version
! Operating System
! Runs
! Sound
! MHz
! Playable
! Comments
|-
|Age of Empires
|
|Microsoft Windows 95
|Yes
|yes
|950
|Yes
|
|-
|Archemdian Dynasty (Schleichfahrt)
|
|Microsoft DOS 6.22
|No
|No
|950
|No
|
|-
|Arctic Baron (Transarctica)
|
|Microsoft DOS 6.22
|No
|No
|950
|No
|
|-
|Ascendancy
|
|Microsoft DOS 6.22
|Yes
|No
|950
|Yes
|
|-
|Alien Breed
|
|Microsoft DOS 6.22
|Yes
|No
|950
|?
|heavy flickering, setup crashes on sound config
|-
|Alien Breed - Tower Assault
|
|Microsoft DOS 6.22
|Yes
|Yes
|950
|?
|heavy flickering
|-
|Alone in the Dark
|
|Microsoft DOS 6.22
|yes
|No
|950
|yes
|slow but playable
|-
|AL-Qadim The Genie's Curse
|
|Microsoft DOS 6.22
|yes
|No
|950
|Yes
|stutters a little
|-
|B.A.T
|
|Microsoft DOS 6.22
|Yes
|No
|950
|Yes
|too fast @950MHz
|-
|Battle Arena Toshinden
|
|Microsoft DOS 7.10
|Yes
|Yes
|870
|Yes
|
|-
|Bundesliga Manager Prof.
|
|Microsoft DOS 6.22
|Yes
|No (Just Music)
|600
|Yes
|It has some graphic bugs and mouse fails sometimes
|-
|Cadaver
|
|Microsoft DOS 6.22
|Yes
|No
|950
|Yes
|
|-
|Command&Conquer
|
|Microsoft DOS 7.10
|Yes
|yes
|950
|Yes
|perfectly
|-
|Crusader: No Remorse
|Gog.com
|Microsoft DOS 6.22
|Yes
|Yes
|950
|Yes
|
|-
|Dune
|
|Microsoft DOS 6.22
|Yes
|Yes
|950
|No
|
|-
|Dune 2
|
|FreeDos
|Yes
|No
|900
|Yes
|
|-
|DungeonKeeper
|
|Microsoft DOS 7.10
|Yes
|Yes
|870
|Yes
|
|-
|Descent
|1
|Microsoft DOS 7.10
|Yes
|Yes
|870
|Yes
|
|-
|Elvira 2 - The Jaws of Cerberus
|
|Microsoft DOS 6.22
|No
|No
|950
|No
|Crashes on "Load last save ?" message after startup
|-
|Fatal Racing
|
|Microsoft DOS 6.22
|yes
|No
|950
|No
|too slow to play
|-
|Gods
|
|Microsoft DOS 6.22
|No
|No
|950
|No
|
|-
|Hanse, die Expedition
|
|Microsoft DOS 6.22
|Yes
|Yes
|600
|Yes
|
|-
|Halloween Harry
|Shareware
|Microsoft DOS 6.22
|Yes
|Yes
|950
|Yes
|smooth, controls adjustable so dpad+action buttons possible
|-
|Ishar III
|
|Microsoft DOS 7.10
|Yes
|No
|870
|Yes
|
|-
|James Pond 2
|
|Microsoft DOS 6.22
|yes
|No
|950
|yes
|runs perfectly without Sound
|-
|Microprose F1GP Demo!
|
|Microsoft DOS 6.22
|Yes
|No
|950
|Yes
|Demo is restricted to 8 FPS
|-
|Need for Speed
|
|Microsoft Dos 7.10
|Yes
|No
|950
|Yes
|runs perfectly without Sound
|-
|One Must Fall 2097
|CD
|Microsoft DOS 6.22
|Yes
|Yes
|950
|Yes
|runs near perfect, with best sound quality
|-
|Popolus 2
|
|Microsoft DOS 6.22
|Yes
|No
|950
|Yes
|too fast @950MHz
|-
|The incredible Machine 2
|DOS
|Microsoft DOS 6.22
|No
|No
|950
|no
|blank screen after start
|-
|Theme Park
|
|Microsoft DOS 6.22
|Yes
|Yes
|950
|Yes
|no music
|-
|Tie Fighter
|
|Microsoft DOS 6.22
|No
|No
|950
|No
|Does not start
|-
|Tomb Raider
|
|Microsoft DOS 7.10
|Yes
|yes
|950
|Yes
|very little Bit of stuttering
|-
|Stunts
|
|Dos 6.22
|Yes
|yes
|800
|Yes
|perfectly
|-
|Syndicate
|
|Microsoft DOS 7.10
|Yes
|yes
|950
|Yes
|smoothly
|-
|Skyroads
|
|Freedos1.1
|Yes
|yes
|950
|Yes
|smoothly
|-
|Silent Hunter
|
|Microsoft DOS 7.10
|Yes
|yes
|950
|Yes
|super playable with Mouse
|-
|Settlers 2 Gold (Die Siedler 2 Gold)
|
|Microsoft DOS 6.22
|Yes
|No
|950
|Yes
|save/load leads to crashes sometimes
|-
|Ultima Underworld : The Stygian Abyss
|
|Microsoft DOS 6.22
|Yes
|No
|950
|No
|too slow to be playable
|-
|WIPEEEOUT
|
|Microsoft DOS 7.10
|Yes
|No
|870
|Yes
|
|-
|Winpolis
|
|Microsoft Windows 3.11
|Yes
|Yes
|600
|Yes
|
|-
|World of Xeen
|
|Microsoft DOS 6.22
|Yes
|Yes
|950
|Yes
|
|-
|World of Xeen
|
|Microsoft DOS 6.22
|Yes
|Yes
|950
|Yes
|
|-
|Xentar(Knights of)
|
|Microsoft DOS 6.22
|Yes
|Yes
|950
|Yes
|perfectly in 2D Mode
|-
|X-Wing
|
|Microsoft DOS 6.22
|Yes
|No
|950
|Yes
|Runs well with low details
|-
|}

PND management workflow

2011-10-10T12:53:39Z

Caine: /* Tag */

== Whom it concerns ==

* Thinkers who oversee the Pandora software platform as a whole and on the long run (core team & others)
* Plus in particular the developers of:
** Launchers like: MiniMenu, XFCE Menu, quick text based launchers
** Package managers like: PNDStore, PanoramaMilky (I use "PanoramaMilky" to refer to "Panorama in UI mode milky test")
** Package metadata/override editors/tools (PND and OVR)

== Topic of this work group ==

Software packages are at the center of the Pandora, hence the overall way how to manage them are key to success of the platform's usability and popularity.

Currently the different aspects of managing and using PNDs are spread over a patchwork of different tools and workflows, and some aspects are yet not covered at all.

I now try to describe what is important from a user's point of view, what already exists (to my knowledge), what should be realized, and point towards possible gap-closing and synergies between existing solutions.

Disclaimer: Generally speaking, the patchwork per se is nothing bad. Openness is the principle of the Pandora, and it should by principle be always possible for a tool to cover/handle just a very small and specific task. Nevertheless from the user's perspective it is appreciated to have as little steps as necessary for common tasks in (at best) one uniform environment.

== Follow up ==

The issue was first brought to attention within the [http://boards.openpandora.org/index.php?/topic/5636-usability-of-package-management-pnd-coordinating-related-development-efforts/ developer forum].

The issue consists of many aspects, which themselves again are complexly inter-connected.

Therefore all follow-ups shall happen HERE INLINE within the wiki-page into the SPECIFIC sections! If necessary mark your addition with author and date (YYYY-MM-DD HH:MM UTC).

----

If your addition is large, please create only a short inline summary, and link the full content to a new page!

The content of the wiki describes aspects, which sometimes implicit bug reports, feature suggestions, etc, but not explicitly written and some of them yet not reported to the issue tracker.

Please be autonomous enough, to realize your responsibility for your own. I spent hours brainstorming and writing this memo, even further dividing the tasks would overburden me. See it as a whole, co-ordinate your efforts (in the thread as this is "meta"), and only then slice it up on single issues. Thanks!

== Main needs around handling of software packages (PNDs): ==

* Discover
* Install ( + Update + Remove)
* Test
* Tag
* Launch
* Overview

== What is meant by this? How are they related? ==

=== Overview ===

The possibility of overview (filtering / sorting) can aid in all other tasks.
The data source for "overview" is the metadata included in the PNDs plus the overrides included from OVRs (or other yet not developed over-ride/lay methods).

=== Test ===

Currently, after installing new apps which you want to test, you have to find them as "the needles in the haystack" among the already installed apps, instead of a convenient mode, in which you can only run "new apps".

One might say: Just remember an app's name and find it from the "All" category. But what if you installed 3-5 new apps or even more … already a bit more complicated then!

If the PND framework would keep track of how often apps have been launched (or just a simple "ran-once" flag), this would provide a data basis for certain display modes like "Show new apps" or "Sort by usage frequency" in "overview" or "launch" applications.

=== Discover ===

Works quite good through:
* Various information media related to OpenPandora like forum announcements, PandoraPress, various feeds.
* Informal ways like chats, forums.
* Formal catalogues / databases like the open handheld archives, appstore, repo), the latter being well suited for integration into software (machine readable). This medias especially increase the chances for newcomers, which are yet un-featured in the information and informal medias! If a user finds a well sorted catalogue, his/her readiness for trying new applications rises!

Application name, description, icon, screenshots, categories deliver a good enough idea. Filter options like categories, or sorting actions like "most recent" help to narrow down the selection even more.

This aspect is already very mature on the Pandora!

What could be slightly improved: If "discover" and "install"/"test"/"remove" are integrated into one application, your system could systematically keep track of already tested and deliberately removed applications as "uninteresting", and hide them in your further "disover" process! Sparing you a lot of time/attention seeing items again and again, which you already once found as uninteresting!

Right now, if you manually scan catalogues, you likely stumble across candidates, you already deliberately rejected, which steals you your time /attention. The only display mode which spares you this: Sort catalogues by "recently published", and thereby all new stuff is really new to you. But of course, all the display modes like, categories, tags, remain crowded with already seen stuff.

=== Install/update/remove ===

These 3 tasks must be hand-able within one environment!

At the Pandora beginnings, no tool existed, meanwhile tools came to the rescue!

I do not expect from the "launch" application (MiniMenu) to have "install/update" abilities, but at least have the "remove" ability, to facilitate "test" process. "Launch app, test wether you like it, quit app" and then "remove" right away if you don't like it!

MiniMenu: Shall be able to delete a PND application (if on remove-able media).

PNDstore and PanoramaMilky handle Install/update/remove quite ok already.

PNDstore: Shall remember default installation locations better, as PanoramaMilky already does.

After running a "scan for updates" the manager shall have the possibility to update all or only certain selected apps. (equivalent to iOS Appstore app).

=== Tag ===

Override the PNDs' metadata, which later aids "overview" and "launch" applications.

Right now there is neither a well-working workflow for "test an app, quit it, tag it" nor a mass-editor for tagging multiple apps according to your memories or notes.

The advantage of "test an app, quit it, tag it" is, that the user's memory of the tested applications is still fresh, hence the tagging is easy to make and appropriate.

''There is currently no tag concept associated with PNDs. It is possible to abuse notes for this purpose, but none of the tooling will really be able to do anything useful with it as there are no semantics specified for the fields.'' Caine 2011-10-10 [12:53 UTC]

==== MiniMenu - Test an app, quit it, tag it ====

Problem 1: After you ran an arbitrary app and quitted it, you do not return to your last position (bug #241). You need to find that app again first. And then go into submenus. And only then tag it.
Problem 2: After the override of ONE SINGLE app, MiniMenu currenty completely restarts, thus rescans **all** .PNDs and .OVRs! Only re-reading the affected PND + OVR would tremendously speed up.

If both problem 1 + 2 would get fixed the method "test an app, quit it, tag it" would practically work.

==== Mass OVR editor ====

A spreadsheet-like list with all apps, with the columns: icon, name, custom note, cat, subcat, possibly also summary/screenshot as obtained from repo-catalogue to refresh one's memory, where one can then quickly edit all the metadata of all apps to suit one's own sorting system better.

Caine already developed "OVR editor", and considers to realize such a "OVR spreadsheet editing mode". http://boards.openpandora.org/index.php?/topic/4201-ovr-editor-and-pnd-aware-application-launcher/

=== Launch ===

Your interface for launching apps. The data source for this comes from the PND files plus your OVR override files ("tag" applications).

Launch could be much more fine grained, please see the section on the possibilities of combining: Launch + overview.

Besides this some suggestions of improving existing features right here in this section.

==== Hotkey application launcher ====

Well known from many OSes, this feature would be fine within the Pandora too.

Triggered by hotkey working from everywhere or from menu/desktop entry -> text input with auto completion of installed apps -> launch.

I think that already exists. I just don't know which one's, and how to set the hotkey for it.

==== XFCE launch menu shall have meta trees "All apps" and "All games" ====

MiniMenu has an "All" category tree. The XFCE launch menu doesn't! Would be fine if it had one meta tree which "holds them all".

== Combinations ==

Many combinations of tasks are already described in one of the affected task "verb" sections. Some of these involve many others, and are therefore described below as combinations of "task verbs".

=== Discover + install + update + remove ===

Right now "discover", "install" and "test" are separate workflows.

PanoramaMilky very well unites "discover" + "install/update/remove".

''I think discovery could be improved in MilkyTest by allowing ordering packages by rating and showcasing random highly rated applications. Not sure how the showcasing would work with the UI, but it's something to consider'' - B-ZaR 2011-10-10 05:41Z

''Discovery should be handled by browsing the apps in the repo along with their preview pictures to get an impression of the content. Sorting orders should include alphabetically, by rating, by author, and newly added (excluding recent updates). Also of note, we are essentially talking about CRUD operations on apps. Create (install), Read (run), Update (upgrade app/edit OVR) and Delete. I've always assumed these to eventually merged into a single application, though so far I omitted the OVR files in that vision.'' Caine 2011-10-10 12:33UTC

PanoramaMilky: Would be cool if it could "launch" apps. You could "test" the app, then quit it. PanoramaMilky must then have the previously launched app selected so that you can immediately "remove" or keep it.

''Already planned, though I'll probably fork MilkyTest to create a more fleshed out UI under a different name. MilkyTest was always about testing milky-plugin. I'll post more on this to panorama's beta thread.'' - B-ZaR 2011-10-10 05:41Z

=== Launch + overview ===

Currently MiniMenu allows a filesystem like browsing with metaphors like tabs as categories / subcategories as subfolders within that tabs, and some generated meta categories like "All".

These additional display modes would help:

==== New meta category "Fresh", "By Date Added", "By Date Published" ====

This is for aiding the "test" process, particularly showing yet untested or fresh apps.

Implementation could be hard: As the PND has no central registry, but rather "certain files at certain places", which are scanned to then provide a "certain basis for certain launchers", the tracking of this dates or usage amounts must happen within that scanners/launchers, which must either have the "test" and "tag" abilities themselves, or must make that data available to those applications. Does anyone know what according data is tracked within MiniMenu?

==== Rating and/or favorite system. ====

Date source for "favorite" and/or "sorting" is provided by from your "tagging" (overrides). In addition the "launch" application may have its own methods to "rate" or "favor" applications. (Again this would be good for the approach: "Run app, test app, tag it".)

MiniMenu should show a tab "Favorites", which contains all apps, which are flagged as "favorite" or which have a rating above a certain treshold (i.e. on a scale from 1-5, all which are equal or higher than 4).

MiniMenu should show one tab "By rating", which contains all apps, sorted by rating (as sort key 1, and by alphabet as sort key 2).

If you navigate within the categories and sub-categories folders/tabs, a certain hotkey or menu command, should trigger the "favorite display" or "sorted display", which filters/sorts the contained items accordingly.

Pressing favorite hotkey first: Shows only favorites.
Pressing favorite hotkey again: Shows favorites on top of others.
Pressing favorite hotkey again: Disables favorite view mode, normal view again.

Pressing sort hotkey first: Sorted from best to worst
Pressing sort hotkey again: Sorted from worst to best
Pressing sort hotkey again: Disables sort view mode, normal view again.

PND management workflow

2011-10-10T12:43:36Z

Caine: /* Discover + install + update + remove */

== Whom it concerns ==

* Thinkers who oversee the Pandora software platform as a whole and on the long run (core team & others)
* Plus in particular the developers of:
** Launchers like: MiniMenu, XFCE Menu, quick text based launchers
** Package managers like: PNDStore, PanoramaMilky (I use "PanoramaMilky" to refer to "Panorama in UI mode milky test")
** Package metadata/override editors/tools (PND and OVR)

== Topic of this work group ==

Software packages are at the center of the Pandora, hence the overall way how to manage them are key to success of the platform's usability and popularity.

Currently the different aspects of managing and using PNDs are spread over a patchwork of different tools and workflows, and some aspects are yet not covered at all.

I now try to describe what is important from a user's point of view, what already exists (to my knowledge), what should be realized, and point towards possible gap-closing and synergies between existing solutions.

Disclaimer: Generally speaking, the patchwork per se is nothing bad. Openness is the principle of the Pandora, and it should by principle be always possible for a tool to cover/handle just a very small and specific task. Nevertheless from the user's perspective it is appreciated to have as little steps as necessary for common tasks in (at best) one uniform environment.

== Follow up ==

The issue was first brought to attention within the [http://boards.openpandora.org/index.php?/topic/5636-usability-of-package-management-pnd-coordinating-related-development-efforts/ developer forum].

The issue consists of many aspects, which themselves again are complexly inter-connected.

Therefore all follow-ups shall happen HERE INLINE within the wiki-page into the SPECIFIC sections! If necessary mark your addition with author and date (YYYY-MM-DD HH:MM UTC).

----

If your addition is large, please create only a short inline summary, and link the full content to a new page!

The content of the wiki describes aspects, which sometimes implicit bug reports, feature suggestions, etc, but not explicitly written and some of them yet not reported to the issue tracker.

Please be autonomous enough, to realize your responsibility for your own. I spent hours brainstorming and writing this memo, even further dividing the tasks would overburden me. See it as a whole, co-ordinate your efforts (in the thread as this is "meta"), and only then slice it up on single issues. Thanks!

== Main needs around handling of software packages (PNDs): ==

* Discover
* Install ( + Update + Remove)
* Test
* Tag
* Launch
* Overview

== What is meant by this? How are they related? ==

=== Overview ===

The possibility of overview (filtering / sorting) can aid in all other tasks.
The data source for "overview" is the metadata included in the PNDs plus the overrides included from OVRs (or other yet not developed over-ride/lay methods).

=== Test ===

Currently, after installing new apps which you want to test, you have to find them as "the needles in the haystack" among the already installed apps, instead of a convenient mode, in which you can only run "new apps".

One might say: Just remember an app's name and find it from the "All" category. But what if you installed 3-5 new apps or even more … already a bit more complicated then!

If the PND framework would keep track of how often apps have been launched (or just a simple "ran-once" flag), this would provide a data basis for certain display modes like "Show new apps" or "Sort by usage frequency" in "overview" or "launch" applications.

=== Discover ===

Works quite good through:
* Various information media related to OpenPandora like forum announcements, PandoraPress, various feeds.
* Informal ways like chats, forums.
* Formal catalogues / databases like the open handheld archives, appstore, repo), the latter being well suited for integration into software (machine readable). This medias especially increase the chances for newcomers, which are yet un-featured in the information and informal medias! If a user finds a well sorted catalogue, his/her readiness for trying new applications rises!

Application name, description, icon, screenshots, categories deliver a good enough idea. Filter options like categories, or sorting actions like "most recent" help to narrow down the selection even more.

This aspect is already very mature on the Pandora!

What could be slightly improved: If "discover" and "install"/"test"/"remove" are integrated into one application, your system could systematically keep track of already tested and deliberately removed applications as "uninteresting", and hide them in your further "disover" process! Sparing you a lot of time/attention seeing items again and again, which you already once found as uninteresting!

Right now, if you manually scan catalogues, you likely stumble across candidates, you already deliberately rejected, which steals you your time /attention. The only display mode which spares you this: Sort catalogues by "recently published", and thereby all new stuff is really new to you. But of course, all the display modes like, categories, tags, remain crowded with already seen stuff.

=== Install/update/remove ===

These 3 tasks must be hand-able within one environment!

At the Pandora beginnings, no tool existed, meanwhile tools came to the rescue!

I do not expect from the "launch" application (MiniMenu) to have "install/update" abilities, but at least have the "remove" ability, to facilitate "test" process. "Launch app, test wether you like it, quit app" and then "remove" right away if you don't like it!

MiniMenu: Shall be able to delete a PND application (if on remove-able media).

PNDstore and PanoramaMilky handle Install/update/remove quite ok already.

PNDstore: Shall remember default installation locations better, as PanoramaMilky already does.

After running a "scan for updates" the manager shall have the possibility to update all or only certain selected apps. (equivalent to iOS Appstore app).

=== Tag ===

Override the PNDs' metadata, which later aids "overview" and "launch" applications.

Right now there is neither a well-working workflow for "test an app, quit it, tag it" nor a mass-editor for tagging multiple apps according to your memories or notes.

The advantage of "test an app, quit it, tag it" is, that the user's memory of the tested applications is still fresh, hence the tagging is easy to make and appropriate.

==== MiniMenu - Test an app, quit it, tag it ====

Problem 1: After you ran an arbitrary app and quitted it, you do not return to your last position (bug #241). You need to find that app again first. And then go into submenus. And only then tag it.
Problem 2: After the override of ONE SINGLE app, MiniMenu currenty completely restarts, thus rescans **all** .PNDs and .OVRs! Only re-reading the affected PND + OVR would tremendously speed up.

If both problem 1 + 2 would get fixed the method "test an app, quit it, tag it" would practically work.

==== Mass OVR editor ====

A spreadsheet-like list with all apps, with the columns: icon, name, custom note, cat, subcat, possibly also summary/screenshot as obtained from repo-catalogue to refresh one's memory, where one can then quickly edit all the metadata of all apps to suit one's own sorting system better.

Caine already developed "OVR editor", and considers to realize such a "OVR spreadsheet editing mode". http://boards.openpandora.org/index.php?/topic/4201-ovr-editor-and-pnd-aware-application-launcher/

=== Launch ===

Your interface for launching apps. The data source for this comes from the PND files plus your OVR override files ("tag" applications).

Launch could be much more fine grained, please see the section on the possibilities of combining: Launch + overview.

Besides this some suggestions of improving existing features right here in this section.

==== Hotkey application launcher ====

Well known from many OSes, this feature would be fine within the Pandora too.

Triggered by hotkey working from everywhere or from menu/desktop entry -> text input with auto completion of installed apps -> launch.

I think that already exists. I just don't know which one's, and how to set the hotkey for it.

==== XFCE launch menu shall have meta trees "All apps" and "All games" ====

MiniMenu has an "All" category tree. The XFCE launch menu doesn't! Would be fine if it had one meta tree which "holds them all".

== Combinations ==

Many combinations of tasks are already described in one of the affected task "verb" sections. Some of these involve many others, and are therefore described below as combinations of "task verbs".

=== Discover + install + update + remove ===

Right now "discover", "install" and "test" are separate workflows.

PanoramaMilky very well unites "discover" + "install/update/remove".

''I think discovery could be improved in MilkyTest by allowing ordering packages by rating and showcasing random highly rated applications. Not sure how the showcasing would work with the UI, but it's something to consider'' - B-ZaR 2011-10-10 05:41Z

''Discovery should be handled by browsing the apps in the repo along with their preview pictures to get an impression of the content. Sorting orders should include alphabetically, by rating, by author, and newly added (excluding recent updates). Also of note, we are essentially talking about CRUD operations on apps. Create (install), Read (run), Update (upgrade app/edit OVR) and Delete. I've always assumed these to eventually merged into a single application, though so far I omitted the OVR files in that vision.'' Caine 2011-10-10 12:33UTC

PanoramaMilky: Would be cool if it could "launch" apps. You could "test" the app, then quit it. PanoramaMilky must then have the previously launched app selected so that you can immediately "remove" or keep it.

''Already planned, though I'll probably fork MilkyTest to create a more fleshed out UI under a different name. MilkyTest was always about testing milky-plugin. I'll post more on this to panorama's beta thread.'' - B-ZaR 2011-10-10 05:41Z

=== Launch + overview ===

Currently MiniMenu allows a filesystem like browsing with metaphors like tabs as categories / subcategories as subfolders within that tabs, and some generated meta categories like "All".

These additional display modes would help:

==== New meta category "Fresh", "By Date Added", "By Date Published" ====

This is for aiding the "test" process, particularly showing yet untested or fresh apps.

Implementation could be hard: As the PND has no central registry, but rather "certain files at certain places", which are scanned to then provide a "certain basis for certain launchers", the tracking of this dates or usage amounts must happen within that scanners/launchers, which must either have the "test" and "tag" abilities themselves, or must make that data available to those applications. Does anyone know what according data is tracked within MiniMenu?

==== Rating and/or favorite system. ====

Date source for "favorite" and/or "sorting" is provided by from your "tagging" (overrides). In addition the "launch" application may have its own methods to "rate" or "favor" applications. (Again this would be good for the approach: "Run app, test app, tag it".)

MiniMenu should show a tab "Favorites", which contains all apps, which are flagged as "favorite" or which have a rating above a certain treshold (i.e. on a scale from 1-5, all which are equal or higher than 4).

MiniMenu should show one tab "By rating", which contains all apps, sorted by rating (as sort key 1, and by alphabet as sort key 2).

If you navigate within the categories and sub-categories folders/tabs, a certain hotkey or menu command, should trigger the "favorite display" or "sorted display", which filters/sorts the contained items accordingly.

Pressing favorite hotkey first: Shows only favorites.
Pressing favorite hotkey again: Shows favorites on top of others.
Pressing favorite hotkey again: Disables favorite view mode, normal view again.

Pressing sort hotkey first: Sorted from best to worst
Pressing sort hotkey again: Sorted from worst to best
Pressing sort hotkey again: Disables sort view mode, normal view again.