New Mono 1.2 Now Supports WinForms 304
smbarbour writes "The Mono project (the open-source .NET compatibility library acquired by Novell when Ximian was purchased) has released version 1.2. They are now including support for WinForms. Ars Technica has a detailed rundown on the new release. The Mono project supports Visual Basic.NET as well, so developers that use VB.NET now have the possibility of directly porting applications to Linux." From the article: "Relatively high memory consumption and performance bottlenecks are commonly perceived as being amongst Mono's most significant weaknesses. Some critics frequently refer to various performance issues to support arguments against broader adoption of Mono technology in open source projects, most notably within the GNOME community. The performance improvements in Mono 1.2 could potentially address such criticisms, but it is likely that a lot more work will be required before the problems are completely resolved."
Very good! (Score:5, Interesting)
Windows Forums means I don't have to rewrite part of the program that uses forms for Linux.
I hope this gets more VS.Net developers porting over to Linux using Mono. Linux can really use more easy to use and easy to develop applications without having to learn kernel hacking and methods that exist only for Linux. This is a good thing and maybe the corporations will decide to have some Linux workstations if they can develop VB.Net applications for them the same way they develop them for Windows.
Indeed. (Score:5, Interesting)
And now with
Re:So what? (Score:3, Interesting)
There are some cool mono projects out there. Now if they would just create a native compiler for mono programs so I don't have to have the entire run-time installed that would be great.
Good for development purposes? (Score:1, Interesting)
What about shady Novell-Microsoft dealing? (Score:1, Interesting)
On the other hand, I do hope Sun will release Java under GPL soon.
Re:Great, even more ways for MS to kill it (Score:2, Interesting)
Sharp Develop (Score:2, Interesting)
Re:Great, even more ways for MS to kill it (Score:0, Interesting)
Stop the FUD.
Re:Great, even more ways for MS to kill it (Score:5, Interesting)
http://techupdate.zdnet.com/techupdate/stories/ma
This was pointed out years ago. No, how long does this agreement last? The answer is, as long as Microsoft wants it to. Should Microsoft revoke this agreement, or initiate a revocation, then the worst that will happen is that the ECMA standards will be revoked. The ECMA wording on this is pathetically weak and under no circumstances gives a legally binding long-term guarantee. This is why we had all that rubbish about a 'letter from Microsoft' that didn't materialise some time back:
http://www.ecma-international.org/memento/codeofc
The whole 'ECMA is safe' thing is what the Mono people would have you believe. It isn't. The RAND stuff is double speak, because Microsoft do have patents that are specific to implementing
It's actually more likely that the Microsoft specific stuff like ADO.Net, ASP.Net and Windows.Forms are safer since these are only namespaces in an API, although their patents basically say that if you're implementing
Re:Whats wrong with Java? (Score:3, Interesting)
My anicdotal evidence suggests that
Let's see some benchmarks to support your claims.
A framework of our own? (Score:3, Interesting)
Seriously, we spend endless hours debating which is less evil---java or mono---and we complain that both don't offer us the flexibility we have grown accustomed to in the F/OSS world, so why haven't we just started from scratch and done our own linux-centric framework to ease RAD work and simplify the task of getting started in Linux development.
I'm not suggesting it has a place everywhere. Certainly most kernel work and most driver work would need to stay C-based, but if we had a framework designed from the ground up to open Gnome and KDE devlopment (well, userspace development in general, really) it would get used. There's obviously a market for it. Developers argue over Java and
I dunno. There may be good reasons, but I don't see them from my vantage point.
Til I see a solid and Free alternative, I'm gonna stick with Mono (which I'm impressed with so far), but I'll keep my eye out.
Tom Caudron
http://tom.digitalelite.com/ [digitalelite.com]
be specific (Score:4, Interesting)
* Which patents is Mono suppose to be violating?
* What reasons does anybody have to believe that those patents actually are worth the paper they're written on?
* Given Microsoft's royalty-free licensing terms, what argument could they possibly make to a judge about damages?
* Why do you believe that those patents are hard to work around should Microsoft be insane enough to assert them?
* Which modern platform is guaranteed to be free from potential patent claims (from Microsoft or anybody else), and where is the evidence?
If people like you can't provide clear, convincing answers to these questions, then we might as well stick with Mono for the time being.
Re:Indeed. (Score:4, Interesting)
Thats for the language. ASP.NET 1 is really where the garbage was (the above was mostly that the languages weren't mature enough). The page model was horrible in every ways, shape, or forms.
Visual Studio 2002/2003 was a fairly poor and feature-lacking IDE, too (and lets face it: in the microsoft world, the IDE is part of the environment).
I guess the reason I felt that way, was that Java 1.5 came out not that long after
If you did
Don't get me wrong, if you look at my posting history, I'm starting to have a reputation to being a Microsoft butt kisser, so I'm definately not biaised against them. I just feel
The more the merrier (Score:4, Interesting)
Re:So what? (Score:3, Interesting)
There aren't that many Mono users out there yet because of a few reasons. First off, the GIMP toolkit looks like crap. (That's a fact, not an opinion.) The only Mono GUI app I've seen is F-Spot, which I won't use due to its poor UI.
Now that Winforms are supported, maybe peeps on the Wintendo side of things can get a decent looking GUI app built in Mono. I suppose we *nix folks would be stuck with GTK+ apps, but then at least some people would get looks.
I would love to get myself off of the wierdo-language constructs of Java and into C#/Mono, but couldn't until now, without relinquishing some serious L&F qualities.
Re:So what? (Score:3, Interesting)
obj.setProperty(sampleValue);
is harder to read than
obj.Property = sampleValue;
Yeah
And, while I am at it - C#'s lack of a "throws" clause on functions is just as annoying. In Java, I have a programmatic way of knowing what exceptions to expect from a function (other than runtime ones, of course). In C#, I have to guess
Re:Very good! (Score:0, Interesting)
Name 3 popular Windows apps that use one of those portable toolkits... I thought so.
Re:A framework of our own? (Score:4, Interesting)
Python is to Linux as VB is to Windows. That has its place, and I'm glad it's there, but I mean a framework that would have compile to a VM that sits above the OS (perhaps even in userspace!) and that has bindings for c#, python, ruby, smalltalk, etc...).
I haven't thought through the details fully, and I could be totally wrong (wouldn't be the first time) but I don't know of anything that makes coding on Linux as easy as coding against
Consider this the feedback of a Windows developer by trade who uses Linux exclusively at home. Anecdotal, but it's the opinion of many/most Windows developers. And they often won't go with mono becuase mono is consistently about 15 months behind MS in its API.
Tom Caudron
http://tom.digitalelite.com/ [digitalelite.com]