On Mon, Nov 22, 2010 at 10:47 AM, Gary L. Robinson <[email protected]>wrote:
> I feel a little bit differently about making a Linux version. I really > want > to see one and obviously, no matter how it is done, I will be looking > forward to it. However, I hope Flex does NOT go the cross compiler route > for their Deep Impact Linux version. I am not sure you mean cross-compiler. I cannot imagine compiling on something other than the native platform for Linux. > Especially, in terms of the GUI, that will be somewhat limiting. This implies you are talking about a standard graphics library rather than cross-compiling. > W1HKJ uses the MingW cross compiler and the FLTK > (fast light tool kit) that defines the GUI. While I am a HUGE fan of > FLDigi > and it is my preferred program the L in FLTK really means LIGHT and > LIMITING. Trying to do an interface that looks like the present PowerSDR > or > anything too fancy and it rapidly becomes a lot more work with the > underlying limitations of the FLTK. > So, if you don't like that graphics library, use a different one. > Having separate versions that are all (or mostly) compiled separately may > have more "up front" cost in terms of time and money BUT going the cross > compiler route puts you in a confining box that may cost you functionality > and create more problems down the line - especially with an evolving piece > of software that controls a real piece of hardware more than just keying a > transmitter and reading/settings it's frequency. > Gary, I think that the goal is to come up with a set of protocols that allow the control functions and display functions to be separated from the RF, IF, and DSP functions. Right now the logic inside the processing is tightly bound to the logic in the GUI. That is a MONUMENTALLY STUPID ARCHITECTURE, as we are all learning. As I understand it, DI will separate these. That will allow anyone to write their own GUI using whatever toolkit they like best, or even make the radio command-line driven, something that offers its own set of advantages when it comes time to build an automated radio. It opens up multiple languages as well. No reason Frank couldn't write his front-end in Lisp while the "standard" front-end is written in Java for easy portability to all three major platforms. You could write your own in whatever language you like using whatever GTK floats your boat. It is really time for people to stop thinking in terms of how PowerSDR currently works. DI will be separate programs to run the radio and interface with the user. It will be a LOT more flexible for everyone. We *SO* need to get PSDR 2.0 put to bed so that development can proceed apace on DI. Yo, Flex! Put the PSDR feature set in concrete and then don't touch it ever again! :-) -- Brian Lloyd, WB6RQN/J79BPL 3191 Western Dr. Cameron Park, CA 95682 [email protected] +1.767.617.1365 (Dominica) +1.931.492.6776 (USA) (+1.931.4.WB6RQN) _______________________________________________ Flexedge mailing list [email protected] http://mail.flex-radio.biz/mailman/listinfo/flexedge_flex-radio.biz This is the FlexRadio Systems e-mail Reflector called FlexEdge. It is used for posting topics related to SDR software development and experimentalist who are using beta versions of the software.
