Re: CodeProject, wxWindows, and wx.Net

"Gopal V" wrote in message news:[email protected]...
> If memory serves me right, Tom wrote:
>
> > Currently, there is no MFC.net and there is no Windows Forms for Win32
> > , and both are proprietary anyway (an issue that this target audience
> > probably won't care too much about).  So wx.Net provides them with the
> > unique opportunity to write a C++ GUI application that can be compiled
> > to native platforms or to dotNet, with minimal modification.
>
> I have no idea how wx.NET API is comparable to the traditional C++ code
> compared to the Managed C++ stuff .. Also Managed C++ does not run
> portably (unless you run your VM inside Wine) ...
>
> Also from all I know , Managed C++ is a proprietary compiler and produces
> a non-public format output code . The rumour mills say that it generates
> a bit of x86 code ,so moving across platforms might be really hard.

Yes, the managed C++ compiler is proprietary.  But, the output CAN be pure
MSIL, and I believe that MSIL is part of the standard (ie. controlled by MS
but otherwise public).   Therefor, I disagree with the statement 'Managed
C++ does not run portably'.  To make sure that the output is pure MSIL you
must avoid using unmanaged classes and API's (this is one of the reasons to
use wx.NET instead of wxWindows).

One problem I had in converting code was that I had to use the STL templates
as un-managed classes.  But apparently Kate Gregory has written an article
showing how to use the STL as managed code.

> > Does this all make sense?
>
> It does , but I don't think you'll be able to run Managed C++ code on
> non-MS VMs.

Again, I think it depends on how you use it.

> But just like any  other C++ program , you can compile your app with
> Managed C++ to get something that MS calls a .NET executable (though
> I can't say that's revolutionary).
>
> Generally speaking you don't need wx.NET to use wxWindows with MS's
> Managed C++ compiler.
>
> But still, it's a good demo for wxWindows as a whole :)

When you use wx.NET with MC++ or any other dotNet language there will be a
managed to unmanaged transition for all your calls, but this is also true
for any part of the dotNet framework that needs to invoke system services.
Windows Forms is no different.  One of the reasons that a developer might
use wx.NET instead of wxWindows in their MC++ program is that Mono or dotGNU
might ship wx.NET with their dotNet runtimes.

I explain I bit more about why I think a developer might be interested in
this in another reply in this thread that I sent to this newsgroup
yesterday.  It appears to have got lost so I'll resend it.

I'm away for the next four days - it's a provincial holiday here - so I won't be responding.

Thanks for your input Gopal,

Tom.

> Gopal
> -- 
> The difference between insanity and genius is measured by success
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
>
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01