Nils Kneuper <[EMAIL PROTECTED]>:
> Agreed, sounds okay. Though we have some corner cases where we would
> have to find a way ho to handle it (attacks and their images). Though
> there we could make an image= tag mandatory.
Actually, I want all resource filenames to be identifiable by their
extensions precisely so tools like macroscopes can spot references
*without* there being an image= or sound= tag nearby (macro calls set
up this sort of situation).
I don't understand why you consider attacks and their images a corner
case. Please explain this, in case I'm missing something important.
> Jepp, clear rules would be a really good thing. Especially since clear
> rules can more easily be automatically checked, what maybe could even be
> implemented ingame eg before uploading content to the campaign server.
That's an *interesting* idea. I take it you're thinking about using
macroscope to check for unresolved references in UMC at upload time, and
bouncing the submission with an error report if any occur?
> > In case it is not obvious, I am willing to do the tedious job of
> > upgrading the mainline WML so that it no longer relies on these
> > misfeatures. Doing so would be a natural way to debug macroscope,
> > in the same way that finding those unresolved sound references was.
> >
> > I'm also willing to write the documentation once we settle on
> > the new rules.
> >
> Hey, that was the last objection I would have had. If you even volunteer
> to do the most dirty work (removing these hacks from the sourcecode
> probably is nicer that writing documentation and applying the needed
> changes to the data/ dir) I see no objections left. Though you will have
> to find somebody doing the codechanges.
Yes, I would really appreciate a volunteer to help with the C++ changes
These will be rather trivial, but it wouldn't be efficient for me to dive
into the C++ yet.
I'll say out a work plan in a later post. (I was going to do in this one,
but I see some replies that raise design issues.)
> In general: You have my support when pushing for something like this. I
> would even vote for no "depricated" tags for this stuff and directly
> drop support of the old style.
Thanks for the supportive response. In this particular case it's hard
to see how we could go through a "deprecated" phase, anyway.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
_______________________________________________
Wesnoth-dev mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-dev
