Linked by Thom Holwerda on Fri 17th Feb 2006 12:53 UTC, submitted by Kelly Rush
SkyOS Just a few days after Mono got ported to SkyOS, SkyOS now has support for System.Windows.Forms. A screenshot of the first C# application using System.Windows.Forms developed in and for SkyOS is available at the SkyOS website. Support is not complete yet, obviously.
Thread beginning with comment 96896
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Make ur own
by Emerson on Fri 17th Feb 2006 23:43 UTC in reply to "RE: Make ur own"
Member since:

"Windows.Forms compatibility on other OSes just makes it easier to write cross-platform software like Java is capable of."

The big problem is that Java's often lampooned for being substandard as far as that goes for GUI applications, and .net is even worse. Windows.forms will make the application look good in windows, bad everywhere else. gtk# will make it look good on linux, so-so on windows, and horrid on osx if it even runs. wx#, never been able to even run at all on any linux distro I've tried it on.

C# had the potential to be 'the' answer to crossplatform development in a reasonably fast language, but, sadly, it's not.

Reply Parent Score: 1

RE[3]: Make ur own
by Botty on Sat 18th Feb 2006 01:46 in reply to "RE[2]: Make ur own"
Botty Member since:

You are calling .net C#, people need to understand there are many languages for .net, C# is just the most common. Boo is probably the best of the languages - the .net platform allows much easier language development. This way you can focus on language usability, features, and syntax niceness, with a fairly fast backend (Boo code is as fast as C#)

There is nothing stopping someone from creating a truely cross platofrm .net gui. I can imagine it being quite nice. XML based, and rather than setting pixel sizes, etc you just create a hierarchy of components. You establish interrelations like this component is on the border of this component, etc. The layout is created based on the target gui/theme. This way it looks right in native guis. Windows support would be easiest - just access System.Windows.Forms.

Reply Parent Score: 3

RE[4]: Make ur own
by umccullough on Sat 18th Feb 2006 02:45 in reply to "RE[3]: Make ur own"
umccullough Member since:

Or even - if developers are nice enough to separate presentation layers from functionality - each OS could have native .NET bindings for GUI - and developers can write .NET code that directly works with each OS as necessary... of course this is a lot more work for the OS vendor, AND for the developer, but it's a heck of a lot better than having every OS with a completely different development platform as the original poster suggested.

Reply Parent Score: 1