Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #35536 > unrolled thread

Re: Conveniance methods in Swing and JavaFX

Back to article view | Back to comp.lang.java.programmer

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Conveniance methods in Swing and JavaFX Arne Vajhøj <arne@vajhoej.dk> - 2016-09-02 14:14 -0400

#35536 — Re: Conveniance methods in Swing and JavaFX

On 9/2/2016 2:06 PM, Stefan Ram wrote:
>   The grandfather of my grandfather had left a blotter, wherein
>   he wrote
>
> jframe.getContentPane().add(
>
>   , but my grandfather told me that in his days, he already was
>   able to write
>
> jframe.add(
>
>   . Apparently, someone must have added a conveniance method name
>   »add« to »javax.swing.JFrame« in the meantime.
>
>   Now, today, we write,
>
> javafxpane.getChildren().add( component )
>
>   . Yeah, we write ».getChildren()«, then ».getChildren()«, and
>   later, ».getChildren()«. It seems to be a step backwards to the
>   days of »getContentPane()«. Surely, someone must have had thought
>   about adding convenience methods to classes like »javafx.scene.
>   layout.StackPane« too, but then he must have refrained from adding
>   such convenience methods for some reason. Why? Maybe there were
>   some bad experiences or consequences of the convenience methods
>   in Swing observed?

Convenience methods tend to be added later.

If you are lucky then JavaFX will get the.

If the tell the team, then you increase the probability of being
lucky.

:-)

Arne

[toc] | [standalone]

Back to top | Article view | comp.lang.java.programmer

csiph-web