[SailfishDevel] Announcing "Mono for Sailfish"

Bob Summerwill bob at summerwill.net
Fri Aug 22 09:48:56 UTC 2014

+ Damien and Dimitar.

Thanks for the links, info and suggestions!

Yes, Sailfish is just one of N platforms where Qt/QML+Mono will be useful.
  The appeal of Sailfish for the initial development is that it lets us hit
a mobile platform where Qt is the standard (and only?) UI technology.

Qt for Tizen is great, but applications using Qt have been rejected from
the Tizen Store.   That will be moot if Tizen mobile devices never make it
to market anyway, but will be problematic as-and-when the platform
succeeds.   You can still do Qt on Intel NUC and other
non-Samsung-controlled Tizen devices, but it's still a problem.     No such
problem on Sailfish.

I would love to bring Qt/QML+Mono to all platforms.

Contributions, collaboration and assistance would be gratefully welcomed.
 Mono for Sailfish is not a commercial enterprise.   It's a labor of love,
because I want to use C# on these emerging mobile Linux platforms
(including wearable and IoT).    I don't believe that OSes or low-level
technologies like programming languages should be proprietary.   It just
stifles innovation and is an unfair barrier to entry for programmers in the
developing markets.   It is just yet another "moat" for the status quo.

I would love to see a teenager in a poor country getting his first computer
(probably a smartphone) and being able to build and sell C# applications
using just that device to see to rich Westerners.

The next 2 billion smartphone customers?   Boring.   Think about the next
million mobile DEVELOPERS, all incentivized and enabled to rip apart the
complacent corporate status quo with disruptive and revolutionary
applications.    Bring it on.    I think that's the most interesting
opportunity for mobile Linux.    That, and the possibility of crowd-funded
"indie" mobile and wearable hardware.


On Fri, Aug 22, 2014 at 2:31 AM, Tomasz Sterna <tomek at xiaoka.com> wrote:

> Dnia 2014-08-22, pią o godzinie 12:12 +0300, Ville M. Vainio pisze:
> > Better path than QtSharp would be just creating a QML bridge to Mono,
> > i.e. instantiate a QML runtime and make Mono talk with it.
> This is how Go-QML [1] does it.
> You don't need the whole Qt wrapped, just the QML engine - the rest
> should be native app interfacing to QML in place of Qt/C++ app.
> [1] https://github.com/go-qml/qml
> --
> smoku @ http://abadcafe.pl/ @ http://xiaoka.com/
> _______________________________________________
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to
> devel-unsubscribe at lists.sailfishos.org

bob at summerwill.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.sailfishos.org/pipermail/devel/attachments/20140822/be7064a1/attachment.html>

More information about the Devel mailing list