Minimenu is probably not a good 'base'; it does the job, and is straight forward, but its 'dumb' in a lot of ways, and makes a lot of assumptions (ie: its code is decent at what its for, but not generalized to be pluggable for other sorts of things.)
Reason: cpasjuste was working on a simplified launcher, but had some RL time constraints or whatever and didn't see mable to deliver in time for the 'official Pandora launch date, part 2'; ie :we'd all gotten our dev units with only a couple of weeks to deliver a userland, so we were going full speed to make .. everything
Craig came along to ask me 'I dont' think cpasjuste will be done, can you make a simple menu and have it ready in 2 weeks?' (or maybe a week, I forget now.) The core of mmenu was written in 4 nights. That doesn't leave a lot of time for elegance, I assure you
At the same time, mmenu was written to run pretty fast, be portable and easy to work with (its SDL, so that it coudl run on X, on /dev/fb, or whatever), and builds on a desktop as well as Pandora no problem. It can do pnd's itself, or do .desktop type work. It does okay, and runs with almost no memory footprint (since it usually exits when running an app.)
So .. it has some good ideas, but I'd rather rewrite it if we wanted to use at all; it should just present a framework (theres that word..) for launching apps; a protocol for communicating with them, and hooks for any future needs .. actions, screen savers, overlay panels, etc. The look and feal and so on, shoudl be plugins, that leverage the core to do work. A consistent interface approach.
Right now, mmenu was 'a different desktop'; the new device shoudl not have 'use desktop A, or desktop B' sort of thing for mmenu; there shoudl be your desktop choice, and mmenu (or whatever) should plug into _that_; we've got the processing power, so why isn't mmenu/etc just a plugin to the DE, or to the window manager? Really just a consistrent API to device specific features. A social media manager, etc.
So, I would suggest a different concept entirely, and a different way of going about it.
--> but if that ends up being 'too heavy' and slow, then I'd also suggest a mini menu that doesn't do any of that, andjust presents a menu to run stuff. But I woudlnt' write it liek mmenu is.. I'd do it as a thin layer on top of a very basic tiled window manager.
I'm certainly open to working on userland firmware for the pyra, but I have less time than I used to.. each year, less and less, with kids and all; fortuantely we have many peopel taking the charge, so we can have a team
jeff