pugl.git - Pugl GUI library

Age	Commit message (Collapse)	Author	Files	Lines
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-24	Separate stub backends from other backends	David Robillard	1	-7/+7
	Stub backends were a dependency of other backends to allow some code reuse. However, that can cause conflicting symbols if multiple backends are linked into the same binary, which should be possible. To avoid this, move the shared code into the platform implementation, and export those symbols so that backends can use them. This adds some semi-public platform-specific API that can only be used by backends included with pugl. They are undocumented, subject to change at any time without a corresponding version change, and may not be used by third parties (for example by custom backends in an application).
2021-01-02	Clean up includes	David Robillard	1	-0/+2

2021-01-02	Simplify clang-format configuration and format all code	David Robillard	1	-14/+14

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-10-30	Move implementation source files to a conventional src directory	David Robillard	1	-0/+75
	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.