Hi John,
6) As a result this new tarball has the following directories
(just ignore those you don't want):
gtk3_bsd/
gtk3_lgpl/
gtk2_bsd/
gtk2_glext/
This is also explained in the README.
This is starting to look promising.
Are you intending to release it as an installable library? Or is it your
intention that users just copy the
code into a their own packages?
In my opinion, as less libraries we have the better.
Libraries put lots of problems for final users, for small Linux distros
and developers as well. How many times we went through this: "I would
like to use your app but when I try to compile it I have this error
message: something.h not found"?
So answering your question, I see two paths that make me happy:
1) developers integrate this code in their own packages (that's why I
was so keen in distributing this as simplified BSD or OO0). This is
great because users can feel in control, they can modify everything to
fit their own needs, they can learn with it, they can improve it, all
the joys of free software. The code is so small (less than 30 lines of
actual commands) that it is easy to maintain (this is important given
the changes that lie ahead: changes in GTK 3, changes in OpenGL 3.0,
changes in X/Wayland... the next 5 years will be difficult for graphic
free software).
2) GTK uses this code as a starting point to add official support for
OpenGL (that's why I added the LGPL version), so it would be included in
the official GTK releases. Looking into the obvious lack of interest of
GTK for OpenGL in the last 15 years I am not very optimistic, but well,
miracles happen...
C
_______________________________________________
gtkglext-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/gtkglext-list
