On 3/20/07, Louis Lenders <[EMAIL PROTECTED]> wrote:
James Hawkins <truiken <at> gmail.com> writes:
> > However, the components could use a major revamping and should be
> > fairly trivial. However I think that one component for each dll might
> > be a bit much.. Maybe narrow the dll's down to categories such as
> > wine-common-controls, and wine-riched..
> >
>
> No, we had vague components before, and they're not useful.
Yeah, i use bugzilla for quite some time and from some components i still have
no idea what they mean, and some are never used at all:
*wine-console (i could guess, but i've never seen a bug with this component)
*directx and directx-d3d. (ok , directx is more than d3d, but we already have
components for dinput, dmusic etc. so why not remove directx)
*wine-files (no idea what it means, no files ever seen with this component)
*wine-gui (what does that mean?)
We made a big push a while back to correctly relabel wine-gui to their
correct components (comctl32, gdi, etc).
*wine-ipc(never seen a bug with that component)
*wine-multimedia (just change to winmm i'd say)
*wine-ports (?)
*wine-Rebar( could be moved to comctl32?)
*wine- resources( (never seen a bug with that component)
*wine-winelib ( (never seen a bug with that component))
My opininion is : please remove /change
The only component in that list that needs to go or change is
wine-gui. Just because we don't have bug reports currently for all
components doesn't mean that we wont get reports for them or that
they're not necessary.
>We need a component per dll.
Yeah, common dlls not yet added that come in my mind are urlmon, mshtml, shlwapi
and advapi32.
>I don't think we should add them all right now,
> but when we have a bug report for a bug in a particular dll that isn't
> a component yet, the component should be added (by request).
>
--
James Hawkins
