Performance Tips n' Tricks wiki page

[Pedro Duque Vieira]

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 explain how one can
debug if the cache hint is being used successfully or if it is hurting
performance.

Thanks, cheers,

On Tue, Jun 4, 2013 at 12:28 AM, Richard Bair <richard.bair at oracle.com>wrote:

> 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 language, it is harder to use it so excessively that it causes a
> problem like it could in FX Script.
>
> Richard
>
> On Jun 3, 2013, at 3:54 PM, Pedro Duque Vieira <
> pedro.duquevieira at gmail.com> wrote:
>
> > 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 stroke with would be more
> efficient
> > to draw 2 rectangles with a fill, so the other one would be used to
> produce
> > the stroke. Don't know if this still applies.
> >
> > My 2 cents. Kind regards,
> >
> > --
> > Pedro Duque Vieira
>
>


-- 
Pedro Duque Vieira