From: Gary Jaeger <gary@(email surpressed)>
Subject: saved Forms
   Date: Fri, 15 Feb 2008 13:08:28 -0500

Gary Jaeger wrote:
> is it possible to have the "Save this Form" go to a central location,
> say a server? so that all artists have access to the same saved submit
> forms? or some other way of sharing these? other than exporting them one
> at a time.

	You have to watch out for "sharing" submit forms, since one person
	might change eg. the "Maya Flags", and save it, causing the next
	user to load that form not to realize that critical field was changed,
	and to have everything go haywire.

	The logic for 'the last form saved' is all in the submit script,
	so you can change it around if you want. The "$G::lastsubmit" variable
	contains that path to where that info is saved. Normally it is saved to
	the user's own home directory (unix), or in the case of windows,
	into the user's c:\temp directory.

	To have that data be global, on a server somewhere, you'd have to
	lock the data somehow, since each time someone submits, the
	'last saved' info is changed.

	Maybe what you want is to have some 'standard form' that gets merged
	in with the user's "last" data, so that all settings except maybe
	Cpus: and Scene File: get pulled in from a master template?

	You can do this by having a master file for each submit form on the
	server, and then when the script is run, code you add to the script
	merges that 'read only' template with the user's last saved data,
	preserving only the few fields you want from the user's last submission
	that is unique to them, such as their last submitted scene file and
	frame range, or some such.

	If you think that would help, I can give you some coding leads
	on how to do that.


-- 
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)

So I could end up with something like this in a hierarchical drop down:

VID
	VID100
	VID200
	VID300

CHT
	CHT100
	CHT200

etc. then I could save submits for dormant jobs even


On Feb 15, 2008, at 2:29 PM, Greg Ercolano wrote:

[posted to rush.general]

Gary Jaeger wrote:

is it possible to have the "Save this Form" go to a central location,

say a server? so that all artists have access to the same saved submit forms? or some other way of sharing these? other than exporting them one

at a time.

	You have to watch out for "sharing" submit forms, since one person
	might change eg. the "Maya Flags", and save it, causing the next

user to load that form not to realize that critical field was changed,

	and to have everything go haywire.

	The logic for 'the last form saved' is all in the submit script,

so you can change it around if you want. The "$G::lastsubmit" variable contains that path to where that info is saved. Normally it is saved to

	the user's own home directory (unix), or in the case of windows,
	into the user's c:\temp directory.

	To have that data be global, on a server somewhere, you'd have to
	lock the data somehow, since each time someone submits, the
	'last saved' info is changed.

	Maybe what you want is to have some 'standard form' that gets merged
	in with the user's "last" data, so that all settings except maybe
	Cpus: and Scene File: get pulled in from a master template?

	You can do this by having a master file for each submit form on the
	server, and then when the script is run, code you add to the script
	merges that 'read only' template with the user's last saved data,

preserving only the few fields you want from the user's last submission

	that is unique to them, such as their last submitted scene file and
	frame range, or some such.

	If you think that would help, I can give you some coding leads
	on how to do that.


--
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)

. . . . . . . . . . . .
Gary Jaeger // Core Studio
86 Graham Street, Suite 120
San Francisco, CA 94129
(Tel# suppressed)
http://corestudio.com	

Gary Jaeger wrote:
> So I could end up with something like this in a hierarchical drop down:
> 
> VID
> 	VID100
> 	VID200
> 	VID300
> 
> CHT
> 	CHT100
> 	CHT200
> 
> etc. then I could save submits for dormant jobs even

	Ya, I'd think a pulldown menu should be possible.

	It sounds like you might want to write a script that pre-generates
	all the form files, and have the submit form just pull an 'ls' listing
	of that directory to fillout the pulldown menu with the filenames,
	such that when the user changes the pulldown, the form file is
	loaded, and all the fields update.

	I'll see if I can follow up with some specific recommendations
	for what to change in eg. submit-shake a bit later so as to do that.

	
-- 
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)

On Feb 15, 2008, at 5:23 PM, Greg Ercolano wrote:

