This site requires JavaScript, please enable it in your browser!
Greenfoot back
NEET
NEET wrote ...

2014/6/16

Become good in greenfoot

NEET NEET

2014/6/16

#
yo guys, I really want to know, how did you became so good in greenfoot? Iam new, but I really want to become good in programming in greenfoot. I know.. I know its all about "training" but still.. you got any tips?
Mint_Greenie Mint_Greenie

2014/6/16

#
Yup. Never,ever, think you know everything. It pushes your learning behind. Don't get discouraged by the people who are ahead of you, take success as an in- vitiation for more success. Practice eve- ready, create projects make a team create a git, execute your ideas!
danpost danpost

2014/6/16

#
I think what are really asking is this: how do you become so good in programming in Java. The classes ('World', 'Actor', 'MouseInfo', 'GreenfootSound', 'GreenfootImage', and 'UserInfo') provided by greenfoot are written in java. They are the support classes that make it easier for beginners to jump right in and create scenarios easily. To get good in java, I suggest you visit the Java tutorials. The second section on the left, labeled in red, called Trails Covering the Basics would be the best starting point.
Mint_Greenie Mint_Greenie

2014/6/16

#
or you can read books and visit websites for java. Sorta like CodeAcademy, but codeacademy doesnt offer java curriculum.
lordhershey lordhershey

2014/6/16

#
I think practice is best. Knowing a bunch of api calls does not make a programmer. Experience will help you learn how to break a problem up into logical steps.
Mint_Greenie Mint_Greenie

2014/6/16

#
Exactly, @lordhershey!
danpost danpost

2014/6/16

#
@lordhershey @Mint_Greenie, it would be difficult to practice anything when you do not know what it is you are to practice. It is like asking someone to speak fluent Mandarin without teaching them a single word (never mind the grammar). One needs to know the 'keywords' and the 'syntax' and the 'constructs' of a language before one can write any workable code in that language. After that APIs are important also. Not that you have to "study' them, but, skimming over them to see what methods are available. You do not need to memorize the names of the methods and what arguments they require. Just knowing that a method is available to do a specific action is more than enough. You can always go back to the API to get the specifics when needed. Even if you do not know if a method is available for a certain action, you can look to the API to find out (or find something else there that will lead to what you want). For the beginner, the World and Actor classes of the greenfoot package should be at least looked at to see what methods are available (expanding from there). I have helped people by referring to APIs of classes I have never used myself. The main non-greenfoot classes I use the majority of the time are 'java.util.List', 'java.util.ArrayList' and 'java.awt.Color' (this one the most). It is quite rare for me to use any other non-greenfoot class. I am not saying the practice is not needed or not important. I am just saying that you cannot practice something that you have not been instructed in. Also, I agree that knowing a bunch of API calls does not make a programmer. But, a good programmer knows a bunch of API calls, from practice -- as well as how to break problems up into logical steps, how to code them in the programming language he is using, and much much more.
lordhershey lordhershey

2014/6/16

#
I was under the impression that the OP was not 100% green at coding.
danpost danpost

2014/6/16

#
lordhershey wrote...
I was under the impression that the OP was not 100% green at coding.
I will not presume anything there as with
NEET wrote...
Iam new, but I really want to become good in programming in greenfoot.
'Iam new' is not qualified in any way.
lordhershey lordhershey

2014/6/16

#
New at Greenfoot. I was new to greenfoot at one time and was all thumbs even though I had vast experience before.
Mint_Greenie Mint_Greenie

2014/6/16

#
Me too!
lordhershey lordhershey

2014/6/16

#
The thing I found hardest was giving up the basic control that I had before. I like this framework since it seems to be fairly robust and provides more than I typically use.
You need to login to post a reply.