Re: Best way to output decoded data to user

On Tue, Apr 15, 2014 at 4:35 PM, Martin B.
[email protected]wrote:

On 04/15/2014 06:14 AM, Francois Gervais wrote:

I’m trying to figure out the best way to print the decoded data
information of packets (received through gnuradio) to the user. File
outputs are not really user friendly so I’m thinking of using a message
queue out of my decoding block connected to the WX GUI Terminal Sink.

Generally: Don’t use a message queue. Also, I recommend not adding any
WX widgets, unless you hate QT, because we’re trying to move away from
them.

Moving away from wxWidgets? Then replace it with what?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

QT, like Martin was saying :slight_smile:

On 15.04.2014 16:27, Activecat wrote:

Generally: Don’t use a message queue. Also, I recommend not
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTTUMSAAoJEBQ6EdjyzlHttvkH/22+aG4q8CaHF/s7MKYJ/70D
gWmnsx4Dz4hd7kfPWomRQ7V4DPRfJwRXC3q7rUcPqAJ6A96bLmKasH5iuChsWF1c
U3CsJvlYH9pt71JGjTn/XgwgQSYoOVtZQLLChZLTIZQgGOd1zG6NiobjIl+ujmPe
73BizMtNDDyKSS0Us4s8JCrK8iUUP++ckqN+BbUllE/ZrN7BEP0AT6y4UlHzjSw7
2Lttn8D2nvrqk64fcKLjCgTXuvrrOXRtEZYsGILAmlWl/ZmUbKwP+T6zGatCMNOX
xcLFM/vS3160UU5fvXdDPfnQHcpoScqxyXRsxOu2Vqre5BS8rnQTB6s2mXlHgzc=
=lu9f
-----END PGP SIGNATURE-----

On 04/15/2014 04:32 PM, Marcus M. wrote:

QT, like Martin was saying :slight_smile:

Right. We’ve discussed this on several dev calls, not sure if here on
the list.
In the far future, we want to focus on QT (for less dependencies etc.).
We (or rather, Tom for the most part) have been porting all features of
WX to QT the last few months, and on the current master, there’s pretty
much nothing you can’t do with QT you could with WX.

But don’t worry, WX widgets will be around for a while, but we won’t be
adding functionality, and will be officially marking them deprecated
them (most likely) in 3.8. Maybe they will go away in 3.9, but that’s
a long way ahead, nothing definitive decided here.

Martin

On 04/15/2014 12:08 PM, Martin B. wrote:

adding functionality, and will be officially marking them deprecated
them (most likely) in 3.8. Maybe they will go away in 3.9, but that’s
a long way ahead, nothing definitive decided here.

Martin
If you thought the 3.6 to 3.7 transition was hard for people, doing a
transition where the WX widgets are no longer available will be
even harder, by a significant amount.


Marcus L.
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org

On Tue, Apr 15, 2014 at 12:11 PM, Marcus D. Leech [email protected]
wrote:

WX to QT the last few months, and on the current master, there’s pretty
transition where the WX widgets are no longer available will be
even harder, by a significant amount.


Marcus L.
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org

Which is why the WX widgets will stay around for a long time. (Longer
than
I’d want, I’m sure.)

Tom

On 04/15/2014 06:14 PM, Tom R. wrote:

Which is why the WX widgets will stay around for a long time. (Longer
than I’d want, I’m sure.)

Yes, we’ll make it as gentle as possible.
Also, there’s no reason for the WX widgets not to become an OOT. This
would make the transition even easier, and we might even be able to
provide a script to convert flow graphs to using the OOT with a couple
of seds.

Martin

On Tue, Apr 15, 2014 at 06:08:45PM +0200, Martin B. wrote:

But don’t worry, WX widgets will be around for a while, but we won’t
be adding functionality, and will be officially marking them
deprecated them (most likely) in 3.8. Maybe they will go away in
3.9, but that’s a long way ahead, nothing definitive decided here.

That is good to know. I use WX widgets in my class, including a video
series I’ll be publishing shortly, because they are the default in GRC
and because of a few features of the instrumentation sinks. Also
stability.

Mike

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs