On 28/05/2013 7:48 PM, Thiago H de Paula Figueiredo wrote:
On Tue, 28 May 2013 00:39:22 -0300, Chris Cureau <cmcur...@gmail.com>
wrote:
Tapestry itself runs on a web container, like tomcat. The served
pages will operate in chrome in android and probably firefox as well,
though I haven't tested it there.
You're mixing apples and oranges here. First you talked about where
Tapestry can run, then, in the second sentence, talked about where
Tapestry pages can be viewed.
Answer to the original question: as long there's a servlet container
running in Android, you can run Tapestry on it just fine.
Yes, but the bytecode enhancement that tapestry does, it wouldn't be
able to be understood by the Dalvik JVM? As is my understanding. I just
don't want to spend a lot of time getting it set up, then have no
possibility of it working :)
Question to the original question: why?
Just to satisfy curiosity :). We have a web app built with tapestry and
a mobile app that goes along with it. The mobile app runs offline then
syncs with the main app. It shares a lot of code, including the tapestry
interface. So it runs it's own tapestry server, and uses an embedded web
browser (xulrunner) to connect to it. It was a lot simpler in
development doing it this way than re-writing all the user interface for
offline support.
But this was before arm tablets were readily available. So we ran it on
Windows tablets. But these days a decent rugged windows tablet (doesn't
actually exist haha) is about $4000, whereas I can get a galaxy note and
a waterproof case for $500 which will do the job.
So we are looking at the cheapest way to port it over to android, but I
guess an alternative would be linux.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
