With this selected (you can see the black surround) now we can type code, using the text editor, into this box. Now we have our first visual element on the canvas: This gets us a new element, Field asks for a name. To create a box (or "visual element") right click on The Canvas to bring up a contextual menu: You can already see a text editor, but to be able to edit text in it, first we need to create a box on the canvas to house the code that we want to write. Your first box of codeįield, like the Processing development environment, is an environment for writing code. But for now, just check the boxes to make your "p" tab look like the screenshot above. We'll discuss the meaning of the selection marked "Applet Namespace" shown above. If you don't get a 'p' tab in your palette then you probably need to turn the Processing Plugin on, using the Plugin manager and the instructions above (remember to restart Field!). Specifically, on the "p" tab of the Palette window you'll have something like: You know you have a working ProcessingPlugin when you have a) a blank Processing window and b) notification that Field has found your Processing application directory (check the "p" tab of the Palette). Field is also evolving so quickly that it's likely that your screenshot won't look exactly like the above. There's a good chance that your layout won't be as nice as this - take a moment to minimize the unimportant ones and tidy up a bit - the placement of the windows is automatically restored between sessions. If all goes well, you can open Field and be greeted with screen something like: If, for some reason, you have your Processing.app hanging out in some odd spot, see the the "processingApplication" option at StartupOptions. To turn Field's Processing Plugin on, go to the Plugins and extensions manager and turn it on there:įield's ProcessingPlugin automatically looks inside /Applications, ~/Desktop, ~/Documents and ~/fieldwork for a "Processing XXX" directory with a Processing.app in it to establish where your Processing installation is (it will pick up the extra libraries installed there). Let's assume that you have a working Field installation, a Processing installation (downloaded from ) and a working ProcessingPlugin. This video gives a motivating whirlwind overview of the early part of this tutorial: The bridge to Processing is compact enough that we believe that this is sustainable, but we'll need your bug reports and contributions to make this work. Thirdly, a warning: OpenEnded Group makes art using Field every day, but we've never made art using Processing inside Field. We think that Field fundamentally changes the nature of Processing development - cleaving what's known as "Processing" into two parts: the first a vibrant community of people using and sharing Java-based libraries for making interesting things and the second a rather conservative and minimal development environment and language that's currently boxed in by its need to be "simple". Field wraps Processing Field hijacks Processing it accesses the same extensions and libraries, and yet offers a far wider range of technologies for the "improvising programmer" - our bet is that with Field you'll be writing code faster, and scaling your projects to greater breadths than Processing has been designed to promote. Secondly, the punch-line: anything that you can do in Processing you can do in Field with one exception: authoring Java applets for web-pages. Firstly, the prerequisites: this tutorial is written for an audience that's familiar with Processing, familiar with either Java or Processing "Java-Lite" language, and not very familiar with Field or perhaps Python - the primary (but not the only) language that Field uses.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |