pugl.git - Pugl GUI library

Age	Commit message (Collapse)	Author	Files	Lines
2021-06-07	MacOS: Reset GL context after initial window reshape	falkTX	1	-0/+1

2021-05-25	Rename event structs in a more readable style	David Robillard	1	-2/+2
	Aside from reading more naturally, this avoids clashes with types that are not events, like PuglEventFlags. This is also more consistent with the C++ bindings, where "EventExpose" would be quite strange, for example. Apologies for the noise. Aliases to the old names will be preserved in the deprecated API like other things for a short while.
2021-05-25	Fix some conversion warnings	David Robillard	1	-2/+2
	Avoids narrowing warnings when building as C++, and uses unsigned operands with bitwise operators in various places.
2021-01-02	Simplify clang-format configuration and format all code	David Robillard	1	-116/+116

2020-11-26	Remove file documentation	David Robillard	1	-5/+0
	These will not be used in the Sphinx documentation, and most were self-explanatory and only there to make the Doxygen index look nice anyway. Where there was actually useful information, it has been preserved as regular comments.
2020-11-25	Move puglEnterContext and puglLeaveContext to GL backends	David Robillard	1	-0/+12
	These only do anything for OpenGL, and it seems unlikely that they will ever be used for anything else. So, move them to the GL headers to remove clutter from the core API, and ensure that they are only used in GL applications that include the appropriate headers and link with a GL backend. Also add missing C++ bindings.
2020-10-30	Simplify header names	David Robillard	1	-1/+1

2020-10-30	Move implementation source files to a conventional src directory	David Robillard	1	-0/+203
	I think this attempt to be optionally header-only was misguided, particularly installing source code to the system include path. Typically anyone vendoring code just includes the repository and builds from there anyway. This commit moves all the implementation code to a typical src directory (Don't Be Weird). I still think there is some value in simple "inline" deployment, but that would be better achieved another way, like producing a single-file amalgamation that builds anywhere, ala sqlite.