Hi Shinmera,

I have been using 3d-vectors and 3d-matrices for probably like 3 or 4 years now, and it has been a trusty companion.  (I do have some bugs to report, tho)

I don't know if you remember talking to me but I am creating a CAD system for mechanical/architectural/civil design (REGEN).  I have lots of big pieces in place but still have to build more.

One of the pieces I have been using is VkTk, meaning Vulkan Toolkit.  I built VkTk with wrappers around the C++ library 'Dear ImGui'.  It always was intended just to be a crutch for a system fully in Lisp.  Anyway, I have followed the immediate mode gui to its logical conclusion that it is not actually the best system for creating GL type guis in Lisp.  Add to that, that one of the people I am helping, Kaveh Kardan, isn't interested in anything with C++ in it.  And I agree.  It's time to drop VkTk.

I have been peripherally interested in Alloy for some time.  I recently started to take a good look at it.  I'm working on replacing the sdf/bmfont stuff with a native Lisp text rendering solution that I helped hatch for Kaveh.  So at this time I would like to get the OpenGL 3.3 version of Alloy running.  Note: you can't find sdf/bmfont anywhere.

In addition I am starting to rip out the vulkan graphics engine from REGEN and make it a module of its own, which I hope to use as a new backend for Alloy.

I still have to implement some stuff related to text size for Alloy to get it working, but I'll get there.

I'll probably fuse the event system/command system from Hemlock (the legacy CL text editor) into the project as well.  I have Hemlock working in VkTk.  It will be much cleaner in Alloy since I will be able to unify the concept of an Alloy window with the Hemlock window.  ImGui makes this an ugly hack.

So I'm working on Alloy if you have any advice.  What was your long term plan (if any) for Alloy?  Are you using it for any software?

Thanks,
Andrew Wolven