After all the debate, gtk# will most likely find its way into GNOME. "The release team has completed its second meeting to try to finish the new module decisions. And, after all the long threads on d-d-l and the many discussions amongst ourselves trying to determine community consensus, we finally have the decisions. In summary: orca, alacarte, and gnome-power-manager are in; gtk# and tomboy are in, assuming the issues mentioned are resolved; sticky notes becomes deprecated, assuming tomboy issues are resolved and gets in." Update: Elijah Newren emailed me concerning an important aspect of the current decision, and asked me to highlight it. So, read more!
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-12-23
At the end of the day, I think, there are many parts which aren't going to be implemented (Indigo, Avalon, XAML) simply because the Novell/OpenSource developers feel that they can provide a better alternative to the Microsoft designed technology; case in point, use GTK# rather than Winforms - GTK# being the preferred widget kit and Winforms being there mainly for compatibility reasons rather than being a 'core component' that developers should rely on.
Where is this blind trust of Microsoft coming from when they aren't open sourcing .NET like Sun is with Java? Is there some sort of 'middle ground' GNOME developers are supposed to except now; where they have to cater to the big guys? Is it even legal to be copying directly from .NET? I know with Java when it was closed, Java ports were considered not Java but completely different languages as was stated on those websites. Eventually MS will have no choice but to seek royalties with Mono as they do with .NET.
Member since:
2005-07-06
Sure, it doesn't exist. RedHat, who was saying it did for the longest time, finally admitted that there was no real issue with the mono core. There MAY be issues with Windows.Forms and other select components that aren't directly part of .NET, but those are already abstracted and if a legal issue arises, its very simple to get them out. Remember, .NET is a ECMA standard submitted by Microsoft, so they won't get very far saying Mono can't implement .NET or C#.
And given the EU ruling on the provision of specifications to third parties to allow better interoperability and compatibility, I doubt Microsoft is going to risk rocking the boat anytime soon.
At the end of the day, I think, there are many parts which aren't going to be implemented (Indigo, Avalon, XAML) simply because the Novell/OpenSource developers feel that they can provide a better alternative to the Microsoft designed technology; case in point, use GTK# rather than Winforms - GTK# being the preferred widget kit and Winforms being there mainly for compatibility reasons rather than being a 'core component' that developers should rely on.
Edited 2006-08-02 19:03