Hello! I tried to google this but didn't find anything, if this has been asked before, I'd love to be pointed in the right direction!
There is a bunch of code corresponding to different tabs that should always appear in many different options of an extension I'm creating. Since they are all the same code, I'd like to create the code for them separately and then just input it inside of each main inx file.
I know that usually, with XML files, we can do this with: <!ENTITY otherFile SYSTEM "otherFile.xml">
Also if it did work, it might make things more difficult.
The xml <param> entry in the .inx maps to a pars.add_argument in the .py file.
I think it would become hideously complex if it was possible, that is because the .inx has no dynamic features - so you cannot use variables to give names/ids to the <params> you have created on the fly.
Even using Glade and Gtk3 I would avoid.
The only time I have done this, is when the number / type of gui widgets are determined by data.
For example - a table in Gtk3 - which grows dynamically depending upon the data source.
Hello! I tried to google this but didn't find anything, if this has been asked before, I'd love to be pointed in the right direction!
There is a bunch of code corresponding to different tabs that should always appear in many different options of an extension I'm creating.
Since they are all the same code, I'd like to create the code for them separately and then just input it inside of each main inx file.
I know that usually, with XML files, we can do this with:
<!ENTITY otherFile SYSTEM "otherFile.xml">
Is something like this possible with inx files?
I would expect this not to work.
Also if it did work, it might make things more difficult.
The xml
<param>
entry in the.inx
maps to apars.add_argument
in the .py file.I think it would become hideously complex if it was possible, that is because the
.inx
has no dynamic features - so you cannot use variables to give names/ids to the<params>
you have created on the fly.Even using Glade and Gtk3 I would avoid.
The only time I have done this, is when the number / type of gui widgets are determined by data.
For example - a table in Gtk3 - which grows dynamically depending upon the data source.
I see, bummer! Specially since I wanted to really just do the simplest thing with it...
Thanks anyway for your reply :)