Interesting and useful site 4u

by d k » Tue, 06 Jan 2009 11:19:50 GMT


Sponsored Links
 *JOBS IN VARIOUS FIELDS 4U < http://jobsinvariousfield.blogspot.com/> ;*

*
< http://ftvbeautymodels.blogspot.com/> ;*

--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Other Threads

1. Making Android development more enjoyable

Hello all

I'm sorry if some of these things have been mentioned before, but I just
joined this list today.


Here's some things Google should look into:

0. Include android market in the emulator/test environment

That should be fast and easy to do.

1. Try finding some ways to speed up the compile/test cycle:

a) Avoid moving too much stuff arround
Currently every time an .apk file must be produced (compressed) on the
developers machine, containing all the code and application resources. This
apk that contains everything is then transferred to the phone or emu. It's
then unpacked on the phone and the install procedure is run. It doesn't
matter if you just changed one class file, the whole thing is moved around.

I understand that permissions are managed during the install process, but
this could be solved in some other way like trusting the code for that app
by default.

b) Make the test environment run in native code during the development
process
I know that using an emulator was a nice and fast solution for you, but a
lot of time and energy is lost on emulating ARM. Davlik runs on x86, and all
other code also. Why don't we just make a jailed/chrooted native environment
for testing available? I know that this is not a straightforward thing to
implement on Windows, and there might be difficulties making this run on Mac
OSX, but it's really worth it.



2. Improve the visual layout editor.

There's so many ways this could be improved, but making it faster/more
intuitive is the general idea.

One quick suggestion: Try making it easier to jump to respective code
implementations or have an option to generate event handlers etc. code if no
code referencing that UI object is found.

Example of a great code editor/UI designer integration is Borland Delphi.
Even really old versions have ease of use that Android developers could only
dream of. Android API is more abstract and UIs have relative layouts, but
most of the great concepts from Delphi still apply.

Item 1 b) could also create possibilities for the UI designer tool.

There's a blog post with the content of this mail at
http://vrodic.blogspot.com/2010/07/making-android-development-more.html

-- 

2. Jual motorola cliq/dext. Full set tmobile unlocked.

Mau ikut jualan cliq nya nih. Buka harga 3jt. Silahkan ditawar
tipisss. Masih 95% keadaannya. Dus buku charger lengkap, tanpa headset
(ilang). Tapi jack udah 3.5mm. Jadi ga masalah. Imei sama dengan box,
semua fungsi normal banget. Hubungi langsung kalo minat 08157118207
(brian).

Thanks.

Gambar asli bisa diliat di forum sebelah.
Link : http://www.kaskus.us/showthread.php?p=244305751#post244305751

-- 
"Indonesian Android Community [id-android]" 

3. Resource folders and scaling

4. Don't see YouTube thumbnails anymore on Froyo

5. Using an AsyncTask instead of a Service in a BroadcastReceiver or AppWidget

6. Best Approach to implementing Polling in Android

7. Best Approach to implementing Polling in Android