thanks for the visual Phil…
Rev
O.K
I will start the Phixings tomorrow i mean today because its 2:51pm here lol i have no school tomorrow.
I am 13yrs old.So some of my speeling’s are very bad.
Although i did find one speeling mistake in a tut i found i will look for that tonite and report it.
Waht i really want to know about my tut is that does it teach you well did you have diffuiculties trying to learn it.
Well yeah i can hold on.
So your saying i should figure out what will make this Tutorial fun and exiting and yet peopple will learn off it.
I am not too sure what you mean.
Yeah No Prolem.
This time when i make the tut it will be better than ever.
It will also have the Upper Body Piece this time.
It will be in HTML format and speeling will Be perfect I promise.
If not well i dont know.
Yeah man… I think the whole point of your spelling is just… You need to clam down a little… 
We all make spelling and grammer mistakes though so don’t worry… Just have someone look over them… For 13 years old you are doing a good job.
That’s right… A bad attitude didn’t gte my 299 game tonight… But it caused others to flip off and screw up their 3 game totals.
Attitude can change your aspects on everything… You can’t code or do something ina program without faith and courage… You also can’t go at it when you’re pissed off either.
I personally like to calm myself out with a cup of jo and a nice orchestration tone from Final Fantasy soundtracks.
oh, and for reference Bulldog, I have about 30 incomplete or just plain crappy, tutorials and 1 on www.kirupa.com. Remember always that even if a tutorial doesn’t make it, it’s a peice of reference for you to learn from. Don’t ever feel like it’s an embarassment or a hinderance to your progress. We take these things a little at a time.
There are also lots of tutorials out there by 13 year olds, so age obviously isn’t too much of a hinderance.
Hopefuly my tutorial will show how to set up the html version very simply. Once I started doing them seriously, I went straight to html. I have dreamweaver which makes placement really easy, but I think that I can make a standard html form that will be only take minor editing to make it work.
If it does get accepted, kirupa will worry about the php set up for the html page. He’s done a ton of those, and he’s really quick with it.
either way… just keep in mind that www.kirupa.com is picky about which tutorials they take, for good reason. If you’ve been to Flashkit you know how hard it is to find what you’re looking for, there are thousands of tutorials on every subject, and most of them only cover a small thing, or effect. Rarely will you get things as comprehensive as you do at kirupa… All we do is scale back the number of acceptables.
Some examples of things that I’ll be putting in a tutorial on writing tutorials. These are just roughly layed out… need lots of editing.
Daves Top list of things to do when creating a tutorial.
-
Draw my ideas on paper. I don’t know about anyone else… but I like a good old fasioned number 2 pencil and some scrap paper. Even with a Wacom tablet, I’m hard pressed to lay out a design of anything without writing notes first. I keep many steno pads filled with ideas. A brainstorming page is one on which you just spend some time thinking about what you want to accomplish with your tutorial. Who do you want to teach what to?
-
Concentrate on depth of explination - how many age and or understanding levels will I cover? Will a korean 16 year old who understands just a little english understand me? Probebly not, but at least if I shoot for high goals I wont leave the majority of people confused.
This is one of my big sticklers for myself. I want to make sure that if you read a tut I make, you can do the effect, even if you just know the keywords that Flash uses anyway to describe it’s tools.
If you want to know why I only have one tutorial done, look at “Ray of Light revisited” on www.kirupa.com and see what I’ve done in that tutorial. It is very difficult to screw up. Likewise it takes a long time to get the wording just right. Probebly I went overboard with that one, but hey… it never hurts to go overboard. -
Visuals - I want good clear visuals which are small in file size, and limited to Flash where it’s needed.
I’ve seen entire flash based tutorials done up really nice, with back and forward setups, and moving cursor clicking, and anything else you can imagine, but in the end, not one of them couldn’t have been done with a still shot and a couple sentences of explination. Don’t ever substitute Flash for the writen word if it’s an easy concept to understand. It makes people read, and there for absorb more data. You’re basicaly tricking their mind into not working with a lot of animations and stuff. -
Steal from other people - I’m joking. Idea theft is just not right. So, I look for a tutorial that covers some peice of what I’m doing, and I’ll do that tutorial over and over again. When I’ve got it to the point where I can produce the effect or whatever without looking at their tutorial, then I can usually write in the description in my own words.
-
Organize - On another peice of scrap paper I tend to gather thoughts, or plans into groups. I want a logical progression from start to finish of the production so that I don’t get hit with too many surprises along the way. The more detailed I draw out my html document, the less trouble it will be to create.
If I can think of any other rules I use I’ll post them,or just include them all in the tutorial.
PS There are a number of other places which also look for tutorials, so if you do get one up on kirupa, be sure to run it around to submissions for places like Flashkit as well.
oh… and keep in mind… these are standards I look for in my own tutorials. I am not the person who accepts tutorials for publication on kirupa.com though. You do not need to adhire to the above rules to have an acceptance or anything like that.
Just wanted to clarify in case anyone was confused.
*Originally posted by david *
some people are at different levels of education…
hehe, especially if those people are from mid-Europe (like me) :trout:
