Showing posts with label opengl. Show all posts
Showing posts with label opengl. Show all posts

Thursday, December 20, 2012

Qix is Back... and introducing CLinch


Well, Qix is back in production. It's been a while so let me bring everyone up to speed. I worked on Qix, and I got some things working. Then I found out about shaders and ended up taking some time to learn how to use them. Then I started to write a game and got as far as porting some of the Bullet Engine and performing some movement tests. Then there were some family issues.

One day I decided to go to the Lambda Lounge Indianapolis Meeting. I made mention of Qix and they asked for a presentation. I created a quick presentation application in lisp using some of the code I had written. That's when I found horde3d. Horde is very well organized, and while it still has some warts in my opinion, I quickly built the program here.

This, however, had whet my apatite. Using Horde as my example I cranked out a new library in a few weeks. Then more family issues and XCOM was released. Finally, a couple of weeks ago I decided I was going to finish enough to release on github. I asked #lispgames for a good name and I ended up choosing CLinch. CLinch is now available to use.

So then I took CLinch and ported my presentation from cl-horde and made a youtube presentation of my original. I have been completely astounded by the response. CLinch is still 0.1 presently, but is quickly approaching 0.2 which is focused on stability and finalizing features. Version 0.3 should be focused on performance and usability. These are just rough guidelines, not hard rules. I have 3D asset importing targeted for 0.3 even though it is a new feature. So CLinch is moving along.

I decided to clean out my Qix repository to start from scratch. I intend to use CLinch as the graphic engine, so work on CLinch is likely work on Qix. I expect to start working on the internals of Qix when CLinch reaches version 0.2. I've posted a rough list of tasks I need in something of an order, in the Qix repository. I hope to get a skeleton project up this weekend. I need to start reading "The Craft of Text Editing" by Craig Finseth to get some idea how to implement Qix's text editor. Until then, my philosophy will be to "put something on screen" rather than design something in my head. This is how CLinch happened and I feel that Qix should evolve rather than be designed. We can always refactor. I've posted on reddit and received some very good feedback. One idea is to modify an implementation of lisp to make Qix simpler and faster. Another is to make Qix an open standard. Both are really good ideas, but I'm not far enough along to discuss either intelligently yet.

So that's where Qix and CLinch stand. I'll continue to close out issues in CLinch as we are more than half way to the next release. Also, I have a Qix reddit for development updates and discussions. Thank you for your support and I look forward to working with you all!

Tuesday, March 17, 2009

The State of the State of a Union...

I took some time last night and got my #@m// #@s/// expressions working. I think I will try to make #@"..." into Perl style strings. I might even turn it into an asdf module, cl-perl-me has a nice ring. But working with Lisp and regular expressions made me start thinking. Since regular expressions are simply state machines, why couldn't I just abstract state machines?

I mean, all I am saying when I type #@m/Bender/ is return true if I match a series of events which each match, in order, b, e, n, d, e, r. Why couldn't I also extend that to be something like this:

(create-recognizer
(dot #\B #\e #\n #\d #\e #\r))
Or, even to extend it some more:

(create-recognizer
(dot 'Bender 'is 'great))
Now it could take symbols and strings or even objects. Since a recognizer is just a subset of state machines, I could also create something more general:

(state-machine ((start
(:on-rest home
(format t "State Machine has Started")))
(home
(:on-rest sweet
(format t "Home ")))
(sweet
(:on-rest home
(format t "Sweet ")))))
This is similar to the state machine generator by Dave Roberts on findinglisp.com. But I seem to remember that many problems can be solved with hierarchical state machines. Can state machine generator handle it? Not as such, yet. As I keep working on the idea the bigger and more general it seems to grow. I would also like to add the ability to add states dynamically. This might come in very handy if I start doing some GUI programming with lisp.

Still, there are even larger problems I would like to solve. For instance, there have been many times when I've needed a YACC style parser and I always hate needing YAL (Yet Another Language). I'll post as I work on this side project.

Finally, you might be wondering what happened to Qix, the 3d Emacs-style user environment. I'm still working on it, but I've been stumped by vertex-arrays in cl-opengl. Hopefully, I should have a fix or a work around soon.