To Be Or Not To Be (Native), was:Look and feel mechanism?
swpalmer at gmail.com
Mon Dec 9 10:53:39 PST 2013
Doesn’t this also imply that you are using AWT/Swing? JavaFX has no way to be hosted in anything other than a JFXPanel or a JavaFX Stage. Only the JFXPanel can be hosted in a windows that allows heavy weight (native) controls, or even allows JNI code to get the window handle so you can integrate your JavaFX with other native bits.
On Dec 9, 2013, at 12:55 PM, Stephen F Northover <steve.x.northover at oracle.com> wrote:
> Today, you can only exercise the choice by writing native code and you face heavyweight / lightweight issues depending on the platform and API.
> On 2013-12-09 12:31 PM, Felix Bembrick wrote:
>> Stephen, I thoroughly agree that JavaFX is by far the best choice for non-native apps/widgets which is precisely my point. They are the kind of apps perfect for using JavaFX.
>> But you refer to giving people the choice to go native where appropriate. How can I exercise that choice? Where is the support for native widgets in JavaFX?
>> And isn't the real Holy Grail being able to mix native and non-native widgets in the same app with all features of Node being available to every widget, with all the effects and transforms, all the CSS/styling and with all the performance?
>> Could JavaFX ever be such a toolkit?
>>> On 10 Dec 2013, at 2:24, Stephen F Northover <steve.x.northover at oracle.com> wrote:
>>> Here are my thoughts on the matter. Give people the choice of whether to use native or non-native components. In some applications, everything will be non-native. In others, only the main content area will be non-native and the rest will be native. In some mobile applications, perhaps the preference pages will be native and other parts will not.
>>> JavaFX is the best choice for non-native widgets and we are committed to making it the best toolkit all around.
More information about the openjfx-dev