On 7 December 2011 09:02, Frank A. Stevenson <fr...@hvitehus.no> wrote: > 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.
>From a usability point of view, I would think a touch screen combined with a waterfall display would be perfect for tuning a mobile / handheld. > 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. If enough people are involved in the coding (for example, one working on the SDR part and one working on the UI, though hopefully this would be one team on each) then this should arise naturally and there would also be less manpower. I'm inexperienced with GUI programming but I am learning, and will happily be part of a volunteer effort to do this. 73, Dan MD1CLV ------------------------------------------------------------------------------ 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
