Hi all, after reading all the different views I thought I add my 2€c...
As Tony mentioned I created an experimental POC for a JavaFX window system on top of NetBeans (ok what remains once you get rid of ALL Swing dependencies). With this experience I would suggest the following: 1. Try to identify what we can reuse in a post Swing world (JavaFX or HTML5 as a replacement does not matter for this step) 2. Decouple this (or more if possible) from actual Swing dependencies 3. Start the discussion again based on the new API's Anyone familiar with E4? Sounds very similar to this? So what do we really expect from a UI agnostic NetBeans Platform? Hope this starts a discussion about API design and ends the flame war.. Thanks for great API's Jarda - let's create even better API's together for the future. Sven P.S. The prototype is available as efx and a sample app vmFX at bitbucket... dormant for a while... Am 15.03.2018 19:43 schrieb <toni.ep...@eppleton.de>: > > >Yes, that would be the logical next step. I created a simple experiment > like that for JavaFX a while ago and Sven > >Reimers did a little more work with JavaFX & a NB Platform with a new > Window System, MenuBar etc.. It's > >totally possible, and this is what I would suggest as the next step. If > you want to join, that would be great." > > Sorry, I just realize that this sounds very confusing. I wanted to say: > The same thing we did for JavaFX could be easily done for a HTML5 based UI, > because NB Platform is quite modular and things like the Window System are > not bound to Swing. > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
