On Thu, Apr 1, 2010 at 11:11 PM, Denis Bolshakov
<[email protected]> wrote:
> 5. Re: Say Goodbye to GTK, Will Meego open to what extent? More
> than Android or Less than? (Auke Kok)
Hi Denis,
First of all, please don't reply to Mailing List Digests, and if you
have to, please *do not* quote the full digest. Remove everything
except for the bits you are replying to.
I don't see why Auke's reply (you indicated reply number 5, which
talked about GTK+, and didn't even mention Android or Dalvik) spiked
your interest, but I'll bite. Did you even read Auke's message, or did
you just go for a quick kill from the name of the thread?
> Actually Android is not just Java Machine,
> Android applications have own life cycle, android java machine(Dalvik)
> has own api.
Again, I don't see anyone contradicting this point, please quote the
relevant messages before answering out of the blue.
> And if Meego says that it will support android application it should
> be mean that you need only to repackage an application without any
> modifications in source files.
Again, I don't recall many people promoting MeeGo as an
Android-compatible Operating System. As far as I am aware, there are
no planned ports for Dalvik to a non-Android OS, and even doing so
would also require a massive port of Apache's Harmony. I really don't
believe any Android application will ever be compatible with MeeGo
from the get-go. They may be ported individually, however binary or
source compatible? Not quite convinced by that.
> How can answer? Will Meego support Android App?
My personal opinion is easy: No, with a capital F. I would much prefer
to see efforts to get Java working (which shouldn't be too hard,
considering that Java works quite nicely in easydebian on Maemo)
initially (AWT and Swing will be a lot easier to get to work,
considering that Moblin/MeeGo is aimed at netbooks, hence uses
paradigms which are compatible with these toolkits), secondly see a
J2ME implementation. Yes, these two *before* thinking about
implementing Dalvik and its bastard UI.
Maemo has been plagued by having too many development options
available to it. Forcing developers to make choices usually
discouraged more people than it encouraged them (especially new
developers). Bringing yet another language isn't going to help things.
In order to make the platform as usable and effective as possible, we
need to have a focused and direction in terms of development
environment. Qt 4.6 is a good example of this. What bindings
(python/c++) are used doesn't make a huge difference, considering the
main toolkit remains the same; inviting yet another toolkit would be
very painful, however.
PS: For anyone not understanding why I hail a unified toolkit under
the Qt umbrella, but afterwards invite Java AWT/Swing in the mix:
AWT/Swing support would provide a lot of applications which are
currently unavailable. Even if MeeGo doesn't recommend users to
develop Java/AWT/Swing applications, the ability to run them would be
massive. Why doesn't this apply to the Dalvik VM? Most Android apps
require access to the Android App Store (or whatever it's called), and
none of them aim anything else than mobile phones.
--
question = ( to ) ? be : ! be;
-- Wm. Shakespeare
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
