• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Android In Practice - Questions

 
Ranch Hand
Posts: 3389
Mac MySQL Database Tomcat Server
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Lucas Jordan & Pieter Greyling,

Congratulations on your book. I had seen the description of the book in Amazon.

I have a few questions.

1. How different is your book from other Android books?
2. What are the challenges while interacting/binding the Android apps with LUA, SL4A etc.,?
3. How about covering any security/authentication aspects in android? Does it have any inbuilt features?

Thanks in advance.

Cheers,
Raghavan alias Saravanan M
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
whats lua sl4a? thnks
 
author
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Raghavan,

Thanks for your questions.

1. Regarding what distinguishes our book from the other Android books out there, please see this post where the same question is answered by Lucas:
https://coderanch.com/t/530779/Android/Mobile/Practical-Android-Projects-Book-Different
2. Like with most architectures that embed one language environment within another, the main challenges are the sharing of data structures, calling code across environment boundaries, exception reporting, security concerns related to trusting code that that calls internal code from external script code etc.
3. The book covers authentication in scenarios such as when the Android application calls a device external service such as Google App Engine, Facebook, or Twitter.

Raghavan Muthu wrote:Hello Lucas Jordan & Pieter Greyling,

Congratulations on your book. I had seen the description of the book in Amazon.

I have a few questions.

1. How different is your book from other Android books?
2. What are the challenges while interacting/binding the Android apps with LUA, SL4A etc.,?
3. How about covering any security/authentication aspects in android? Does it have any inbuilt features?

Thanks in advance.

Cheers,
Raghavan alias Saravanan M

 
Pieter Greyling
author
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Jeff,

Jeff Swope wrote:whats lua sl4a? thnks



Lua is a powerful scripting language that is very well suited for embedding into applications thus making them script-able or controllable from external scripts. In the book we present a chapter (Chapter 4: Embedding Lua in Android Applications) that shows via practical projects how to extend an Android application using the Kahlua2 Java-based Lua implementation.
More information on the Lua programming language can be found here: http://www.lua.org/
Kahlua2 is hosted here: https://github.com/krka/kahlua2

SL4A stands for "Scripting Layer for Android". It strives to be a generic software layer/architecture for bringing scripting languages to the Android Platform. Chapter 5 of our book provides an introduction to SL4A.
The SL4A home is here: http://code.google.com/p/android-scripting/
 
Raghavan Muthu
Ranch Hand
Posts: 3389
Mac MySQL Database Tomcat Server
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thank you Peter for the answers.

can you please throw some lights on the #2 especially sharing of data structures, calling code across environment boundaries, exception reporting? what caution would you have to exercise?
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic