could I write an SDL-based program and init SDL without video, audio,
and all the other bells and whistles just for the core functionality
in order to work with SDL-net, or would I even be
able to compile it?
I’m not sure if this is possible or not, but can somebody explain to me
what the “core” functionality of SDL is when you take away audio and
video?
Well, I find the software blitting code and SDL_Surfaces very handy for
various comand line image processing tools - especially in combination
with SDL_image. (Beind able to save in all those formats would have been
great…)
Anyway, the biggest advantage is probably that you can move that kind of
code back and forth between your “design time tools” and the game
engines. For example, “Kobo Deluxe” has most of the “tools” built right
in. (Various scaling filters, alpha dynamics/level, colorkey->alpha w/
“fuzziness factor”, alpha cleaning filter etc.) If I’d want to edit the
processed result in GIMP, would it make sense to port the code to another
API?
And of course, you don’t need to learn yet another API.
I think you may want to look for a different package, Mike.
Possibly - but then again, many networked games these days have a
built-in, in-process server. (Partly because of the poor multitasking of
some platforms, I guess…) Obviously, firing up the full client+server
combo on a (possibly headless) game server won’t work, so they usually
come with a dedicated server executable - which should obviously be
identical to the integrated server!
It will also need to share a great deal of stuff with the game engine;
perhaps even to the extent that the dedicated server contains a version
of the game engine, with the graphics and sound code stripped off. (At
least, that will be the case with “Kobo Deluxe” when I get around to add
network multiplayer support.)
At this point, the question is “should SDL_net be used at all”, rather
than “should SDL_net be used only in SDL applications”.
IMHO, if SDL_net is too simple, or broken, it should be fixed - not
ignored. Who wants to port networking code to various platforms with
silly non-Unix networking APIs over and over again? (Ok, hackers enjoy
different kinds of hacking - I prefer engines, API design and low level
audio processing.
As to the original subject; if there’s any technical reason not to link
network-only applications with SDL, how about adding a “stand-alone
library” build target to SDL_net, dragging in what it needs from the SDL
code?
//David Olofson — Programmer, Reologica Instruments AB
.- M A I A -------------------------------------------------.
| Multimedia Application Integration Architecture |
| A Free/Open Source Plugin API for Professional Multimedia |
----------------------------> http://www.linuxdj.com/maia -' .- David Olofson -------------------------------------------. | Audio Hacker - Open Source Advocate - Singer - Songwriter |
-------------------------------------> http://olofson.net -'On Tuesday 23 October 2001 19:42, Shawn Wheatley wrote: