Cookbook text files

Started by themarquis

themarquis Lv 1

I noticed that cookbook recipes can be accessed as plain text files in my foldit directory. However, it is difficult to tell what is going on in them (lots of "////////////", etc.)

It seems to me that it would be useful if people could easily modify these text files, either by hand or via an established programming language (for those of us with more programming skills) and then run them as recipes. I think even folks without programming experience who wanted to develop larger or more complex "recipes" (it sounds like people are itching to do so!) could just write them as plain text files (so much easier and quicker than using the cookbook interface)! Of course, those with programming skills would be able to do all sorts of exciting stuff with the text files by generating them in some other programming language.

So I guess my question is a) what the heck is going on in those text files w/ all the garbage "////" in them (so I can modify them) and b) in the future, could these text files not look garbagey and possibly even have somewhat user-friendly, simple-to-understand text in them (the actual text that appears in the in-game cookbook would be just fine)

LennStar Lv 1

that was already asked for and answered e.g. here:
http://fold.it/portal/node/985883
http://fold.it/portal/node/985889

Have no fear, we fully intend to provide a programmatic way of providing recipes. It's just that we wanted to get recipes to the 99% of foldit players that don't program first.

the LUA scripting should be released in a month or so. all operations currently existing in the graphical UI and probably a few more will be in the API. if you want to get a head start, look up the syntax/examples in Lua programming language.

about the text files:
the all.macro contains all scripts. The first entry in each line is the name of the script. The rest is basicaly the same that can be seen in the cookbook. Create your script there for the time beeing.
To copy a script, just choose the name and copy the complete line into your all.macro (of course, always make backups if you do those kind of operations).

the single.macro contains only the last cookbook-edited script and can savely be ignored from my experiences.

@TeaM: How's the LUA thingy going on?