Re: Redsquare NEWT ES2 demo on OSX
Posted by
BrickFarmer on
Dec 02, 2010; 10:40am
URL: https://forum.jogamp.org/Redsquare-NEWT-ES2-demo-on-OSX-tp1995777p2005203.html
Don't take it the wrong way, I just really hate the bugzilla tool, it feels too much like my day job where the tool is used mostly for politics. I never did understand why managers consider projects with the highest bug fixing rates, to be better than the projects with hardly any bugs.
Everyone has their own way of feeding back into a community, although some would just squat on the sidelines watching. I'm actually doing my best to help in my own way. My plan was to write some demos showing NEWT functionality, possibly as a maven achetype, but I can't do that so far because of the OSX issues. Plus I had the OSX build issues, and now I have some wierd errors at deployment time. So it seems like I'm just not having much luck.
I've spent a solid week of my holidays now trying to get various parts of JOGL working and reporting my findings. Plus the time it took to work out how to install and use git to access the sources. In the meantime I've been trying to get things working with maven, which I've also been feeding back into the community. My understanding of JOGL/OpenGL is very weak, and I'm still trying to understand what NEWT even is. Which is part of the reason for my efforts. By working on a demo I could help document what it is you are doing. But my understanding is far from being at the level of a true developer, think of me more as a Tester. Someone who is able to cut and paste some code and get something working, but far from understands it all. If I post something here, I'm not necessarily looking for support, since I know you are busy trying to finish the product, but I do feel a duty to document my findings.
If something as simple as the gears demo stops working under OSX, I don't think responses along the lines of 'write a test case' or 'log a bug' is helpful. I took the effort to download and install 7 different versions of JOGL to isolate the build that caused the issue. I also identified a possible 'check in' comment via hudson that sounded related. I think that's already quite a lot more than many of your users would do. Although I admit that without knowing my background with bugzilla, my comment sounded rude. So I apologise for that.