Re: error in tutorial
ated,
and needlessly self harming *technical* error defended using the
worst possible defense against very real issues(the creation of this
thread is proof). Source files(or zips containing such) are not
libraries(AKA "libs") and it causes IDE issues(among other things).
The fix is *really* simple.
and the whole (in essence) "everyone who works on JavaFX is a someone
doing it in their free time is BS. Oracle developers are payed to
work on JavaFX and are the ones who originally made JavaFX(AFAIK) and
(presumably) the Gradle script. If someone with basically no
knowledge of Gradle such as myself can scan through a file or use
ctrl + f and read variable names then I'd hope someone with actual
experience could do better. Maybe I'm wrong and am the one in
actuality that is smoking shrooms.
B: I friendly discuss issues and opportunities with fellow community
members, where I respect other opinions, keep discussions polite and
technical.
That's funny because I seem to remember during a JDK(or maybe it was
exclusively JavaFX?) event that a presenter made a rather rude joke
about my multi-threading issue I brought up on this list a long time
ago. I don't remember specifically who made the joke but I do know as
someone who watches said events on YouTube that those events are very
incestuous. I guess because it was the other way around that it was
OK though.
TL;DR: People in glass houses shouldn't throw stones.
C: somewhere between A and B?
- Johan
On Sat, Dec 28, 2019 at 12:11 AM Ty Young <mailto:youngty1...@gmail.com>> wrote:
On 12/27/19 4:40 PM, John-Val Rose wrote:
> Ty,
>
> If it’s so easy to fix then why don’t you just fix it?
I don't exactly have the ability to directly push changes to the
repo...
>
> John-Val
>
>> On 28 Dec 2019, at 09:14, Ty Young mailto:youngty1...@gmail.com>> wrote:
>>
>>
>>> On 12/27/19 4:19 AM, Johan Vos wrote:
>>> Hi David,
>>>
>>> What tutorial are you talking about? If you refer to
https://openjfx.io,
>>> that is a community-initiative, developed at
>>> https://github.com/openjfx/openjfx-docs .
>>> So if you have issues and PR's, that is the place to submit
and discuss
>>> with the other contributors to that site.
>>
>> Only the Netbeans section has a warning telling you to delete
src.zip. Neither Intellij nor Eclipse do.
>>
>>
>> A user shouldn't have to do that anyway though! This could be
easily fixed. Literally all you need to do is in this section:
>>
>>
>> // Zip module sources for standalone SDK
>> //
>> // NOTE: the input is taken from the
modular-sdk/modules_src dir
>> // so that we don't have to duplicate the logic and create
another
>> // temporary directory. This is somewhat inelegant, since
the bundled sdk
>> // and the standalone sdk should be independent of one
another, but seems
>> // better than the alternatives.
>> def zipSourceFilesTask =
project.task("zipSourceFilesStandalone$t.capital", type: Zip,
dependsOn: buildModulesTask) {
>> destinationDir = file("${standaloneLibDir}")
>> archiveName = standaloneSrcZipName
>> includeEmptyDirs = false
>> from modulesSrcDir
>> include "**/*.java"
>> }
>>
>>
>> change:
Re: error in tutorial
nd it causes IDE issues(among other things).
The fix is *really* simple.
and the whole (in essence) "everyone who works on JavaFX is a someone
doing it in their free time is BS. Oracle developers are payed to
work on JavaFX and are the ones who originally made JavaFX(AFAIK) and
(presumably) the Gradle script. If someone with basically no
knowledge of Gradle such as myself can scan through a file or use
ctrl + f and read variable names then I'd hope someone with actual
experience could do better. Maybe I'm wrong and am the one in
actuality that is smoking shrooms.
B: I friendly discuss issues and opportunities with fellow community
members, where I respect other opinions, keep discussions polite and
technical.
That's funny because I seem to remember during a JDK(or maybe it was
exclusively JavaFX?) event that a presenter made a rather rude joke
about my multi-threading issue I brought up on this list a long time
ago. I don't remember specifically who made the joke but I do know as
someone who watches said events on YouTube that those events are very
incestuous. I guess because it was the other way around that it was
OK though.
TL;DR: People in glass houses shouldn't throw stones.
C: somewhere between A and B?
- Johan
On Sat, Dec 28, 2019 at 12:11 AM Ty Young <mailto:youngty1...@gmail.com>> wrote:
On 12/27/19 4:40 PM, John-Val Rose wrote:
> Ty,
>
> If it’s so easy to fix then why don’t you just fix it?
I don't exactly have the ability to directly push changes to the
repo...
>
> John-Val
>
>> On 28 Dec 2019, at 09:14, Ty Young mailto:youngty1...@gmail.com>> wrote:
>>
>>
>>> On 12/27/19 4:19 AM, Johan Vos wrote:
>>> Hi David,
>>>
>>> What tutorial are you talking about? If you refer to
https://openjfx.io,
>>> that is a community-initiative, developed at
>>> https://github.com/openjfx/openjfx-docs .
>>> So if you have issues and PR's, that is the place to submit
and discuss
>>> with the other contributors to that site.
>>
>> Only the Netbeans section has a warning telling you to delete
src.zip. Neither Intellij nor Eclipse do.
>>
>>
>> A user shouldn't have to do that anyway though! This could be
easily fixed. Literally all you need to do is in this section:
>>
>>
>> // Zip module sources for standalone SDK
>> //
>> // NOTE: the input is taken from the
modular-sdk/modules_src dir
>> // so that we don't have to duplicate the logic and create
another
>> // temporary directory. This is somewhat inelegant, since
the bundled sdk
>> // and the standalone sdk should be independent of one
another, but seems
>> // better than the alternatives.
>> def zipSourceFilesTask =
project.task("zipSourceFilesStandalone$t.capital", type: Zip,
dependsOn: buildModulesTask) {
>> destinationDir = file("${standaloneLibDir}")
>> archiveName = standaloneSrcZipName
>> includeEmptyDirs = false
>> from modulesSrcDir
>> include "**/*.java"
>> }
>>
>>
>> change:
Re: error in tutorial
her rude joke
about my multi-threading issue I brought up on this list a long time
ago. I don't remember specifically who made the joke but I do know as
someone who watches said events on YouTube that those events are very
incestuous. I guess because it was the other way around that it was OK
though.
TL;DR: People in glass houses shouldn't throw stones.
C: somewhere between A and B?
- Johan
On Sat, Dec 28, 2019 at 12:11 AM Ty Young <mailto:youngty1...@gmail.com>> wrote:
On 12/27/19 4:40 PM, John-Val Rose wrote:
> Ty,
>
> If it’s so easy to fix then why don’t you just fix it?
I don't exactly have the ability to directly push changes to the
repo...
>
> John-Val
>
>> On 28 Dec 2019, at 09:14, Ty Young mailto:youngty1...@gmail.com>> wrote:
>>
>>
>>> On 12/27/19 4:19 AM, Johan Vos wrote:
>>> Hi David,
>>>
>>> What tutorial are you talking about? If you refer to
https://openjfx.io,
>>> that is a community-initiative, developed at
>>> https://github.com/openjfx/openjfx-docs .
>>> So if you have issues and PR's, that is the place to submit
and discuss
>>> with the other contributors to that site.
>>
>> Only the Netbeans section has a warning telling you to delete
src.zip. Neither Intellij nor Eclipse do.
>>
>>
>> A user shouldn't have to do that anyway though! This could be
easily fixed. Literally all you need to do is in this section:
>>
>>
>> // Zip module sources for standalone SDK
>> //
>> // NOTE: the input is taken from the
modular-sdk/modules_src dir
>> // so that we don't have to duplicate the logic and create
another
>> // temporary directory. This is somewhat inelegant, since
the bundled sdk
>> // and the standalone sdk should be independent of one
another, but seems
>> // better than the alternatives.
>> def zipSourceFilesTask =
project.task("zipSourceFilesStandalone$t.capital", type: Zip,
dependsOn: buildModulesTask) {
>> destinationDir = file("${standaloneLibDir}")
>> archiveName = standaloneSrcZipName
>> includeEmptyDirs = false
>> from modulesSrcDir
>> include "**/*.java"
>> }
>>
>>
>> change:
Re: error in tutorial
On 12/28/19 4:53 AM, Johan Vos wrote: Hi Ty, Since I have absolutely no idea what you are talking about, I have a few questions: 1. "... push changes to the repo..."? -> It would help giving a bit context instead of talking about "the repo". Since this is the openjfx-dev list, chances are high you're talking about the JavaFX repository at https://github.com/openjdk/jfx. In that case, please read the README and CONTRIBUTING files there for advice on how to propose/make changes (note that this will probably take longer than 1 minute, as we have strong quality checks in place). If you talk about a different "repo", please follow the explicit or implicit rules on that repo(sitory). For example, if you talk about https://github.com/openjfx/openjfx-docs , please create an issue and file a PR, and work with the community to get it accepted. (note that in this case, this should not be discussed on the openjfx-dev list (note the *dev*)). This is not an issue of documentation. IDEs can and do provide the ability to designate an entire folder as a location of project libraries. You can specify a directory manually via command line in which contains Java 9 modules. To continue to entertain the idea that this is an issue of documentation is simply crazy. It's an easily fixable technical error. 2. You refer to informal or formal talks you had, but it is totally unclear to me who you talked to about what. Frankly, we spent lots of time moving all code and as much as possible the documentation to github, so we can easily track discussions. (for JavaFX bugs, we use JBS, so that can be discussed there) If someone said "it’s the way we’ve always done it”" please refer to the issue where your request has been made and subsequently rejected, so I can have a look at the context, It was an email a very long time ago on this list. Too lazy to dig it up, but I'm pretty sure it was from Kevin Rushforth. Again, very long time ago at this point. 3. Can you write a few words about what the word "Community" means to you? Many people in the JavaFX Ecosystem spent tons of spare time in making the JavaFX "Community" a friendly place. I'm interested in your opinion about that word. To give a few options, does it mean A: I insult people and companies, use words like "smoking shrooms" and "stubborn" and I expect everything I think about to be fixed magically (since I suppose the volunteers have no life apart from doing what I want them to do) "community" is a funny word to describe JavaFX given it is 100% owned by Oracle and which no one(AFAIK) can contribute to without signing away their rights to their own code. If this was a feature request I'd understand this nonsense but that's not at all what this is. This is a self created, self perpetuated, and needlessly self harming *technical* error defended using the worst possible defense against very real issues(the creation of this thread is proof). Source files(or zips containing such) are not libraries(AKA "libs") and it causes IDE issues(among other things). The fix is *really* simple. and the whole (in essence) "everyone who works on JavaFX is a someone doing it in their free time is BS. Oracle developers are payed to work on JavaFX and are the ones who originally made JavaFX(AFAIK) and (presumably) the Gradle script. If someone with basically no knowledge of Gradle such as myself can scan through a file or use ctrl + f and read variable names then I'd hope someone with actual experience could do better. Maybe I'm wrong and am the one in actuality that is smoking shrooms. B: I friendly discuss issues and opportunities with fellow community members, where I respect other opinions, keep discussions polite and technical. That's funny because I seem to remember during a JDK(or maybe it was exclusively JavaFX?) event that a presenter made a rather rude joke about my multi-threading issue I brought up on this list a long time ago. I don't remember specifically who made the joke but I do know as someone who watches said events on YouTube that those events are very incestuous. I guess because it was the other way around that it was OK though. TL;DR: People in glass houses shouldn't throw stones. C: somewhere between A and B? - Johan On Sat, Dec 28, 2019 at 12:11 AM Ty Young <mailto:youngty1...@gmail.com>> wrote: On 12/27/19 4:40 PM, John-Val Rose wrote: > Ty, > > If it’s so easy to fix then why don’t you just fix it? I don't exactly have the ability to directly push changes to the repo... > > John-Val > >> On 28 Dec 2019, at 09:14, Ty Young mailto:youngty1...@gmail.com>> wrote: >> >> >>> On 12/27/19 4:19 AM, Johan Vos wrote: >>> Hi David, >>
Re: error in tutorial
14, Ty Young mailto:youngty1...@gmail.com>> wrote:
>>
>>
>>> On 12/27/19 4:19 AM, Johan Vos wrote:
>>> Hi David,
>>>
>>> What tutorial are you talking about? If you refer to
https://openjfx.io,
>>> that is a community-initiative, developed at
>>> https://github.com/openjfx/openjfx-docs .
>>> So if you have issues and PR's, that is the place to submit
and discuss
>>> with the other contributors to that site.
>>
>> Only the Netbeans section has a warning telling you to delete
src.zip. Neither Intellij nor Eclipse do.
>>
>>
>> A user shouldn't have to do that anyway though! This could be
easily fixed. Literally all you need to do is in this section:
>>
>>
>> // Zip module sources for standalone SDK
>> //
>> // NOTE: the input is taken from the
modular-sdk/modules_src dir
>> // so that we don't have to duplicate the logic and create
another
>> // temporary directory. This is somewhat inelegant, since
the bundled sdk
>> // and the standalone sdk should be independent of one
another, but seems
>> // better than the alternatives.
>> def zipSourceFilesTask =
project.task("zipSourceFilesStandalone$t.capital", type: Zip,
dependsOn: buildModulesTask) {
>> destinationDir = file("${standaloneLibDir}")
>> archiveName = standaloneSrcZipName
>> includeEmptyDirs = false
>> from modulesSrcDir
>> include "**/*.java"
>> }
>>
>>
>> change:
Re: error in tutorial
Hi Ty,
Since I have absolutely no idea what you are talking about, I have a few
questions:
1. "... push changes to the repo..."? -> It would help giving a bit context
instead of talking about "the repo". Since this is the openjfx-dev list,
chances are high you're talking about the JavaFX repository at
https://github.com/openjdk/jfx. In that case, please read the README and
CONTRIBUTING files there for advice on how to propose/make changes (note
that this will probably take longer than 1 minute, as we have strong
quality checks in place). If you talk about a different "repo", please
follow the explicit or implicit rules on that repo(sitory). For example, if
you talk about https://github.com/openjfx/openjfx-docs , please create an
issue and file a PR, and work with the community to get it accepted. (note
that in this case, this should not be discussed on the openjfx-dev list
(note the *dev*)).
2. You refer to informal or formal talks you had, but it is totally unclear
to me who you talked to about what. Frankly, we spent lots of time moving
all code and as much as possible the documentation to github, so we can
easily track discussions. (for JavaFX bugs, we use JBS, so that can be
discussed there) If someone said "it’s the way we’ve always done it”"
please refer to the issue where your request has been made and subsequently
rejected, so I can have a look at the context,
3. Can you write a few words about what the word "Community" means to you?
Many people in the JavaFX Ecosystem spent tons of spare time in making the
JavaFX "Community" a friendly place. I'm interested in your opinion about
that word. To give a few options, does it mean
A: I insult people and companies, use words like "smoking shrooms" and
"stubborn" and I expect everything I think about to be fixed magically
(since I suppose the volunteers have no life apart from doing what I want
them to do)
B: I friendly discuss issues and opportunities with fellow community
members, where I respect other opinions, keep discussions polite and
technical.
C: somewhere between A and B?
- Johan
On Sat, Dec 28, 2019 at 12:11 AM Ty Young wrote:
>
> On 12/27/19 4:40 PM, John-Val Rose wrote:
> > Ty,
> >
> > If it’s so easy to fix then why don’t you just fix it?
>
>
> I don't exactly have the ability to directly push changes to the repo...
>
>
> >
> > John-Val
> >
> >> On 28 Dec 2019, at 09:14, Ty Young wrote:
> >>
> >>
> >>> On 12/27/19 4:19 AM, Johan Vos wrote:
> >>> Hi David,
> >>>
> >>> What tutorial are you talking about? If you refer to
> https://openjfx.io,
> >>> that is a community-initiative, developed at
> >>> https://github.com/openjfx/openjfx-docs .
> >>> So if you have issues and PR's, that is the place to submit and discuss
> >>> with the other contributors to that site.
> >>
> >> Only the Netbeans section has a warning telling you to delete src.zip.
> Neither Intellij nor Eclipse do.
> >>
> >>
> >> A user shouldn't have to do that anyway though! This could be easily
> fixed. Literally all you need to do is in this section:
> >>
> >>
> >> // Zip module sources for standalone SDK
> >> //
> >> // NOTE: the input is taken from the modular-sdk/modules_src dir
> >> // so that we don't have to duplicate the logic and create another
> >> // temporary directory. This is somewhat inelegant, since the
> bundled sdk
> >> // and the standalone sdk should be independent of one another,
> but seems
> >> // better than the alternatives.
> >> def zipSourceFilesTask =
> project.task("zipSourceFilesStandalone$t.capital", type: Zip, dependsOn:
> buildModulesTask) {
> >> destinationDir = file("${standaloneLibDir}")
> >> archiveName = standaloneSrcZipName
> >> includeEmptyDirs = false
> >> from modulesSrcDir
> >> include "**/*.java"
> >> }
> >>
> >>
> >> change:
>
Re: error in tutorial
On 12/27/19 4:40 PM, John-Val Rose wrote:
Ty,
If it’s so easy to fix then why don’t you just fix it?
I don't exactly have the ability to directly push changes to the repo...
John-Val
On 28 Dec 2019, at 09:14, Ty Young wrote:
On 12/27/19 4:19 AM, Johan Vos wrote:
Hi David,
What tutorial are you talking about? If you refer to https://openjfx.io,
that is a community-initiative, developed at
https://github.com/openjfx/openjfx-docs .
So if you have issues and PR's, that is the place to submit and discuss
with the other contributors to that site.
Only the Netbeans section has a warning telling you to delete src.zip. Neither
Intellij nor Eclipse do.
A user shouldn't have to do that anyway though! This could be easily fixed.
Literally all you need to do is in this section:
// Zip module sources for standalone SDK
//
// NOTE: the input is taken from the modular-sdk/modules_src dir
// so that we don't have to duplicate the logic and create another
// temporary directory. This is somewhat inelegant, since the bundled sdk
// and the standalone sdk should be independent of one another, but seems
// better than the alternatives.
def zipSourceFilesTask =
project.task("zipSourceFilesStandalone$t.capital", type: Zip, dependsOn:
buildModulesTask) {
destinationDir = file("${standaloneLibDir}")
archiveName = standaloneSrcZipName
includeEmptyDirs = false
from modulesSrcDir
include "**/*.java"
}
change:
Re: error in tutorial
Ty,
If it’s so easy to fix then why don’t you just fix it?
John-Val
> On 28 Dec 2019, at 09:14, Ty Young wrote:
>
>
>> On 12/27/19 4:19 AM, Johan Vos wrote:
>> Hi David,
>>
>> What tutorial are you talking about? If you refer to https://openjfx.io,
>> that is a community-initiative, developed at
>> https://github.com/openjfx/openjfx-docs .
>> So if you have issues and PR's, that is the place to submit and discuss
>> with the other contributors to that site.
>
>
> Only the Netbeans section has a warning telling you to delete src.zip.
> Neither Intellij nor Eclipse do.
>
>
> A user shouldn't have to do that anyway though! This could be easily fixed.
> Literally all you need to do is in this section:
>
>
> // Zip module sources for standalone SDK
> //
> // NOTE: the input is taken from the modular-sdk/modules_src dir
> // so that we don't have to duplicate the logic and create another
> // temporary directory. This is somewhat inelegant, since the bundled sdk
> // and the standalone sdk should be independent of one another, but seems
> // better than the alternatives.
> def zipSourceFilesTask =
> project.task("zipSourceFilesStandalone$t.capital", type: Zip, dependsOn:
> buildModulesTask) {
> destinationDir = file("${standaloneLibDir}")
> archiveName = standaloneSrcZipName
> includeEmptyDirs = false
> from modulesSrcDir
> include "**/*.java"
> }
>
>
> change:
Re: error in tutorial
On 12/27/19 4:19 AM, Johan Vos wrote:
Hi David,
What tutorial are you talking about? If you refer to https://openjfx.io,
that is a community-initiative, developed at
https://github.com/openjfx/openjfx-docs .
So if you have issues and PR's, that is the place to submit and discuss
with the other contributors to that site.
Only the Netbeans section has a warning telling you to delete src.zip.
Neither Intellij nor Eclipse do.
A user shouldn't have to do that anyway though! This could be easily
fixed. Literally all you need to do is in this section:
// Zip module sources for standalone SDK
//
// NOTE: the input is taken from the modular-sdk/modules_src dir
// so that we don't have to duplicate the logic and create another
// temporary directory. This is somewhat inelegant, since the
bundled sdk
// and the standalone sdk should be independent of one another, but
seems
// better than the alternatives.
def zipSourceFilesTask =
project.task("zipSourceFilesStandalone$t.capital", type: Zip, dependsOn:
buildModulesTask) {
destinationDir = file("${standaloneLibDir}")
archiveName = standaloneSrcZipName
includeEmptyDirs = false
from modulesSrcDir
include "**/*.java"
}
change:
destinationDir = file("${standaloneLibDir}")
to:
destinationDir = file("${standaloneSdkDir}")
That's it. Literally less than a minute, like I said. You can put zip
files in zip files, it doesn't matter. This is a really stupid thing to
be stubborn about.
Thanks,
- Johan
On Thu, Dec 26, 2019 at 9:26 PM David Green
wrote:
This step fails:
3\. Create a library
Go to File - Project Structure - Libraries and add the JavaFX 13
SDK
as a library to the project. Point to the lib folder of the JavaFX SDK.
The src.zip located in this package lib will cause the build in IJ to
fail. I
don't know why, since it is source, albeit zipped.
To get the project to build, I had to remove it. I placed it in a new src
folder I created at the same level as lib in the sdk.
Re: error in tutorial
Hi David, What tutorial are you talking about? If you refer to https://openjfx.io, that is a community-initiative, developed at https://github.com/openjfx/openjfx-docs . So if you have issues and PR's, that is the place to submit and discuss with the other contributors to that site. Thanks, - Johan On Thu, Dec 26, 2019 at 9:26 PM David Green wrote: > This step fails: > > > > 3\. Create a library > > Go to File - Project Structure - Libraries and add the JavaFX 13 > SDK > as a library to the project. Point to the lib folder of the JavaFX SDK. > > > > The src.zip located in this package lib will cause the build in IJ to > fail. I > don't know why, since it is source, albeit zipped. > > > > To get the project to build, I had to remove it. I placed it in a new src > folder I created at the same level as lib in the sdk. > > > >
error in tutorial
This step fails: 3\. Create a library Go to File - Project Structure - Libraries and add the JavaFX 13 SDK as a library to the project. Point to the lib folder of the JavaFX SDK. The src.zip located in this package lib will cause the build in IJ to fail. I don't know why, since it is source, albeit zipped. To get the project to build, I had to remove it. I placed it in a new src folder I created at the same level as lib in the sdk.
Re: tutorial
On 10/01/2018 05:45 PM, Karl-Philipp Richter wrote: > Am 27.09.2018 um 16:39 schrieb Glenn Holmer: >> On https://openjfx.io/openjfx-docs/ I don't see any content, just >> buttons and links that don't seem to do anything. Tried both Firefox and >> Chrome. Is it just me? > Works for me on Firefox on Ubuntu 18.04. I have NoScript installed and > needed to active some scripts (jsdelivr.net) in order to be able to see > the content. Provide a screenshot if you have further trouble. I tried it again this afternoon and it was working properly. -- Glenn Holmer (Linux registered user #16682) "After the vintage season came the aftermath -- and Cenbe."
Re: tutorial
Hi, Am 27.09.2018 um 16:39 schrieb Glenn Holmer: > On https://openjfx.io/openjfx-docs/ I don't see any content, just > buttons and links that don't seem to do anything. Tried both Firefox and > Chrome. Is it just me? Works for me on Firefox on Ubuntu 18.04. I have NoScript installed and needed to active some scripts (jsdelivr.net) in order to be able to see the content. Provide a screenshot if you have further trouble. -Kalle
Re: tutorial
Glenn Holmer wrote: On https://openjfx.io/openjfx-docs/ I don't see any content, just buttons and links that don't seem to do anything. Tried both Firefox and Chrome. Is it just me? Works for me on SeaMonkey. Regards, Joe1962
Re: tutorial
Works for me on Vivaldi. On Thu, Sep 27, 2018 at 5:39 PM Glenn Holmer wrote: > On https://openjfx.io/openjfx-docs/ I don't see any content, just > buttons and links that don't seem to do anything. Tried both Firefox and > Chrome. Is it just me? > > -- > Glenn Holmer (Linux registered user #16682) > "After the vintage season came the aftermath -- and Cenbe." >
tutorial
On https://openjfx.io/openjfx-docs/ I don't see any content, just buttons and links that don't seem to do anything. Tried both Firefox and Chrome. Is it just me? -- Glenn Holmer (Linux registered user #16682) "After the vintage season came the aftermath -- and Cenbe."
Re: Tutorial
I should note that this is an early-access build. The final release is planned for next week [1] at which time we will send out an announcement with more information. -- Kevin [1] http://mail.openjdk.java.net/pipermail/openjfx-dev/2018-June/022004.html On 9/14/2018 5:51 AM, Kevin Rushforth wrote: A basic set of instructions is here: http://docs.gluonhq.com/javafx11/ Read the Introduction and then click on the other links for information on downloading the SDK or using JavaFX via maven modules. -- Kevin On 9/13/2018 11:47 AM, Amno Jeeuw wrote: I'm looking for a installation tutorial for OpenJavaFX. Is there one that's up-to-date? Thanks in advance.
Re: Tutorial
A basic set of instructions is here: http://docs.gluonhq.com/javafx11/ Read the Introduction and then click on the other links for information on downloading the SDK or using JavaFX via maven modules. -- Kevin On 9/13/2018 11:47 AM, Amno Jeeuw wrote: I'm looking for a installation tutorial for OpenJavaFX. Is there one that's up-to-date? Thanks in advance.
Tutorial
I'm looking for a installation tutorial for OpenJavaFX. Is there one that's up-to-date? Thanks in advance.
Is there a guide/tutorial on writing your own Effect? At the same level as say SepiaEffect
Just to be clear, I know how to WritePixels to a buffer and manipulate them ad nauseum. But I want to write an Effect the way SepiaEffect extends Effect. BTW why is there even a SepiaEffect? it makes no sense at all -- rjs
Re: Is there a guide/tutorial on writing your own Effect? At the same level as say SepiaEffect
Hi Ramon, Currently the effects framework has no public API for extending it for new effects. WritableImage would be the only option of a public API that you could use at this point... ...jim On 2/3/2016 1:44 PM, Ramon Santiago wrote: Just to be clear, I know how to WritePixels to a buffer and manipulate them ad nauseum. But I want to write an Effect the way SepiaEffect extends Effect. BTW why is there even a SepiaEffect? it makes no sense at all
Re: bad TableView example in the tutorial
On 23.07.15 13:35, Henning Brackmann wrote:
https://docs.oracle.com/javase/8/javafx/user-interface-tutorial/table-view
.htm
Why are the SimpleStringProperties in the person class private?
IMHO the Person class should be:
Example 13-3 Creating the Person Class
public static class Person {
public final SimpleStringProperty firstName;
public final SimpleStringProperty lastName;
public final SimpleStringProperty email;
private Person(String fName, String lName, String email) {
this.firstName = new SimpleStringProperty(fName);
this.lastName = new SimpleStringProperty(lName);
this.email = new SimpleStringProperty(email);
}
}
public fields are never a good idea! If you want a JavaFX Bean then
those should be exposed with firstNameProperty(): StringProperty, ...
Example 13-5 Setting Data Properties to Columns
firstNameCol. setCellValueFactory(param - param.getValue().firstName);
lastNameCol.setCellValueFactory(param - param.getValue().lastName);
emailCol.setCellValueFactory(param - param.getValue().email);
I think the tuturial should promote typesafe bindings.
The advantage of the PropertyValueFactory is that it also works for
Pojos/JavaBeans.
The real question is what one wants to present and teach people with
those examples.
If you eg want to make them aware of PropertyValueFactory because in
most applications data will be coming from a backend who most like only
sends simple DTOs then example is perfectly fine.
Tom
--
Thomas Schindl, CTO
BestSolution.at EDV Systemhaus GmbH
Eduard-Bodem-Gasse 5-7, A-6020 Innsbruck
http://www.bestsolution.at/
Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck
bad TableView example in the tutorial
https://docs.oracle.com/javase/8/javafx/user-interface-tutorial/table-view
.htm
Why are the SimpleStringProperties in the person class private?
IMHO the Person class should be:
Example 13-3 Creating the Person Class
public static class Person {
public final SimpleStringProperty firstName;
public final SimpleStringProperty lastName;
public final SimpleStringProperty email;
private Person(String fName, String lName, String email) {
this.firstName = new SimpleStringProperty(fName);
this.lastName = new SimpleStringProperty(lName);
this.email = new SimpleStringProperty(email);
}
}
Example 13-5 Setting Data Properties to Columns
firstNameCol. setCellValueFactory(param - param.getValue().firstName);
lastNameCol.setCellValueFactory(param - param.getValue().lastName);
emailCol.setCellValueFactory(param - param.getValue().email);
I think the tuturial should promote typesafe bindings.
Best regards!
Henning
