GRC Code Organization: Difference between revisions

From GNU Radio
Jump to navigation Jump to search
No edit summary
No edit summary
 
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
These notes are an attempt to figure out how big of a project porting from pygtk to pyqt will be, by identifying which files have pygtk code and how much of it.
These notes are an attempt to figure out how big of a project porting from pygtk to pyqt will be, by identifying which files have pygtk code and how much of it.


/gnuradio
All of the pygtk code is in gnuradio/grc/gui, other than a few lines in gnuradio/grc/scripts
  /grc
 
    /blocks - '''no pygtk''', these are just yml definitions for built in blocks (e.g. variable, pad, options, note)
gi is GObject Introspection which seems to be a python GTK thing
    /converter - ''no pygtk'', this is code to convert from old xml to new yml format
 
    /core -
grc uses GTK 3.0 and PangoCairo 1.0 which seems to be a way to render text using GTK
    /gui
 
    /scripts - contains gnuradio-companion and grcc scripts, which have a few lines of pygtk
the entry point for GRC is in /gnuradio/grc/'''main.py''' which has no actual GTK code in it, it calls '''Application'''()
    /tests - ''no pygtk'', just a bunch of test scripts

Latest revision as of 20:43, 19 May 2019

These notes are an attempt to figure out how big of a project porting from pygtk to pyqt will be, by identifying which files have pygtk code and how much of it.

All of the pygtk code is in gnuradio/grc/gui, other than a few lines in gnuradio/grc/scripts

gi is GObject Introspection which seems to be a python GTK thing

grc uses GTK 3.0 and PangoCairo 1.0 which seems to be a way to render text using GTK

the entry point for GRC is in /gnuradio/grc/main.py which has no actual GTK code in it, it calls Application()

Retrieved from "https://wiki.gnuradio.org/index.php?title=GRC_Code_Organization&oldid=5057"