From: Gary Jaeger <gary@(email surpressed)>
Subject: Re: saved Forms
   Date: Fri, 15 Feb 2008 19:25:15 -0500
Msg# 1684
View Complete Thread (8 articles) | All Threads
Last Next
Well, I guess in a larger sense I'm trying to figure out a good way of organizing the saved forms. We have a show right now that's 70 shots. So just saving one form per shot, never mind all the render passes per shot, generates a list that's longer than my screen is tall. If they could be organized (and edited) on disk in a hierarchy that would then be read in when the submit script is launched that would be ideal.

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	



Last Next