[Mono-dev] Mono on Android: state of the union?
bell.jeremy at gmail.com
Thu Apr 8 17:09:44 EDT 2010
There might be a possibility that the core runtime will be free, but not the
bindings that would let you use the native Android APIs that would allow you
to do anything outside of a hello world console program:
Quote from Miquel de Icaza:
> It seems like you can use Mono on the Android today, but there is no
> binding to their Java-based APIs.
> At Novell we are going to offer a commercial product to target the
> Android with the native APIs, but do not have yet a timeline ready.
On Thu, Apr 8, 2010 at 3:07 PM, Stifu <stifu at free.fr> wrote:
> Is it a given that MonoDroid won't be free?
> I know MonoTouch isn't, but Mono for MeeGo is free, for example...
> JeroMiya wrote:
> > Koush responded to my tweet saying that he stopped working on it when
> > Novell
> > announced their own plans for Droid bindings. I don't think he ever
> > committed the binding generator code to his git repository. It's a pity,
> > because as a hobbyist mobile developer I certainly couldn't afford the
> > licensing fee for a commercial monodroid license, but given even basic
> > bindings without the kind of Visual Studio/MonoDevelop tooling support
> > would expect in the official MonoDroid, I could certainly make due. It
> > would
> > be easy to allow the user to replace the runtime on their phone - just
> > distribute the code for the bindings and the eclipse project to build the
> > android package that installs it. I believe that would satisfy the
> > requirements of the LGPL. Or am I missing something?
> > On Thu, Apr 8, 2010 at 1:15 PM, Joe Dluzen <jdluzen at gmail.com> wrote:
> >> I would think that you could develop your own bindings, as there are
> >> at least 3 other implementations that I know of. However, like most of
> >> us, IANAL. The MonoDroid and the efforts by Koushik Dutta may be
> >> one and the same, but I don't know right now. On Novell's side, there
> >> is quite literally no information other than "we're working on it and
> >> here's the name." I'm eagerly watching Koush's RSS for anything
> >> Android + Mono related. It appears that the last part of the puzzle
> >> which is still missing, is a tool to generate the C# bindings from the
> >> Java API.
> >> As for the LGPL, the mono runtime binaries installed on the phone
> >> should easily be user replaceable. And if it's an open source app,
> >> then there's no problem at all.
> >> If anyone has any more info, please reply. I'd imagine that many
> >> people are waiting for any information at all.
> >> Joe
> >>  http://www.koushikdutta.com/2010/01/androiddll.html
> >> > Message: 2
> >> > Date: Thu, 8 Apr 2010 05:20:16 -0800 (PST)
> >> > From: JeroMiya <bell.jeremy at gmail.com>
> >> > Subject: Re: [Mono-dev] Mono on Android: state of the union?
> >> > To: mono-devel-list at lists.ximian.com
> >> > Message-ID: <1270732816608-1774004.post at n4.nabble.com>
> >> > Content-Type: text/plain; charset=us-ascii
> >> >
> >> >
> >> > Would I be allowed to develop my own java bindings (obviously they
> >> wouldn't
> >> > be as high-quality as Novell's commercial product) for mono on android
> >> and
> >> > deploy mono-based applications without licensing Novell's commercial
> >> > product? Would I subsequently be able to release said bindings under
> >> > appropriate open source license?
> >> >
> >> > It seems natural to assume so, but you need to be a lawyer to
> >> understand
> >> > software licensing these days.
> >> _______________________________________________
> >> Mono-devel-list mailing list
> >> Mono-devel-list at lists.ximian.com
> >> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> > _______________________________________________
> > Mono-devel-list mailing list
> > Mono-devel-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> View this message in context:
> Sent from the Mono - Dev mailing list archive at Nabble.com.
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list