Talk:Getting Ready to Learn LSL

From Second Life Wiki
Revision as of 17:46, 5 November 2007 by Steamy Latte (talk | contribs) (Name comments)
Jump to navigation Jump to search

Best Article Name

I agree the old name Getting SL Started To Learn LSL was an astonishingly long name for this article.

I think the new name Learning LSL misses the point and misleads. This article does not talk about learning LSL. This article talks about all the SL you have to learn before you can learn LSL. This article talks about learning SL to get SL out of the way so that you can start learning LSL. That's a different perspective than articles about learning SL to begin living the second life.

Can we do better? Is there a short name we can choose that doesn't miss the point? Do we agree that Learning SL would work better as a name than Learning LSL does? Do we agree Learning LSL is unacceptable? Is that Learning SL name good enough, or can we do better still by discovering some other more cogent phrase? SL The Prerequisite? Too arcane, yes? What name does work better?

-- Ppaatt Lynagh 16:12, 4 November 2007 (PST)

I think the new name is misleading too. I would split it just before talking about content creation and make that SL Basics (my favorite), SL Crash Course, Beginner SL or Learning SL. At the end of it I would add a section like "Content Creation" and give links to articles about learning building, clothing, texturing, animations and scripting. In doing so we contribute to the greater wiki not just the LSL Portal.

-- Strife Onizuka 17:15, 4 November 2007 (PST)

Oh, ah, progress yes, I like that, thank you. Now with that insight in place ...
I think myself I vote for the article name SL Crash Course. I like how that name conveys both the essential information of the name SL Basics but then also a hint of this article's style of getting the other out of the way for people headed straight towards LSL -- people maybe driven to learn the scripting languages of the popular systems. I'm thinking the exemplar style we want here is the "Wikipedia logo"For_Dummies style: "non-intimidating guides for readers new", "a reference for the rest of us (R)".
I do also like the idea of inviting these people who came into SL to learn LSL to make time soon to also learn the rest of SL. The next thing I learned myself was how to write a profile, as User_talk:Ppaatt_Lynagh#Profile_of_Ppaatt_Lynagh explains. I think I've got that figured out in world, and I'm halfway thru the project of figuring out how to copy my profile out into my user page, in these early days before our wiki gets that right itself already.
-- Ppaatt Lynagh 18:15, 4 November 2007 (PST)
I really like the idea of splitting up the article and breaking out into a quick start and a content creation section. The name of the article raises the question of the article's focus.
You could re-slant the article to not be LSL-specific. So a new SL user might read the article, even if they're not wondering how much SL they need to know in order to try LSL. If that's the direction, then names like SL Quick Start and SL Crash Course do make sense.
If the current slant (covering enough about SL to learn LSL) is maintained, then a name like LSL Prerequisites might make better sense.
BTW, I love the other changes you've made here. --Steamy Latte 17:46, 5 November 2007 (PST)

Table Of Contents

Ah. That's it! Thanks to Strife for adding the TOC of section as the way to number thirteen complex items. That change has fixed the main trouble with the white space, I think. -- Ppaatt Lynagh 13:40, 3 November 2007 (PDT)

It was hard to read, a big wall of text, It needed dividing and the lead sentences were essentially headings anyway. I personally prefer the TOC on the right as to not waste article space (though it similarly could be placed on the left in the same fashion). -- Strife Onizuka 17:18, 4 November 2007 (PST)

Gobbledygook

This page is very hard to understand. After reading this page I really have no idea how I'm supposed to get started in SL.

And I'm saying that as someone who's already created objects and written some cool scripts in SL. --Steamy Latte 16:35, 1 November 2007 (PDT)

So let's fix it. What's the first word you trip over? Or how else would you fix it? -- Ppaatt Lynagh 16:43, 1 November 2007 (PDT)

I added something at the beginning that I felt would make the tutorial more understandable. I didn't do a major overhaul of the remaining text that was already there, but I'd love to spend more time on this and make it really sing -- if nobody has any objection, that is. --Steamy Latte 16:51, 1 November 2007 (PDT)

I agree your new beginning improves this article. I'd love to see you make this article sing.
I think no one should object. The fine print we attach to every contribution includes the phrase "if you don't want your writing to be edited mercilessly and redistributed at will, then don't submit it here". Me, I highly value that freedom to work together more easily by thinking of all submitted text as our imperfect text, forgetting as quickly as possible that the pieces of the old text that I typed myself once bizarrely did appear perfectly beautiful to me.
-- Ppaatt Lynagh 17:16, 1 November 2007 (PDT)
By the way, I'm reminded of the http://www.paulgraham.com/popular.html argument: "to become popular, a programming language has to be the scripting language of a popular system".
-- Ppaatt Lynagh 17:16, 1 November 2007 (PDT)
You have a fantastic perspective, Ppaatt!! In that case, I'd like to take the existing observations (which have loads of helpful information in them) and expand the text to make them even more useful for a newbie. I'll be very happy if someone dismantles it all later and makes it even better.
--Steamy Latte 09:49, 2 November 2007 (PDT)
Kind words! Thank you for those, also for your open invitation to everyone who can help us hereafter, also for the delightful edits of the article - a great leap forward now, I agree. I think it sings!
As for suggestions on how to next approach perfection yet more closely, ...
1. I think we could/ should make more clear the fact that the student can start scripting when all the student know's is how to make a single prim cube. The programmer learning to script in SL doesn't have to get into multiple prims til later.
2. I'd vote to think back thru some of the white space/ font design. I was somehow slow to appreciate visually the textual convention we have now established of beginning each point with a summary of its meaning followed by explanatory details.
3. I wonder what we mean when we say premium membership delivers benefits to serious scripters. I've collected ~L$200 thru camping while I debug scripts. I found my way to Sirena's Workspace Buster for moving in 3-space to a private corner of a public sandbox. All the same, the Describe Chatter script correctly reports my DATA_PAYINFO says no credit card registered, no credit card used. What am I missing? (This is an academic point. I spent all my money on my computer -- now I don't have the money to go premium -- but I'm curious?)
-- Ppaatt Lynagh 13:12, 2 November 2007 (PDT)
Those are great suggestions. I went back through orientation and re-ordered the steps to bring them in line with what I experienced -- some of your original orderings may have been restored in the process(!). I also edited the text to take account of your great suggestions.
Feel free to make any more changes, I think I'm done with this for now and I'm going to look at some of the to-do's and also try to improve anything else I bump into that needs work.
Love, Steamy 16:45 2 November 2007 (PDT)
I appreciate your enduring volunteer spirit.
I suspect the to-do's you mean are the LSL_Portal_To-do list including the Category:LSL Needs Example list and the hopes of creating Category:LSL FixMe, and Category:LSL Stub lists.
Glad you liked the suggestions. Sounds like I should give us all a rest before discovering more suggestions for this article. I did glance at the article yesterday, I didn't feel any suggestion strongly enough yet to remember it today. Thanks again for making the article sing. -- Ppaatt Lynagh 06:39, 3 November 2007 (PDT)