Provide a user manual with lots of examples on how to use this new recipe/cookbook thing.
It's totally worthless just throwing it out without any instructions - a complete waste of programming resources.
It's full of terms that have never been used in relation to Fold.it
like - What is "stride" ?
How does it do iterative processes? Evaluate results? Branch based on results?
Don't take this as an official statement, but I think we were hoping that you all could come up with the examples? As far as I know, we on the development team don't have much in terms of particular ideas for how this might be used. It was a frequently requested item. We implemented a basic version of the feature. Now we can begin a dialog about what it might be used for and what could be added or changed about it.
In terms of explaining basic terms, yes it would be nice if the developer who implemented the system could write up a quick guide to what everything means. I personally don't know what "stride" refers to.
By the way, looping and branching are not yet supported. We're still figuring out the best way to approach that.
the problem is, its fairly basic. (As talked about in the already existing cookbook feedbacks)
How to use:
You click in the blue box, choose one action, and the same or other actions some times more ;)
e.g. I have an "settle in" script consisting of a longer wiggle, a shake, a medium wiggle, a shake and a small wiggle.
that can be used after you have done some bigger changes. you click in the script arrow (start) and watch it do your work ;)
There is even a script somewhere for a backbone walk. Now that is something very useful. Don't sit araound one hour do it manually, lets the computer do it while you eat ;)
If some of these examples could have been posted, instead of leaving everyone flopping around wondering how this feature is in any way useful.
I can't see how your first example of a couple of wiggles/shakes is any more useful from the cookbook than just hitting a couple of hotkeys.
In the case of a backbone walk, how does it know how how long to let each section wiggle? sometimes there are immediate results, then a hard stop, or other times the score will go down immediately, then slowly come back up past the starting point. the difrfernce in time can be significant. How does the script monitor that?
Without doing any kind of looping, how could you do a backbone walk without explicitly locking and unlocking each required segment as the walk progresses? It seems like that "recipe" could be hundreds or even thousands of lines long.
This certainly sounds backwards.
Let's implement a feature that the project team doesn't know will be useful, or even how to use it, and then open a dialog about the design features needed.
It's a good thing real software development isn't done this way.
Set details.
"I can't see how your first example of a couple of wiggles/shakes is any more useful from the cookbook than just hitting a couple of hotkeys."
You don't need to hit a couple of keys ;)
As I said, the current verson of the cookbook is fairly simple and needs a lot of more options to be really useful
"how could you do a backbone walk without explicitly locking and unlocking each required segment as the walk progresses"
That is done by the script. There is lock, there is unlock, and there is the option "every 3".
"It seems like that "recipe" could be hundreds or even thousands of lines long."
Thats why I stressed the point of repeats and metascripts in my entry to the cookbook.
This project is looking more and more like a science fiction book I once read, in which those with mental prowess were forced to undergo lobotomies and state-mandated physical deformityt to bring them down to the level of the "masses".
Incidentally that's great coming from the guy who wants us to hobble the speed of rebuilds to the speed of the slowest computer used by a foldit player. :)
Tool-tips in GUI recipes.
LUA described on wiki.
Closing.