Improving Min/Max performance in "e4-on-JavaFX" applications

When it comes to performance in JavaFX one of the biggest problems is that if you detach and reattach a big SceneGraph-Part you run:

• CSS-Pass
• Layout-Pass

So in general one should avoid those operations as much as possible but there are situations you can't get something implemented without doing exactly this kind of thing. In the current architecture of e(fx)clipse we need to use this reparenting in case of minimizing/maximizing certain areas of your e4-on-JavaFX application which might lead to a very poor user experience if you eg have a MPartStack with many complex substructures (like eg our code editor). Today we took a closer look for one of our customers to find out if we - the e(fx)clipse - framework can do anything to fix that problem and after some experiments we managed to come up with a solution who allows us to reparent the content of an MPartStack in constant time: Watch on YouTube In general I'd say that such optimization should not be required and JavaFX CSS and Layout performance HAS to be improved in general and JavaFX-Components have to get smarter in not running CSS-Passes on SG-Parts who are currently not showing.