"Steven Edwards" <[EMAIL PROTECTED]> wrote:
> I have been but I've put my work on it on hold pending a new round of
> patches from Emmanuel. My point was that you asked for patches, there
> is one for your pleasure. I welcome your thoughts and I am sure
> Emmanuel does as well. I know Pierre seeme
Any developer that wants to maintain source and/or binaries on the
Darwine project at SF.net is welcome to do so.
I have responded to every such request that I have seen, which isn't to
say of course that someone hasn't sent such a message that I haven't
seen. Folks should be aware that you mu
On Sun, Mar 2, 2008 at 10:45 PM, Dmitry Timoshkov
<[EMAIL PROTECTED]> wrote:
> I have no idea why you're treating asking the questions as a "hostility".
> This is the developers list, not the list for user complaints. Sending
> the patches is a usual activity here, not vague reasoning.
Sorry I
Dmitry Timoshkov wrote:
> Looks like you overreacted, http://www.kronenberg.org/darwine/ has nothing
> to do with darwine except using its name.
>
>
Actually, I have Mike's code and it uses the Darwine build system and
applies two patches to it. One brings in FontForge so that Apple Native
fo
"Steven Edwards" <[EMAIL PROTECTED]> wrote:
> On Sun, Mar 2, 2008 at 10:00 PM, Dmitry Timoshkov
> <[EMAIL PROTECTED]> wrote:
>> "Neat" is what sense? It's not clear what additional functionality they
>> provide,
>> what's the status of quartz.drv in their sources, and why they don't send
>> pa
On Sun, Mar 2, 2008 at 10:00 PM, Dmitry Timoshkov
<[EMAIL PROTECTED]> wrote:
> "Neat" is what sense? It's not clear what additional functionality they
> provide,
> what's the status of quartz.drv in their sources, and why they don't send
> patches
> to WineHQ. Besides that sites claims that "D
"Dmitry Timoshkov" [EMAIL PROTECTED] wrote:
>> There're very neat Wine Mac builds made on http://www.kronenberg.org/darwine/
>> Do you have contact with the maintainer? I believe you can work out
>> great Mac distro together especially once quartz is ready.
>
> "Neat" is what sense? It's not cl
"Adam Strzelecki" <[EMAIL PROTECTED]> wrote:
> There're very neat Wine Mac builds made on http://www.kronenberg.org/darwine/
> Do you have contact with the maintainer? I believe you can work out
> great Mac distro together especially once quartz is ready.
"Neat" is what sense? It's not clear wh
Adobe Contribute 4, released in Nov 2006 or so, had a nice online trial at
http://trials.adobe.com/Applications/Contribute/Adobe_Contribute_4_Win/Adobe_Contribute_4_Win.exe
and still online, I think, at
http://www.soft32.com/download/63-129953-1/Adobe_Contribute_4_Win.exe
Starting it fails with
e
On Mon, 3 Mar 2008, Dmitry Timoshkov wrote:
[...]
> Perhaps we could agree on a common constant to mark not initialized data in
> tests? I'd suggest to use 0xCC (standard debugging trick) for that purpose.
I'm open to suggestions. So 0xcc is commonly used for this purpose?
If it's used by debugge
On Sun, 2 Mar 2008, Dan Kegel wrote:
> Hey, on that topic, there are also a bunch of other possible suspects:
>
> ./dlls/ntdll/tests/atom.c:memset(abi->Name, 0x55, 255 * sizeof(WCHAR));
> ./dlls/ntdll/tests/atom.c:memset(abi->Name, 0x55,
[...]
> And 0xaa can also interfere:
>
> ./dlls/ke
>> Keep an eye on
>> http://wiki.winehq.org/MacOSX/QuartzDriver
>
> Oh, that's awesome! How did I missed this.
I know, I didn't looked there for over month, and it was recently
updated.
I keep my fingers crossed for QuartzDriver!
Good night,
--
Adam Strzelecki |: nanoant.com :|
> Keep an eye on
> http://wiki.winehq.org/MacOSX/QuartzDriver
Oh, that's awesome! How did I missed this.
> And hopefully in the next few weeks we will have a newer patch in the
> winequartzdrv tree for a more recent version of Wine. I am not sure
> what design changes Emmanuel is wanting to make
>> Let me ask this way, why Wine don't use standard C library functions
>> for lstringsomething kernel32 implementation? Current GLIBC, OSX LIBC
>> are Unicode libraries since quite long time. Is Wine supposed to work
>> on platforms where wchar_t is unimplemented or differs from unsigned
> WCHAR i
Hi,
Due to the bad weather I had some spare hacking time this weekend, and I've
done some work and investigation on a fixed function pipeline replacement.
The product of that is a hacky fixed function pipeline replacement via
GL_ATI_fragment_shader(*).
Functionality wise the code is doing pret
Hi,
On Sun, Mar 2, 2008 at 12:50 PM, Stefan Dösinger <[EMAIL PROTECTED]> wrote:
> Am Sonntag, 2. März 2008 18:14:45 schrieb Adam Strzelecki:
> > Do you guys think about reviving winequartz.drv?
> I think everyone would greatly welcome efforts to continue it, and in fact
> Steven Edwards is curr
Adam Strzelecki wrote:
> Let me ask this way, why Wine don't use standard C library functions
> for lstringsomething kernel32 implementation? Current GLIBC, OSX LIBC
> are Unicode libraries since quite long time. Is Wine supposed to work
> on platforms where wchar_t is unimplemented or differ
Am Sonntag, 2. März 2008 18:14:45 schrieb Adam Strzelecki:
> I know that CodeWeavers supports quite nicely Mac builds of Wine, and
> CrossOver for Mac, yet all of them are X11.
> There was also once Darwine - an effort to provide Carbon Wine UI
> driver and Mac optimizations & L&F.
> Pretty many of
Hi,
I know that CodeWeavers supports quite nicely Mac builds of Wine, and
CrossOver for Mac, yet all of them are X11.
There was also once Darwine - an effort to provide Carbon Wine UI
driver and Mac optimizations & L&F.
Pretty many of those were merged back to Wine, but not winequartz.drv.
Do
> Wine already had at some point strlen along with some other string
> functions
> implemented in asm, however they have been removed after it was
> proved that
> gcc optimized C code outperforms it.
Let me ask this way, why Wine don't use standard C library functions
for lstringsomething ke
"Dan Kegel" <[EMAIL PROTECTED]> wrote:
> Hey, on that topic, there are also a bunch of other possible suspects:
>
> ./dlls/ntdll/tests/atom.c:memset(abi->Name, 0x55, 255 * sizeof(WCHAR));
> ./dlls/ntdll/tests/atom.c:memset(abi->Name, 0x55,
> lstrlenW(testAtom1) * sizeof(WCHAR));
> ./dlls/
Hey, on that topic, there are also a bunch of other possible suspects:
./dlls/ntdll/tests/atom.c:memset(abi->Name, 0x55, 255 * sizeof(WCHAR));
./dlls/ntdll/tests/atom.c:memset(abi->Name, 0x55,
lstrlenW(testAtom1) * sizeof(WCHAR));
./dlls/user32/tests/menu.c:memset( bmfill, 0x55, sizeof
"Adam Strzelecki" <[EMAIL PROTECTED]> wrote:
> I believe the further discussion is pointless. If you ever dared to
> look how MSVCRT or GLIBC strlen function is implemented you would know
> that it is exactly same algorithm (that just differs in the
> implementation) using 4 byte fetching wi
I believe the further discussion is pointless. If you ever dared to
look how MSVCRT or GLIBC strlen function is implemented you would know
that it is exactly same algorithm (that just differs in the
implementation) using 4 byte fetching with magic bits matching, also
described in few books
24 matches
Mail list logo
