Bläddra i källkod

Update quickstart.adoc

Fixed broken new lines.
mitm001 9 år sedan
förälder
incheckning
00afa7de4d
1 ändrade filer med 14 tillägg och 21 borttagningar
  1. 14 21
      src/docs/asciidoc/jme3/contributions/tonegodgui/quickstart.adoc

+ 14 - 21
src/docs/asciidoc/jme3/contributions/tonegodgui/quickstart.adoc

@@ -10,14 +10,14 @@ ifdef::env-github,env-browser[:outfilesuffix: .adoc]
 
 == Quick Start Guide:
 
-For anyone who just wants to jump right in and read as you go, here are the basics for getting a UI up and running in minutes.+
-+
+For anyone who just wants to jump right in and read as you go, here are the basics for getting a UI up and running in minutes.
+
 
 
 === Step 1: Creating the Screen Control
 
-This can be done one of two ways.+
-+
+This can be done one of two ways.
+
 *Method 1* - Using the provided default style information:
 
 [source,java]
@@ -40,7 +40,6 @@ guiNode.addControl(screen);
 
 ----
 
-
 [NOTE]
 ====
 style_map.xml consists of a list of xml documents containing varied styles for varied use. You can copy the default style map and replace one, many, all with project specific style (Covered later in this tutorial).
@@ -50,9 +49,9 @@ style_map.xml consists of a list of xml documents containing varied styles for v
 
 === Step 2: Adding a Control to the Screen
 
-Might as well start with something interesting as all control contructors follow the same format. Let go with a window and then we’ll add a button to it.+
-+
-*Constructor 1:*+
+Might as well start with something interesting as all control contructors follow the same format. Let go with a window and then we’ll add a button to it.
+
+*Constructor 1:* +
 Here are the three contrustor choices for creating the window:
 
 [source,java]
@@ -69,9 +68,9 @@ screen.addElement(win);
 
 ----
 
-And… boom! You have a fancy new resizable, movable window as part of you’re UI. Now, let’s take a look at the two additional constructors.+
-+
-*Constructor 2:*+
+And… boom! You have a fancy new resizable, movable window as part of you’re UI. Now, let’s take a look at the two additional constructors.
+
+*Constructor 2:* +
 The second adds a 4th parameter to specify the windows dimensions, like such:
 
 [source,java]
@@ -87,7 +86,7 @@ screen.addElement(win);
 
 ----
 
-*Constructor 3:*+
+*Constructor 3:* +
 The third option adds 2 more parameters and looks like this:
 
 [source,java]
@@ -106,16 +105,13 @@ screen.addElement(win);
 
 ----
 
-
 [NOTE]
 ====
 3 new constructor options have been added recently.  They are the same as the 3 above minus the UID parameter.
 ====
 
-
 Any parameters not specified are derived from the defaults specified in the Window style information.
 
-
 [NOTE]
 ====
 The occasional control extends this contructor format, adding an additional Orientation parameter or possibly a boolean flag for controls that provide multiple configurable layouts.
@@ -125,10 +121,9 @@ The occasional control extends this contructor format, adding an additional Orie
 
 === Step 3: Adding a Button to the Window
 
-Now we can add a button to the window that will create even MORE windows!+
-+
-The Button class is one of the only +++<abbr title="Graphical User Interface">GUI</abbr>+++ control classes that implements JME’s Control interface. The Control only becomes active if setInterval is called because the Button requires the use of stillPressed events. This and much more will be cover in later documentation. Again, you ave the three options above for creating an instance of the button control.+
+Now we can add a button to the window that will create even MORE windows!
 
+The Button class is one of the only +++<abbr title="Graphical User Interface">GUI</abbr>+++ control classes that implements JME’s Control interface. The Control only becomes active if setInterval is called because the Button requires the use of stillPressed events. This and much more will be cover in later documentation. Again, you ave the three options above for creating an instance of the button control.
 
 [NOTE]
 ====
@@ -179,14 +174,13 @@ win.addChild(makeWindow);
 
 ----
 
-
 [TIP]
 ====
 For layout purposes, it is suggested that you add all child Elements to a control PRIOR to adding the control to the screen… so, create a window, add a button, add window to screen.
 ====
 
 
-*A Bit More Info:*+
+*A Bit More Info:* +
 All controls are based on the Element class which has access to all default behaviors. Behaviors can be enabled disabled on ANY control or primitive Element.
 
 
@@ -225,7 +219,6 @@ element.setIgnoreMouse(boolean);
 
 ----
 
-
 [NOTE]
 ====
 There are more behaviors, however, these are the most critical when creating custom controls to ensure that nested Elements react as you would like when a parent Element is altered.