On Mon, May 4, 2009 at 12:28 AM, Ben Klein wrote:
> 2009/5/4 Austin English :
>> 2009/5/3 Rosanne DiMesio :
>>> What I would suggest is making the default severity normal rather than
>>> enhancement, as that's what's appropriate in most cases anyway (and there's
>>> already a bug report, 13363,
2009/5/4 Austin English :
> 2009/5/3 Rosanne DiMesio :
>> What I would suggest is making the default severity normal rather than
>> enhancement, as that's what's appropriate in most cases anyway (and there's
>> already a bug report, 13363, suggesting just that), and perhaps allowing
>> users to
2009/5/3 Rosanne DiMesio :
> What I would suggest is making the default severity normal rather than
> enhancement, as that's what's appropriate in most cases anyway (and there's
> already a bug report, 13363, suggesting just that), and perhaps allowing
> users to lower the severity if they want.
> >
> > Let's try user education. You only get to choose normal and we get to
> > up/downgrade until you can prove that you know how to do it right. This
> > is how some companies do it.
> >
> > James McKenzie
> >
>
> +1. Or just remove priorities for users altogether.
>
I think you mean seve
2009/5/3 James McKenzie :
> Ken Sharp wrote:
>>
>>
>> Nicklas Börjesson wrote:
>>
>>> I think that the users should have quite a say with regards to how
>>> important a bug is, because for every user putting in the
>>> (considerable for a user) effort of reporting a bug, there are dozens
>>> that d
Ken Sharp wrote:
>
>
> Nicklas Börjesson wrote:
>
>> I think that the users should have quite a say with regards to how
>> important a bug is, because for every user putting in the
>> (considerable for a user) effort of reporting a bug, there are dozens
>> that don't say anything at all.
>
> To ev
On Sun, May 3, 2009 at 10:36 PM, James Hawkins wrote:
> On Sun, May 3, 2009 at 1:52 PM, Mike Kaplinskiy
> wrote:
>> On Thu, Apr 30, 2009 at 1:08 PM, James Hawkins wrote:
>>> On Thu, Apr 30, 2009 at 4:03 AM, Austin English
>>> wrote:
On Tue, Apr 28, 2009 at 9:27 PM, Mike Kaplinskiy
w
On Sun, May 3, 2009 at 1:52 PM, Mike Kaplinskiy
wrote:
> On Thu, Apr 30, 2009 at 1:08 PM, James Hawkins wrote:
>> On Thu, Apr 30, 2009 at 4:03 AM, Austin English
>> wrote:
>>> On Tue, Apr 28, 2009 at 9:27 PM, Mike Kaplinskiy
>>> wrote:
I was looking at the trace of the crash from bug 1760
2009/5/4 Austin English :
> 2009/5/3 Nicklas Börjesson :
>>>Why should there be multiple support forums?
>>
>> Well, not forums, but as I said different lists for different kinds
>> of applications(games/business/graphics), since they should(?) have related
>> problems.
>> I would think so, anyway
2009/5/3 Nicklas Börjesson :
> It just feels like the entire project should become a bit more user-centric.
> Now I am not just talking about shinier graphics but about attitude.
Bugzilla not user tool. Bugzilla developers' tool. Bugzilla need work
like developers want.
2009/5/4 Nicklas Börjesson
2009/5/3 Nicklas Börjesson :
>>Why should there be multiple support forums?
>
> Well, not forums, but as I said different lists for different kinds
> of applications(games/business/graphics), since they should(?) have related
> problems.
> I would think so, anyway.
The forums seem to serve this w
Nicklas Börjesson wrote:
How many times does this have to be repeated? Severity levels are NOT
determined by how much a user wants the app to work. They're just not,
deal with it.
I have never said it is, either.
I said it think it should be determined by how severe the user thinks
it is
Roderick Colenbrander ha scritto:
Have you also tried to use the GDI AlphaBlend function? This is the
one which should be used I think and we back it by XRender ..
Roderick
Sorry for the OT :
apropos AlphaBlend and RGBA bitmaps... what happens with BitBlt on
a destination DIB which has al
On Sun, May 3, 2009 at 6:28 PM, Roderick Colenbrander
wrote:
> On Sat, May 2, 2009 at 11:18 PM, Joel Holdsworth
> wrote:
>> On Sat, 2009-05-02 at 22:56 +0200, Roderick Colenbrander wrote:
>>> On Sat, May 2, 2009 at 8:57 PM, Joel Holdsworth
>>> wrote:
>>> > On Sat, 2009-05-02 at 20:38 +0200, Rode
On Thu, Apr 30, 2009 at 1:08 PM, James Hawkins wrote:
> On Thu, Apr 30, 2009 at 4:03 AM, Austin English
> wrote:
>> On Tue, Apr 28, 2009 at 9:27 PM, Mike Kaplinskiy
>> wrote:
>>> I was looking at the trace of the crash from bug 17600, and it looks like
>>> a custom action is calling MsiViewExec
IneedAname wrote:
On Sun, 03 May 2009 18:10:03 +0100
Ken Sharp wrote:
That would be the "Show Apps affected by this bug" link then.
http://appdb.winehq.org/viewbugs.php?bug_id=16281
Thanks I missed that so how but my first point still stands.
Not really. 16281 certainly isn't a major
2009/5/3 Nicklas Börjesson :
>> You'd be surprised...
> We'll I've looked around at "invalids", but to me it seems that people in
> general(with a few exceptions of course), tries quite hard until they file a
> bug report.
> At least way harder than they do in other FOSS projects I have been invo
Nicklas Börjesson wrote:
To every Wine user, their application not working is critical. This is
clear by all the bugs that are logged incorrectly every day, because
nobody bothered reading the FAQ.
Yep, but that's more an indication on how much work remains to be done on wine
than it is an
On Fri, 01 May 2009 22:15:16 +0200, you wrote:
>Rein Klazes writes:
>
>> What is already in the tests:
>>
>> 1) You need the alloc flag for instance when SetScrollInfo or
>> SetScrollRange is called on a window without the WS_[HV]SCROLL styles. I
>> can add a test that shows that the window style
IneedAname wrote:
On Sat, 2 May 2009 16:52:06 +0200
Nicklas Börjesson wrote:
3. Major"Major loss of functionality for a wide range of applications
- Isn't this just all bugs that has more than $arbitrary_number of applications
linked to them? An aggregate, rather than a level?
In
>I disagree. When first introduced to them, I found the severity levels
>to be suitably vague to make me read the definitions. Once I read
>them, it was clear to me what each level means.
Suitably? Do you mean that the severity levels are the way they are to make
people read their definitions?
> You'd be surprised...
We'll I've looked around at "invalids", but to me it seems that people in
general(with a few exceptions of course), tries quite hard until they file a
bug report.
At least way harder than they do in other FOSS projects I have been involved
in, so I can't really say that I
On Sat, 2 May 2009 16:52:06 +0200
Nicklas Börjesson wrote:
> 3. Major "Major loss of functionality for a wide range of applications
>
> - Isn't this just all bugs that has more than $arbitrary_number of
> applications linked to them? An aggregate, rather than a level?
In that case #16281
wine-devel-requ...@winehq.org wrote:
> ___
> wine-devel mailing list - wine-devel@winehq.org
> http://www.winehq.org/mailman/listinfo/wine-devel
>
>
>
>
> Subject:
> Re: RFC on
On Sat, May 2, 2009 at 11:18 PM, Joel Holdsworth
wrote:
> On Sat, 2009-05-02 at 22:56 +0200, Roderick Colenbrander wrote:
>> On Sat, May 2, 2009 at 8:57 PM, Joel Holdsworth
>> wrote:
>> > On Sat, 2009-05-02 at 20:38 +0200, Roderick Colenbrander wrote:
>> >> On Sat, May 2, 2009 at 6:55 PM, Joel Ho
Nicklas Börjesson wrote:
I think that the users should have quite a say with regards to how important a bug is, because for every user
putting in the (considerable for a user) effort of reporting a bug, there are dozens that don't say anything at all.
To every Wine user, their application n
Vincent Povirk ha scritto:
This is by design. Each call to ok() is an individual test,
independent of the others, and todo_wine marks them all as todo.
If you have the same code running multiple tests, you can mark some of
them as todo by putting a todo flag in your data.
If you really want mul
This is by design. Each call to ok() is an individual test,
independent of the others, and todo_wine marks them all as todo.
If you have the same code running multiple tests, you can mark some of
them as todo by putting a todo flag in your data.
If you really want multiple checks to be dependent,
Today writing a testcase I found a "problem" on todo_wine construct.
In short :
void first_test_part()
{
ok(test1(), "failed\n");
}
void second_test_part()
{
ok(test2(), "failed\n");
}
todo_wine
{
first_test_part();
second_test_part();
}
this "fails" (i.e. is marked as passing inside
2009/5/3 Nicklas Börjesson :
>
>>I disagree. When first introduced to them, I found the severity levels
>>to be suitably vague to make me read the definitions. Once I read
>>them, it was clear to me what each level means.
>
> Suitably? Do you mean that the severity levels are the way they are to ma
On Sun, May 3, 2009 at 2:44 AM, Ben Klein wrote:
> 2009/5/3 Joel Holdsworth :
>> On Sat, 2009-05-02 at 22:56 +0200, Roderick Colenbrander wrote:
>>> Why again did you need this specific alphablend method? The icon can't
>>> be converted to use some basic color keying for transparency or so?
>>
>>
2009/5/3 Dmitry Timoshkov :
> "Stefan Leichter" wrote:
>
>>> Also you might be interested that according to
>>>
>>> http://www.geoffchappell.com/viewer.htm?doc=studies/windows/shell/shell32/h
>>> istory/names351.htm ExtractVersionResource16W is discontinued starting
>>> from
>>> Windows Vista.
>>
Am Sonntag, 3. Mai 2009 13:42:24 schrieb Paul TBBle Hampson:
> The point made as I recall it in the earlier thread is that this is a
> false sense of security, and that apps can already get outside the drive
> mappings for filesystem access.
>
> I don't know how, but that was the point that was mad
On Sun, May 03, 2009 at 08:54:32PM +1000, Ben Klein wrote:
> 2009/5/3 Paul TBBle Hampson :
>> On Sun, May 03, 2009 at 03:07:35PM +1000, Ben Klein wrote:
>>> It's NOT a networked drive, is it? Drive mappings are the only way to
>>> tell Wine and apps running in Wine where your files are in your
>>>
2009/5/3 Nicklas Börjesson :
> Ok..you seem to have misunderstood the tone in my mail.
>
>>Without common sense, all bug reports would be "Enhancement" requests,
>>or "Critical", depending on how arrogant the reporter is. Common sense
>>must *always* be applied.
>
> I should be needed to be applied
2009/5/3 Paul TBBle Hampson :
> On Sun, May 03, 2009 at 03:07:35PM +1000, Ben Klein wrote:
>> It's NOT a networked drive, is it? Drive mappings are the only way to
>> tell Wine and apps running in Wine where your files are in your
>> host-system (Unix-style) filesystem.
>
> The discussion on wine-d
2009/5/3 André Hentschel :
> Dimitriu Petru schrieb:
>>
>> I'm here again for the Romanian translation of Wine.
>> I only want somebody to change in the translation "Proprietă?i pentru"
>> with "Proprietăţi pentru" because it shows ugly in ReactOS.
>>
>> Thanks in advance,
>> Petru
>>
>>
>>
>
> Pat
2009/5/3 Dimitriu Petru
> I'm here again for the Romanian translation of Wine.
> I only want somebody to change in the translation "Proprietă?i pentru"
> with "Proprietăţi pentru" because it shows ugly in ReactOS.
>
> Thanks in advance,
> Petru
>
>
> you can send translations patches to wine (you
"Stefan Leichter" wrote:
Also you might be interested that according to
http://www.geoffchappell.com/viewer.htm?doc=studies/windows/shell/shell32/h
istory/names351.htm ExtractVersionResource16W is discontinued starting from
Windows Vista.
What does the second point means for wine?
That mean
Dimitriu Petru schrieb:
I'm here again for the Romanian translation of Wine.
I only want somebody to change in the translation "Proprietă?i pentru"
with "Proprietăţi pentru" because it shows ugly in ReactOS.
Thanks in advance,
Petru
Patch sent:
http://www.winehq.org/pipermail/wine-patches/
On Sun, May 03, 2009 at 03:07:35PM +1000, Ben Klein wrote:
> It's NOT a networked drive, is it? Drive mappings are the only way to
> tell Wine and apps running in Wine where your files are in your
> host-system (Unix-style) filesystem.
The discussion on wine-devel in April related to bug 15883 sug
I'm here again for the Romanian translation of Wine.
I only want somebody to change in the translation "Proprietă?i pentru"
with "Proprietăţi pentru" because it shows ugly in ReactOS.
Thanks in advance,
Petru
2009/5/2 Nicklas Börjesson :
>>> 2. Critical "Critical problem that prevents all applications from working"
>>>
>>> - Possible, if everyone stopped testing code completely, and also unlikely
>>> to be reported by a user.
>
>>No, critical bugs are usually opened by non-Linux users.
>
> Here I did
Ok..you seem to have misunderstood the tone in my mail.
>Without common sense, all bug reports would be "Enhancement" requests,
>or "Critical", depending on how arrogant the reporter is. Common sense
>must *always* be applied.
I should be needed to be applied only to the least possible amount. On
>I think "middle-aged college English teacher who couldn't code if her life
>depended on it" counts as non-technical. :-) The only thing that sets me
>>apart from most users is the fact that I actually do RTFM, but that's just
>because I'm one of those eccentric academics who thinks reading is
>The problem is, however, that many of those problems only break an
>application or two. What is a blocker for Photoshop isn't a blocker
>for World of Warcraft or Microsoft Office, for example.
You mean because Photoshop often use the more obscure parts of the APIs?
Otherwise bugs in GUI shouldn'
Not applications, issues.
My point is that user experience issues gets a lower severity than they should.
Let's take photoshop CS 4 with two old but relevant actual issues as an
example.
1. There is a problem with the text tool functionality, it did not work.
Everything else works, though.
2. Th
The normal user doesn't even understand that the definitions should be read,
most people think they know what "trivial", "minor","normal","major" means
anyway. I actually discussed this with some friends recently. I just think that
it could be more user-oriented.
Non-technical? Posting on and f
>Wine is meant to support _ALL_ windows applications. It doesn't give
>priority to 'server' or 'desktop' applications (there is no
>difference, really), but instead tries to make all of them work.
Yes, but I wasn't talking about server applikations per se, but that the
severity levels would be pe
Ok, I have made better posts.
>> 1. Blocker "Blocks development and/or testing work"
>>
>> - Is this even possible?
>Yes.
I am sorry. Of course it is possible to have these problems. I thought it meant
that it blocks ALL
development and/or testing work(since it is above critical).
In the l
I am not sure that common sense is the issue. I think it is a question of who
you are and what you know.
Among the ones submitting bugs now is a quickly rising percentage of
normal-to-advanced end users, and that percentage is likely to rise even
further, as Linux adoption rates increase. 10 mi
On Sunday 03 May 2009 07:07:35 Ben Klein wrote:
> 2009/5/3 chris ahrendt :
Replying to Ben's email as I didn't get Chris' email Ben replied to.
I would also like to note that I don't appreciate the tone both of these
emails are taking in the end. Please try to be civil.
That being said, let me g
52 matches
Mail list logo
