L.D wrote: >> I ran and used DesQView. I cant see any connection. Qube is an engine. >> Not a software suite or a useable GUI. > >> Its like comparing the engine of a car to a fully built Honda. >> "The engine has no doors or A/C! So its worthless!" > >Excuse me, but I fail to see a connection. From what I've seen of Qube >it is a paint job without a car to go on. > >Just what *is* your definition of "engine" in this context? I _think_ I know what Or wanted as definition on engine. Qube is in it's present state only showing how the "graphical engine" works. This term is used in programming, it's resemblance to a cars engine (which I know little or nothing about) is that it's what gets things going. You can't drive a car without an engine - except if you are Fred Flinstone of course. In the same sense you can't have a graphical interface without a graphical engine. >I can run a car engine on a workbench, with no car attached, and >determine if it is good or bad. I can make repairs on a car engine, and >know that when I reinstall it in the car I'll have a complete and >operational machine if nothing else is broken. Exactly, and Qube is an engine. But without wheels (the program launcher?) it isn't going to take you anywhere. >From what I think I read further down in your message, are you saying >that the ability to move stuff on a screen and have buttons respond to >clicking is an "engine" ????? Yes, that's the definition of a graphical engine. I assume I've made the same kind of error that Or has, as have we all at some point in our lives. The ability to assume that everyone else has the same knowledge as yourself isn't hard to get ;-) >If so, it doesn't deserve a name like "engine" because an engine >produces work/output and moving stuff on a screen is a video game. The work is the ability to display things on the screen and react to certain events. A game is much more complex than Qube, it has a graphical engine, Artificial Inteligence, game engine (handles the rules and reacts upon input from the players, both human and AI). Hmm... well those are the three basic ones anyway. BTW: Please remember that you can't write an AI as good as the professional ones in only a few days, I'm talking from experience :/ And design the entire gameengines interfaces before starting to code, it's worth it - but very boring. >Don't you have separate mailing lists for people who want to watch stuff >get developed but never get to play with it along the way??? But you can play with it. It's just not useful yet, and I doubt it ever will be :( //Bernie
