Am Samstag, 16. September 2006 20:14 schrieb Christian Ohm: > On Tuesday, 12 September 2006 at 23:45, Dennis Schridde wrote: > > Am Dienstag, 12. September 2006 02:29 schrieb Christian Ohm: > > > On Saturday, 9 September 2006 at 2:30, Dennis Schridde wrote: > It was just a (bad) example, I don't like those aligned variables - if > you add a new one with a longer name, you have to re-align all others, > that's just stupid. Jup, agreed.
> > And it is still a complete draft. Maybe some things are totally
> > irrelevant and maybe very relevant things are missing...
>
> Aye. We're working on it, right? :)
Erm... Not directly. ;)
> > > If not, which one do we keep? In my opinion, the wiki is more suitable
> > > for that as it can be changed more easily.
> >
> > Actually I don't know. It seems like not so many people look into a TODO
> > file as look into a wishlist Wiki page.
> > We probably need to decide on that question.
>
> Idea: Have the wiki page for larger changes (a longer term roadmap),
> while the TODO file contains more immediate matters (things that can be
> fixed without larger rewrites, and stuff like "Oh, while coding I
> noticed something odd, investigate later").
Sounds reasonable.
> > > Not all of the points you listed are major changes ("Make it possible
> > > to close Warzone with ^C, ALT+F4 or closing the window", "Fix memleaks
> > > in lexer files").
> >
> > That page was all about design questions, which both points involve to
> > some extend.
> > Closing with ^C requires Warzone to be design in a way which makes it
> > possible to call a subsystem's init function and register it's exit
> > function to atexit().
> > Those memleaks are also similar: It is perhaps more a question like: How
> > can we help prevent memleaks by design? Instead of how can we fix this
> > memleak. And even fixing that memleak is tricky, because eg MSVC's
> > memleak detection fails on all of those memleaks, because it doesn't know
> > where they come from, because they don't have the crtdbg.h redefinitions
> > of malloc and free.
>
> OK. It just looked kinda out of place in that list.
Maybe because of missing background info.
> > > DDS looks to Microsoft/DirectX specific to me,
> > > which Linux program can edit those files?
> >
> > Now that you remind me of this I find the flaw in my idea... GIMP seems
> > to not support it and actually I don't know of any other... (Perhaps
> > there are converters?)
>
> I was almost convinced about DDS, until I tried (wanted to try) your
> example. It compiled and ran and showed a white cube. Then I installed
> the GIMP plugin and wanted to convert the tertiles image. But the plugin
> complains about "GL_S3_s3tc or GL_EXT_texture_compression_s3tc is not
> supported by your OpenGL implementation" (the mesa3d r300 driver). Your
> test program doesn't seem to use those extensions, can you send me the
> dds file to test it?
Erm, well, the example _does_ use it.
glCompressedTexImage2D is part of the GL_EXT_texture_compression and
li->internalFormat contains eg. GL_COMPRESSED_RGBA_S3TC_DXT1_EXT (for a DXT1
compressed image).
So it seems like the Mesa drivers do not support S3TC. :( Pretty odd since the
extension itself is supported even by TNT2 or Radeon (1st generation) cards.
And sad, since Grim told me some time ago that it would be easier for him to
create better effects/textures with DDS files.
> > > And what's wrong with PNG /
> >
> > I think some time ago someone said that he/she thinks that pngs are quite
> > big.
>
> Compared to what?
I don't know. I just heard someone saying that.
> > I don't remember who it was. (I think one of the devs.)
> > And png needs an external library. :P
>
> I think I saw a PNG loader without libpng somewhere (might depend on
> zlib, though), I could try to find it again. But is it a problem to
> depend on libpng? That one should be quite standard, no?
No, I don't want to strip the libpng dep... There was this ":P" in the
sentence. ;)
> > > what's better about TGA?
> >
> > Don't ask me that, that idea is from Kamaze. ;)
>
> The only advantage of TGA I know of is that it's quite simple, so you
> can write a quite small loader for it. But it's about twice as large as
> PNG (for the tertiles image).
> Addendum: S3TC seems to be lossy compression.
Could be.
> Not good.
Why not? Are you able to see the difference? I saw comparisons of different
images from an original 32bit image to 16bit, S3TC and FLX1. S3TC had nearly
no difference to the original expect in hard cases. (Very dark images with
some pattern in it.)
> (As is OGG, by the way. Strictly speaking, the conversion of the WAV files
> to OGG is a GPL violation.
Are you going to sue us?
> ("The source code for a work means the preferred
> form of the work for making modifications to it", and that's WAV, not OGG.)
Doesn't that depend on the POV? If I like to work with OGG files because they
are smaller, then that's my preffered form of work. Does the GPL also define
what prefered means to me?
--Dennis
pgpQYnC3JhVR9.pgp
Description: PGP signature
_______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
