I was interested to read several comments on this list in respect of such
comments as 'IQ of zero'. Such comments were the final straw in leading me to
take this action.
A few days ago I sent a comment to the list. Nothing really sinister, just an
observation and an experience. Before long I had a particularly vicious and vile
diatribe sent in reply to my comment - to my private email address. I have
appended the lower headers and the bulk of the message I received at the end of
this …
[View More]message (trimming the html from the bottom).
I thought long and hard before taking this action. It is not something I would
normally do, but in this instance I was so incensed at this individual's
behaviour that I felt that 'naming and shaming' was the only way forward. Not
even so much as to the fact that he directed his comments to me, but more the
fact that had I been a new prospective developer, the effect such diatribe would
have would not in any way be positive. It certainly would taint their perception
of the open-source community. Furthermore I sincerely doubt that I am the only
one to experience this behaviour. Others may just suffer in silence.
I have worked with many smaller community projects, on OS/2 and latterly on
Linux, and never been subjected to this kind of abuse from members of the
community. I joined this list because I felt that there was something I could
contribute to Wine, and in the instance it turned out that there was. I did not
join it to receive unsolicited email of an abusive nature from members of the
community.
Had he done this by telephone I could have had him prosecuted, at least in the
UK. But he hides behind a gmail.com address and makes comments I seriously
suspect he would not have the balls to say to my face.
No, I do not believe that we need a 'net police force'. Common decency between
individuals, however, is essential. Diversity, discussion, criticism,
expression, even annoyance are all valuable when driving a project forward.
Blatant personal abuse is not tolerable. It is not tolerable in society, it
should not be tolerated in the developer community. The community needs to
police itself, rather than be policed, and individuals who bring the community
into disrepute need to be dealt with by the community. That is why I bring this
into the open.
How to prevent such actions? I do not think it that this is possible in its
entirety. I can (and have) simply add this individual's address to my blocked
list. However, I may have been a newcomer to open-source development who would
not have been so tolerant, and whose opinions of the community may have been
changed by this action. May I suggest that whoever is responsible for the
hosting of the mailing list change the configuration so that email addresses are
not placed in the header? (I am no expert on mailing-list software but it does
not immediately seem to be impractical.) That way all replies have to go to the
list and this would prevent such unsolicited email being sent.
This is my last word on this matter. Make of it what you will. I refuse to be
prevented from contributing to vital projects such as Wine when I can by the
antics of some depraved individual. It has left a sour taste in my mouth though,
and like it or not, it does not portray Wine developers in a good light.
-------------------------------------------------------------------------------
Disposition-Notification-To: Segin <segin2005(a)gmail.com>
Date: Fri, 24 Mar 2006 15:01:11 -0500
From: Segin <segin2005(a)gmail.com>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051202)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dr J A Gow <J.A.Gow(a)furrybubble.co.uk>
Subject: Re: Winetools -> wine doors
References: <1143192770.25116.22.camel(a)despair.kent-music.com>
<442441D7.7020107(a)furrybubble.co.uk>
In-Reply-To: <442441D7.7020107(a)furrybubble.co.uk>
Content-Type: multipart/alternative;
boundary="------------010900050103010506060607"
X-BV-Spam-Score: 0.4 (/)
X-Envelope-From: segin2005(a)gmail.com
X-Virus-Scanned: by amavisd-new
This is a multi-part message in MIME format.
--------------010900050103010506060607
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Dr J A Gow wrote:
>
>> I've looked through the winetools code and it is a clusterf*ck of
>> nonsense. It appears to be in the final stages of code rot, however
>
>
> This "clusterf*ck of nonsense" helped me to get a microcontroller
> development suite running under Wine, which otherwise would not install
You're a fucking retard, RTFM! You'd learn you need to use DLLOverrides
in Winecfg.
> natively. After over ten years designing and developing embedded systems,
> there is one thing that stands out.
That you're a dumbfuck?
> Code that is 'nonsense' does not work
> at all.
That's 100% definitive of Winetools.
> Code that works may not be elegant, it may not be pretty and
> you may hate the style, but it _works_
Nope, wine doesn't do ~/.wine/config, which makes winetools COMPLETELY
useless. **WINETOOLS DOES NOT DO A DAMN REDEEMING THING FOR WINE USERS
THAT ARE UP TO DATE!!!!**
> and therefore it is not nonsense.
Yes, it is.
> This code works, is useful and serves a purpose. Just because you don't
> like the way it is written does not make it nonsense. Language, please!
>
No IT DOES NOT!
> John.
>
>
So you're saying that you don't know how to use dlloverrides on winecfg,
right? that's basically the same thing winetools does except that wine
now ignores the config file (makine winetools utterly useless, 100%, no
questions asked). please just install all the native DLLs that winetools
installs, and set a dlloverride in winecfg of * (native, builtin) for
your exe file. Please stop spouting your mis-infomation.
[View Less]
On 3/29/06, Troy Rollo <wine(a)troy.rollo.name> wrote:
> The recent changes to the desktop have revealed a problem with recursive
> processing of X messages. The problem started to manifest with commit
> 1a4f6e579b6aab685fae2e649fd5accee7ec0b4f (7th March). A symptom is a stack
> that looks like this:
>
> <application Window procedure>
> WINPROC_wrapper
> ...
> CallWindowProcW
> ...
> SendMessageW
&…
[View More]gt; X11DRV_SetWindowPos
> SetWindowPos
> X11DRV_ConfigureNotify
> process_events
> X11DRV_MsgWaitForMultipleObjectsEx
> wait_message_reply
> send_inter_thread_message
> SendMessageTimeoutW
> SendMessageW
> send_parent_notify
> DestroyWindow
>
> In other words, a destroy notification is being sent to the parent window with
> SendMessageW, and before that message returns an unrelated X message is
> processed. Under Windows the equivalent could never happen - if a thread is
> in SendMessage(), the only messages that can be delivered to it are ones sent
> by SendMessage() from another thread.
>
> The consequences of this can be unpleasant if the code that processes (in this
> case a window movement notification) the message interferes with state that
> is being dealt with in earlier stack frames.
Yep, that's why the launching of War3 seems to only paint explorer or
the launch window depending on how I hacked wine.
This is the problem exhibited in bugs 4948, 4897, and 4847.
>
> wait_message_reply calls X11DRV_MsgWaitForMultipleObjectsEx with:
>
> res = USER_Driver->pMsgWaitForMultipleObjectsEx( 1, &server_queue,
> INFINITE, QS_ALLINPUT, 0 );
>
> The brute-force approach of changing this to the following makes the
> application work, but gives rise to some pack_message FIXMEs (for WM_NCPAINT
> and WM_ERASEBKGND), and since this is an extremely sensitive piece of code to
> change I thought it best left to people with more familiarity with it.
>
> --
> Troy Rollo - wine(a)troy.rollo.name
>
>
>
Last thing I did today was looking at the message passing and signal
handling. The signal handling doesn't look any different than before.
I figured something could be up with the message handling as it
seemed one thread was stomping on another but I don't know anything
about wineserver. I'll take a better look tomorrow!
Jesse
[View Less]
> How do you propose we prevent people from emailing people that post to
> wine-devel? How do we choose who gets to email people directly and
> who doesn't? How do we filter the contents of their email?
I want to chime in and say that I'm with Tom and the ole Doc here. I don't think there's any way to filter somebody's contents, but I think it's important for the community to speak up when somebody is out of line.
I know I was the first to respond to Sergin's email by asking that …
[View More]he be more constructive in his feedback, but past that, none of the regulars on this thread said much. Now, his thread has spawned into something that is soooo far out there that it almost has no relevancy to this list. I want to note that I don't see how Sergin's comments and behavior could have been interpreted as anything but inappropriate; however, with the majority of people not saying anything, I can only imagine that Sergin felt that what he did was perfectly okay and acceptable on this list.
I'm trying to say two things here:
1) If somebody says/ does something that is not okay, say something to that person. Of course, be constructive about it. For example, when I first joined this list, people got upset that I was top-posting - I learned that it was not ok in this community because people said someting. So, I try to bottom post (when I remember.)
2) I've always said Wine is an awesome thing - probably the best thing to come out of the Linux community since ... well, Linux and its desktops. Now, more than ever, Wine need as many developers as possible to keep it improve b/c as Linux adoption continues people will look to Wine and CrossOver for application cross-compatibility. And, I'm not talking about the developer who pops in with a patch every 6 months (I see that person as a patch submitter), but instead, I'm talking about a developer who dedicated him/herself to the Wine project. And with that, the team can't afford to lose that good talent b/c the "newbie talent" was mistreated in this community.
Those are my 2 cents that I think will go a long way.
Thanks,
Hiji
[View Less]
Hi there.
I think I just found a very nice D3D testapp: fr-025 by Farbrausch. A nice,
small (8.2MB) graphics demo, already works somewhat with Wine (starts, plays,
music and everything works, good performance), but lots and lots of effects
are simply missing or wrong. It does quite a bit interesting stuff wined3d
doesn't seem to handle: strange viewport handling, glow, blending,
reflections, blur(?). So many unimplemented features I won't even dare to
file bugreports for every single one.…
[View More].. :)
It's the all-time most popular demo on pouet.net (obviously, given it's called
"fr-025 - the.popular.demo" ;) ) You can get it at:
http://www.pouet.net/prod.php?which=9450
--
Willie Sippel
//////// | Tritium Studios
// | ______________________________
//// /// | http://www.tritium-studios.com
<willie(a)froq.net>
[View Less]
I've long wondered why winehq.com does not provide an RSS feed. I've
created one using the feed43.com sitescraping tool. Works well and it
should be very low impact to your webserver (it only hits the URL at
most once every 6 hours and caches the result for subsequent queries)
Feel free to post this RSS link on the winehq homepage.
http://feed43.com/winehq.xml
Best Regards,
Dan Schwarz
Monday, March 27, 2006, 12:51:03 AM, Petr Tesarik wrote:
> Hi,
> this patch fixes a bug in get_thread_context(). Currently, this
> routine assumes that all registers except debug registers are saved in
thread->>context if it exists. However, it does not include FPU
> registers.
> IMO, we should not blindly assume which registers are present in
thread->>context but look at ContextFlags.
> BTW I found this bug when winedbg stopped working with programs using
…
[View More]> the FPU.
> ChangeLog:
> * Look at ContextFlags to see which registers are saved in
> thread->context.
Sorry this is not correct. Exception handler should get full context
including FPU context. If we not saving it that's the problem on the
other end.
Vitaliy Margolen
[View Less]
Alexandre Julliard wrote:
> Module: wine
> Branch: refs/heads/master
> Commit: db6608ac9f9bbc2ddd7f8bf201d1387d079dfd5f
> URL: http://source.winehq.org/git/?p=wine.git;a=commit;h=db6608ac9f9bbc2ddd7f8bf…
>
> Author: Alexandre Julliard <julliard(a)winehq.org>
> Date: Mon Mar 27 22:43:03 2006 +0200
>
> x11drv: Moved desktop mode handling to the explorer process.
>
> Per-application desktop mode settings are no longer supported. Apps
> can be …
[View More]launched in a specific desktop window by using:
>
> explorer /desktop=name[,widthxheight] app.exe [args]
>
> If the named desktop already exists the app is launched inside it. The
> default desktop is cleverly named "default".
>
So if I understand this correctly all programs will share the same
desktop. Is it also true that I cannot specify in winecfg that one
program can run full screen and another in a desktop window.
If this is the case we will have a fair amount of crying over this one.
At the very least we need to put a note in winecfg. (preferabley befor
next release).
--
Tony Lambregts
[View Less]