@bourne, after your last post, I decided to try a bunch myself (with no luck).
$SYSTEMDATE, $SYSTEMDAY, $SYSTEMMONTH, $SYSTEMYEAR,
$MMDDYYYY (which I did not think would work),
$TIME, $SYSTEMTIME, $NOW, $CURRENTDATE, $CURRENTTIME,
$CURRENTDAY, $CURRENTYEAR, $APPLICATIONDATE
Thanks for trying. Maybe someone from the Greenfoot team can shed some light on if any exist? And if none do, if they can implement them.
I think the only ones supported are CLASSNAME and EXTENDSANDSUPERCLASSNAME - the bare essentials. It's not really intended to be a general purpose mechanism; the main purpose for allowing the templates to be edited is for translation to other languages.
@danpost
Just learned that how to create the default templates here, thx.
@davmac is there any way that I may write extentions for Greenfoot? Just notice that BlueJ has such a fuction.
I would like Greenfoot to allow setPaintOrder to accept interfaces. It would help a lot with my game by saving space, and adding simplicity.
What do you mean by interfaces
Oh, that makes sense. I would just like to make my game a lot simpler by having actors implement a HUD interface and than making HUD.class the first objects painted.
It would be nice to have some sort of Interface inheritance visually represented in the list of classes in the Greenfoot workspace. If anything - if a class implements another, it could display "implements.." italicized, grayed, and in smaller font within the class box, beneath the name. And when the class box is selected, boxes of the Interfaces it implements appears, say to the right with arrows pointing to them.
And perhaps having Interface boxes distinguished like they are in BlueJ would be nice.
Good idea! I like how it's laid out in BlueJ, and it would be nice to see some connection/identification between other classes.
If you are working with interfaces, then you are probably working beyond the intended scope of Greenfoot, which is to be an introduction to OOP and Java programming. In other words, the intent of Greenfoot is to get your feet wet and stay afloat (not to help you swim the channel).
I realize that stance to a degree, but would venture to say it falls close here. Interfaces are not all that complicated and are introduced in introductory Java courses. What can make them complicated for Greenfoot users would be how they are not distinguished or shown relationships with what implements them as they are in like BlueJ.
@danpost I thick interfaces were very important parts of OOP. They described how things(Objects) going(no matter what ther are), it's also very useful in game develop~
