Sorry, missed your message. See:
http://github.com/remvee/clojurehelloandroid/
for a hello world example.
On Thu, Mar 12, 2009 at 3:04 PM, rob wrote:
>
> Ok, duh, somehow didn't catch that this link was the code I was
> wondering about:
>
> http://github.com/remvee/clojure/tree/master/
>
>
Ok, duh, somehow didn't catch that this link was the code I was
wondering about:
http://github.com/remvee/clojure/tree/master/
Also, this is interesting:
http://translate.google.com/translate?sl=auto&tl=en&u=http%3A%2F%2Fblog.remvee.net%2F2009%2F01%2F18%2FsetText_tv_Hello_Android_from_Clojure
That is exciting! Have you posted any code or advice/instruction on
how one could repeat what you did with Clojure on the Android phone?
Rob
On Feb 6, 12:29 pm, "Remco van 't Veer" wrote:
> Got startup time down to 5 seconds by completely eliminating the use
> of lispreader and putting of load
Hi Remco,
If you've written up anything, or plan to, on your progress on getting
Clojure going on the Android platform I'm very interested in learning
more.
Thanks!
Rob
On Feb 6, 12:29 pm, "Remco van 't Veer" wrote:
> Got startup time down to 5 seconds by completely eliminating the use
> of li
I looked into this briefly; I'm amazed at the progress you've made. Please
keep updating!
On Fri, Feb 6, 2009 at 11:29 AM, Remco van 't Veer wrote:
>
> Got startup time down to 5 seconds by completely eliminating the use
> of lispreader and putting of loading the xml, set and zip namespaces.
> T
Got startup time down to 5 seconds by completely eliminating the use
of lispreader and putting of loading the xml, set and zip namespaces.
There's no clear bottlenecks left to fix.
On Fri, Feb 6, 2009 at 1:06 AM, Remco van 't Veer wrote:
> I've managed to get to startup time down from 12 second
I've managed to get to startup time down from 12 seconds to 7 on the
emulator and hope get it below 4 seconds tomorrow. A lot of time is
spend in LispReader when the core constants are initialized. I've
altered the compiler to emit type specific code for the basic cases,
thus bypassing LispReade
Having a lisp to do android app development is definately worth some efford.
Kawa already has some android support in svn trunk but it doesn't seem in a
usable state; my experiments break because a lot of expressions do not seem
to compile AOT. The parts that do compile are very fast on the other h
On Feb 4, 10:12 am, "Remco van 't Veer" wrote:
> Caching Reflector.getMethods, as described below, works pretty well.
> Performance seems acceptable for now. Startup time is still dramatic,
> need to investigate. Considering releasing changes as a fork on
> github is anybody is interested.
>
I
Caching Reflector.getMethods, as described below, works pretty well.
Performance seems acceptable for now. Startup time is still dramatic,
need to investigate. Considering releasing changes as a fork on
github is anybody is interested.
On Sat, Jan 31, 2009 at 8:35 PM, Remco van 't Veer wrote:
Some naive caching code does speed up my sample by 4 times. Will
investigate further later this week, need to take my flu to bed now..
diff --git a/src/jvm/clojure/lang/Reflector.java
b/src/jvm/clojure/lang/Reflector.java
index f530b78..eccebb8 100644
--- a/src/jvm/clojure/lang/Reflector.java
+
I've been playing around with clojure on the android platform. To my
surprise it was pretty easy to get running, after removing the bean
method from the clojure.jar as hinted by Rich somewhere. Of course
clojure code needs to be compiled AOT and eval doesn't work, as was to
be expected, but all
12 matches
Mail list logo
