Fresh Android SDK version: m5-rc14

Supervised News & Rumors concerning the Google Android Platform.

Postby res » Fri Feb 15, 2008 9:03 pm

plusminus have you given any thought into setting up a wiki?

Updating the SDK is a perfect example, while the documentation provided by Google is nice it doesn't cover everything. For example many of the methods have been changed but their is no simple way to check what they have been changed too. We could have a page listing methods for m3 and what the names have been changed to for m5. Possibly updating this in the future if m6/m7 is released.

edit: a lot of people wont actually read all the documentation so when they go to compile their source with m5 it throws up lots of errors and they will have no idea why.
res
Senior Developer
Senior Developer
 
Posts: 146
Joined: Tue Nov 20, 2007 8:14 pm
Location: United States

Top

Postby plusminus » Sat Feb 16, 2008 3:08 pm

Hello res,

Google already got two pages on what changed/added and what was removed:

http://code.google.com/android/migratin ... anges.html

and

http://code.google.com/android/migratin ... anges.html

Regards,
plusminus
Image
Image | Android Development Community / Tutorials
User avatar
plusminus
Site Admin
Site Admin
 
Posts: 2688
Joined: Wed Nov 14, 2007 8:37 pm
Location: Schriesheim, Germany

Postby res » Sat Feb 16, 2008 11:27 pm

True but these pages list the new method names their is no mention of the OLD method names.

As an example search either page for onMotionEvent and their is no results, this was the old method used to get touch screen input however it has since been renamed. To find the new method name you need to revisit the
View documentation for example and read through all the methods to find out what it has been changed to.

It would be nice to have a single page displaying old and new method names ie. onMotionEvent --> onTouchEvent
res
Senior Developer
Senior Developer
 
Posts: 146
Joined: Tue Nov 20, 2007 8:14 pm
Location: United States

Postby plusminus » Sun Feb 17, 2008 1:17 pm

Hello res,

when you visit the second link, deleted things are [s]striked-through[/s], like:
onMotionEvent
type [s](MotionEvent)[/s] in android.view.View
type [s](MotionEvent)[/s] in android.widget.Button
type [s](MotionEvent)[/s] in android.widget.EditText
type [s](MotionEvent)[/s] in android.widget.ImageButton
type [s](MotionEvent)[/s] in android.widget.ScrollView


and when you click it you'll get:
boolean onMotionEvent(MotionEvent)............Renamed android.view.View.onTouchEvent(android.view.MotionEvent).


It does what you were suggesting ... :|

Regards,
plusminus
Image
Image | Android Development Community / Tutorials
User avatar
plusminus
Site Admin
Site Admin
 
Posts: 2688
Joined: Wed Nov 14, 2007 8:37 pm
Location: Schriesheim, Germany

Postby plusminus » Sun Feb 17, 2008 3:28 pm

tum0rc0re wrote:.... (( Btw, funny feature is a jalousie (if everybody doesn't know click main title) :)
Image Image
...


Just found out, why this jalousie exists. Missed Calls are placed in there ^^

Regards,
plusminus
Image
Image | Android Development Community / Tutorials
User avatar
plusminus
Site Admin
Site Admin
 
Posts: 2688
Joined: Wed Nov 14, 2007 8:37 pm
Location: Schriesheim, Germany

Postby res » Sun Feb 17, 2008 6:22 pm

plusminus wrote:Hello res,

when you visit the second link, deleted things are [s]striked-through[/s], like:
onMotionEvent
type [s](MotionEvent)[/s] in android.view.View
type [s](MotionEvent)[/s] in android.widget.Button
type [s](MotionEvent)[/s] in android.widget.EditText
type [s](MotionEvent)[/s] in android.widget.ImageButton
type [s](MotionEvent)[/s] in android.widget.ScrollView


and when you click it you'll get:
boolean onMotionEvent(MotionEvent)............Renamed android.view.View.onTouchEvent(android.view.MotionEvent).


It does what you were suggesting ... :|

Regards,
plusminus


Ah so it does, wonder why I didn't see that earlier :(
res
Senior Developer
Senior Developer
 
Posts: 146
Joined: Tue Nov 20, 2007 8:14 pm
Location: United States

Top

Postby Shepherd » Mon Feb 18, 2008 11:44 am

Did someone notice changes in AndroidManifest.xml?

Examples that were build with old plug-in are not compatible with the new one. It is asking for different attributes defined in AndroidManifest.xml.
Shepherd
Freshman
Freshman
 
Posts: 8
Joined: Thu Feb 14, 2008 11:44 pm

Postby Shepherd » Mon Feb 18, 2008 12:00 pm

And there is that annoying:

Application error:
com.google.android.gtalkservice.....etc

Like system is trying to initialize gtalkservice and every 30 seconds or so, trows this error message. I assume there is a setting sort of, that turn this initialization off. But I can't find one.

Does anyone know how to fix this, it's very annoying and slowdown my productivity :D .
Shepherd
Freshman
Freshman
 
Posts: 8
Joined: Thu Feb 14, 2008 11:44 pm

Postby plusminus » Mon Feb 18, 2008 12:17 pm

Shepherd wrote:Did someone notice changes in AndroidManifest.xml?

Examples that were build with old plug-in are not compatible with the new one. It is asking for different attributes defined in AndroidManifest.xml.

Hello Shepard,

changes to the AndroidManifest.xml are listed here: :arrow: viewtopic.php?t=879

Regards,
plusminus
Image
Image | Android Development Community / Tutorials
User avatar
plusminus
Site Admin
Site Admin
 
Posts: 2688
Joined: Wed Nov 14, 2007 8:37 pm
Location: Schriesheim, Germany

Postby Shepherd » Mon Feb 18, 2008 10:01 pm

Sorry, I didn't see that topic.
Aj, pa u zdravlju se videli!
Shepherd
Freshman
Freshman
 
Posts: 8
Joined: Thu Feb 14, 2008 11:44 pm

Top
Previous

Return to News & Rumors

Who is online

Users browsing this forum: Yahoo [Bot] and 1 guest