JavaFX, I18N, FXML and me

Similar Questions

• With the help of vector graphics with fxml and JavaFX

  HY
  
  I wonder about the use of vector graphics scalable, svg, files in my project JFX.
  I know how to display the png with an imageview images and who can handle via CSS style (like fx-background-image)
  But for now, I want to add a vector graphic to my scene.
  I'm not shure if I use .ai, .svg or other file formats and how to load that.
  
  I read on SVGGraph but failed to get the idea behind it
  (and think that's not for files)
  
  So please can someone tell me how single charge and show a graphic vector and formaterait which should take?
  
  Ah: A way to make this replaceable graph via CSS style would be nice too ;)
  
  Thank you
  
  BR

  This .fx file is probably the old 1.x JavaFX, which is no longer supported for JavaFX 2.x and to my knowledge there is also no converter for this.

• I can't seem to grasp how FXML and data binding is useful beyond basic, static views

  The markup is not any sort of logic/iteration as the additional taglibs in JSP capabilities (i.e. < c:forEach var = "${model.") (Person}"> < c: out >$ {person.name} < / c:forEach >) so you're stuck making the dynamic aspects of the UI in pure Java (unless you are supposed to use < fx:script > to do this, that there is little or no documentation/examples/etc.).  Makes organizing difficult associated classes because you so specific to the logical view of the controller (i.e. for each complexItem - create a graph of node that represents a complexItem, add to the list;). It seems that this sort of thing belongs to the "view" class  What happens if the complexItem is a custom control specified in FXML.  What grade is supposed to handle the onMouseClicked event when the user clicks on complexItem.  The controller class that supports that the first of the complexItem, or the controller class displayed several complexItems in the list?  You're supposed to pass the event in the chain of controllers, each parent is to know?

  I can't just wrap your head around this design and how it can be used to create a correct application of the MV * with a clean design.  FXML basically breaks controllers me by exposing specific UI widgets.  Looks like there should be a separate view class that stores the FXML.  Especially in cases where you need to "Finish" the view because all you want to do, cannot be expressed in FXML (like using half of the ControlsFX controls).  So you want a separate controller class to manage the model update (and switch to the update view in the case of Passive View or update the properties in the case of Supervising Controller) and managing events behaviors.  It works well, because FXML and the associated RAD tools requires you to use one and fx:controller only category excluded.

  I want to as JavaFX, I don't really have, but the lack of attention in this area, it's mind-boggling.  I read through tons of blog posts and it seems that there are tons of questions and debates but few answers and resolutions.  I even bought two books on JavaFX8 Apress and or design a model address other than a small introductory text or two and a reference to Afterburner and Dolphin something or other.  It seems that no one has proved a solid design with lots of views/controllers/presenters/viewmodels nested... I don't know even what term used more because it's so confusing.

  > The markup is not any sort of logic/iteration as the additional taglibs in JSP capabilities (i.e. ${person.name}) so you're stuck making the dynamic aspects of the UI in pure Java

  Taglibs themselves are implemented in Java.  You can implement a custom control in fxml, which could allow you to get similar functionality.  Personally I don't really make sense in XML, I think it is better expressed in a procedural or functional programming language and just leave XML for declarative programming; that is for straight definitions of things.

  If you really want to combine JSF taglib features with JavaFX style, you should look into CaptainCasa, that serves as a front end of JavaFX for JSF applications (I've never used this framework).

  > unless you are supposed to be used for this

  Yes, you are made to define custom controls, use the logic of the controller or use scripts (in whatever language please).  The model is the same that javascript html (which is also usually XML based like FXML), which I think turned out based on how many javascript/html is there.  I'm not a big fan of the javascript/xml model, but at least with JavaFX, you have a little more flexibility based on the ability to choose between several languages for scripts and controllers, a collection more complete and accurate the confrontations of control in element names widget and a possiblity to extend the basic elements to create your own custom elements to incorporate the new controls and layouts rather than continuously replace the div and span.

  > It seems that this sort of thing belongs to the "view" class

  I don't really know what the view class is in your definition.  There is no view defined in JavaFX class.  The closest thing is probably a control's appearance, but I feel that is different from what you are suggesting.  The FXML system was built not to be opinionated concerning the architecture used to build applications with it (like an anti-RAILS framework).  The reason for this is that it's just a basic shipped with Java runtime component and not a framework for application complete.  You can always build a style of RAILS framework that had such notions as the view classes and operate with FXML.  There are samples of these frames if you are interested; JRebirth, Griffin.  And there are others who do not use FXML at all; for example FXForm.  Perhaps my favorite and start studying is Afterburner.fx because of its simplicity.

  > What happens if complexItem is a custom control specified in FXML.

  I guess that there are different types of "custom controls", those who actually extend its control and provide an API and control skin following the architecture of JavaFX controls.  In this case the control generally encapsulates the view state (for example who did, how event handlers are defined) and delegates to the skin and a pattern of behavior (interface keyboard controls, etc.) to manage the predetermined nodes, etc.  In many cases for the application code, such a complicated configuration is unnecessary and can make your code more difficult to understand due to the increase of indirection involved by the model.

  The other type of control is something a controller FXML that loads its definition of layout of the user interface in FXML and encapsulates its hierarchy and control node interface in a class that can be instantiated in FXML, as defined in the tutorial Oracle Mastering FXML.

  Both types of controls have their place in a JavaFX application, with extensions of control usually from libraries such as ControlsFX instead of the application code.

  > What grade is supposed to handle the onMouseClicked event when the user clicks on complexItem.  The controller class that supports that the first of the complexItem, or the controller class displayed several complexItems in the list?

  Initially, a UI (node) element that represents your complexItem will receive the mouse click event.  One way to do it is to have a class of skin (encapsulating nodes) associated with your model (or the view in some modern managers model) and which may have observable properties that are set when the actions are performed on the node.  Then your view model/presenter can observe the changing properties in the skin to react based on the observable properties.  You can see many examples of this model in the JavaFX controls source code base or this app of TIC-TAC-TOE (most of these samples are not based FXML).  Most simple, is often to encapsulate the nodes and the event handlers in a single class (e.g. the FXML controller), as is done in the FXML connected mastering tutorial above.

  > Are you supposed to pass the event in the chain of controllers, each parent is to know?

  Generally not, I would say.  Treatment of JavaFX event will automatically events up and down the hierarchy of nodes.  Your controllers (or skins) according to what is in fact linked with the nodes, can add appropriate listeners and filters which react to the events of the UI and update your State application model directly or set the observable properties that domain not associated with GUI logic could listen and react on.  You can also introduce a bus event to propagate and manipulate events (if your application warranted and such an architecture is consistent with your app needs).  If you want to be really sophisticated, then you slap on an Messaging model-based architecture, but by then you're really in a lot of complexity and really need to know what you're doing.

  > I can not just wrap your head around this design and how it can be used to create a correct application of the MV * with a clean design.  FXML basically breaks controllers me by exposing specific UI widgets.  Looks like there should be a separate view class that stores the FXML.

  Well what are the 'controllers' FXML.  Maybe just don't call them controllers.  They don't really control anything, unless you put the logic in them to do (and you don't need to).  By default, they are just holding FXML and Java classes link to allow references to JavaFX nodes and events related to the FXML Java handlers.  You do not even need to call your controllers to controllers in your code, you might call them just something like myItemUIBinding.  Again, I suggest that you take the time to look at afterburner.fx, to see how a more 'opinionated' framework defines a simple architecture to help impose a stronger separation of concerns than the standard vanilla to FXML controller installation.

  > Then you want a separate controller class to manage the model update (and switch to the update view in the case of Passive View or update the properties in the case of Supervising Controller) and managing events behaviors.  It works well, because FXML and the associated RAD tools requires you to use one and fx:controller only category excluded.

  I guess I don't understand that.  You can incorporate several controllers of the child.  You can create your own controllers.  You can set the listenable properties on the controllers.  You can pass objects to model to the controllers.   You can bind a controller to a skin or you can use an Ombudsman model to create a controller supervisor.  Acquired some of these things may be obvious or not clearly demonstrated in tutorials.  There is no equivalent (well used) JavaFX to say spring or Play that sets common criteria in a unique setting and open source large scale the application based on it you could read or derive best practices of.

  > No one has proved a solid design with lots of views/controllers/presenters/viewmodels nested, it seems...

  Agreed is that there is a lack of scale large source code public for applications that rely heavily on FXML and demonstrate an architecture for building complex applications based on it.  Is perhaps the closest, you can find the source code of SceneBuilder, but, unless you create a development such as scenebuilder tool, you can see that some of the reasons he doesn't quite apply to your use case.

• Documentation for FXML and CSS

  Where can I find documentation that lists all the different things that you can do using FXML and CSS for JavaFX?

  For example, how am I supposed to know that I can do "police - fx - size: 12px" for the size of the font in CSS or ' = 'System' size =' 12.0 font name ' / > ' to FXML?

  CSS style

  Here is the css reference guide, which is a great start.

  Complete by carefully studying caspian.css (the 2.2 JavaFX stylesheet) and modena.css (the stylesheet of JavaFX 8).

  There is also information disseminated in the Oracle JavaFX tutorialscss style.

  Try to use the material in the reference Guide css for the style of some of the simple default controls, like buttons etc.

  Once you have the hang of this, move on to something more complex like tables and graphics.

  Don't forget tips as the constant substitution of some of the default paint for example try because it is a style much easier if all you need is a change in color, the following style sheet:

  .root { -fx-base: antiquewhite; }
  

  FXML reference

  It is (and will never) such a thing (as least not a complete).

  FXML works reflecting on classes.

  As you add more classes in your classpath or change existing classes, you can add more elements and attributes to fxml.

  Best current documentation of fxml is the Introduction of FXML and the tutorials FXML from Oracle.

  In terms of learning some of the elements and attributes to FXML for most common standard JavaFX controls try to load up SceneBuilder and examining the FXML it generates.

  Also, as FXML is a reflection of the JavaFX Java API, you can get know which attributes and elements, it can use in looking at the standard javadoc JavaFX.

  Whatever he says, I think that the FXML documentation could be improved, so if after that you are going through in detail by studying the available information, I have provided in this post, you have concrete ideas to improve the documentation, feel free to file detailed and specific applications in the Tracker JavaFXor send your comments to the e-mail address of the JavaFX documentation team : [email protected]

• JavaFx 8 FXML CellFactory own

  Hello

  I wrote my own Cell Factory:

  public class ServerCommitTextFieldTableCell<Role, String> extends TextFieldTableCell<Role, String> {
     
       @Override
       public void commitEdit(String val)
       {
          super.commitEdit(val);
          System.out.println("update!");
       }
  }
  
  

  and I'm trying to use it in a dialogue of fxml definition:

  <TableColumn id="col1" fx:id="col1" prefWidth="150.0" text="Name">
       <cellFactory>
            <ServerCommitTextFieldTableCell fx:factory="forTableColumn" />
       </cellFactory>
       <cellValueFactory>
            <PropertyValueFactory property="name"/>
       </cellValueFactory>
  </TableColumn>    
  
  

  I expect to get the "update!" in the console, whenever I have change the cell and press enter in the textfield in the TableView, but this does not happen.

  I use 8 build JavaFx 1.8.0_05 - b13

  Could someone help me with the problem?

  OK, I found the answer

  FXML:

  and I had to define my new cell and it's factory:

  public class ServerCommitTextFieldTableCell extends TextFieldTableCell {
  
      static Logger LOGGER = Logger.getLogger(ServerCommitTextFieldTableCell.class);
  
      public ServerCommitTextFieldTableCell(){
          super((StringConverter)new DefaultStringConverter());
      }
  
      @Override
      public void commitEdit(String val)
      {
          super.commitEdit(val);
          LOGGER.info("updated:"+ val);
      }
  }
  
  public class ServerCommitTextFieldTableCellFactory  implements Callback, TableCell> {
  
      @Override
      public TableCell call(TableColumn param) {
          return new ServerCommitTextFieldTableCell();
      }
  } 
  

• FXML and son

  I have a file FXML which establishes certain elements on a Panel.  Since there are multiple instances of the Group of experts who are assembled together (think it's a VBox with multiple cards), I did experiences of ways to initialize the panels in their own net.  The bulk of the work, it's that it should:

  1. Load the fxml
  2. initialize the component with data from the database.
  3. return the initialized component so that it can be added to the VBox.

  My initial assumption was that I could stick it in the method of work #call , but I immediately got an exception because the FXML charger wasn't on the thread of the application.  is there a reason any loading configuration of a component must be on the application thread?  Ideally, he should care only when I try to add this element to the graphic scene.

  To work around this problem, my task overrides the Task #scheduled () method to initialize the FXML charger Panel.  It uses the call() method to construct a model for the chart and then use the succeeded() method to bind the model to the table.  Given that both on-demand and managed are supposed to be on the thread of the application, it should work.

  My assumption was that behind the scenes, the task was running the methods in the following order: regular, call succeeded or failed , as the case may be.  However, when I try to get the Panel returned by the call to method, I still get null.  As I call the task using the ThreadPoolExecutor and get a future, I expect that the future should always give me the results of the method call, and it would be non-zero since the Panel is initialized in the regular method.

  Am I missing something?

  > You would think you could do something (the values of the field of play, set of attributes for components) out of the thread of the application.

  Yes, one might think that, but, no, you can't for popup controls associates.

  > The exception I received was thrown when adding a context menu.

  I logged a bug report on it years ago:

  https://JavaFX-JIRA.Kenai.com/browse/RT-17716 "some controls can only be created on the FX application thread.

  It is a problem because things like a ContextMenu or the ToolTip are implemented in the form of PopupControls with their own windows and JavaFX, currently windows must be created on the JavaFX application thread.  Sprittibee found a hack (mentioned in the comments on the jira below), set your own skin that differs from the creation of the pop-up window, but I'm not sure I want to do.

  https://JavaFX-JIRA.Kenai.com/browse/RT-25127 "ToolTip tab (and other controls) can be defined in FXApplicationThread.

• FXML and Menus

  Someone at - it menu working in FXML because 2.0 was released?
  
  I answered a question on this point, so this code example must have worked at some point: width problem MenuItem
  
  I just ran the same code FXML again (after hitting a problem in my main application) and got this error:
  

  Caused by: javafx.fxml.LoadException: java.lang.InstantiationException: javafx.scene.control.Menu
       at javafx.fxml.FXMLLoader$InstanceDeclarationElement.constructValue(FXMLLoader.java:609)
       at javafx.fxml.FXMLLoader$ValueElement.processStartElement(FXMLLoader.java:371)
       ...

  I am doing something stupid, or something has changed here (I couldn't see a bug for this)?
  
  zonski

  Hello
  I just tried the code FXML from your previous post here
  Width of problem MenuItem
  and it worked without problems (Windows 7, JDK7, JavaFX 2.0 U1)
  Michael

• FXML and style sheets

  FXML another question I'm afraid.
  
  The FXML [url http://download.oracle.com/javafx/2.0/fxml_get_started/jfxpub-fxml_get_started.htm] guide shows how we can define a style directly in the FXML, but anyone know if it is possible to define a style on a node class in FXML which is defined in a style sheet? In the code, this would be through:
  

  myLabel.styleClass().add("myLabelStyle")

  In FXML, I tried the following options (each fails in different ways):
  

  <Label text="My Label" style="myLabelStyle"/> 
  <Label text="My Label" styleClass="myLabelStyle"/>
  <Label text="My Label" fx:style="myLabelStyle"/>
  <Label text="My Label" fx:styleClass="myLabelStyle"/>

  Better that I came up with this day consists of defining the 'id' of the node, and then use the id selector "#" in the style sheet. It works but it is clumsy and if I have a fx:id for mapping to the controller I need to put both that is painful:
  

  <Label text="My Label" fx:id="myLabel" id="myLabel"/>

  Anyone got the best options?
  
  See you soon,.
  zonski

  Hello

  Here is a concrete example of what you wish to achieve.

  The fx:id is here also because this is necessary for the label stored in the right place in the controller. For style, I use the style class.

  .my-label {
     -fx-text-fill: green;
  }
  

  Michael

  Published by: MiPa on 04.09.2011 23:13

  Published by: MiPa on 04.09.2011 23:17

• Questions about JavaFX, Swing, Touch and Netbeans

  Hi all. I'm trying to implement a touch support with JavaFX within a Netbeans application and met with a wall of problems.

  When running through JavaFX, everything works fine. Touch events are recorded and processed as expected. However, it seems that the JFXPanel who lives my scene in, or the Netbeans window system itself, interferes with key events.

  The Panel is multitouch. I mainly work with JavaFX obtaining buttons to work properly.

  • Committee will draw mouse down and mouse released event, but the event of mouse button is raised only AFTER the finger is removed from the Panel. In my mind, the mouse down event should pull your finger touches the Panel, as this event is triggered when you click with the mouse button otherwise. This of course could very well have nothing to do with Java, Swing or Netbeans, since it's the BONE that fires the original event.
  • The Panel goes off the pressed key, touch stationary and released touch events correctly, but these events are not detected with JavaFX in Netbeans/Swing.
  • The onAction event behaves the way the mouse pressed event. Tire only after removing your finger, not to touch.
  • If you move your finger (within the limits of the button) after a touching, onAction and the mouse goes off. But only if.

  Does anyone have experience with the creation of tactile support JavaFX in Netbeans framework?

  It is on 7u25, Win7 Enterprise Java.

  OK, so there's actually a windows control panel to change settings touch. Buried in a settings dialog box is the option to disable press it and hold for right-click fully function. This causes a mouse down event to be fired as planned on the button down.

  So, the solution is to disable the right click of press and hold Windows itself. Just enter 'touch' in the search box and you should see an option "Change touch input parameters" in the control panel.

• How focus a JavaFX Group properly and set the pivot (reverse) by using translations in 3D space?

  Description:

  I m referring to the Oracle tutorial http://docs.Oracle.com/JavaFX/2/transformations/jfxpub-transformations.htm using the transformations.zip source code, which is available for download on this page. I Don t understand why they Center the xylophone in space 3D like this and why they calculate the pivot (reverse) using translations. So they are creating a large number of groups, including rectangles, representing the xylophone, in addition to finally to a group called "cam".    

  class Cam extends Group {     
       Translate t  = new Translate();     
       Translate p  = new Translate();     
       Translate ip = new Translate();     
       Rotate rx = new Rotate();     
       { rx.setAxis(Rotate.X_AXIS); }     
       Rotate ry = new Rotate();     
       { ry.setAxis(Rotate.Y_AXIS); }     
       Rotate rz = new Rotate();     
       { rz.setAxis(Rotate.Z_AXIS); }     
       Scale s = new Scale();     
       public Cam() { 
            super(); getTransforms().addAll(t, p, rx, rz, ry, s, ip); 
       }     
  }    
  
  final Cam camOffset = new Cam();    
  final Cam cam = new Cam();    
  ...    
  camOffset.getChildren().add(cam);    
  ...    
  final Scene scene = new Scene(camOffset, 800, 600, true);    
  ... 
  

  The Group "cam" is added to another group called "camOffset", which is added to the 'scene' as root the node.

  Until there , everything is understandable to me, but there is a method, called "frameCam (.)" which calls 4 other methods: ""

  public void setCamOffset(final Cam camOffset, final Scene scene) {         
       double width = scene.getWidth();         
       double height = scene.getHeight();         
       camOffset.t.setX(width/2.0);         
       camOffset.t.setY(height/2.0);     
  }    
  
  //=========================================================================    
  // setCamScale    
  //=========================================================================    
  
  public void setCamScale(final Cam cam, final Scene scene) {        
       final Bounds bounds = cam.getBoundsInLocal();         
       final double pivotX = bounds.getMinX() + bounds.getWidth()/2;         
       final double pivotY = bounds.getMinY() + bounds.getHeight()/2;         
       final double pivotZ = bounds.getMinZ() + bounds.getDepth()/2;         
       double width = scene.getWidth();         
       double height = scene.getHeight();         
       double scaleFactor = 1.0;         
       double scaleFactorY = 1.0;         
       double scaleFactorX = 1.0;         
  if (bounds.getWidth() > 0.0001) {            
       scaleFactorX = width / bounds.getWidth(); // / 2.0;        
  }        
  if (bounds.getHeight() > 0.0001) {            
       scaleFactorY = height / bounds.getHeight(); //  / 1.5;         
  }        
  if (scaleFactorX > scaleFactorY) {            
       scaleFactor = scaleFactorY;         
  } else {            
       scaleFactor = scaleFactorX;         
  }        
       cam.s.setX(scaleFactor);         
       cam.s.setY(scaleFactor);         
       cam.s.setZ(scaleFactor);     
  }    
  
  //=========================================================================    
  // setCamPivot    
  //=========================================================================    
  
  public void setCamPivot(final Cam cam) {        
       final Bounds bounds = cam.getBoundsInLocal();         
       final double pivotX = bounds.getMinX() + bounds.getWidth()/2;         
       final double pivotY = bounds.getMinY() + bounds.getHeight()/2;        
      final double pivotZ = bounds.getMinZ() + bounds.getDepth()/2;         
  
  //*1*        
       cam.p.setX(pivotX);         
       cam.p.setY(pivotY);         
       cam.p.setZ(pivotZ);         
  //*1*        
  
  //*2*        
       cam.ip.setX(-pivotX);         
       cam.ip.setY(-pivotY);         
       cam.ip.setZ(-pivotZ);         
  //*2*     }    
  
  //=========================================================================    
  // setCamTranslate    
  //=========================================================================    
  
  public void setCamTranslate(final Cam cam) {        
       final Bounds bounds = cam.getBoundsInLocal();         
       final double pivotX = bounds.getMinX() + bounds.getWidth()/2;         
       final double pivotY = bounds.getMinY() + bounds.getHeight()/2;         
       cam.t.setX(-pivotX);         
       cam.t.setY(-pivotY);     
  } 
  

  If the method ' setCamScale (...) 'is understandable,' setCamOffset (...) ' puts the root node ('camOffset') in the center of the screen, but I Don t understand the 2 following methods at all. Of course, the child ("cam") is not centered, by putting just the root node ('camOffset') in the center of the screen, but how they focus the xylophone / "cam" and set the pivot, using translations:

  Questions:

  1. Why they use 3 different translations (', 'ip', 'p')?
  2. Referring to ' setCamPivot (...) ': Why they are the first translation of 'cam.p' to "pivotX", 'pivotY' and 'pivotZ' and then 'cam.ip' to '-pivotX', '-pivotY' and '-pivotZ' (marked in the source code with * 1 * and * 2 *)? Should he not just put the Group at his position, where it has been positioned before, as if the method has never been called? That would be my guess, because I expect that an object is placed in the same position as before, if I first move with the values X, Y, Z and then return with the same values - X, - Y, - Z in the opposite direction.
  3. Even with the method ' setCamTranslate (...) ' ': Why use another translation "cam.t", moving the Group ("cam") with the same values "-pivotX', '-pivotY' (and not '-pivotZ'), which they used in the"setCamPivot (...) method `?

  Annotations:

  Of course it works, the xylophone is located in the center of the screen and could turn perfectly, without change of rotation point / pivot point, but I Don t understand how they did it. I read everything about layoutBound, boundsInLocal, boundsInParent, blogs about page layout and page layout goes into javaFX https://blogs.oracle.com/jfxprg/entry/the_peculiarities_of_javafx_layout and http://amyfowlersblog.wordpress.com/2011/06/02/javafx2-0-layout-a-class-tour/ and finally a large number of questions to stackoverflow, but I still Don t understand the meaning behind the methods stated.

  Before the call of ' frameCam (...) ', they ask:

  double halfSceneWidth = 375;  // scene.getWidth()/2.0;     
  double halfSceneHeight = 275;  // scene.getHeight()/2.0;    
  cam.p.setX(halfSceneWidth);    
  cam.ip.setX(-halfSceneWidth);    
  cam.p.setY(halfSceneHeight);    
  cam.ip.setY(-halfSceneHeight); 
  

  I deleted these lines, because it doesn't change anything.

  The base in place, is that there are three defined different rotations, one around each axis. Of course, these could be combined into a single rotation, but doing so would make the geometry in the mouse dragging very complex managers. As it is, the degree of rotation around each axis can be calculated and changed independently.

  In general, the rotations are defined by an angle, an axis and a (pivot) point. The axis is a 3D vector and goes through the pivot point; the rotation is around this axis through that point.

  In the configuration in the example, the pivot of each of the individual rotations is set to the default (0,0,0). Because we really want the rotation to be around the center of the group, not the original, the Group translates first point appropriate pivot (ip), the rotations are applied then (around (0,0,0) after translation by ip), then the group is reflected in its location of origin (p). These operations are not commutative, yes show ip, then the rotation, then p is not the same as when you run ip, then p, then the rotation (in the second, ip and p would cancel and rotation would be about (0,0,0) instead of around the Center).

  For good measure, there is a scale, that is also applied after ip (so that scaling occurs from the Center, not the original) and then a final translation.

  The final effect is that there is a lot of transformations that can be controlled independently. There is a scale (s), a rotation about each axis (rx, ry, rz), and a translation (t). The p in translations and its inverse ip are just "housekeeping" to ensure that rotation and scaling are done from the center of the screen, instead of (0,0,0).

  So:

  1. Why they use 3 different translations (', 'ip', 'p')?

  p and ip are translations for the rotation and scaling are done from the Center and not to the origin. t is a general translation, the user sees.

  Referring to ' setCamPivot (...) ': Why they are the first translation of 'cam.p' to "pivotX", 'pivotY' and 'pivotZ' and then 'cam.ip' to '-pivotX', '-pivotY' and '-pivotZ' (marked in the source code with * 1 * and * 2 *)? Should he not just put the Group at his position, where it has been positioned before, as if the method has never been called?

  He puts the group to its original position, but other changes are between p and ip. These transformations behave differently (in a planned way) because the group is translated when they are applied.

  Even with the method ' setCamTranslate (...) ' ': Why use another translation "cam.t", moving the Group ("cam") with the same values "-pivotX', '-pivotY' (and not '-pivotZ'), which they used in the"setCamPivot (...) method `?

  The t values are changed in the mouse Manager (with alt-middle mouse button-drag, which I can't test actually using my trackpad...). As you have noted, the effect of p and IP translation cancel out, so we end up with t, which can be changed by the user. They could have combined t and p a single transformation, but updated since the mouse Manager would have been more delicate, and the intent of the code would be less clear.

• Option buttons: ToggleGroup in JavaFX 8 (FXML)

  Hello!

  Since JDK8 b115 or b116, toggle groups of option buttons seems to not want to work more in the FXML files.

  Before, it worked:

  <fx:define>
      <ToggleGroup fx:id="RB_Group" />
  </fx:define>
  <RadioButton fx:id="rb1"  mnemonicParsing="false" toggleGroup="$RB_Group" />
  <RadioButton fx:id="rb2"  mnemonicParsing="false" toggleGroup="$RB_Group" />
  <RadioButton fx:id="rb3"  mnemonicParsing="false" toggleGroup="$RB_Group" />
  

  Then I tried the following...

      <ToggleGroup fx:id="RB_Group">
          <toggles>
              <RadioButton fx:id="rb1"  mnemonicParsing="false" />
              <RadioButton fx:id="rb2"  mnemonicParsing="false" />
              <RadioButton fx:id="rb3"  mnemonicParsing="false" />
          </toggles>
      </ToggleGroup>
  

  who does not work either.

  Then, I tried 2 scene generator, but I could not find any possibility to define groups of on/off radio buttons.

  No idea how to get it working again? Separated radio buttons are pretty useless...

  Thank you and best regards,

  J. Ishikawa

  The first version of your installer works for me on 1.8.0 - ea-b123 (do not use SceneBuilder).

• JavaFX 2.0 and CoverFlow

  Is there an example of CoverFlow in Java FX 2.0?
  
  I found this one, but it works with Java FX1.3 = > http://download.oracle.com/javafx/1.3/howto/Cover-Flow-Tutorial.html

  You can find the source code here
  \javafx-SDK2.0-beta\apps\src\DisplayShelf
  After unpacking the current construction of JavaFX beta and it doesn't
  work.

• Space for the heap JavaFx2 OutOfMemoryError:Java

  I create a simple application of JavaFx with FXML and CSS to change the theme in the user interface during execution. There are three buttons and a label in the scene. I define the different CSS for Label and ' background - fx - image "(format PNG, taille 1.23M) for BorderPane in the CSS file." " Application can change the theme in the user interface by clicking the button "Style. But Mem Usage will trigger and won't release when I click on one of the button "Style." Request will be OutOfMemoryError theme after about 30 times. I don't know how to fix it. Can someone help me?

      java.lang.OutOfMemoryError: Java heap space
       at java.awt.image.DataBufferInt.<init>(DataBufferInt.java:75)
       at java.awt.image.Raster.createPackedRaster(Raster.java:467)
       at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:1032)
       at java.awt.image.BufferedImage.<init>(BufferedImage.java:359)
       at com.sun.prism.j2d.J2DTexture.<init>(J2DTexture.java:46)
       at com.sun.prism.j2d.J2DResourceFactory.createTexture(J2DResourceFactory.java:72)
       at com.sun.prism.impl.BaseResourceFactory.createTexture(BaseResourceFactory.java:127)
  
  

  My environment: jdk1.7.0_51, Windows Server 2003 x 86, 3 G of RAM

  I'm sorry that I don't know how post IMG file - background.png (Pixel 1024 * 768, size 1.23 M) to the forum.

  Click on the button "AutoSwitch" for auto switching theme.

  Source code: Main.Java

     public class Main extends Application {
     
       private Stage primaryStage;
      
       public Stage getPrimaryStage() {
        return primaryStage;
       }
     
       public void setPrimaryStage(Stage primaryStage) {
        this.primaryStage = primaryStage;
       }
      
       private BorderPane rootPane;
      
       public BorderPane getRootPane() {
        return rootPane;
       }
     
     
       @Override
       public void start(Stage primaryStage) {
        try { 
         setPrimaryStage(primaryStage);
        
         URL url = new URL(getClass().getResource("AppFrame.fxml").toExternalForm());
      
         FXMLLoader loader =new FXMLLoader(url);
         rootPane = (BorderPane)loader.load();
        
         Scene scene = new Scene(rootPane,400,400);
        
      //   scene.getStylesheets().add(style1Url);
        
         primaryStage.setScene(scene);
        
         //MAX screen
         Screen screen = Screen.getPrimary();
         Rectangle2D bounds = screen.getVisualBounds();
      
         primaryStage.setX(bounds.getMinX());
         primaryStage.setY(bounds.getMinY());
         primaryStage.setWidth(bounds.getWidth());
         primaryStage.setHeight(bounds.getHeight());
        
         primaryStage.show();
       
         AppFrameController appFrameController = (AppFrameController)loader.getController();
         appFrameController.setAppMain(this);
        
        } catch(Exception e) {
         e.printStackTrace();
        }
       
     
       }
      
       public static void main(String[] args) {
        launch(args);
       }
      }
  

  AppFrameController.java

      public class AppFrameController  {
          private String style1Url = getClass().getResource("FxStyle1.css").toExternalForm();
          private String style2Url = getClass().getResource("FxStyle2.css").toExternalForm();
     
          @FXML private Label lblSceneTitle;
      
          private Main appMain;
     
       public Main getAppMain() {
        return appMain;
       }
     
       public void setAppMain(Main appMain) {
        this.appMain = appMain;
       }
     
     
       private int switchCount=0;
       
       public AppFrameController()
       {
       }
      
      
     
       public void handleClickStyle1()
       {
      //  System.out.println("handleClickStyle1");
       
        ObservableList<String> stylesheets = getAppMain().getRootPane().getStylesheets();
       
      //  System.out.println("Current Style="+stylesheets);
       
        stylesheets.remove(style2Url);
        if(!stylesheets.contains(style1Url))
        {
         stylesheets.add(style1Url);
        }
       
      //  System.out.println("    New Style="+stylesheets);
       
      //  lblSceneTitle.setText("FxStyle1");
       }
      
       public void handleClickStyle2()
       {
      //  System.out.println("handleClickStyle2");
       
        ObservableList<String> stylesheets = getAppMain().getRootPane().getStylesheets();
       
      //  System.out.println("Current Style="+stylesheets);
       
        stylesheets.remove(style1Url);
        if(!stylesheets.contains(style2Url))
        {
         stylesheets.add(style2Url);
        }
       
      //  System.out.println("    New Style="+stylesheets);
       
      //  lblSceneTitle.setText("FxStyle2");
       }
     
       public void handleClickSwitch()
       {
           SwitchCssTask handleTask = new SwitchCssTask(); 
        new Thread(handleTask).start();            
       
       }
      
          private class SwitchCssTask implements Runnable {
     
        @Override
        public void run() {
         while (true) {
     
          if (switchCount % 2 == 0) {
           handleClickStyle1();
          } else {
           handleClickStyle2();
          }
     
          switchCount++;
     
          System.out.println("Switch count=" + switchCount);
          try {
           Thread.sleep(1000);
          } catch (InterruptedException e) {
           e.printStackTrace();
          }
         }
        
        }
          
          
          }
      }
  

  AppFrame.fxml

  <?xml version="1.0" encoding="UTF-8"?>
  
  <?import java.lang.*?>
  <?import java.net.*?>
  <?import javafx.geometry.*?>
  <?import javafx.scene.control.*?>
  <?import javafx.scene.image.*?>
  <?import javafx.scene.layout.*?>
  <?import javafx.scene.layout.BorderPane?>
  
  <BorderPane prefHeight="362.0" prefWidth="749.3739013671875" xmlns:fx="http://javafx.com/fxml/1" xmlns="http://javafx.com/javafx/2.2" fx:controller="application.AppFrameController">
    <!-- TODO Add Nodes -->
    <center>
      <BorderPane id="center-pane" prefHeight="-1.0" prefWidth="-1.0" BorderPane.alignment="CENTER">
        <center>
          <VBox alignment="CENTER" prefHeight="200.0" prefWidth="100.0" spacing="20.0">
            <children>
              <Button mnemonicParsing="false" onAction="#handleClickStyle1" prefHeight="70.0" prefWidth="148.0" text="Style1" />
              <Button mnemonicParsing="false" onAction="#handleClickStyle2" prefHeight="70.0" prefWidth="148.0" text="Style2" />
              <Button mnemonicParsing="false" onAction="#handleClickSwitch" prefHeight="70.0" prefWidth="148.0" text="AutoSwitch" />
            </children>
          </VBox>
        </center>
      </BorderPane>
    </center>
    <stylesheets>
      <URL value="@FxStyle2.css" />
    </stylesheets>
    <top>
      <HBox alignment="CENTER" prefHeight="100.0" prefWidth="200.0" spacing="10.0" BorderPane.alignment="CENTER">
        <children>
          <Label id="scene-title" fx:id="lblSceneTitle" alignment="TOP_CENTER" prefWidth="371.0" text="Test FxStyle" />
        </children>
        <padding>
          <Insets bottom="15.0" left="12.0" right="12.0" top="15.0" />
        </padding>
      </HBox>
    </top>
  </BorderPane>
  
  

  FxStyle1.css

  #center-pane {  -fx-background-image: url("background.png");
  }
  
  #scene-title {
      -fx-font-family: "Tahoma";
      -fx-background-insets: 0;
      -fx-text-fill: green;
      -fx-font-weight: bold;       
      -fx-font-size: 4em; 
  
      -fx-effect: dropshadow( one-pass-box , rgba(0,0,0,0.9) , 1, 0.0 , 0 , 1 );
  }
  
  

  FxStyle2.css

  #center-pane {  -fx-background-image: url("background.png");
  }
  
  #scene-title {
      -fx-font-family: "Courier New";
      -fx-background-insets: 0;
      -fx-text-fill: red;
      -fx-font-weight: bold;       
      -fx-font-size: 4em; 
  
      -fx-effect: dropshadow( one-pass-box , rgba(0,0,0,0.9) , 1, 0.0 , 0 , 1 );
  }
  
  

  You change the stylesheets on a separate Thread (and not the FX Application thread), which is not allowed because it breaks the JavaFX threaded model. I highly doubt that it is the origin of the problem of memory (although it can, in theory).

  There was some memory leak problems in JavaFX 2.x associated with adding and removing the leaves of style and parent nodes. Have you tried to run this code in 8 JavaFX? There the same problems? You can also try to set the style sheet on the stage instead of the scene root pane.

  Either way, there is no need to implement all the ugly coupling of your Application class with the controller class. You can inject the defined root pane in the FXML directly into the controller by specifying a fx:id on this subject:

  and then in the controller just do

  @FXML
  private BorderPane rootPane ;
  

  Then do a

  ObservableList stylesheets = rootPane.getStylesheets();
  

  to change the style sheets in the rootPane, or

  ObservableList stylesheets = rootPane.getScene().getStylesheets();
  

  to change the style sheets in the scene.

• FX: understand and fx:script - when the included fxml file is parsed?

  I'm curious to know when an inclusive (through fx: include the tag) fxml document is parsed and if a script defined in the document main fxml can reference the elements of this document included. The example below, the results in the following error message: + "sun.org.mozilla.javascript.internal.EcmaError: ReferenceError: 'loadOrdersButton' is not defined." (< unknown source > #2) in < unknown source > on line number 2 "+"
  
  Example:
  
  Main.fxml
  The script fails to find the loadOrdersButton defined in HeaderFields.fxml. (Yes fx:id the button has the value loadOrdersButton)

  <?xml version="1.0" encoding="UTF-8"?>
  ...
  <BorderPane prefHeight="800.0" prefWidth="1200.0" xmlns:fx="http://javafx.com/fxml">
      <top>
              <fx:include source="HeaderFields.fxml">
                  <fx:script><![CDATA[ 
                      loadOrdersButton.setVisible( false );
                  ]]></fx:script>
              </fx:include>
      </top>
      <center>
      ...
      </center>
  ...
  </BorderPane>

  HeaderFields.fxml

  <?xml version="1.0" encoding="UTF-8"?>
  ...
  <AnchorPane xmlns:fx="http://javafx.com/fxml">
    <children>
      <Pane>
        <children>
  ...
          <Button fx:id="loadOrdersButton" />
        </children>
      </Pane>
    </children>
  </AnchorPane>

  I'm curious to know when an inclusive (through fx: include the tag) fxml document is parsed

  It is analyzed as soon as it is encountered. In other words, the include is completely processed before the next item in the file to include is processed.

  and if a script defined in the document main fxml can reference the elements of this document included.

  It can not. FXML IDs are considered "private" for the document and its associated controller (or any script code directly defined or referenced by this document). It is not possible to "inject" script in an inclusion code, as you seem to be attempting to do here.

  However, controller of inclusion is available for the document. So if the controller of HeaderFields.fxml exposed a property 'loadOrdersButton' via a getLoadOrdersButton() method, you could do something like this:

  Of course, another option is to simply include the script in the HeaderFields.fxml file:

  But I guess there's a reason you won't do.

• Differences between JavaFX CSS and css w3c standard

  This is a discussion topic that comes to mind after reading the comments in this thread Re: FXML, css and - fx-are-family
  
  Feel free to comment or share your ideas on the subject.
  
  Note that these comments relate to the meaning of assignment of names and semantics of the css tags and not the syntax and parsing of css (such as the w3c css and css javaFX seem to be equivalent with respect to later).
  
  You know, sometimes I find refreshing absence of JavaFX features in css. It is nice to have, well, almost everything, the JavaFX CSS documented on one page. I think that if you were to do the same for the w3c css then it would end up with a much bigger, more difficult to understand the document and even what should be the content of this document would probably quite controversial, in the same kind of way that ends up being the HTML5 specification. Microsoft has helped more than 7,000 w3c tests just to cover only a subset of css rules that are available in browsers today. The webkit project lists open CSS nearly a thousand bugs: https://bugs.webkit.org/buglist.cgi?product=WebKit & component = CSS & resolution =-. If the implementation even partial w3c CSS support is a complex project.
  
  When I started using JavaFX CSS I found differences in w3c CSS quite shocking, and it was difficult to account for their. Now that I'm used to JavaFX CSS, I don't have as much of a problem. The difference in names and semantics will be an obstacle to working on JavaFX developers who are familiar with w3c CSS - but the designers quickly will also discover that FXML is not HTML and Java isn't JavaScript and JavaFX deployment is not HTML deployment. Then, perhaps, in the bigger picture, it is not as big a deal that he would appear. Yet, one cannot think that any obstacle to the people easily pick up and adopting JavaFX makes the technology a disservice.
  
  There are other benefits that the JavaFX CSS in its own space of names to w3c css, in what she can evolve separately, it shouldn't be exactly the same because it has a different name, it should not implement fully w3c css as browsers do so because it is clearly something different by name etc. There is even precedent for it in the use of mozilla to moz - CSS and css properties http://css-infos.net/properties/webkit - web webkit prefixes as not in standard as many people have suggested. JavaFX CSS supports a JavaFX rendering engine and not an HTML rendering engine. It is quite remarkable that Oracle has been able to build and make available a model CSS for JavaFX which feels as familiar as to the w3c css, w3c css is very strongly targeted towards style a game completely different technology (HTML markup document object model and).
  
  It would be useful to have a tool which translates as w3c css to the approximations of JavaFX css and vice versa, or the ability for JavaFX to have a mode (perhaps a Boolean value when a style sheet is loaded) to perform an automatic alias or the mapping of the w3c css for javafx (at least for the subset of w3c css that would make sense to automatically translate for JavaFX css). I haven't checked the jira JavaFX in detail, then maybe a request for support already exists - it's perhaps in the private http://javafx-jira.kenai.com/browse/RT-9272 jira.
  
  The JavaFX css model is really powerful and I found really useful some of the additions that it adds above the css 2.1 Basic found regularly in browsers. With the next CSS Java model object http://javafx-jira.kenai.com/browse/RT-17293, you will also better get access by Java programming.
  
  Then, good work on the construction and implementation of this complex device...

  Thanks for the comments. The gap between JavaFX CSS and CSS from W3C will be an evolutionary process. It would be nice to use the stylesheet of a standard basis, but there is not always a mapping from 1-1 to JavaFX. But for properties that can be mapped, it is something that should be supported. For example, we should be able to deal with 'police' or '- fx - police '.

  I made public http://javafx-jira.kenai.com/browse/RT-9272.