On Mon, 19 Jun 2000, Dmitry Timoshkov wrote:
> I would like to know what criteria is currently used to show
> current percentage of Wine completeness. These are just magic digits
> for (not only) me now.
There's not much more metric than my own guesstimate or judgement (which I
thought would at least be better than no metric), and any corrections the
developers would like to tell me about. I didn't try to devise anything
complicated...
> I think that having some sort of "to do list" for every "Aspect or
> Component" would be very helpful thing. Everyone who want to participate
> in Wine development might easy choose the things of interest to do.
Well, if developers would like to provide such a list, I could certainly
put it online...
In a few cases (especially if it's "almost done"), I've tried put a line
under the percentage saying what is missing, but I didn't want to spend
too much time on it.
> I would like to complete as much as possible those areas on which
> I'm currently "responsible" (i.e. NLS, code pages, unicode) before
> I'll leave for two or more weeks on holidays in the middle of July.
My justification for the current NLS and Unicode metrics are:
NLS:
-missing certain magic NLS codepages (IE4 provides a codepage for
UCS2, I think, and the UTF8 codepage is not implemented)
-missing a big load of NLS data (the ole/nls directory is mostly
"stubs" (and apropos, I still think nls should be moved out of OLE, it has
nothing to do with OLE...))
Unicode:
-as above (UCS2 and UTF8 codepages not implemented)
-most API routines are implemented as A, not W; many W routines are
even just stubs.
I doubt you can get the Unicode state to 100% in just a few weeks...
but in case it is of interest, I have written UTF-8<->Unicode conversion
routines in another project, and I could probably 'donate' them to the
Wine project, if someone else wants to integrate them. (It's just not like
it's incredibly hard to write them yourself, either...)
