On Fri, 2005-10-14 at 23:27 +0200, Matevz Jekovec wrote:
> Now that Wine supports different theme packs for Windows, would it be
> possible to render Windows widgets using the native current desktop
> KDE/Gnome theme? Also other stuff like font size, name and colors for
> Windows widgets, could the
Friday, October 14, 2005, 9:17:19 PM, Hiji wrote:
>> Additionally, you might want to read this part of
>> the LICENSE file again:
>>
>> "This program is distributed in the hope that it
>> will be useful, but
>> WITHOUT ANY WARRANTY; without even the implied
>> warranty of
>> MERCHANTABILITY or FIT
Hiji wrote:
In the context of this example and referring to what
I'm getting at, you get one improvement, but in
return, something else gets broken. That just doesn't
seem right. It's like the little kid who makes
breakfast for mom & dad, but in the process, makes a
mess of the kitchen (that
> Additionally, you might want to read this part of
> the LICENSE file again:
>
> "This program is distributed in the hope that it
> will be useful, but
> WITHOUT ANY WARRANTY; without even the implied
> warranty of
> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> See the GNU
> Lesser Gen
Besides, without this type of "responsibility" in
place, I could theoretically pay a developer to fix a
bug for me, and then, 3 months down the line, some
other developer breaks it. What do I do then? Pay
money again to have someone refix it?
Additionally, you might want to read this part of
Besides, without this type of "responsibility" in
place, I could theoretically pay a developer to fix a
bug for me, and then, 3 months down the line, some
other developer breaks it. What do I do then? Pay
money again to have someone refix it?
If you think that a newer version of Wine is "bro
Now that Wine supports different theme packs for Windows, would it be
possible to render Windows widgets using the native current desktop
KDE/Gnome theme? Also other stuff like font size, name and colors for
Windows widgets, could they all be unified? That would *really* be
something:).
Big thank
Lionel Ulmer wrote:
On Fri, Oct 14, 2005 at 04:52:37PM +0100, Christian Costa wrote:
Since vertex buffer support is a hack, I think you can use standard
wined3d drawing primitives for the moment.
Well, vertex buffer support is only a hack in the case of 'pre-transformed'
buffers (i.e
--- Lionel Ulmer <[EMAIL PROTECTED]> wrote:
> On Fri, Oct 14, 2005 at 09:50:48AM -0700, Hiji
> wrote:
> > However, there is a more fundamental problem here.
> I
> > don't see "bugs" in a black vs. white type of
> view; in
> > fact, I can classify bugs in two ways:
> > 1) A bug is something that
Hi Vitaliy,
The message error i gave in the bug report is actually all what Wine gives me...
I can provided you with a detailed trace, but i don't know what switches to use.
Can you please tell me what's necessary for you to investigate, and i'll do my
best.
Regards, Sebastien.
--- Stefan Dösinger <[EMAIL PROTECTED]> wrote:
> Hello,
> I have come across a D3D7 call where I need some help with:
> IDirect3DDevice::DrawIndexedPrimitiveVB. The prototype is
> DrawIndexedPrimitiveVB(LPDIRECT3DDEVICE7 iface,
>D3DPRIMITIVETYP
It seems that NSIS installers have regressed in Wine 0.9 - at least, the
PE Explorer setup which looks and feels like an NSIS based installer won't
install with a "The folder name is invalid" error message. I poked at this
a bit but got nowhere.
The installer of PE Explorer has been created
On Fri, Oct 14, 2005 at 04:52:37PM +0100, Christian Costa wrote:
> Since vertex buffer support is a hack, I think you can use standard
> wined3d drawing primitives for the moment.
Well, vertex buffer support is only a hack in the case of 'pre-transformed'
buffers (i.e. if the application transfo
On Fri, Oct 14, 2005 at 09:50:48AM -0700, Hiji wrote:
> However, there is a more fundamental problem here. I
> don't see "bugs" in a black vs. white type of view; in
> fact, I can classify bugs in two ways:
> 1) A bug is something that has always been broken
> 2) A bug is something that is broken,
On Thu, 13 Oct 2005 10:19:02 -0600, Vitaliy Margolen wrote:
> Looks like a known problem introduced by uxtheme changes [Bug:3241].
I have a nasty suspicion that these applications are simply not themable.
Theming is opt-in on Windows precisely because it's not fully backwards
compatible, but we ar
Am Freitag, den 14.10.2005, 16:29 +0200 schrieb Molle Bestefich:
> Why not do this:
> Accept the patches into trunk, and do the "code freeze" in a branch.
>
> Cons:
> - Can't think of any?
Most Developer are doing the same as before: Working on there Patches.
The Code-Freeze and the Stabilisa
> John Smith wrote:
Before y'all take this too seriously, consider the email address and the
name. "John Smith" at an anonymous hotmail account smells like a troll
to me.
>From my point of view, Wine is a godsend and the amount of work going
into it is fabulous. We at Muse Research depend on your
Hi
http://lists.transgaming.org/pipermail/winex-devel/2004-May/000259.html
Good news. This is working in wine too, with some modifications. I must
set FIXED flag so I really get the desired addresses.
With the attached patch WoW is working for me, clicks on the playfield
are now ok!
This patch
> 3. Ask nicely
This is key, and I completely agree.
However, there is a more fundamental problem here. I
don't see "bugs" in a black vs. white type of view; in
fact, I can classify bugs in two ways:
1) A bug is something that has always been broken
2) A bug is something that is broken, but i
John Smith wrote:
Hmmm... Out of 4 replies I've seen now 3 (or 75%) were about money.
Which leads to the question - why _that_ many people in the wonderful
world of OpenSource are obsessed with money?
If you want to boss people round and complain when people don't spend
their time fixing bu
James Hawkins wrote:
On 10/11/05, Alex Villacís Lasso <[EMAIL PROTECTED]> wrote:
Could you please point me to the URL of the patch that is supposed to
fix the IDA installer and has not been committed? I would like to try it
with the Japanese RPG installer I asked about earlier. I tried goog
> BTW, you might be able to clarify how it can happen that Crossover
> (derived from LGPL-ed WINE, if I understand it correctly) doesn't have
> one of these bugs, but WINE does? I used to think that LGPL requires
> availability of modified source, and therefore WINE developers should be
> able to '
[I can the rest ... there is just one real point I need to make here.]
> I'm saying that from a newcomers fantastically objective POV, there
> might be a more efficient way than what everybody here's used to. And
> I do appreciate that you take time to tell me why I'm wrong. Thanks!
We work thi
> BTW, you might be able to clarify how it can happen that Crossover
> (derived from LGPL-ed WINE, if I understand it correctly) doesn't
> have one of these bugs, but WINE does?
Crossover has a limited set of applications that it supports, whereas Wine
tries to support "all" applications. Sometim
On Fri, 14 Oct 2005, Molle Bestefich wrote:
[...]
Ok, maybe there's one. You need a release manager to pick which
patches gets in the RC / release.
But there must be a million ways of doing that automatically, besides
from having an actual release manager. Script your way out of it.
Automatica
Hi,
On Fri, Oct 14, 2005 at 08:51:06AM -0600, Vitaliy Margolen wrote:
> Again that's not in my power to decide. But I would say - not a good time to
> branch Wine. It's not stable enough to have "stable" and "development"
> branches.
> All fixes are important. And lots of fixes are additional fea
Hi,
On Friday 14 October 2005 16:00, John Smith wrote:
> > > Yes, we welcome you to the wonderful world of OpenSource.
> >
> >Or hire a wine developer to specifically work on those tasks ,-)
>
> Hmmm... Out of 4 replies I've seen now 3 (or 75%) were about money. Which
> leads to the question - wh
> > Why not do this:
> > Accept the patches into trunk, and do the "code freeze" in a branch.
> > Pros:
> > - Developers of patches will not get pissed (ahem) for their stuff not
> > getting in.
>
> In the open source world, anyone submitting
> a patch has to count on patiently resubmitting it
> >Please do not keep up such high expectations, they are not warranted
> >and will not be fulfilled.
[...]
> Once again: originally I didn't have any expectations, but tried to suggest
> a generic workaround for different kind of bugs (those that can be fixed by
> tweaking configuration parameters
I don't want to step on any toes, but I plan on redoing the User Guide
this weekend. Mostly it'll just be an extension of the existing stuff
I wrote and bringing it up to date. I figure I can probably bang it
out in a few hours.
Is anyone else close to having docs completed?
-Brian
Friday, October 14, 2005, 8:29:19 AM, Molle Bestefich wrote:
> Vitaliy Margolen wrote:
>> > You're rejecting a perfectly fine patch to Wine, because
>> > it's the wrong season of the year to send good patches?
>> I have no power to accept nor reject path. All I'm trying to say, is that
>> right
>>
Molle Bestefich wrote:
>Why not do this:
> Accept the patches into trunk, and do the "code freeze" in a branch.
>
>Pros:
> - Developers of patches will not get pissed (ahem) for their stuff
>not getting in.
> - Development doesn't stop just every time a release is coming up.
> - Developers can ac
Hi Stefan,
Stefan Dösinger wrote:
Hello,
I have come across a D3D7 call where I need some help with:
IDirect3DDevice::DrawIndexedPrimitiveVB. The prototype is
DrawIndexedPrimitiveVB(LPDIRECT3DDEVICE7 iface,
D3DPRIMITIVETYPE
d3dptPrimitiveT
Molle Bestefich wrote:
> Pros:
> - Developers of patches will not get pissed (ahem) for their stuff
> not getting in.
> - Development doesn't stop just every time a release is coming up.
> - Developers can actively select whether they'd like to help with the
> release (switch to '0.9-rc' branch)
On 10/14/05, John Smith <[EMAIL PROTECTED]> wrote:
> Hmmm... Out of 4 replies I've seen now 3 (or 75%) were about money. Which
> leads to the question - why _that_ many people in the wonderful world of
> OpenSource are obsessed with money?
John, you really need to chill out.
Free Software works l
Vitaliy Margolen wrote:
> > You're rejecting a perfectly fine patch to Wine, because
> > it's the wrong season of the year to send good patches?
> I have no power to accept nor reject path. All I'm trying to say, is that
> right
> now (Oct 14 2005) Wine is in a "code freeze" (see announcement abou
John Smith wrote:
> Yes, we welcome you to the wonderful world of OpenSource.
Or hire a wine developer to specifically work on those tasks ,-)
Hmmm... Out of 4 replies I've seen now 3 (or 75%) were about money.
Which leads to the question - why _that_ many people in the wonderful
world of Ope
If your business depends upon getting a Wine bug fixed,
From my perspective, the only thing that depends upon getting a Wine bug
fixed, is making Wine a decent competitor to Windows on desktop in, say, 3
years (let's be optimistic).
including the one I work for) that can do this for you.
BTW,
> Yes, we welcome you to the wonderful world of OpenSource.
Or hire a wine developer to specifically work on those tasks ,-)
Hmmm... Out of 4 replies I've seen now 3 (or 75%) were about money. Which
leads to the question - why _that_ many people in the wonderful world of
OpenSource are obsessed
Friday, October 14, 2005, 5:24:40 AM, Molle Bestefich wrote:
> Vitaliy Margolen wrote:
>> 2. This is not a good time for this changes (code freeze is still in affect).
>>
>> Find some bugs in bugzilla to fix
> I'm getting a sick feeling to my stomach here.
> Maybe I'm just misunderstanding things
Please do not keep up such high expectations, they are not warranted
and will not be fulfilled.
Isn't it too high to expect that before answering somebody will read
original posting?
Once again: originally I didn't have any expectations, but tried to suggest
a generic workaround for different ki
Hello,
I have come across a D3D7 call where I need some help with:
IDirect3DDevice::DrawIndexedPrimitiveVB. The prototype is
DrawIndexedPrimitiveVB(LPDIRECT3DDEVICE7 iface,
D3DPRIMITIVETYPE
d3dptPrimitiveType,
On 10/14/05, Molle Bestefich <[EMAIL PROTECTED]> wrote:
> Vitaliy Margolen wrote:
> > 2. This is not a good time for this changes (code freeze is still in
> affect).
> >
> > Find some bugs in bugzilla to fix
>
> I'm getting a sick feeling to my stomach here.
> Maybe I'm just misunderstanding thing
On Thu, Oct 13, 2005 at 10:21:46PM +0200, Raphael wrote:
> Hi,
>
> On Wednesday 12 October 2005 22:07, Oliver Stieber wrote:
> > --- Daniel <[EMAIL PROTECTED]> wrote:
> > > Tribes. The other attachment is some system info (even though DRI is
> > > disabled, enabling ist changes nothing).
> Why y
Molle Bestefich wrote:
I'm getting a sick feeling to my stomach here.
Maybe I'm just misunderstanding things?
You're rejecting a perfectly fine patch to Wine, because
it's the wrong season of the year to send good patches?
People tell me that Wine are always two steps behind.
Doesn't surp
Vitaliy Margolen wrote:
> 2. This is not a good time for this changes (code freeze is still in affect).
>
> Find some bugs in bugzilla to fix
I'm getting a sick feeling to my stomach here.
Maybe I'm just misunderstanding things?
You're rejecting a perfectly fine patch to Wine, because
it's the w
Troy Rollo <[EMAIL PROTECTED]> writes:
> When I got to implementing this it turned out that "my" way ended up
> including
> this as part of it, so I will only submit one since there isn't really a
> "different" way would do anything other than result in lots of duplicated
> code.
I'm afraid I
47 matches
Mail list logo
