Talk:Lessons

I am about to start a series of scripting tutorials starting from the very basics and building up into more advanced topics, all in order, and all in a series form. Each tutorial will be called a lesson, and its name will be something like this: "index.php/Lesson:Variables". The "index.php/Lesson" page will be the HQ for all the pages keeping them all organized. Unlike the rest of the tutorials on the site, these will be in the form of a series, where the lessons build up over time. Any help would be appreciated...

Mattchewy (talk • contribs)

01:46, 16 November 2010 (UTC)

Are you proposing that we should have a Lesson namespace?

^{Posted by blocco (talk) on Nov 16, 2010 (Tuesday) at 02:12 (UTC) [Discuss format]}

Yea, pretty much. Whatever makes it as organized as possible.

Mattchewy (talk • contribs)

02:15, 16 November 2010 (UTC)

Either that, or something like "index.php/Lessons/Variables"

Mattchewy (talk • contribs)

02:18, 16 November 2010 (UTC)

I like the subdirectories idea AND the namespace idea. I'm ultimately voting on subdirectories because it is easier to set up and you can have a base for everything and it can branch out.

^{Posted by blocco (talk) on Nov 16, 2010 (Tuesday) at 02:20 (UTC) [Discuss format]}

Subdirectories aren't a good idea. For one, they're stongly discouraged by wikipedia. Go with the (pseudo)namespace, and then categorize them, just to be extra safe

NXTBoy (talk • contribs)

20:33, 16 November 2010 (UTC)

Sounds good. I'm going to need lots of help with these, but it will work out :)

Mattchewy (talk • contribs)

02:21, 16 November 2010 (UTC)

Let's see an outline. You can't start writing until you know what's going where. --Anaminus 02:24, 16 November 2010 (UTC)

My Proposed Outline.

^{Posted by blocco (talk) on Nov 16, 2010 (Tuesday) at 02:35 (UTC) [Discuss format]}

Here is what I was thinking: The main Lesson page will be a brief introduction into Lua and an explanation of how powerful it can be. Then all of the lessons will be categorized into easy, medium, and hard sections with links to all of the lessons. Each lesson will have an introduction into the topic and at least 1 example of a productive way the current topic can be used in a real situation. The the lesson will explain the topic, etc. At the end of each lesson, there will be at least 5 assignment questions on the current topic that the user can answer if they would like. Here is the proposed structure:

• Lessons
  • Topic
    • Introduction(with real lift scripting examples, etc)
    • Main Lesson
    • Assignment Questions(at least 5)
    • See Also

At the end, we might would even want to add a glossary with scripting terms and definitions and the pages that the definition was covered

I probably forgot some stuff, so give me some feedback.

Mattchewy (talk • contribs)

02:51, 16 November 2010 (UTC)

That's a nice structure you have there, but it's no outline. When I say what goes where, I mean which lesson will explain which aspect, what order to put them in, etc. This will actually require some thinking. This project is something that wont be successful unless you have a plan. Especially if it's a group effort (why do you think the wiki's a mess?). You're already jumping the gun here. Here's a simplified example:

Lession 1: Variables
Lession 2: Types
Lession 3: Expressions

Once you all agree on a good outline, assign each person to write an article. --Anaminus 02:59, 16 November 2010 (UTC)

Yea, I get what your saying now. I will try to make a really good list tomorrow. I g2g for tonight, though.

Mattchewy (talk • contribs)

03:04, 16 November 2010 (UTC)

Here's my basic outline suggestion:

1. Absolute basics - studio, output, Hello World script
2. The Lua language
   1. Arithmetic
   2. Basic booleans, comparison
   3. Variables
   4. If statements
   5. Loops
   6. Local variables
   7. Functions
   8. Tables, pairs, ipairs
3. Using Lua with Roblox - I think it's better to get them capable of using the language first before introducing all the Roblox stuff. Lots of help problems in SH seem to come from people knowing the API but not the language (e.g. confusion about "end")
   1. Instances - the tree structure, methods, properties
   2. Events, wait, delay, spawn
   3. The other data types - Vector3, UDim2...

Comments/Suggestions? Probably needs a bit more detail. --SNCPlay42 20:46, 16 November 2010 (UTC)

First, in the very FIRST intro, we need to explain what the term "RBX.Lua" really means, and what is different about it, and then tell the users to forget everything they think they know about "RBX.Lua", because that is where most problems come from. Here would be my rough draft outline:

• Setting up studio - Open Studio, View Output, Command, Properties, and Explorer Windows
• Variables - Simple Variables(Numbers, Strings, Bools), probably no local variables until later on, so no local keywords.
• Arithmetic - Messing with all kinds of arithmetic, etc.
• Bool Operators - (==, <=, >=, etc)
• If-Then statements - Basic Use
• While-Do loops - Basic Use
• For-Do loops - Basic Use
• Tables - Index tables, using keys, etc. Basic Use
• Functions - Introduce it as a new variable type? Show anonymous functions? Basic use
• Metatables - Metamethods, Basic use.

• Glossary - Scripting terms from lessons with links to where they were discussed in the lesson.

I am probably missing a lot and my points need to be split into even more lessons. Please give feedback.

Mattchewy (talk • contribs)

00:34, 17 November 2010 (UTC)

Here is an example of what I think it should look like: Variables. Keep in mind that it just a rough draft and it needs lots of work.

Mattchewy (talk • contribs)

01:41, 17 November 2010 (UTC)

I was actually just thinking about this... --LPGhatguy

New Writers

Ok, I am going to try to start this up again. I need all of the writers help for it. If you would like to help please leave your name and any suggestions you have for it.

Mattchewy (talk • contribs)

20:41, 24 December 2010 (UTC)