Several times I or others have tried to make a good tutorial for PyWright. It is a very important piece that is missing, as the comprehensive but terse doc.txt can make the simplicity of PyWright seem, well, not so simple.

The main thing that has stopped these tutorial projects has been overambition. What starts as writing a quick, simple tutorial eventually grows into an all-encompassing guide of everything. Eventually, it gets too big to actually write and finish. Another issue, is both myself and Ferdielance have focused a lot on the presentation of the tutorial, with me spending a lot of effort on good html; and FerdieLance working with pdf.

I think for now we really need a good, short, tutorial that schools users in the basics enough to get their feet wet. At that point, asking questions, trying things out, or searching doc.txt will be more productive, but before that just getting started can seem impossible.

I want to discuss here with any potential collaborators (StBacchus ) how to get this project off the ground and into the hands of the general public.

My idea is for the tutorial to be a few chapters, covering most of the basic things that people will want to do. Getting started will be the first "chapter", and should not be more than a few "pages" long. I think pictures are a must, especially showing how to create the folders for a game, and what you should see when it is running right. Other chapters would focus on dialog, investigations, and court. Different people can write each chapter too, so that all of the work isn't thrust on one person.

Anyone who has good writing skills can help with this, and I think StBacchus will be the leader of the project. It may just be me and StBacchus, but others can help by commenting on the output to improve it!

Which getting started did you like? I like those pictures, they can enhance it a lot.

Yes, having screens showing both the code, and what the code does, will be helpful. I almost think that less text and more pictures might be better than the other way around. The focus of these guides would be in getting users comfortable with the language and process, rather than showing all of the different ways to do things, or all of the myriad options they have.

Here's a tentative list of chapters that we should think about:

• How to do a talk scene
• Investigations
  • The menu command and menu options
  • Talking and moving
  • Presenting
  • Examining
  • Psyce-locks
• Court scenes
  • Court macro for dealing with all of the characters
  • Introducing evidence
  • Cross examination
• Transitions
  • How to go from an introduction to a court scene, how to go from a court scene to an investigation
• Finishing touches
  • Guilty/not guilty, the penalty bar, exiting the case when it's finished
  • Distributing your game

The talk scene chapter is first, after that I'm not sure what the best order to do them in would be. I would like to focus on one chapter at a time, and release each one as it is finished.

Thanks for the offer to help!

Great job StBacchus, I think they look really beautiful. When the rest of it is set up, we can link commands to their full description so that people who want to see more can, but excess information doesn't overwhelm.

So what I'm getting is, stick with the general text of the current docs up to the scripting, but add the screenshots and fix formatting of everything, and then add these onto that? That sounds good, since I am none too happy with the direction things went once I got into the scripting part.

I also really like the two panes, where a quick glance at the screenshots conveys enough information to get your feet wet.

If my "Scripting and Commands" is going away, I think you should start "Setting up your script" with a line or two about using a text editor. It's something that frequently trips up new users.

Nicely done! I don't mind if it fits into wordpress or not, it might be better as a separate entity, it can come packaged with the engine that way.

The more people to help on this the better!

I couldn't find a good wiki plugin for wordpress, so we should have it separate. I can host it (would be pywright.dawnsoft.org/wiki) but I'm not sure what a good wiki software is. The best would be if I can make it use the same user accounts from wordpress, so people don't have to sign up twice

Reusing http://www.gyakutenwiki.net/ sounds perfect. No extra maintenence needed by us, and most of us will have accounts already. I made a stub at http://www.gyakutenwiki.net/in…..ialProject

Like I said, I linked to a spot on GyakutenWiki where you can start putting it, if you would like to use it. It's just a stub right now (nothing really posted) but there is nothing stopping us from fleshing it out. It is linked to the PyWright page, which I think is a good start for it. It might be easier to use that then another site, because at least most of us already have accounts there.