All you said make a lot of sense. I agree with you, especially about the file structure, and the control schemes. In my opinion for both of the mentioned topics, dingux should mimic the original firmware.
On Windows systems, you can achieve this by using programs like Total Commander.
I don't use windows, and I don't like to suggest using non-standard/odd tools. I am for the "Keep it small and simple" phylosopy. We can "create" our system from scratch.. why should we make it complex to manage?
Besides, we're looking forward an idea of using ipkg/opkg package system instead of local packs, and that should render the replacing/updating of the apps more handy.
That's why I wrote my how-to. Unfortunately I had no feedback from developers, and I have not the will/time to package all the available apps myself.
Dingux applications should come with a predefined metadata file, with information about the application (title/developer/version/command-line parameter definition etc). specification to be determined, possibly extension of DMenu spec.
This would be included into the control file for ipkg/opkg.
Dingux executables should ideally come with their own default icon, named like the executable, but with the icon (.png?) extension.
I agree again. Unfortunately this won't work with dmenu.
The problem is that dmenu is generally bad designed IMO: I don't see the need for different config files for every theme. It just makes it more difficult to add software, and make it crash when you wrong something (i.e. you don't have a theme-specific icon). I have shown how this could be handled with ipkg, but i am really looking forward to avoid it at all.
XMB looks better, natively embeds some useful applications like the picture viewer or the audio player, and is a more mature project, even though came to dingux later. Therefore I would not spend more time in making dmenu usable: it had his time. XMB just needs a file selector, that could be ripped off dmenu, in order to select roms to be passed to emus which don't embed a gui.
EDIT: last but not least, with dinguXMB a package manager could be not essential.
I would add to the list:
- dingux applicaitons and sources should be added to a common repository, being it openhandhelds, or a google code page, or whatever; so that the community could easily "burden the pain" of apply the modifications to "standardize" them (i.e. changing controls, file structure and adding package scripts).