[Kde-bindings] some info needed

[SE1]

Arno Rehn-3 wrote:
> 
> 
> Maybe we should blog about this discussion a bit. It would certainly raise 
> awareness of Qyoto/Kimono and we'd also get community responses regarding
> the 
> topic.
> 
> 

Let me just chime in as lurker and Qyoto user for some of my own little
tools. I think that for as far as Qyoto is concerned you're doing a
absolutely awesome job, but for the wrong audience. Mono is the main focus
point of all C# linux and MacOS development, even that specifically targeted
to GNOME, but yet there are only 9 discussion mentioning Qyoto on their
mailing lists in the past year. Considering that Mono by default ships with
full GTK bindings, has documentation and examples on them, there is hardly
any reason for a 'linux C# developer' to start using Qyoto.

However what I like about Mono is that (next to the easy C# language) it
provides a 'write once - run everywhere' environment. And one that's already
pre-installed on probably 90% of the Windows user base if you limit yourself
to the .NET compatible parts. The only thing missing is a decent GUI:
Microsoft's WPF isn't ported, Windows.Forms looks just horrible on linux and
while GTK is cross-platform, it never impressed me on Windows. So I started
using Qyoto as my cross-platform GUI, the Qt design fits almost flawlessly
with the C# way of things and provides a smooth and native experience on all
platforms. The only thing holding me back is that Qyoto is not very
accessible outside of KDE, I've got to gather the Qt-only pieces together,
there's hardly any examples or documentation, and support for Windows or
MacOS is basically 'in theory it should work, more or less'. In short I'd
say try to convince the Mono community what a wonderful platform you have
here and make it more accessible for the non-KDE user, and you might very
well end up with the odd Windows or Mac user that's willing to lend a hand.

As for the whole 'Microsoft discussion', I think there's nothing (maybe
short of GPL-ing the whole .NET platform) that will convince the general
F/OSS community that using Mono might be a good or even acceptable thing.
Afaik Mono has always tried their very best to prevent even the risk of
possible copyright contamination of their implementation (which is fully MIT
licensed) and Microsoft has made a public, irrevokable, statement that they
won't actively pursue any of their patents they might have on the core .NET
technology. That's more or less the opposite of the situation of just about
any other linux project (Microsoft loves to tell how you risk patent
litigations using it). Ofcourse, Mono has made the choice to make their
implementation compatible with the .NET one, but they've also worked on
extending it. They could have made their very own 'C# standard', but there's
nothing forcing Microsoft to follow it either, so you'd end up having two,
very similar, but incompatible environments.
-- 
View this message in context: http://old.nabble.com/Re%3A-some-info-needed-tp28952248p28993173.html
Sent from the kde-bindings mailing list archive at Nabble.com.