You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(2) |
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(1) |
Feb
|
Mar
(3) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(5) |
Oct
(9) |
Nov
|
Dec
(1) |
2007 |
Jan
|
Feb
(37) |
Mar
(7) |
Apr
|
May
|
Jun
(3) |
Jul
(5) |
Aug
(6) |
Sep
|
Oct
(9) |
Nov
(9) |
Dec
(2) |
2008 |
Jan
|
Feb
(9) |
Mar
(6) |
Apr
|
May
(2) |
Jun
(5) |
Jul
(4) |
Aug
(6) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
2009 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(7) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2011 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Bertrand C. <bco...@cl...> - 2006-03-24 21:50:56
|
Steven Queen wrote : > I've used GLC on SGI's for several years and I've *very* happy to see an > updated and portable version of this library. I'm not a C++ fan and > since OpenGL is C based, it's wonderful to have a native (anti-aliased!) > font rendering capability with a clear and well documented API. I'm > going to begin integrating QuesoGLC into all my current and future > projects. > > Thank you for making this available to the public! > > sq...@so... Thank you very much for your enthusiastic support. I really appreciate it and I am glad to see that QuesoGLC fits your needs. Since you are a user of the original GLC library from SGI, feel free to report any difference between QuesoGLC and SGI's that you may encounter so that I can improve QuesoGLC compatibility with SGI's implementation of GLC. Also keep an eye on the web site since I plan to release version 0.4 in the next few weeks. Best regards, Bertrand Coconnier. |
From: Steven Q. <Ste...@na...> - 2006-03-24 11:32:59
|
I've used GLC on SGI's for several years and I've *very* happy to see an updated and portable version of this library. I'm not a C++ fan and since OpenGL is C based, it's wonderful to have a native (anti-aliased!) font rendering capability with a clear and well documented API. I'm going to begin integrating QuesoGLC into all my current and future projects. Thank you for making this available to the public! sq...@so... |
From: Bertrand C. <bco...@cl...> - 2006-01-30 23:58:29
|
This release brings internal improvements and many bugfixes. Among others, the following minor feature enhancements have been added : - Support of the Unicode format UTF-8 has been finalized. - The GLC_SGI_full_name extension that allows you to get the "full name" of Type 1 fonts has been added. - The management of character maps in QuesoGLC has been revamped (conformance with the GLC specs 0.2 has been improved). More details in the changelog. Feedback is highly appreciated ! |
From: Bertrand C. <bco...@us...> - 2005-10-22 11:44:09
|
William Swanson wrote : > Hello, > I am working on an OpenGL project under the Windows platform. QuesoGLC looks > very useful to me, and I am considering writing a port. Does anyone have > some general advice in this area? So far, the source seems pretty much > Linux-only, with a hint that the code is portable (but not yet ported). The > biggest issue seems to be replacing the fontconfig library with a Win32 > equivalent. Are there any other gotchas that I should look out for? > > -s_tec Hi William, Welcome to the QuesoGLC project ! It would be great if you could write a Win32 port for QuesoGLC. But since I've almost never coded seriously under Windows, I am not sure that my advices are very helpful. Moreover, I am afraid that the code is not yet that portable since some Unix-only functions are disseminated all over the code. First of all, you should have a look to src/global.c and src/misc.c where some POSIX threads functions are used. QuesoGLC uses a mutex and thread specific datas (pthread_key_create, pthread_getspecific and pthread_setspecific) that must be replaced by their Win32 counterpart. Then you should get rid of the fontconfig dependency and replace it by the corresponding Win32 functionalities. IMHO this is not the easiest part since, no effort has been made to isolate fontconfig functions from the main codebase. I can barely estimate the difficulty of the task but it may not be as easy as it seems at a first glance... Anyway, you should consider to work with the CVS codebase rather than the QuesoGLC 0.2 codebase since the former has evolved pretty much since release 0.2. Of course, don't hesitate to send me an e-mail if you need any explanation about what the code is *supposed to* do and what it actually does ;-) Keep me posted, Bertrand. |
From: William S. <swa...@gm...> - 2005-10-18 02:04:03
|
Hello, I am working on an OpenGL project under the Windows platform. QuesoGLC look= s very useful to me, and I am considering writing a port. Does anyone have some general advice in this area? So far, the source seems pretty much Linux-only, with a hint that the code is portable (but not yet ported). The biggest issue seems to be replacing the fontconfig library with a Win32 equivalent. Are there any other gotchas that I should look out for? -s_tec |
From: Bertrand C. <bco...@ho...> - 2005-09-17 14:14:50
|
Since QuesoGLC is a project that is not much active, a blog has been made public in order to post the few (and slow) events related to QuesoGLC life... For more details see the blog itself : http://quesoglc.sourceforge.net/redblog Special thanks to the guys of RedBlog for their work. |
From: Yves B. <kaf...@la...> - 2005-07-17 21:38:57
|
SGVsbG8gYWxsLAoKSXMgdGhlcmUgc29tZW9uZSBvdXQgdGhlcmUgPyBJIGhhdmUgYSBsaXR0bGUg cXVlc3Rpb24gYWJvdXQgUXVlc29HTEMuLi4KCkJlc3QgcmVnYXJkcywKCi0tIAoobzwgfCBZdmVz IEJhaWxseSDCoDogaHR0cDovL2thZmthLWZyLm5ldCDCoCB8IC1vKQovL1wgfCBMaW51eCBEaWpv biDCoDogaHR0cDovL3d3dy5jb2FndWwub3JnIHwgLy9cClxfLyB8IMKgIMKgIMKgIMKgIMKgIMKg IMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgfCBcXy9gCg== |
From: Bertrand C. <bco...@ho...> - 2005-04-27 20:12:24
|
This is the first mail ever on the QuesoGLC general mailing list. |