Hi, I think we rather use mono project's libgdiplus(gdiplus.dll implementation) than a stub implementation. This will help in later implementing the .Net Compatibility Layer to Wine. Thanks, Vijay
Hi,
On 6/15/06, Vijay Kiran Kamuju infyquest@gmail.com wrote:
I think we rather use mono project's libgdiplus(gdiplus.dll implementation) than a stub implementation. This will help in later implementing the .Net Compatibility Layer to Wine.
What do you mean? I looked at this before and even if we are to use libgdiplus we need some way to wrap it in a way the Windows app expects. I tried to make a stub wrapper that dlopened libgdiplus and forwarded the calls but I kept running in to some sort of problem. In any case I don't see whats wrong with accepting this stub dll. It will force us to implement it rather than depending on the Microsoft version of the dll.
Hi,
The libgdiplus for mono is implementing things quite differently. I think its only working with mono. We need to modify our wine code so that it works with mono. (You must really ask Julliard for this) or modify libgdiplus of mono to work with wine. What I am saying is why re-invent the wheel, its already implemented by mono project or we can keep a modified version of libgdiplus in our sources. (This might cause some problems if you have mono installed). Regarding the stub dll, how does mono install the gdiplus, if it install the gdiplus as gdiplus.dll.so, it might be a problem.
Those are all my concerns. Thanks, Vijay
On 6/16/06, Steven Edwards winehacker@gmail.com wrote:
Hi,
On 6/15/06, Vijay Kiran Kamuju infyquest@gmail.com wrote:
I think we rather use mono project's libgdiplus(gdiplus.dll implementation) than a stub implementation. This will help in later implementing the .Net Compatibility Layer to Wine.
What do you mean? I looked at this before and even if we are to use libgdiplus we need some way to wrap it in a way the Windows app expects. I tried to make a stub wrapper that dlopened libgdiplus and forwarded the calls but I kept running in to some sort of problem. In any case I don't see whats wrong with accepting this stub dll. It will force us to implement it rather than depending on the Microsoft version of the dll.
-- Steven Edwards
"There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo
On Fri, 16 Jun 2006 03:56:04 -0400, Steven Edwards wrote:
What do you mean? I looked at this before and even if we are to use libgdiplus we need some way to wrap it in a way the Windows app expects.
Why? GDI+ is distributed with applications, so we can put off implementing it for some time yet. Using Monos GDI+ means using the Windows build of Cairo too; definitely a good idea IMHO as GDI+ is somewhat nontrivial and the code has already been written.
thanks -mike
On 6/16/06, Mike Hearn mike@plan99.net wrote:
Why? GDI+ is distributed with applications, so we can put off implementing it for some time yet. Using Monos GDI+ means using the Windows build of Cairo too; definitely a good idea IMHO as GDI+ is somewhat nontrivial and the code has already been written.
Like the parent said, some installers don't ship with it, they expect the OS to have it. Office 2007 only runs on XP and higher and it expects the dll to already be there.
On Fri, 16 Jun 2006 11:52:37 -0400, Steven Edwards wrote:
Like the parent said, some installers don't ship with it, they expect the OS to have it. Office 2007 only runs on XP and higher and it expects the dll to already be there.
So we find some free application that contains it and install that first :)
thanks -mike
-
Mike Hearn -
Steven Edwards -
Vijay Kiran Kamuju