On Mon, May 09, 2011 at 03:23:21PM -0400, Philip Balister wrote: > Rather than flog the topic of what is wrong with GNU Radio, I'd > prefer to emphasize that it is only as good as we make it. So how > can we make it better. Here are some of my thoughts: > > 1) Expand the pool of people contributing code. > > 2) Improve the grc help files and parameter descriptions. > > 3) Divide the code base in to true core functions, signal processing > libraries, and applications.
3a) Remove inconsistencies which have popped up due to the organic 'growth' of GNU Radio over the last years. > 4) Use cmake instead of autotools. (Not my first choice, but may > help the windows people) 5) Improve the development interface. When you're developing stuff with GNU Radio, you'll probably be using a lot of existing blocks and adding a few of your own. This process is still quite clumsy in my opinion and would be easier if - there were better DSP debugging tools (e.g. nicer graphical sinks you can simply connect your blocks -- I'd say that anytime I need to pipe the output from a block into a file_sink and then analyse it with Matlab, that's when the development interface is lacking), - GRC could be tied into the development chain (e.g. inspect hier_blocks by double-clicking them, inspect output of individual sub-blocks) MB -- Karlsruhe Institute of Technology (KIT) Communications Engineering Lab (CEL) Dipl.-Ing. Martin Braun Research Associate Kaiserstraße 12 Building 05.01 76131 Karlsruhe Phone: +49 721 608-43790 Fax: +49 721 608-46071 www.cel.kit.edu KIT -- University of the State of Baden-Württemberg and National Laboratory of the Helmholtz Association
pgp83euXPyxUw.pgp
Description: PGP signature
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
