From: Daniel Browne <dbrowne@(email surpressed)> Subject: GUI Elements Date: Mon, 06 Jun 2011 15:05:28 -0400 |
Msg# 2105 View Complete Thread (4 articles) | All Threads Last Next |
Hi Greg, Is there a guide anywhere to the various specifiers/placeholders you use in your submit script GUI's? I have our Maya (python) submit set up to render from a copy of the scene file, but I want to show the user based on the scene file's location where the render copy will be made. I can do this with the locals() format substitution done for the submit form, but the only placeholder for text within a form I can find that works is <<HEADING>>. Without it, the text by itself doesn't show because its hidden behind the tab layout. -Dan ---------- Dan "Doc" Browne System Administrator Evil Eye Pictures dbrowne@(email surpressed) Office: (415) 777-0666 x105 |
From: Greg Ercolano <erco@(email surpressed)> Subject: Re: GUI Elements Date: Mon, 06 Jun 2011 15:26:14 -0400 |
Msg# 2106 View Complete Thread (4 articles) | All Threads Last Next |
On 06/06/11 12:05, Daniel Browne wrote: > Is there a guide anywhere to the various specifiers/placeholders you use in= > your submit script GUI's? Yes, the 'input' program's command language is documented here: http://www.seriss.com/rush-current/input/ ..however, it /doesn't/ cover the new 'ascii art' format that I've been using in the last few years, which gets converted into the above command language by a large block of logic in .common.pl. All that ascii art stuff (eg. <<HEADING>>, etc) was developed to simplify the specification of the input forms, and was never documented, it was just kind of 'developed'. I figured anyone wanting to customize the input forms would either just add simple fields, or rewrite the GUI in a more flexible GUI builder, like pyqt + qtdesigner, or pyfltk. I'll try to follow up to this thread, though, with a description of the 'ascii art' placeholders. If you're writing python code, and want to make your own 'ascii art' forms, you may want to use the new input program (that will be in the next release) which I can provide you that handles reading the 'ascii art' forms directly, instead of needing all that perl logic in .common.pl to convert it. I was confronted with that issue when I did the python port of submit maya, and modified the input program to parse the ascii art stuff directly, so that both python and perl (and other languages) could make ascii art forms easily. > I have our Maya (python) submit set up to render= > from a copy of the scene file, but I want to show the user based on the sc= > ene file's location where the render copy will be made. I can do this with = > the locals() format substitution done for the submit form, but the only pla= > ceholder for text within a form I can find that works is <<HEADING>>. Witho= > ut it, the text by itself doesn't show because its hidden behind the tab la= > yout. Note that blank lines allow you to add 'vertical space' into the form. If you email me directly your code that generates the form and the screen shot showing the problem, I can surely help you get it to work right. -- Greg Ercolano, erco@(email surpressed) Seriss Corporation Rush Render Queue, http://seriss.com/rush/ Tel: (Tel# suppressed)ext.23 Fax: (Tel# suppressed) Cel: (Tel# suppressed) |
From: Daniel Browne <dbrowne@(email surpressed)> Subject: Re: GUI Elements Date: Mon, 06 Jun 2011 21:46:51 -0400 |
Msg# 2107 View Complete Thread (4 articles) | All Threads Last Next |
Thanks Greg. I actually had to go back to using a regular input field due to the way data is passed to the input routine in this script. I was not able to get the input engine to recognize the guy elements (i.e. box {}) directly. How do I create a custom launcher app? The included ones seem to break when I duplicate and edit them. On Jun 6, 2011, at 12:26 PM, Greg Ercolano wrote: [posted to rush.general] On 06/06/11 12:05, Daniel Browne wrote: > Is there a guide anywhere to the various specifiers/placeholders you use in= > your submit script GUI's? Yes, the 'input' program's command language is documented here: http://www.seriss.com/rush-current/input/ ..however, it /doesn't/ cover the new 'ascii art' format that I've been using in the last few years, which gets converted into the above command language by a large block of logic in .common.pl. All that ascii art stuff (eg. <<HEADING>>, etc) was developed to simplify the specification of the input forms, and was never documented, it was just kind of 'developed'. I figured anyone wanting to customize the input forms would either just add simple fields, or rewrite the GUI in a more flexible GUI builder, like pyqt + qtdesigner, or pyfltk. I'll try to follow up to this thread, though, with a description of the 'ascii art' placeholders. If you're writing python code, and want to make your own 'ascii art' forms, you may want to use the new input program (that will be in the next release) which I can provide you that handles reading the 'ascii art' forms directly, instead of needing all that perl logic in .common.pl to convert it. I was confronted with that issue when I did the python port of submit maya, and modified the input program to parse the ascii art stuff directly, so that both python and perl (and other languages) could make ascii art forms easily. > I have our Maya (python) submit set up to render= > from a copy of the scene file, but I want to show the user based on the sc= > ene file's location where the render copy will be made. I can do this with = > the locals() format substitution done for the submit form, but the only pla= > ceholder for text within a form I can find that works is <<HEADING>>. Witho= > ut it, the text by itself doesn't show because its hidden behind the tab la= > yout. Note that blank lines allow you to add 'vertical space' into the form. If you email me directly your code that generates the form and the screen shot showing the problem, I can surely help you get it to work right. -- Greg Ercolano, erco@(email surpressed) Seriss Corporation Rush Render Queue, http://seriss.com/rush/ Tel: (Tel# suppressed)ext.23 Fax: (Tel# suppressed) Cel: (Tel# suppressed) ---------- Dan "Doc" Browne System Administrator Evil Eye Pictures dbrowne@(email surpressed) Office: (415) 777-0666 x105 |
From: Greg Ercolano <erco@(email surpressed)> Subject: Re: GUI Elements Date: Tue, 07 Jun 2011 01:58:24 -0400 |
Msg# 2108 View Complete Thread (4 articles) | All Threads Last Next |
On 06/06/11 18:46, Daniel Browne wrote: > Thanks Greg. I actually had to go back to using a regular input field due > to the way data is passed to the input routine in this script. Can you describe more of what you're doing? Maybe include some examples and such. > I was not able to get the input engine to recognize the [gui] elements > (i.e. box {}) directly. Take a look at the rush/examples/input-example.pl or for python, the rush/examples/input-example.py These show simple examples of how the input elements work. Some of the older submit scripts still use the raw input command language instead of the ascii art stuff, eg. submit-arnold.pl. Search that file for "Arnold-Submit" and you'll find the beginning of the input command file. Also, you can find the raw input command language generated from the ascii art as ~/.rush/submit-xxxx.in You can then take this, paste it into a python script and modify it to taste, and pass it to the input program to customize. For instance, when I run submit-maya.pl, I end up with: ------------------------------------------------------- $ ls -la ~/.rush/submit-maya.in -rw-rw-rw- 1 root root 18076 Jun 6 12:30 /root/.rush/submit-maya.in $ more ~/.rush/submit-maya.in window { name "Rush Maya Submit" xysize 720 546 color 49 resizable menubar scroll 1 saveid "Maya-Submit" } xy 150 25 # EMPTY 'SEPARATOR' BOX box { align 0 type 0 # use '1' for debugging color 0 xywh 0 25 8 8 } [..] ------------------------------------------------------- ..and to bring up the input interface for that file, I can run: ------------------------------------------------------- $ /usr/local/rush/examples/bin/input -d ~/.rush/submit-maya.in ------------------------------------------------------- ..and the interface pops up. -- Greg Ercolano, erco@(email surpressed) Seriss Corporation Rush Render Queue, http://seriss.com/rush/ Tel: (Tel# suppressed)ext.23 Fax: (Tel# suppressed) Cel: (Tel# suppressed) |