[posted to rush.general]

Gary Jaeger wrote:

So I could end up with something like this in a hierarchical drop down:

VID
	VID100
	VID200
	VID300

CHT
	CHT100
	CHT200

etc. then I could save submits for dormant jobs even

	Ya, I'd think a pulldown menu should be possible.

	It sounds like you might want to write a script that pre-generates

all the form files, and have the submit form just pull an 'ls' listing

	of that directory to fillout the pulldown menu with the filenames,
	such that when the user changes the pulldown, the form file is
	loaded, and all the fields update.

	I'll see if I can follow up with some specific recommendations
	for what to change in eg. submit-shake a bit later so as to do that.

	
--
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)

. . . . . . . . . . . .
Gary Jaeger // Core Studio
86 Graham Street, Suite 120
San Francisco, CA 94129
(Tel# suppressed)
http://corestudio.com	

Gary Jaeger wrote:
> [posted to rush.general]
> 
> that all sounds like a possible solution. we're using maya, if it  
> makes any difference.
> 
> if, for the time being, I wanted to have artist B have access to all  
> the forms artist A has save, how might I do that?

	You'd have artist A use "File -> Export as" to save the form
	into a directory that artist B would use "File -> Import" to load.

	I believe the default directory both of these operations use
	is the 'current directory', so if you have a specific directory
	in mind, such as "/yourserver/somewhere/rushforms/", then I think
	you can make that the default directory by finding these lines
	at the top of the submit script:

# LOAD COMMON VARIABLES + FUNCTIONS
require "$FindBin::Bin/.common.pl";

	..and adding the following line directly below it:

$G::input = "cd /yourserver/somewhere/rushforms && $G::input";

	This will cause that directory to become the current directory
	just before the 'input' program is opened, which handles the
	GUI submit form.

	Meanwhile, I'm putting together an example that shows how
	to make the 'Shot' pulldown menu work. To do it right involves
	giving you a new 'input' binary (that will be in the 102.42a9
	maintenance release) to handle the GUI pulldown automatically.

-- 
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)

Greg Ercolano wrote:
>> if, for the time being, I wanted to have artist B have access to all  
>> the forms artist A has save, how might I do that?

	Oh, one other way is to have artist A create a bunch of forms
	via 'Forms -> Save'. These forms will be saved in a ".hist"
	history file in artist A's home directory, eg. for shake, the
	filename would be  ~/.rush/.submit-shake.hist

	If you look at that file, it's all ascii (ie. can be generated
	by a script if you want) containing all the forms artist A has saved.

	You could then copy that file to artist B's home directory with the
	same filename, and when that user brings up the submit form, the
	saved forms should show up in the 'Forms' menu.

	I just sent you (via private email) a link to a version of a submit
	script that has the pulldown menu we talked about earlier in this
	thread. If you have luck with it, I'll post it here for everyone
	on the group.

-- 
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)

On Feb 19, 2008, at 5:32 AM, Greg Ercolano wrote:

[posted to rush.general]

Greg Ercolano wrote:

if, for the time being, I wanted to have artist B have access to all
the forms artist A has save, how might I do that?

	Oh, one other way is to have artist A create a bunch of forms
	via 'Forms -> Save'. These forms will be saved in a ".hist"
	history file in artist A's home directory, eg. for shake, the
	filename would be  ~/.rush/.submit-shake.hist

	If you look at that file, it's all ascii (ie. can be generated
	by a script if you want) containing all the forms artist A has saved.

	You could then copy that file to artist B's home directory with the
	same filename, and when that user brings up the submit form, the
	saved forms should show up in the 'Forms' menu.

	I just sent you (via private email) a link to a version of a submit
	script that has the pulldown menu we talked about earlier in this
	thread. If you have luck with it, I'll post it here for everyone
	on the group.

--
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)

. . . . . . . . . . . .
Gary Jaeger // Core Studio
86 Graham Street, Suite 120
San Francisco, CA 94129
(Tel# suppressed)
http://corestudio.com