-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Synchronizing Controllers and FXML file automatically #13
Comments
@OlivierAlves could you provide a pull request for this feature? Just in case can we somehow Combine this with the "Generate Controller" command? |
Hey! I was wondering, if that feature eventually made it into the release version. From what I read here, it doesn't look like it... is there any further development planned? I'm currently teaching JavaFX at an institute and I think this feature could improve adoption among people new to the topic of JavaFX-MVC-based development. Please let me know! Johannes |
as no PR has ever been provided no this feature is not available |
Good morning,
Here is a new the issue related to this topic on eclipse community forum: Check topic here
While developing a small Eclipse plugin for our developers, we implemented a feature that allows to generate missing FXML fields and handlers in the associated controller.
The option is called at the moment "Generate missing FXML Fields and Handlers" and is accessible in the "Source" popup menu when right-clicking on the Controller class.
At the moment we rely on a naming convention for both controller and FXML i.e. an FXML file called Xyz.fxml is expected to have XyzController.java in the same package. Like this, from the controller name one can find out the associated FXML file. Not having a specific naming convention would require an additional dialog for the user to select the FXML file.
It supports generation of fields (from elements having fx:id attribute), event handlers (e.g. onAction, onMouseDragOver, etc), property change listeners and observable collections change listeners. All of them having FXML annotation and default (package) access.
Please let us know how to proceed.
Cheers,
Olivier
The text was updated successfully, but these errors were encountered: