Re: [Discuss-gnuradio] [GSoC] GNU Radio Companion Extensions: Output C++ Code

Hi Sebastian, awesome! :) I've had a look at your code, it looks like a sensible way to start tackling this feature. About the parameter values, thanks for bringing that up! It sure does complicate things, but from what I can see your suggestion sounds like a good plan. Best regards, Håkon

Re: [Discuss-gnuradio] [GSoC] GNU Radio Companion Extensions: Output C++ Code

On 03/31/2017 07:32 AM, Koslowski, Sebastian (CEL) wrote: > Dear Håkon, > > I am very excited to see interest in this topic! A few additional comments: > > - Any new templating should be done using Mako. The new YAML format > Martin mentioned roughly looks like this: The more I think about it,

Re: [Discuss-gnuradio] [GSoC] GNU Radio Companion Extensions: Output C++ Code

Dear Håkon, I am very excited to see interest in this topic! A few additional comments: - Any new templating should be done using Mako. The new YAML format Martin mentioned roughly looks like this: """ id: blocks_add_const_vxx label: Add Const parameters: - id: type label: IO Type

Re: [Discuss-gnuradio] [GSoC] GNU Radio Companion Extensions: Output C++ Code

Hi Martin, okay, I see. This is useful information, thanks a lot! Best regards, Håkon Vågsether There's another thing: On 3.8, we'll be going to a different model of > writing GRC bindings (YAML-based). It's difficult to summarize the > changes, but basically, don't assume that we'll be using

Re: [Discuss-gnuradio] [GSoC] GNU Radio Companion Extensions: Output C++ Code

Hi Marcus, thank you for your feedback. > Also, would kind of had preferred to read "I've not used GNU Radio much > before, but I've played around with the LiveDVD (or whatever you'd have > done)" instead of reading "I've not used GNU Radio before(at all)" and > seeing you use pretty dated

Re: [Discuss-gnuradio] [GSoC] GNU Radio Companion Extensions: Output C++ Code

Hi Ben, thank you for your comments. On Wed, Mar 29, 2017 at 6:33 PM, Ben Hilburn wrote: > Hi Håkon - > > Hah, indeed, your update and my e-mail flew past each other. I just took a > read over your update, and have some further comments: > >- I see you added some

Re: [Discuss-gnuradio] [GSoC] GNU Radio Companion Extensions: Output C++ Code

There's another thing: On 3.8, we'll be going to a different model of writing GRC bindings (YAML-based). It's difficult to summarize the changes, but basically, don't assume that we'll be using XML files forever. -- M On 03/29/2017 08:52 AM, Ben Hilburn wrote: > Hi Håkon - > > Welcome! I'm

Re: [Discuss-gnuradio] [GSoC] GNU Radio Companion Extensions: Output C++ Code

Woops, forgot to actually add the link. gsoc.pdf Sorry! :) Best regards, Håkon Vågsether 29. mar. 2017 5.53 p.m. skrev "Håkon Vågsether" : Hi Marcus, thank you for your feedback! You've

Re: [Discuss-gnuradio] [GSoC] GNU Radio Companion Extensions: Output C++ Code

Hi Håkon - Welcome! I'm really excited to see someone tackling C++ Code Generation. As Marcus said, it's something that people have been asked about for years, and it would be great to get it implemented. A few questions / suggestions on your proposal: - As Marcus mentioned, simple proposals

Re: [Discuss-gnuradio] [GSoC] GNU Radio Companion Extensions: Output C++ Code

Dear Håkon, cool! The C++ output option for GRC has been on many wishlists for a long long time. I do like the brevity of your proposal, however I miss a bit of you describing /how/ exactly you want to do things, and what to focus on in which order. We're well aware of this specific idea being

[Discuss-gnuradio] [GSoC] GNU Radio Companion Extensions: Output C++ Code

Hello! My name is Håkon Vågsether, and I am a first year MSc student in Cybernetics and Robotics at NTNU's (Norwegian University of Science and Technology, Trondheim). I am very interested in participating in GSoC 2017 for GNU Radio and I have added a link below to my proposal draft for the GRC