Forum > OpenGL
Provided GL, GLext librarys vs dglOpenGL
ChrisR:
1. The license for my raycast project is included with the source project. It would be nice to have this included:
https://github.com/neurolabusc/vx
2. I agree that for Linux and Windows (but not MacOS), you can mix-and-match legacy and modern OpenGL. These operating systems support OpenGL, and well coded legacy OpenGL can be as efficient as modern OpenGL. There are two reasons I prefer modern OpenGL. First, it abandons immediate mode, so the code only uses the efficient modes that better leverage GPU hardware. Second, it is a lot easier to port code to other platforms (MacOS, or handheld devices that use OpenGL ES).
Seenkao:
Давайте смотреть объективно. Я ни кого не принуждаю использовать "устаревший" OpenGL и, так же не принуждаю пользоваться "новым".
Всё зависит от создаваемого приложения и от разработчика который будет выбирать, что ему использовать.
Но по поводу MacOS и OpenGL ES, я не совсем согласен, но "новый" OpenGL более совместим, только на начальном уровне, когда узнаёшь лучше, то вполне понимаешь, что OpenGL ES - это сильно урезанная версия OpeGL, и в любом случае, надо будет доделывать многое, для использования OpenGL ES как (вместо) OpenGL. Если, конечно, не использовать библиотеки, где это всё уже реализовано. Но опять же и в "устаревшем" OpenGL ES так же есть реализации OpenGL.
А MacOS, ни как не влияет, на OpenGL, кроме выбора версии OpenGL. А если выбран "устаревший" OpenGL, то тут уже зависит от того, какая видеокарта. Если старая, то будет работать немедленный доступ, если новая, то будет простая эмуляция "устаревшего" режима.
И, не стоит забывать, что на "устаревшем" OpenGL некоторые вещи мы в любом случае не сможем сделать, так как в "новом". :)
google translate:
Let's look objectively. I do not force anyone to use the "outdated" OpenGL, and I also do not force anyone to use the "new" one.
It all depends on the application being created and on the developer who will choose what to use.
But about MacOS and OpenGL ES, I don't quite agree, but the "new" OpenGL is more compatible, only at the initial level, when you get to know better, then you quite understand that OpenGL ES is a heavily stripped-down version of OpeGL, and in any case, it is necessary will do a lot to use OpenGL ES as (instead of) OpenGL. Unless, of course, you use libraries where all this has already been implemented. But again, the "legacy" OpenGL ES also has OpenGL implementations.
And MacOS doesn't affect OpenGL in any way, except for the choice of the OpenGL version. And if "outdated" OpenGL is selected, then it already depends on what video card. If an old video card, then immediate access will work, if a new one, then there will be a simple emulation of the "outdated" mode.
And, do not forget that on the "outdated" OpenGL we will not be able to do some things anyway, as in the "new" one. :)
avra:
--- Quote from: avra on December 24, 2019, 08:29:42 am ---
--- Quote from: ChrisR on December 23, 2019, 04:29:35 pm ---The project '6e_raycast' is based on my code, specifically https://github.com/neurolabusc/vx but it does not include the BSD license
--- End quote ---
Is it OK if I add https://github.com/neurolabusc/vx/blob/master/license.txt to '6e_raycast' dir? I would automate that with my conversion script, and that will work as long as they keep that directory structure. If you give me a green light I will do it like that. I still think that you should also report that to PilotLogic forum, since I can not fix license violation in CodeTyphon (where I get pl_* components from). I can not do that because they banned me after seeing that I have made pl_* open source components available to Lazarus users.
--- End quote ---
I did not receive a reply from ChrisR neither here neither via PM, so I will delete '6e_raycast' directory from pl_opengl package examples in new ct4laz. If someone has an objection for any other directory or package, please report it.
ChrisR:
You are free to use my code as long as you respect the license. The included license is a simple BSD 2-Clause license, which requires you to include the license when you share the code.
https://opensource.org/licenses/BSD-2-Clause
This is a permissive license that is fully compatible with sharing. You can even use my code in professional projects without paying me anything, as long as you include the license.
avra:
--- Quote from: ChrisR on October 27, 2020, 06:46:11 pm ---You are free to use my code as long as you respect the license. The included license is a simple BSD 2-Clause license, which requires you to include the license when you share the code.
https://opensource.org/licenses/BSD-2-Clause
This is a permissive license that is fully compatible with sharing. You can even use my code in professional projects without paying me anything, as long as you include the license.
--- End quote ---
I have already finished packing pl_opengl for new ct4laz and '6e_raycast' dir is excluded. If you have any other directory that you wish excluded please say so. If you give me your mail in private message, I can send you pl_opengl for full check before official release. There will also be RC candidate available for a while.
At the end I have decided not to be the one who should fix this specific CodeTyphon licensing issue, and as with all previously known cases I will exclude reported code from ct4laz. So, the real address for fixing issues will be PilotLogic. Once they have your license back into sources - I can include that dir again.
Navigation
[0] Message Index
[*] Previous page