Ethan Quach wrote: > > 'a profile' is listed as one of the three ways users provide input to > the engine, so then is the profile something a user can fully hand craft > (if the syntax were known), and bypass the GUI or Cmd?
We have not decided on the syntax or the content of the profile. At least in the beginning, when things are changing rapidly, we don't recommend for people to hand edit the file. If we decided to choose a format that is text based, for example, XML, they can obviously choose to hand edit the file themselves. If they make a mistake doing that, they are on their own to figure out what's wrong. If they use the GUI or cmd to create the config file, and the config file can't be interpreted, then, that's obviously going to be supported. > > If so, then what's the initiating process that starts the engine in this > case? Can a full profile get fed to the GUI and Cmd? > > In the beginning, the user can choose to start completely blank, or they can use an existing profile. When we ship the March 2008 release, we will provide a few "useful" profiles for people to start as a baseline. We have not decided what "useful" profiles to be made available yet. When we get to make that decision, we will elicit comments and requests from the caiman-discuss alias. > Are the various 'Post processing' methods modifiable/appendable, or are > they just selectable predefined sets of tasks? > This is not yet decided either. There are definitely going to be a set of predefined, and tested, and guaranteed to work post processing methods that we will ship. If they are modifiable, I think that whatever modification people decide to make to them will not be supported, if the image created from these modified scripts doesn't work well or whatever... --Karen
