Okay, so I've just started working on this program that I'm gonna get finished Sometime™.
Basically, the idea is to write a little game completely in C#. Why? Because I can. I know I can. I know C; I know C++; I know Java; I should be able to teach myself a language based on the above and write a program in it. Right? Right?
So the other day, I got into the graphics. I spent 4 fucking hours trying to turn a black box white.
Yes, 4 hours.
Black -> White.
you'd think it'd be:
1c1
Cdk.Color clr = new Gdk.Color( 0xff, 0xff, 0xff );
Oh, you'd think that, wouldn't you...Anyway, I found it finally (Gdk.GC.RgbFgColor = new Color( 0xff, 0xff, 0xff ); if you're curious). I now have a nice white 800x600 screen sitting there that displays 0 fps and a red dot in the very center. (Another few hours was getting that dot from black to red.)
So, today I decided to expand on it a little more.
$ ls -l
0.o I've edited every single file that isn't 0-length. Wow.
Today, I drew a splash screen on program startup.
Okay, so I haven't actually got the splash screen. It's more a black box that'll get replaced with Gdk.Window.DrawPixmap( file ); ... Someday™.
But. it's its own object ^_^ - I managed to get a lot of base classes that I need done to the point that I can write a Splash Screen object and then add it into the tree and have it get drawn when needed.
Deletion is a problem for another day.
So is the kinetics system.
So is physics.
So is gameplay.
(See the pattern?)
Hey, I've only been working on it for 2 days. It compiles and there are no errors or warnings; what more do you want from me?
Oh yeah, and I have most of the 3D->2D conversion math done. I really should implement that Someday™.
Note to self: Gtk.Application.Run() blocks until the Gtk.Window gets closed, so everything has to already be added to the display tree before I actually call that function. Maybe implement a thread to just keep blocking while the other one(s) work?
:wq