Greenfoot Live will be a regular chat event where members of the Greenfoot team will be live online and talk about Greenfoot, among ourselves and with you – the users of Greenfoot. Programming Education Chat With The Greenfoot Team
#GREENFOOT DISPLAY TEXT SERIES#
In order to provide more ways to support teachers who are using Greenfoot (or thinking about using Greenfoot), as well as anyone else interested in Greenfoot, we are starting a series of live chat sessions: I would like to thank all our reviewers who contributed many useful comments and suggestions, especially Jens Mönig and John Maloney, and the special editions editor Franklyn Turbak. The rest of the special issue is very much worth reading as well – you can find it here. It has been published in a special edition of the Journal of Visual Languages and Sentient Systems (focussed on blocks programming). Kölling, Brown & Altadmri: Frame-Based Editing I’m glad it is out now you can read it here: It also describes related work and background (which you might like to read in its own right if you are interested in the history of block-based systems or structure editing), and a few small user studies. In parallel, we have worked on a comprehensive paper, describing the design ideas and rationale behind many of the detailed aspects. Then, more recently, we also incorporated Stride into BlueJ, making the new frame-based editor available to a much larger audience. /r/shittyprogramming - Q&A with shitty programmers.We (that is: Neil, Amjad and I) have worked on Stride and its frame-based editor for about four years now, and there is a lot of work in it.įirst, Stride was designed and released as part of Greenfoot, and we wrote a few smaller papers about specific aspects of use cases around Stride.
#GREENFOOT DISPLAY TEXT CODE#
/r/itsaunixsystem - over the top and bad code in TV shows and movies./r/programminghorror - stories about horrible programming./r/ProgrammerHumor - programming humour.Explain why you think the code is bad in the comments, that way a discussion on good and bad ways to do what your code snippet does can start.Don't post huge snippets unless it's all terribly amusing. Provide just enough code so that we know what's going on.If you have a language that whatever paste bin your using doesn't support, try picking a similar dialect. Enable syntax highlighting appropriately.Your post will not be removed because of any of these, we'll like you more if you follow them though. See something particularly sinister from something like the IOCCC? Probably OK to post. Do not post intentionally obfuscated code.Do not post snippets in esoteric languages.This sub is about bad code, not the people who write it. We all write bad code, and a lot of it is hilarious. If you want to share the context put it in the comments or title. Use flair to mark the language of your post instead. For example, do not make your title something along the lines of " #defines everywhere!", instead try simply "#defines everywhere!".
0 kommentar(er)
