On Tue, 2011-12-06 at 15:23 -0800, Bruce Perens wrote: [SNIP] > The plan is to produce a mobile first, because we know we can fit > everything in the form factor today. The radio design presently looks a > lot like USRP with a multi-band receiver front-end and transmitter, a > speaker amplifier and microphone preamp, a Linux system as the built-in > "host" and application platform, and a touch-screen as the user interface.
I would like to caution against going for a touch screen user interface. I have worked on such writing touch GUI framework code for years, and the complexity of making a good touch UI should not be underestimated. The work involved will also detract significantly from the development effort needed for just a working SDR radio. My advice would be to aim lower in the UI look and feel, but still a little higher than the current mass marked radio. Ex colour screen 320x240, fixed bitmap fonts. Directional navigation key, numeric keypad. Menu driven UI, with some nice widgets (waterfall etc) Most importantly, there needs to be a very very clean separation between UI code and the radio layer, (event driven), such that a touch UI can be added later without having to do major changes to the radio layer. Frank ------------------------------------------------------------------------------ Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ _______________________________________________ Freetel-codec2 mailing list Freetel-codec2@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freetel-codec2
