I did consider adding a built in script editor, but dropped it thinking most people have some kind of favorite editor they like best when programming/scripting.
As for generating basic scripts, the problem is there are quite a few variables even for very simple model/animations. So the user would have to fill out a whole list of questions they might not completely grasp (like rotation vector directions etc).
With 1.5 I'm considering extending the scripting api into macro's so you can also generate (sub) models using script. With macro's in place it might be far more productive to let people write (and share) little scripts able to generate little starting scripts tailored to their own needs etc instead of having a couple of static wizards.
As for generating basic scripts, the problem is there are quite a few variables even for very simple model/animations. So the user would have to fill out a whole list of questions they might not completely grasp (like rotation vector directions etc).
With 1.5 I'm considering extending the scripting api into macro's so you can also generate (sub) models using script. With macro's in place it might be far more productive to let people write (and share) little scripts able to generate little starting scripts tailored to their own needs etc instead of having a couple of static wizards.