The first are the "original" variety and the ones that have been here since the beginning of Funky Trees: "input variables". There are largely two different kinds of variables available to you in Funky Trees. If you're new to computer science, these terms may sound completely alien to you- but don't worry, it'll make sense in due time (this is the only reason why programming experience comes in handy, to help orient yourself quicker). They must be enclosed in quotations (“” marks) (e.g. Previously, before 1.9.2, booleans were inconsistent, this now has been fixed to be much more predictable. If you use them in conjunction with other data types, true or false can output the numbers 1 or -1 respectively.
To explain, all usable data types in Funky Trees have now been organized into one of three categories- numbers, booleans, and strings. To give an input to the part, you probably need some sort of data to work with, right? Since version 1.9.2, Funky Trees was revamped to have data type organization. The following sections elaborate on these three categories in great detail, just after the data types section. If these "very specifc combinations of symbols" are likened to functional "elements", it is possible to categorize these elements into to one of three categories. However, the expression Altitude has a very specifc value and meaning to the system, and the expression will evaluate accordingly. For example, in the eyes of Funky Trees, the expression altitude has no meaning to the system. Often this may be the case for complicated input expressions that yield errors.Īnother common idea from programming comes into play in Funky Trees- when a certain, specifc order of symbols are grouped together in a very specifc way, they can hold meaning in the eyes of the system. One small error leads to the entire expression not evaluating / evaluating incorrectly.Mathematical operations in Funky Trees follows standard order of operations (see "operators").Capitalization matters: Hello and hello are two very different things.Spelling matters, including spacing (see "semantics").
There aren't a large number of rules in Funky Trees- they can be generalized to the following: It takes various inputs, processes them, and relays an output that is then taken by the part (whatever "part" you're putting FT inputs into) to result in some kind of of behavior by the part.īy the same token, Funky Trees follows a set of predefined rules to make the system work. Not unlike other conventional programming languages, Funky Trees utilizes a system of inputs and outputs. This particular guide is primarily tailored to help the learning of newer learners.
#SIMPLEPLANES XML FULL#
As it stands, Funky Trees can be considered a very specifically designed programming language- it fufills the definition of one.įor a new learner, it is strongly recommended that the document be read in its full length, in chronological order. Funky Trees expands the options here and allows for much more complex programming of the inputs to allow for very special input programming to allow creation of incredibly powerful and useful parts.įor example, users have created parts that carry out complex actions that weren't possible before 1.9, such as functional all-altitude bombsights, the first functionally complete chronographs, and automatic flight control systems. To be more specific, when a user does things in SimplePlanes, like controlling an aircraft by moving the joystick or pressing the keyboard, essentially what's being done is that the user is sending a signal to the various functional components on the craft to move it as the user intends it to. Difficulty with basic XML editing may prove detrimental to learning the Funky Trees system. By nature, Funky Trees is a special subfield of what's known as XML editing/modding in SimplePlanes. First implemented in game version 1.9, Funky Trees is a special subset of XML editing/modding in SimplePlanes that specifically deals with the group, activationGroup, and input attributes of parts.
0 kommentar(er)
