A few points: 1. The demos we ran on iPads at Dayton 2012 were screen sharing applications showing the .NET windows app. No native iOS app from Flex was involved. 2. We have 2 layers of APIs defined at this point. One at the ethernet layer and one in .NET to facilitate further Windows client development. Each was necessary to complete a Windows client (where the majority of the market in general, and our customers specifically reside). 3. The ethernet API which is being proven in the windows client, can (and will) be used to enable clients on other platforms. 4. We looked around at what the major players in the technology world are doing and what we found was that everyone was doing native apps for each platform (for example, you are seeing google do gmail/drive/maps apps for iOS/android/etc). With this in mind, we chose to follow this model with an emphasis on defining a clear API at the ethernet level to speed development. This is a different approach than trying to build the one-size-fits-all cross platform application.
Eric Wachsmann FlexRadio Systems On Tue, May 21, 2013 at 10:40 AM, Mickey Baker <[email protected]>wrote: > Tim wrote: > > At this time, FlexRadio Systems is only working on the Windows client. > > There have been no announcements regarding any different client software. > > That's all I know, Ed, although multiple client support was a clear future > at product announcement. Demos were running (obviously mockups) at Dayton > 2012 on iPads. > > "Free beer tomorrow." > > 73, > > Mickey N4MB > > On Tuesday, May 21, 2013, Ed Haskell wrote: > > > Mickey, did I miss something? Did Flex Radio announce that the only > > interface software will be this .NET package or is it just the first of > one > > or more others? > > > > Ed W1PN > > > > > > On Tue, May 21, 2013 at 11:28 AM, Mickey Baker > > <[email protected]<javascript:_e({}, > 'cvml', '[email protected]');> > > > wrote: > > > >> Thanks, Tim, for your frank and cogent answers, although I must tell you > >> that I am disappointed in what appears to be a divergence in product > >> direction for the client. > >> > >> .NET is itself a proprietary system that makes cross-development for > >> non-windows platforms that much tougher. Last year's exhibit of iPads > >> running simulation code gave me hope that y'all were committed to a true > >> lightweight, cross platform client. It is now clear that expediency won > >> out over design intent in this case. > >> > >> I've not complained the first time about late product. I know that > >> engineers and software people are basically optimistic people or they > >> would > >> have never chosen these careers, and that good intentions do not resolve > >> development issues. I have stood in front of angry customers and tried > to > >> explain late product and I know that it is uncomfortable and that things > >> take as long as they take. > >> > >> But the choice to go Windows only, painting development into that corner > >> with .NET, is my biggest disappointment yet. > >> > >> 73, > >> > >> Mickey N4MB > >> > >> > >> On Tuesday, May 21, 2013, Tim Ellison wrote: > >> > >> > See my answers in-line below > >> > > >> > Tim Ellison > >> > On 5/21/2013 9:22 AM, Mickey Baker wrote: > >> > > >> > Tim, > >> > > >> > That seems clear at this point. > >> > > >> > A few related questions that were outstanding and answered vaguely at > >> > Dayton 2012, but I'm checking to see if the answers have changed... > >> > > >> > Where does the "ubiquitous client" stand? You'll recall discussion > >> about > >> > tablet, Mac and Linux support, but "not in the first release." Are > there > >> > resources working on this, given the .NET 4.0 decision? Has the > roadmap > >> > changed? > >> > > >> > At this time, FlexRadio Systems is only working on the Windows client. > >> > There have been no announcements regarding any different client > >> software. > >> > > >> > > >> > Since there will be an ongoing cost for SmartSDR support, and > >> apparently > >> > there is no open source client, has a decision been reached to release > >> > specifications so that third part developers (that aren't employed by > >> > FlexRadio Systems) can produce client software? Or not to do so? > >> > > >> > Yes. There is an evolving API available to developers to facilitate > the > >> > communication between a client and the radio. > >> > > >> > > >> > Thanks and 73, > >> > > >> > Mickey N4MB > >> > > >> > > >> > > >> > > >> > On Tuesday, May 21, 2013, Tim Ellison wrote: > >> > > >> > James T, SmartSDR is *not* a browser application, it is a Windows WPF > >> > application that uses .NET 4.0. > >> > > >> > All you have to do is connect the FLEX-6000 to your wired Ethernet > LAN, > >> > install SmartSDR on a Windows XP SP3 and above PC that is also > >> connected to > >> > the same LAN, start SmartSDR, choose your FLEX-6000 from the radio > >> > discovery list and you are operational. > >> > > >> > The other standard radio connections apply; 13.8 VDC power supply > >> > connection, antenna, speakers or headphones, microphone or key. > >> > > >> > Tim Ellison > >> > On 5/21/2013 2:34 AM, Michael Hasenfratz wrote: > >> > > >> > Neal, > >> > > >> > I don't think SmartSDR is a browser app. I believe it is a Windows > >> APP; > >> > otherwise, it would be MAC comparable. > >> > > >> > Michael Hasenfratz > >> > ======================== > >> > Light travels faster than sound. > >> > This is why some people appear bright until you hear them speak. > >> > > >> > On May 20, 2013, at 11:00 PM, "James T Kirk" < > [email protected]> > >> > wrote: > >> > > >> > Speaking of slathering, what type of “guaranteed setup” do you need > for > >> > your signature SDR other than an Ethernet port and browser capability? > >> It’s > >> > is one step up from plugging in a monitor...not necessarily a bad > thing. > >> > The VT100 lives on. > >> > > >> > From: Neal Campbell > >> > Sent: Monday, May 20, 2013 7:07 PM > >> > To: James T Kirk > >> > Cc: [email protected] > >> > Subject: Re: [FlexEdge] FLEX-5000A End of Manufacturing Announcement > >> > > >> > You are right because it really doesn't matter what the "procurement > >> > difficulties" were. > >> > > >> > One thing I could sense while working at the Flex booth last weekend: > >> > These guys are all really excited about this rig and the things they > >> have > >> > dreamed up for it. > >> > > >> > They have drunken their own koolaid. > >> > > >> > Being in senior management for most of my career, I have seen fake > >> > enthusiasm slathered on defective products that would never provide > 10% > >> of > >> > promised functiona > >> -- > >> Mickey Baker, N4MB > >> Fort Lauderdale, FL > >> *“Tell me, and I will listen. Show me, and I will understand. Involve > me, > >> and I will learn.” *Teton Lakota, American Indian Saying. > >> _______________________________________________ > >> Flexedge mailing list > >> [email protected] <javascript:_e({}, 'cvml', > >> '[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 innovation and other > >> technical SDR topics. > >> > > > > > > -- > Mickey Baker, N4MB > Fort Lauderdale, FL > *“Tell me, and I will listen. Show me, and I will understand. Involve me, > and I will learn.” *Teton Lakota, American Indian Saying. > _______________________________________________ > 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 innovation and other > technical SDR topics. > _______________________________________________ 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 innovation and other technical SDR topics.
