Why don’t loki adds svgalib support to SDL? when lookin through code I
foun some strange comments
like ‘how to flip pages using svgalib?’ hmm… the things is simple -
vga_setpage()–
With best regards Razor.X.Jackie
"The choise is yours… walk now and live or stay and die"
Why don’t loki adds svgalib support to SDL? when lookin through code I
foun some strange comments
like ‘how to flip pages using svgalib?’ hmm… the things is simple -
vga_setpage()
Go for it. I haven’t used SVGAlib in a very long time, and don’t currently
need it. There have been zero requests for enhancements, but you’re welcome
to improve it. 
See ya!
-Sam Lantinga (slouken at devolution.com)
Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec
I believe SVGAlib support is there, just considered beta/unsupported.
You have to pass a configure option to compile SDL for svgalib.
svgalib is antiquated and pretty much considered “deprecated” in the linux
world.–
Brian
On Wed, 22 Mar 2000, razorjack wrote:
Why don’t loki adds svgalib support to SDL? when lookin through code I
foun some strange comments
like ‘how to flip pages using svgalib?’ hmm… the things is simple -
vga_setpage()With best regards Razor.X.Jackie
"The choise is yours… walk now and live or stay and die"
Go for it. I haven’t used SVGAlib in a very long time, and don’t currently
need it. There have been zero requests for enhancements, but you’re welcome
to improve it.See ya!
-Sam Lantinga (slouken at devolution.com)Lead Programmer, Loki Entertainment Software
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec
Hmm… I can write somethin but I don’t want to contibute anythin. Ok.
may be i write initial release for svgalib and send it to you. But it is
someone else who’s continue development.
Hmm… I can write somethin but I don’t want to contibute anythin. Ok.
may be i write initial release for svgalib and send it to you. But it is
someone else who’s continue development.
Well, much of the work is already done:
src/video/svga/
Please don’t submit code you are not willing to accept bug reports for.
See ya!
-Sam Lantinga (slouken at devolution.com)
Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec
Sam Lantinga wrote:
Hmm… I can write somethin but I don’t want to contibute anythin. Ok.
may be i write initial release for svgalib and send it to you. But it is
someone else who’s continue development.Please don’t submit code you are not willing to accept bug reports for.
Really? Myself, I figured that some unsupported code is better than no
code at all, but it seems it’s not a universal idea…–
Pierre Phaneuf
Systems Exorcist
Sam Lantinga wrote:
Hmm… I can write somethin but I don’t want to contibute anythin. Ok.
may be i write initial release for svgalib and send it to you. But it is
someone else who’s continue development.Please don’t submit code you are not willing to accept bug reports for.
Really? Myself, I figured that some unsupported code is better than no
code at all, but it seems it’s not a universal idea…
Not if I have to maintain it.
People often gripe if something only partially works, much more than if it
isn’t supported at all.
See ya!
-Sam Lantinga (slouken at devolution.com)
Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec
Sam Lantinga wrote:
Please don’t submit code you are not willing to accept bug reports for. > > Really? Myself, I figured that some unsupported code is better than no
code at all, but it seems it’s not a universal idea…Not if I have to maintain it.
People often gripe if something only partially works, much more than if it
isn’t supported at all.
I see… What about this: add an --enable-unsupported flag to the
configure script. Make it so that other --enable and --with options that
are not supported won’t work without also putting --enable-unsupported
(with a small message saying so). When you use --enable-unsupported,
have the configure script output a message at the end in big capital
letters about how this particular build is not supported and how risky
it is and blablabla.
If there is internal version information compiled into the library (I
don’t remember), make sure it knows whether the build is an
"unsupported" one.
You can make the “unsupported” message as complete as you want, with
notes like “do not send requests for improvements or bug reports, only
fixes and patches”.
That ought to get you the best of both worlds, no?–
Pierre Phaneuf
Systems Exorcist
Newsgroups: loki.open-source.sdl
Please don’t submit code you are not willing to accept bug reports
for. > > Really? Myself, I figured that some unsupported code is better than
nocode at all, but it seems it’s not a universal idea…
Not if I have to maintain it.
People often gripe if something only partially works, much more than if
itisn’t supported at all.
I see… What about this: add an --enable-unsupported flag to the
configure script. Make it so that other --enable and --with options that
are not supported won’t work without also putting --enable-unsupported
(with a small message saying so). When you use --enable-unsupported,
have the configure script output a message at the end in big capital
letters about how this particular build is not supported and how risky
it is and blablabla.God no. You don’t want to have chunks of unsupported code floating around in
a library! The end result is that you get so much of this unsupported code
flying around that it starts to interfere with the supported code, all hell
breaks loose. It’s bad enough trying to go through somebody else’s code to
add something new; it’s even worse for the maintainer of the main code base
if he has to wade through seventeen piles of broken kludge.Look… what the hell’s wrong with the SVGAlib/fbcon/GGI support at this
point in time anyways? If worst comes to worst, I can try to get SVGAlib
working on my machine (anybody want to send me a new video card?) and write
a new driver. (This windowing stuff is beginning to take its toll on me, and
I can’t help feeling that I need a nice easy project… I can handle writing
video drivers, I can’t handle rewiring the entire code base!)–
Pierre Phaneuf
Systems ExorcistNicholas
Nicholas Vining “While you’re out there struggling
vining at pacificcoast.net with your computer, I’m naked,
icq: 20872003 clueless, and feeling good!”
- Ratbert----- Original Message -----
From: pphaneuf@sx.nec.com (Pierre Phaneuf)
To: sdl at lokigames.com
Date: Thursday, March 23, 2000 10:50 AM
Subject: [SDL] Re: svga support
That ought to get you the best of both worlds, no?
Yeah, sounds good.
You can currently do --enable-video-svga to get SVGAlib support.
See ya!
-Sam Lantinga (slouken at devolution.com)
Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec
Sam Lantinga wrote:
That ought to get you the best of both worlds, no?
Yeah, sounds good.
You can currently do --enable-video-svga to get SVGAlib support.
I wasn’t exactly looking after SVGAlib support, but I was just thinking
that not accepting unsupported patches is somewhat of a problem. For
example, someone drops you an unsupported patch to do something and
disappear. A while later, another guy wants the same thing, but this
time would support it. He doesn’t necessarily have to start from
scratch, he can pickup where the other guy left it (possibly working,
possibly broken, whatever).–
Pierre Phaneuf
Systems Exorcist