Hi,
I am almost complete with implementing mixed-mode support for Mono only some
code cleanup is remaining. Note that however this still will not support
MSVCRT becuase that assumes that is running on .NET Framework. Also note
that applications using unmanaged API (COM interfaces and DLL
Ove Kaaven wrote:
Debian's ia32-libs package isn't an example of a whole lot. It grabs
compiled binaries from the official Debian archive, and nowhere else. It
isn't built on a 32-bit system. If ia32-libs had contained binaries that
could not be built 100% automatically using Debian's official
On Wed, 16 Apr 2008 06:52:49 -0700
Scott Ritchie [EMAIL PROTECTED] wrote:
Ove Kaaven wrote:
Debian's ia32-libs package isn't an example of a whole lot. It grabs
compiled binaries from the official Debian archive, and nowhere
else. It isn't built on a 32-bit system. If ia32-libs had
Stephan Hermann skrev:
When there are people interested in going a hard way of fixing todays
situation in debian/ubuntu and other distris, please let's do it
, sane and with a plan.
There's already work going on to try to get a better solution into
Debian lenny. There's a new ia32-libs-tools
Hi,
From: Hin-Tak Leung [EMAIL PROTECTED]
I can't comment on anything else, but after trying to get a .NET WinForms
application
(mentioned in some of the bugs I filed) for a few months under the 3
options of
native linux mono, wine+.NET and wine+mono, I can say that win32 mono uses
Kornél Pál [EMAIL PROTECTED] wrote:
The only major difference I know is that Mono uses UTF-8 instead of ACP for
ANSI functions.
UTF-8 will break most of Windows applications since they don't expect to see
strings in a multibyte encoding.
--
Dmitry.
The only major difference I know is that Mono uses UTF-8 instead of ACP
for
ANSI functions.
UTF-8 will break most of Windows applications since they don't expect to
see
strings in a multibyte encoding.
I know that. And the problem is that there is a mess of ACP and UTF-8 inside
native
Scott Ritchie skrev:
Agreed. The one tricky thing here is making a proper source package.
There is some precedent for source packages that don't actually build
on the architecture they're for. The ia32-libs package, for instance,
contains both binary and source versions of the 32 bit
On Sun, Apr 13, 2008 at 10:11 AM, Steven Edwards [EMAIL PROTECTED]
wrote:
Rather than ignoring mono these issues make it sound like Wine and
mono should try to work together again. The EULA for the .NET runtime
prohibits distributing it and using it on non-windows licensed systems
so
On Sun, Apr 13, 2008 at 11:14 PM, Roderick Colenbrander
[EMAIL PROTECTED] wrote:
What we really need is mono's windows.forms to be layered on top of gdi32
and user32 for windows controls like buttons, textboxes and so on .. As lots
of programs do overrides using native dlls on them, so
--- On Sun, 13/4/08, Dan Kegel [EMAIL PROTECTED] wrote:
snipped
2) porting Mono's WinForms on top of Wine
gdiplus
instead of Mono gdiplus (and making it more
win32-ish as
a result)
Mono is using MS GDI+ on Windows since it uses GDI+.
Mono's libgdiplus is
only used on non-Windows
On Fri, Apr 11, 2008 at 8:50 AM, Roderick Colenbrander
[EMAIL PROTECTED] wrote:
For a part the issue is that lots of programs are hybrid ones. Some of them
behave 'nicely' in the way they just call a few functions from a native win32
dll. I think apps that embed COM objects (like a Word
On Sun, Apr 13, 2008 at 10:11 AM, Steven Edwards [EMAIL PROTECTED] wrote:
Rather than ignoring mono these issues make it sound like Wine and
mono should try to work together again. The EULA for the .NET runtime
prohibits distributing it and using it on non-windows licensed systems
so we
Hi,
1) support for mixed assemblies in Mono for Windows
I'm trying to do some work on that.
2) porting Mono's WinForms on top of Wine gdiplus
instead of Mono gdiplus (and making it more win32-ish as
a result)
Mono is using MS GDI+ on Windows since it uses GDI+. Mono's libgdiplus is
only
On Sun, Apr 13, 2008 at 12:55 PM, Kornél Pál [EMAIL PROTECTED] wrote:
1) support for mixed assemblies in Mono for Windows
I'm trying to do some work on that.
Cool!
2) porting Mono's WinForms on top of Wine gdiplus
instead of Mono gdiplus (and making it more win32-ish as
a result)
Dan Kegel wrote:
On Thu, Apr 10, 2008 at 7:40 PM, Scott Ritchie [EMAIL PROTECTED] wrote:
Wine-mono on the other hand is probably premature.
How many apps are helped at the moment by
winetricks mono12
? I don't think it's a large number.
Honestly I don't know. Is this due to
Dan Kegel wrote:
On Thu, Apr 10, 2008 at 7:40 PM, Scott Ritchie [EMAIL PROTECTED]
wrote:
Wine-mono on the other hand is probably premature.
How many apps are helped at the moment by
winetricks mono12
? I don't think it's a large number.
Honestly I don't know. Is this
A wine-gecko package would be very useful.
Wine-mono on the other hand is probably premature.
How many apps are helped at the moment by
winetricks mono12
? I don't think it's a large number.
The wine-gecko package should just be a repackaging
of the same blob that is normally downloaded,
at
Dan Kegel wrote:
A wine-gecko package would be very useful.
Wine-mono on the other hand is probably premature.
How many apps are helped at the moment by
winetricks mono12
? I don't think it's a large number.
Honestly I don't know. Is this due to inadequacies in the current mono,
or
On Thu, Apr 10, 2008 at 7:40 PM, Scott Ritchie [EMAIL PROTECTED] wrote:
Wine-mono on the other hand is probably premature.
How many apps are helped at the moment by
winetricks mono12
? I don't think it's a large number.
Honestly I don't know. Is this due to inadequacies in the
20 matches
Mail list logo
