alcscript documentation in the wiki

[Gbadji]

I'm not sure I'm writing this in the good forum, so please move it if it's not.

I would like to understand alcscripting so I would like to read the documentation in the wiki but I can only access to the first three pages because of right access.
Where can I find information about alcscript ? Or someone can explain me what is wrote in the mysterious hidden pages?

Thanks

[Trylon]

Mmh, no one can access more than three pages, because the other ones (the blue ones) haven't been written yet.

It's partly my fault, I get really bored after a while when writing documentation, so I only got as far as three pages.

[Gbadji]

So, no mysterious pages. Thanks Trylon for the first three.

I have to find an other way to understand alcscript , I'm not arrived (That's a french expression, I'm not sure I can use it in english ...).

[greendragoon]

I think this gets at the problem that the people who really understand all the changes going into the plugin are also the same people who are busy actually making said changes to the plugin. I wonder if there is a way that we could better distribute the task of completing/updating the wiki.

Keep in mind that this is just an idea. When I'm done, feel free to change/shoot down things that you don't think would work including the entire thing. I wonder that amongst the guild of writers, there are those who actually find their greatest skill is writing. I mean literal writing. Those who have a good understanding of a subject/topic could try and convey that knowledge to those who are good at polishing the tutorial and doing a proper writeup. You could maybe then have a third person who's job it is to go through and provide visuals i.e. screenshots and project files for the tutorial. The expert could then kind of oversee things and make sure the tutorial still conveys the correct information as well as answer the invariable questions that will arise considering that the writer and visuals person may not have the same level of knowledge as the expert. What do you think?

[Robert The Rebuilder]

I have to find an other way to understand alcscript , I'm not arrived (That's a french expression, I'm not sure I can use it in english ...).

Perhaps you could say, "I'm not quite there yet"?

[Gbadji]

thank you Robert for the lesson . I will keep that in mind.

@greendragon: it could be a good idea, actualy I'm feeling like in Minkata, searching which direction to follow .

[greendragoon]

Now how you feel. For the longest time I couldn't get the unit of distance right because I was basing it on the wrong flag. There were some red herrings in that age.

[Trylon]

I like your idea, greendragoon...

Can we consider you to be on the list of wiki volunteers ?

[greendragoon]

My knowledge is still somewhat limited, but sure I'll help where I can. To be honest, it seems like a great opportunity to learn more.

[Marcello]

Good idea Greendragon. I remember when writing a few of the tuts I had to go back and forth to Trylon to get the facts right. I think making a tutorial comes down to:

1. having all the facts about settings and how to apply then
2. being able to make a sandbox in Blender with reallife examples
3. being able to write every step down thoroughly and as a fun read
4. being able to provide all the images to clear things up

The most frustrating part is the first and the fourth. I believe you have to show as much menu's and images as necessary. Personally when something out of a tutorial doesn't work I always have this feeling I don't have all the settings. So that's why I try to show as much as needed and possible. This however takes a lot of time print screening and pasting and cropping and stitching and... you get the point.

I would be willing to help writing and make more tuts. Somehow though there should be an expert database of facts. It may be unreadable for most, it may have as many spelling errors as someone can make, but it should include facts. Others could use that database/expert wiki to write accessible tutorials.