Re: [Xenocide-programming] c# problems

[Hymie t. C. R. <con...@sh...>]

----- Original Message ----- 
From: "Ermete Gaudenzi" <ex...@li...>
To: <xen...@li...>
Sent: Tuesday, June 01, 2004 3:55 AM
Subject: [Xenocide-programming] c# problems


> The problem is that to use the exported functions of a DLL (in .NET
they're
> called "unmanaged dll function") we have to declare it again in C# and we
> can forget to simply handle classes.
>
> Concretely in paqfiles.dll there are 129 exported functions that must be
> declared again. Plus this if we want to group them again into classes or
> (better) if we want to use them like classes we have to write a wrapper
for
> each class and for each datatype.

I just started messing around with C# (just installed it) and didn't realize
it was this limited for supporting C++.  Man, this is no better than Visual
Basic's support for C++.  :(

Do you think we can manage to interface PAQExplorer and PAQFiles by only
using functions?  It'd be a lot less convenient, but for interfacing between
the UI and PAQFiles do we necessarily need classes?

> We can have the insane idea of porting the whole PAQFiles under C++
> managed  (.NET) or C# but what about the rest of the project? I don't
think
> there's a way to access .NET code from outside. I mean without declare
> again every exported function and write wrappers.
>
> What are the alternatives?
> 1) leave PAQExplorer under C++ but use gtk or qt as graphic libraries,
> which are multiplatform and non-microsoft (fortunately!). I don't know if
> there's an IDE that supports them

wGlade is a windows port of Glade (graphical creation of GTK code), and
might be promising.  But isn't using GTK even more work than writing
wrappers in C#?


Item ob du ainen pauren wild schaczen so vass
im dy haut zu samen an seinen hals und stich
im dar durch, als hie gemalt stet so maint
er man hab im denn hals ab geschnitten und schat nit

                               -- a great party trick from the Codex
Wallerstein