Nov 3 | 3:55 PM |
Mark M. | has entered the room |
Mark M. | turned on guest access |
Nov 3 | 4:00 PM |
Filbert | has entered the room |
Filbert |
Hi Mark
|
Mark M. |
howdy, Filbert!
|
David R. | has entered the room |
Mark M. |
howdy, David!
|
Mark M. |
Filbert: you got here first -- do you have a question?
|
Filbert |
I do...
|
Filbert |
I basically have multiple, similar apps that all have their own content
|
David R. |
Hello
|
Nov 3 | 4:05 PM |
Filbert |
but they all pull from the same system, and I want to implement login such that persists across the apps
|
Mark M. |
why are they multiple apps?
|
Filbert |
each one is customized to a particular content
|
Mark M. |
so?
|
Mark M. |
do you install separate Web browsers per Web site?
|
Filbert |
nope, but the website has its own landings and domains for each content source
|
Filbert |
but really, it's not about whether that is a good design or bad
|
Mark M. |
regardless, I think that AccountAuthenticator and
SyncProviders are perhaps the solution for centralized credentials, but I
haven't played with them yet
|
Filbert |
okay I'll look into those
|
Mark M. |
David: do you have a question?
|
David R. |
I do
|
David R. |
I'm researching a problem I have for work. I've
been working on this issue for a few weeks. I want to be able to monitor
all the events of an application. I've discovered that is next to
impossible with android api, but I was wondering if it was possible
though maybe having them person developing the application add my
library into the build?
|
Nov 3 | 4:10 PM |
Mark M. |
what do you mean by "all the events of an application" ?
|
David R. |
Touch events
|
David R. |
basically user input
|
Mark M. |
not only would they need to add your library, they
would need to add logic to all their activities (and perhaps all their
widgets)
|
Mark M. |
basically, everywhere there is potential for user input, they would have to call your code
|
David R. |
Yeah, I am trying to make it as user friendly as possible. So as little overhead as I can.
|
Mark M. |
this is certainly doable, but not a lot of fun, and prone to forgetting stuff
|
David R. |
Any other ideas to have it work besides making them add logic to all of their own activities?
|
David R. |
I've got this concept working on the iphone, but I have been hiting a brick wall on the android.
|
Mark M. |
not really
|
David R. |
Is it possible to write a version of the SDK, and
have them include it in project.. The .jar file with my own
modifications to the source or would they have to root it.
|
Mark M. |
that's called "modding the firmware"
|
Mark M. |
and it would replace the OS on the device
|
Mark M. |
also doable
|
Mark M. |
but I don't know much about the mechanics
|
Nov 3 | 4:15 PM |
Mark M. |
and it's not exactly something an ordinary app developer would do
|
David R. |
Yeah, would be a bit of a pain for someone to do, just to test their application.
|
Mark M. |
this is for testing purposes?
|
David R. |
Yes
|
Mark M. |
ah
|
Mark M. |
in that case, read the chapter in the Advanced Android book entitled "Tapjacking"
|
David R. |
Got it working perfectly on the iphone.
|
David R. |
tapjacking..
|
David R. |
Maybe I missed that in the advanced book.
|
Mark M. |
for creating a test recorder, tapjacking is a reasonable approach, assuming the app isn't set up to defend against it
|
David R. |
Does that go though the usb?
|
Mark M. |
page 441 in the current edition
|
Mark M. |
no
|
David R. |
Alright.
|
Mark M. |
it's all on the device
|
David R. |
I will take a look at it.,
|
Mark M. |
in fact, you wouldn't even need to add anything to the app
|
David R. |
Sweet thank you.. I did love your books.
|
David R. |
Read the first one twice.
|
Mark M. |
as a production technique, it screams "security issue", but for internal testing, it's OK
|
Mark M. |
glad you like them!
|
Mark M. |
Filbert: do you have another question?
|
Mark M. |
OK, if anyone has a question, chime in
|
Nov 3 | 4:20 PM |
David R. |
Mark, is TapJacking considered a security flaw that could be fixed in updates?
|
Mark M. |
I consider it a security flaw
|
Mark M. |
Google does not
|
Mark M. |
I am not aware that they plan to change anything
|
Mark M. |
that being said, anything is possible
|
Mark M. |
which is another reason not to use it in production
|
David R. |
Okay, thank you for the information.
|
David R. |
Why am I able to write an application on 1.8 using
the android_1.8.jar (whatever its called) and compile it and run it on
device using 2.3.
|
Nov 3 | 4:25 PM |
Mark M. |
there is no 1.8
|
David R. |
Thats why I figured I could mod the firmware and just have them include it.
|
David R. |
1.6
|
Mark M. |
android.jar is not the firmware
|
Mark M. |
android.jar is just a bunch of stubs
|
Mark M. |
enough to allow you to compile
|
Mark M. |
and no real logic
|
Mark M. |
the real implementation lives on the device
|
David R. |
Ah
|
David R. |
Okay that makes sense.
|
Mark M. |
as to why you can specify one Android release as
the build target and run on others, it's because Android is (generally)
forwards and backwards compatible
|
David R. |
Makes sense
|
Nov 3 | 4:30 PM |
Mark M. |
again, if anyone has any questions, just chime in
|
Nov 3 | 4:40 PM |
Filbert |
i know RTSP is natively supported on android, as is supposedly HLS
|
Filbert |
any idea where i can find more specifics about those implementations?
|
Mark M. |
never heard of HLS
|
Mark M. |
there isn't much documented about "implementations" per se
|
Filbert |
[Apple] Http live streaming
|
Mark M. |
ah, ok
|
Filbert |
hmm
|
Mark M. |
never saw the acronym before
|
Mark M. |
yes, that's in there somewhere
|
Mark M. | |
Mark M. |
that's the sum total of the formal documentation, outside of JavaDocs
|
Mark M. |
actually, there's http://developer.android.com/guide/topics/… too, but it doesn't get into formats much
|
Filbert |
i've seen that stuff... it's pretty unspecific
|
Mark M. |
yup
|
Mark M. |
I'd almost call it anti-specific :-)
|
Nov 3 | 4:45 PM |
Filbert |
but we're having no luck making those technologies work with our CDN's Wowza media server
|
Filbert |
*sigh*
|
David R. |
Do you ever plan on selling printed copies of your books?
|
Mark M. |
David: the Advanced Android and Tutorials books are in print
|
Mark M. |
in fact, recently updated
|
Mark M. |
the Tuning book will see print when it hits 1.0 (1st Edition)
|
David R. |
Really? When/Where can I buy a hard copy?
|
Mark M. |
the original The Busy Coder's Guide to Android Development *has* been in print as _Beginning Android_ from Apress
|
Mark M. |
they're available in your favorite online bookstore, particularly ones named after large South American rivers
|
Mark M. |
anyway, _Beginning Android_ and I are parting ways after this summer's _Beginning Android 3_
|
Mark M. |
due to contractual limitations, I will be unable
to return _The Busy Coder's Guide to Android Development_ to print
myself, though
|
David R. |
A new version of it eh?
|
Mark M. |
a new version of what?
|
David R. |
You said _Beginning Android and you are parting ways.
|
Mark M. |
ah
|
David R. |
Figured you were writing a different copy or something.
|
Mark M. |
yes, they will be updating it to _Beginning Android 4_
|
Mark M. |
*I* won't be updating it to _Beginning Android 4_
|
Mark M. |
they basically demanded that the book be done by around Thanksgiving, and we might not even have ICS hardware by then
|
David R. |
Yeah its pretty lame.
|
David R. |
Thats the only thing I dislike about android..
|
David R. |
All the different versions and lack of support on phones.
|
Nov 3 | 4:50 PM |
David R. |
I think my Evo is still running 2.2
|
Nov 3 | 5:00 PM |
Mark M. |
OK, that's it for today's chat
|
Mark M. |
next one 10am Eastern Tuesday
|
Mark M. |
have a pleasant day, all!
|
Filbert | has left the room |
David R. | has left the room |
Mark M. | turned off guest access |