Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.programmer > #30563

Re: casting/converting android API calls to java.awt objects

From me <noone@all.net>
Subject Re: casting/converting android API calls to java.awt objects
Newsgroups comp.lang.java.programmer
References <rgoiw.651760$Hb3.399373@fx03.iad> <wj8ee7d6mja6.1kcygnjgdpou4.dlg@40tude.net> <YcKiw.1070489$yK.33665@fx14.iad> <1gqhb3ln6qcu6$.1m41pb9khy4nu.dlg@40tude.net>
Message-ID <nQTiw.866192$UR.315581@fx04.iad> (permalink)
Organization Newshosting.com - Highest quality at a great price! www.newshosting.com
Date 2014-12-13 09:40 +0000

Show all headers | View raw


On Sat, 13 Dec 2014 09:47:40 +0100, Joerg Meier wrote:

> 
>> It is important to me that I be able to develop and unit test non-
>> hardware specific code directly on the PC, and deal with eclipse and
>> android emulator only when really necessary.
> 
> But yes, it will let you do that, as that is exactly what it was made
> for. You can pretty much write your entire game (or whatever you are
> making) on the desktop, and only test the finished code on Android/the
> emulator to deal with the little quirks where things work on desktop but
> not on Android (like, say, memory related).

I looked at libGdx.  I'm not convinced it's worth "the cost", especially 
since at that point I've introduced a 3rd party library requirement into 
my project, just for the convenience of developing what should be 
"platform neutral" functions on the PC.  I think it makes more sense in 
this case to bite the bullet and stage the code on the android emulator 
and not have to deal with the libGdx quirks like selective garbage 
collection requirements.  I want the code to be as android specific as 
possible.  I just thought I might get lucky but I'm now thinking that 
something even as trivial as packing bitmaps with graphics primitives are 
going to probably have some native JNI code to optimize the memory 
operations, thus prohibiting any real platform portability.

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

casting/converting android API calls to java.awt objects me <noone@all.net> - 2014-12-11 21:45 +0000
  Re: casting/converting android API calls to java.awt objects Joerg Meier <joergmmeier@arcor.de> - 2014-12-12 16:49 +0100
    Re: casting/converting android API calls to java.awt objects me <noone@all.net> - 2014-12-12 22:44 +0000
      Re: casting/converting android API calls to java.awt objects Joerg Meier <joergmmeier@arcor.de> - 2014-12-13 09:47 +0100
        Re: casting/converting android API calls to java.awt objects me <noone@all.net> - 2014-12-13 09:40 +0000
  Re: casting/converting android API calls to java.awt objects Roedy Green <see_website@mindprod.com.invalid> - 2014-12-15 16:57 -0800
    Re: casting/converting android API calls to java.awt objects me <noone@all.net> - 2014-12-16 07:36 +0000

csiph-web