Hi, Am Monday, 09. April 2007 19:34 schrieb Eric S. Raymond: > The thing I most want abolished is the option to have the WML > autocomplete the file extension. Or, to put it another way, > macroscope needs all image file references to be detectable in a > context-independent way with a regular-expression match, rather than > by requiring a WML-aware parse of the file. The easiest way to do > this is to require that all references have one of a small set > of recognizable suffixes like ".png", ".wav", ".ogg", and ".jpg". > Adding to that set of extensions is not a big deal, but the set > has to exist for any tool like macroscope to have a prayer of working.
This will not work in any case where the actual image name is constructed from
(one or more) parameters inside a macro.
One very common case are rotations in terrain WML:
| [image]
| layer={LAYER}
| [EMAIL PROTECTED]
| [/image]
| rotations=n,ne,se,s,sw,nw
So a macro call like
| {SOME_TERRAIN_MACRO some/image.png}
would result in image names like some/image.png-se which is obviously wrong
and wouldn't help with reference checking at all.
I think your proposal makes sense for most cases, but terrain WML isn't one of
them. It just can't be done without a WML parser.
Regards,
Moritz
pgpE6zVYQF8uh.pgp
Description: PGP signature
_______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
