First, some prerequisites for developing (with) Field:
See the instructions on our GitHub page.
Take a look at the /extensions
directory, and its documentation and most importantly the UI for this extensions directory, the Plugin Manager [PaletteOverview#ThePluginandExtensionmanager] — there's even a tutorial video. Specifically, it's likely that you'll want to add an entry that points Field towards your own java class-files and sources (and your own Python sources if you have any).
You could also take a look at RunningField and StartupOptions to familiarize yourself a little with what's actually happening when you run Field, and decide exactly how you want to run it (Marc recommends the command line). Of particular interest is the -field.scratch
option which changes which workspace file you are loading on startup (such files are created on demand), and the -main.class
option that just uses Field's Launcher
to run the class you pass into it. You can open the Field UI in your own code later, or if needs be load and execute sheets without instantiating any UI at all.
The top three early answers to questions:
from my.java.codebase import *
or from still.more.java.code import Wonder
to access your codebase. In this case, typing Won
and hitting Command-I might help. See CompletionAndInspection.System.exit
). The quickest way to exit without saving is a swift kill -9
from the command line. There's also a menu option in the File menu. If you make a mistake, and, worse, end up saving it, don't worry: all versions of your sheet are version controlled.Programmers should take a glance at StartingPlaceForPythonProgrammers — then, next, at the StandardLibrary or, if you are coming over from Processing, the tutorial for Processing.