I didn't see this post until I already replied to that other guy >_< sorry.
> Another more radical option (although it may be more work for you > case, I don't know) is to write two separate programs - one which is > pure SDL and contains the core emulation and "real-time" aspects > (audio, in-game keyboard activity, joystick, etc...) and another > which is pure-fltk and handles the GUI aspects, e.g. config, game > selection, saving state, etc... I thought about this... I'm still a little unsure how well it'd work. I plan on adding debugging tools to aid ROM hackers / translators (similar to the one in FCEUXD, if you've ever used that -- I don't know how into emulation you guys are). A runtime debugger with breakpoints, memory and graphic viewers that update in realtime, etc. All of this would require a *lot* of constant communication and synchronisation between programs. I haven't used sockets before so I don't know how much work this would be -- but keeping it all in the same program just seems like it'd be much simpler. > Allegro is certainly worth another look, I'd suggest - I've used it > for a few things in the past, it works pretty well and was easy to > get going with... It may be hasty to judge it based on the examples > you have looked at so far, perhaps. And it does have it own GUI/ > widget sets, more or less, which might be good enough for your needs. heh... I might check it out more later. But right now I've already built up all this steam for FLTK XD _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
