Shawn Rutledge wrote:
I don't have one. I think making games on small devices is junk. I'll worry about OpenGL ES if that's what Playstation3 is using. If I go that route, I'm certainly not going to be worrying about free implementations.On 2/11/06, Brandon J. Van Every <[EMAIL PROTECTED]> wrote: Dunno. I'm a game designer. The most basic question is, what game are you trying to write? Then, to what audience are you trying to sell it? Do small portable devices fit your vision? They don't for mine. Cellphone games, at any rate, seems like a really bozo market to try to succeed in. You can't brand your product, you've got like a 15 character game title in some big list of "free downloadables." There are articles on Gamasutra about this sort of thing. Cellphones look like the game industry "writ small." Like if you want to do something that was cutting edge in the early 80s or whatever. YMMV for handhelds. Probably much better money there, and I have no idea what technologies they're using.klimt claims to be very similar (maybe it's a subset) but not quite compliant. Are there licensing issues, or having to pay in order to claim to be compliant? This is only more to the point on cell phones. The standards are unstable. There's no marketing potential in it. So why bother? Have you heard about any compelling cell phone games at all? That should tell you something. It's not like they're brand new. I'm still waiting for someone to inform me why, as a game designer, I'm supposed to care about cell phones. Either Windows, one of the consoles, or one of the handhelds. You could even do Macs if you're funky. They have a tiny market, but also few game developers, so almost no competition. Linux is useless as a consumer desktop OS. They can't get 3D drivers right because of NVIDIA / GPL tiffs, and that issue isn't going away. Forget the cell phones, it's a waste of time. Keep your eye on whether the market conditions change for cell phones, though. It just doesn't pay to be the 1st one pouring blood on the table for stuff like this. I'd feel a lot better if I had a working Chicken toolchain. I'm probably going to give up on Eclipse and Schemeway. For some reason, the Schemeway interpreter doesn't work in recent versions of Eclipse. Meanwhile, I haven't found Eclipse particularly intuitive to use. It looks nice and is reasonably documented, but there's still a learning curve for getting non-Java things to work with it. The thing that bugged me the other day is trying to search files to find stuff. Seems like Eclipse wants me to set up all these projects and whatnot before I can do that. The idea of just picking a directory and saying "search it for what I want" seems alien. So, I gotta RTFM... and that's the main thing I didn't like about XEmacs. If I gotta RTFM anyways no matter what, then I may be better off with XEmacs. I don't have to worry about the Scheme tools being "bleeding edge" and so forth. Cheers, Brandon Van Every |
_______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
