1427 2020-05-07 13:52:02 +0200 Move JMonkeyEngine's JogAmp backend into JogAmp repositories 2023-07-12 01:25:40 +0200 1 1 1 General Default default 3.0.0 All all UNCONFIRMED https://hub.jmonkeyengine.org/t/merged-dropping-jogl/43046 P5 enhancement --- 814 0 gouessej sgothel FEATURE --- oldest_to_newest 6668 0 gouessej 2020-05-07 13:52:02 +0200 More than 10 years ago, I tried to use JMonkeyEngine 2 with JOGL, a contractor (paid by me) fixed a few things but those contributions have never been contributed back into upstream. I contributed to JMonkeyEngine 3 for months, especially its JogAmp backend based on JOGL 2 but as it was very time consuming, I looked for another maintainer for this backend since 2018. As far as I remember, it was dropped twice. It was dropped for the last time in April 2020: https://github.com/jMonkeyEngine/jmonkeyengine/pull/1339 At most 3 bugs remained unfixed: https://github.com/jMonkeyEngine/jmonkeyengine/issues/796 https://github.com/jMonkeyEngine/jmonkeyengine/issues/1045 https://github.com/jMonkeyEngine/jmonkeyengine/issues/1092 JMonkeyEngine's maintainers haven't fixed those bugs, they are few and they seem to be very busy. As I don't want to resurrect this backend again in JMonkeyEngine's repository as it would be dropped again later, I suggested its engine leader to host JMonkeyEngine's JogAmp backend in our repositories. That way, I could contribute without using Github and our work wouldn't be lost. Please, can you create a GIT repository for JMonkeyEngine in our infrastructure? I'll upload the subproject jme3-jogl into it. I think that I'll be able to fix at least the very first bug and I'll look for a maintainer to take care of this backend on the long term. In the meantime, I'll do what I can to make it work. You can assign this bug to me after the creation of the GIT repository. I'll move the bug reports above into our bug tracker later and assign them to myself. References: https://hub.jmonkeyengine.org/t/merged-dropping-jogl/43046 6669 1 gouessej 2020-05-07 21:19:51 +0200 In my humble opinion, fixing the very first bug I mentioned will be a lot easier with full support of relative mouse motion events, see bug report 814.