Paul, I applaud your use of xml for data persistence. I don't think you will get any argument from the rest of the programmers about that. I did some early experiments on a "different" UI (not to be confused with the "new architecture") using it in basically the same manner as you have. My motivation was to be able to store and recall a large number of very precise radio configuration plus get the benefit of not having a proprietary database. Someone will have to write a good xml editor so those who like to play directly with the configuration data can do so without blowing things up.
In the "new architecture" version of CAT, the dictionary will be in an xml file as opposed be being stored in code as it is now. I have done a lot of work over the past few months (mostly bringing myself up to speed) using regular expressions to parse the CAT commands. This technique seems to work quite well and certainly gets rid of a lot of ugly code. I can't speak for FlexRadio as I'm just a volunteer programmer like you, but I can say there has been no attempt to keep any of the development secret. Eric, Bob, and Frank have been very generous in answering all my dumb questions when answers were available. Sometimes the anwser is "I don't know" or "we haven't gotten that far yet". The concepts are just now becoming firm enough for any kind of meaningful discussion. This is still the greatest adventure going ... for me anyway! 73, Bob, K5KDN -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Paul Shaffer Sent: Tuesday, August 29, 2006 5:14 PM To: [email protected] Subject: Re: [Flexradio] A modified PowerSDR architecture One thing I would add is a well defined interface for plugging in digital mode processing software and UIs, thus eliminating the need for VAC. I think it could be done. I reworked the powersdr console and setup classes to conform to vs2005 requirements for threading. I made extensive use of data binding for the setup and console forms. I haven't done anything on it since March. The source code for it is at http://www.cyberplasm.com/temp/xmldemo.zip. There is no access database required, all settings are persisted in xml. Much of the console UI is non-functioning, but the settings form is mostly complete. The classes could be refactored in numerous ways to support a new architecture. Flex is doing their own thing for a new version with Eric and outside contributors, so they are really the ones in control. They don't comment on the details I guess. The radio interface is really simple when you get into it, just set the frequency, mode, filter edges, volume plus a few other settings. Its already defined in dttsp. _______________________________________________ FlexRadio mailing list [email protected] http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/ FlexRadio Homepage: http://www.flex-radio.com _______________________________________________ FlexRadio mailing list [email protected] http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/ FlexRadio Homepage: http://www.flex-radio.com
