I remembered one more. Maybe it's already included in the "use
FXCollections" bit but it's not explicitly stated.
I think that using FXCollections methods toFront, toBack, etc is faster
than reorganizing the collection manually, yourself, right?
On another subject, I think it would be important to
Thanks Pedro, will put these on the wiki. The layout vs. bind is an interesting
question and one that isn't entirely clear. I use some of both depending,
really, on what is most natural for the case I'm facing rather than on a strict
performance basis. Because Java doesn't have binding in the la
Dan, Thanks for the thoughts / questions, I've added them to the tail of the
wiki for processing.
> 1) turning cache to true and cache hint to SPEED I haven't seen explained
> what the drawbacks are to doing this. I assume there is some trade-off for
> turning this on otherwise it would be on
Hi,
Some of my ideas (might be wrong):
- use layouts whenever possible instead of binds for laying out nodes
- reduce use of effects. If the effect is static use images instead of
effect
- In javafx 1.3 it would cost more to use stroke instead of a fill. For
instance if you have a rectangle with a
etc? How does a web browser manage to
cache all these pages in history and would the same approach be performant
for JFX?
On Tue, Jun 4, 2013 at 7:11 AM, Richard Bair wrote:
> Hi,
>
> We had a brief meeting this afternoon and kicked off a performance tips n'
> tricks wik
Hi,
We had a brief meeting this afternoon and kicked off a performance tips n'
tricks wiki page, which is presently a dumping ground of ideas that will get
massaged into something useful. The content on this wiki will then be used by
the docs team to produce some official documentation
