This gives teachers of other subjects an easy-to-use tool to create domain specific visual scenarios for students. Because Greenfoot has built-in support for exporting scenarios to applets and the web, it provides a very easy way to quickly prototype games, utilities and other ideas. Greenfoot is a joint project funded by Sun Microsystems and implemented at the University of Kent at Canterbury (UK) and Deakin University, Melbourne (Australia). The goal is to target students in the pre-teen years and older by providing a development environment which is both engaging and flexible. Greenfoot was built by some of the same people who created BlueJ: Poul Henriksen, Michael Kölling, Davin McCall, Bruce Quig ( BlueJ, by the way, is a great teaching tool for understanding simple Java object relationships via UML.) Although Greenfoot uses the same UML as BlueJ to clearly show the object oriented design of each scenario, its true power resides in object visualization.
#GREENFOOT WORLD API CODE#
It greatly lowers the bar for building graphical applications in Java this is important because the quick positive feedback inspires students to work with the code more.
#GREENFOOT WORLD API FULL#
There are just a few classes to learn in order to make full use of the platform. The Greenfoot API is made up of only five classes (for details, see Greenfoot Java docs). The two primary classes that will be used in any scenario are World and Actor. These two are the base classes for everything that will have a visual representation in the scenario. World represents the canvas and provides the cell size and coordinate system for positioning the Actors. Actors are visual representations of objects which can interact with one another and the world. Both of these classes have an act() method which should be overridden with the desired behavior for the World or Actor. The act() method will be called by Greenfoot in a round-robin fashion on each object and this process will repeat as long as the scenario is running. This is a simplistic threading model however, it provides a great opportunity for students to learn about the consequences of wasteful processes and encourages efficient code. To make an actor react to mouse clicks, use the following code: if(Greenfoot.This feature also gives the student an opportunity to think about asynchronous solutions without burdening them with other complexities such as synchronization. In designing the mouse support, we aimed at making it both flexible, and easy to use.
#GREENFOOT WORLD API DOWNLOAD#
It needed some careful rework to pass the right mouse events on to the user application, and processing some in the environment.īut now it’s all done, and you can download the new Greenfoot with mouse support. Previously, mouse gestures were interpreted by the Greenfoot environment itself, for things such as dragging objects, and popping up their menus. Such as Minesweeper.Īdding mouse support to Greenfoot was a bit tricky, since Greenfoot already processed many mouse events. This means that you can now write games that use the mouse as a control. This has been the single most requested feature for some time.
Greenfoot is finally getting proper support for mouse input.
0 kommentar(er)
