3:57
*To: *John Hendrikx
*Cc: *[email protected]
*Subject: *Aw: Developer documentation
I like this idea as well. And I agree, especially the snapping insight
are good to document as this topic really isn't trivial.
I think we should stick to the official JDK, which also follows the
i
o render this
format.
-- Marius
*Gesendet:* Freitag, 12. Mai 2023 um 21:02 Uhr
*Von:* "John Hendrikx"
*An:* [email protected]
*Betreff:* Developer documentation
In PR https://github.com/openjdk/jfx/pull/910 a lot of "new" insights
were gained in the snapping logic. Michael Str
y
*From: *openjfx-dev on behalf of Marius
Hanl
*Date: *Friday, May 12, 2023 at 13:57
*To: *John Hendrikx
*Cc: *[email protected]
*Subject: *Aw: Developer documentation
I like this idea as well. And I agree, especially the snapping insight
are good to document as this topic real
On 5/12/23 12:02 PM, John Hendrikx wrote:
The build documentation may be a good candidate to place there as well.
I'm all for it. Some of us were in agreement on moving at least the
build instructions back in November 2022. See the following thread on
the mailing list from a pull request disc
ate: Friday, May 12, 2023 at 13:57
To: John Hendrikx
Cc: [email protected]
Subject: Aw: Developer documentation
I like this idea as well. And I agree, especially the snapping insight are good
to document as this topic really isn't trivial.
I think we should stick to the official JD
s format.
-- Marius
Gesendet: Freitag, 12. Mai 2023 um 21:02 Uhr
Von: "John Hendrikx"
An: [email protected]
Betreff: Developer documentation
In PR https://github.com/openjdk/jfx/pull/910 a lot of "new" insights
were gained in the snapping logic. Michael Straus
second John's suggestion, but also I am curious as to what other people think.
-andy
From: openjfx-dev on behalf of John Hendrikx
Date: Friday, May 12, 2023 at 12:02
To: [email protected]
Subject: Developer documentation
In PR https://github.com/openjdk/jfx/pull/910 a lot of "new
of work, I usually encourage projects to include
developer documentation as part of the Git repository. This allows any
developer to access and modify the documentation easily, and allows you
to keep documentation in sync with relevant commits (and one can ask
developers to do so as part of the
