Difference between revisions of "GRCWG"

From GNU Radio
Jump to navigation Jump to search
(Imported from Redmine)
 
(remove old information re: a GRC-specific github repo)
 
Line 47: Line 47:
* We meet semi-regular to discuss current and upcoming develop work.
* We meet semi-regular to discuss current and upcoming develop work.
** Calls are always announced on the mailing list
** Calls are always announced on the mailing list
* GRC is maintained in a separate repository on GitHub (https://github.com/gnuradio/gnuradio-wg-grc)
** All patches and contributes are merged here before pulling them into the main GR repo.
* Ideas and new developers are always welcome =)
* Ideas and new developers are always welcome =)

Latest revision as of 20:19, 26 January 2018

GNU Radio Companion Working Group[edit]

The GNU Radio Companion Working Group (GRCWG) was created to develop new features for the GNU Radio Companion (GRC) and improve its user experience.

GRCroadmap

Tasks / Projects[edit]

  • Tutorials
    • Developing for GRC
      • description of different parts of GRC, gr-qtgui, and the qtport.
      • Go over the basics of the workflow: where to submit PRs, setting up the GRC environment, executing from the source tree, etc.
      • List some different tutorials for PyQT, QT, QSS, GTK, etc.
  • Wiki
    • Update to fit the current status of GRC:
      • Current works in progress
      • general areas
      • things we are brainstorming
    • Add an indication of the level of effort required to work on these features
  • Documentation
    • update the GRC wiki page to include newer features
    • how to write block XMLs
    • add button to open doxygen pages
  • Usability
    • add examples menu
  • Features
    • block groups (for e.g. variables)
    • remote fg execution
    • frames (visual sugar to replace note blocks)

Long-term goals[edit]

  • port GRC from GTK to QT
    • relaunch port w/o rewrite of the of flowgraph ui
  • Python3k support
    • find an alternative to Cheetah (not py3k compatible)
  • cleap-up and refactoring =)

Mode of operations[edit]

  • We meet semi-regular to discuss current and upcoming develop work.
    • Calls are always announced on the mailing list
  • Ideas and new developers are always welcome =)