Bug 1141 - Release 2.3.0 - Drop all requests here .. (group)
Summary: Release 2.3.0 - Drop all requests here .. (group)
Status: RESOLVED FIXED
Alias: None
Product: General
Classification: JogAmp
Component: builds (show other bugs)
Version: unspecified
Hardware: All all
: --- enhancement
Assignee: Sven Gothel
URL:
Depends on:
Blocks:
 
Reported: 2015-03-06 23:45 CET by Sven Gothel
Modified: 2015-03-11 18:46 CET (History)
1 user (show)

See Also:
Type: ---
SCM Refs:
Workaround: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Gothel 2015-03-06 23:45:19 CET

    
Comment 1 Johann Sorel 2015-03-06 23:48:42 CET
Finding appropriate constants in GL and it's subclasses GL2ES2, GL4. is painfull, so much constants.

Here is different approach, maybe mixing a tree like organization with heritage GL,GL2ES,GL4,.. could be a solution to obtain something more friendly and reduce errors.

partial example :
https://bitbucket.org/Eclesia/unlicense/src/tip/engine/engine-opengl-util/src/main/java/un/impl/opengl/GLC.java?at=default
Comment 2 Sven Gothel 2015-03-06 23:50:00 CET
(In reply to comment #1)
> Finding appropriate constants in GL and it's subclasses GL2ES2, GL4. is
> painfull, so much constants.
> 
> Here is different approach, maybe mixing a tree like organization with
> heritage GL,GL2ES,GL4,.. could be a solution to obtain something more
> friendly and reduce errors.
> 
> partial example :
> https://bitbucket.org/Eclesia/unlicense/src/tip/engine/engine-opengl-util/
> src/main/java/un/impl/opengl/GLC.java?at=default

I see, you do a semantic split - manual. However, this cannot be generated, since states can be used for many purposes and I dislike duplication

I know the GL* interfaces mix up things .. however, they at least give a notion of what profile is being run. Even though devs still need to validate whether the function / enum is an extension .. and supported.
Comment 3 Sven Gothel 2015-03-06 23:53:09 CET
Allow me to state that we shall not make a fundamental change for 2.3.0.

With the upcoming Vulkan, things will be quite different,
since states will only remain for internal operation
and the user needs to 'invent' own semantics and its code.
Comment 4 Sven Gothel 2015-03-11 18:46:49 CET
in process of closing ..