Bug 216592 - New Controller from an existing FXML
New Controller from an existing FXML
Status: RESOLVED FIXED
Product: javafx
Classification: Unclassified
Component: Editor
7.3
PC Linux
: P3 (vote)
: 7.3
Assigned To: Svata Dedic
issues@javafx
: PLAN
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-09 12:01 UTC by Svata Dedic
Modified: 2012-08-09 12:15 UTC (History)
0 users

See Also:
Issue Type: TASK
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Svata Dedic 2012-08-09 12:01:33 UTC
Create a new Controller class, based on an existing .fxml description file.
Comment 1 Svata Dedic 2012-08-09 12:15:38 UTC
Very basic behaviour implemented. 

Fields types are overwritten for components with ID, and overloaded methods added for event handlers. If a binding/handler is not matched to XML, it looses its @FXML annotation and if not used (and empty, in the case of handlers), it is removed from the source.

Controller is generated according to the fx:controller attribute, or if the name is missing, controller name is guessed from fxml filename.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo