Paul Vriens wrote:
I've sent in a patch that got some remarks by Juan Lang. The patch is
already applied to mmbranch.
Most patches sent to wine-patches that have (valid) comments will not be
applied by AJ.
Should I now resend to make sure it gets applied when AJ is back AND
sent a patch to
On 04.09.2006 07:33, Ivan Gyurdiev wrote:
... using:
GL_ARB_texture_float
GL_ARB_half_float_pixel
The internal format is RGB16/32F, which is wasteful (2 unused colors),
but there's no way around that.
What about INTENSITY or LUMINANCE textures?
-f.r.
On 9/3/06, Mike McCormack [EMAIL PROTECTED] wrote:
Code that originates in ReactOS will generally not be accepted into Wine
due to that project's acceptance of developers that participate in
dirty reverse engineering (ie. translating assembly code to C).
??
From :
Frank Richter wrote:
On 04.09.2006 07:33, Ivan Gyurdiev wrote:
... using:
GL_ARB_texture_float
GL_ARB_half_float_pixel
The internal format is RGB16/32F, which is wasteful (2 unused colors),
but there's no way around that.
What about INTENSITY or LUMINANCE textures
It seems they
Tom Wickline [EMAIL PROTECTED] wrote:
Looks to me like reverse engineered code is not permitted for
inclusion in ReactOS so how is it there participating in dirty
reverse engineering?
That's just a declaration supposed to create a better face on public,
nothing more to take it seriously. Same
[EMAIL PROTECTED] wrote:
Thanks for the helpful replies.
I have been working on the Winelib approach
suggested by Jeremy. As my first step I wanted to get a windows console
application
to compile and run anyway.
I now have an executable that runs and calls
functions in the windows dll,
On 04/09/06, Paul Chitescu [EMAIL PROTECTED] wrote:
Changelog: Avoid a segfault in IWineD3DDeviceImpl_ProcessVertices by checking
if SrcImpl (parameter pVertexDecl) is NULL.
The function is called from dlls/d3d8/device.c
IDirect3DDevice8Impl_ProcessVertices with an explicit NULL as vertex
On Mon, 4 Sep 2006, H. Verbeet wrote:
On 04/09/06, Paul Chitescu [EMAIL PROTECTED] wrote:
Changelog: Avoid a segfault in IWineD3DDeviceImpl_ProcessVertices by
checking
if SrcImpl (parameter pVertexDecl) is NULL.
The function is called from dlls/d3d8/device.c
In this patch I create new library svrapi.dll
There are:
dlls/svrapi/svrapi_main.c
dlls/svrapi/scrapi.spec
dlls/svrapi/Makefile.in
include/svrapi.h
And changes in:
configure.ac
include/Makefile.in
dlls/Makefile.in
--
Best regards, Konstantin Petrov
--- /dev/null 2006-07-03 10:36:18 +0400
In this patch I make 3 functions (FIXME): NetShareEnum, NetShareDel,
NetShareAdd
Files to change:
dlls/svrapi/svrapi_main.c
dlls/svrapi/svrapi.spec
--
Best Regards, Konstantin Petrov
--- dlls/svrapi/svrapi_main.c 2006-09-04 20:18:12 +0400
+++ dlls/svrapi/svrapi_main.c1 2006-09-04 20:19:10
* On Mon, 4 Sep 2006, Dmitry Timoshkov wrote:
* Tom Wickline [EMAIL PROTECTED] wrote:
Looks to me like reverse engineered code is not permitted for
inclusion in ReactOS so how is it there participating in dirty
reverse engineering?
That's just a declaration supposed to create a better
On 04/09/06, Paul Chitescu [EMAIL PROTECTED] wrote:
Well, what do you thing it did before at the line
if(SrcImpl-vbo) {
...
if SrcImpl is NULL?
I don't understand what the code does but every part of it depends on
having a non-NULL SrcImpl. I think screaming bloody murder but
Hi,
I don't understand what the code does but every part of it depends on
having a non-NULL SrcImpl. I think screaming bloody murder but continuing
is better than crashing.
I agree that the code doesn't look good but at least testing can proceed
past this point.
For some reason I didn't get
On 9/4/06, Saulius Krasuckas [EMAIL PROTECTED] wrote:
Well, Dmitry and Mike, this sound very probable, but have you any proof of
all ReactOS code audit process being fake ?
The audit went awfully quickly, for one thing,
and it was done without a neutral third party.
Wine's been doing its own
Sorry Mike but from an external point of view your argument sounds like
ideology:
1) I dont understand why someone contributing to ReactOS would have
his/her code rejected in all cases. Contributing to ReactOS does not
necessary means the code is dirty reverse engineering.
2) The author stressed
On 9/4/06, Julien [EMAIL PROTECTED] wrote:
Sorry Mike but from an external point of view your argument sounds like
ideology:
1) I dont understand why someone contributing to ReactOS would have
his/her code rejected in all cases. Contributing to ReactOS does not
necessary means the code is dirty
* On Mon, 4 Sep 2006, Dan Kegel wrote:
* On 9/4/06, Saulius Krasuckas [EMAIL PROTECTED] wrote:
have you any proof of all ReactOS code audit process being fake ?
The audit went awfully quickly, for one thing,
and it was done without a neutral third party.
Wine's been doing its own audit
I'm afraid it's the other way around at this
point - the burden of proof is on ReactOS to show
that their code is clean :-(
A)-no offense, but this sounds like something SCO
would say. if you got something (from reactOS current
that is already audited..) that you can prove is
dirty- please
On 9/4/06, Saulius Krasuckas [EMAIL PROTECTED] wrote:
BTW, can results of Wine's own audit process be seen somewhere on the web?
Good question. I don't know the answer, but I'll see if I can find one.
It would be nice to know at least what speed was Wine project audited and
when did it
Dan Kegel writes:
I doubt the audit is completed yet (these things are asymptotic; you
can get to 90%
complete a lot faster than 99% complete, etc.).
I am not trying to be a jerk and I am not taking a shot at you personally.
I actually think you are a good guy Dan so don't take this the
On 9/4/06, Brandon Mark Turner [EMAIL PROTECTED] wrote:
I think it would be nice if everyone just left this thread alone for now.
You guys made up your minds that you don't want our patches. And thats
fine.But there is no reason to continue to express hateful opinions
about ReactOS.
I
Hi Paul,
+ * Write a singe value and it's data to:
s/singe/single/, s/it's/its/
+/* Turn OID into a wide-character string */
+Len = MultiByteToWideChar( CP_ACP, 0, OID, -1, NULL, 0 );
+OIDW = HeapAlloc( GetProcessHeap(), 0, Len * sizeof(WCHAR) );
+MultiByteToWideChar( CP_ACP, 0,
Julien wrote:
/ I was very interested in comparing the implementation status of reactos
// and wine. So I coded a little python script to list all the api that are
// implemented in reactos AND are only stub in wine. Attached to this mail
// is the list of identified functions.
//
// One may
23 matches
Mail list logo
