LG dropping new silver version of the Prada phone

With over 700,000 of these babies sold its no surprise they are trying something new to see how much longer they can capitalize on this single design, and they really are truly amazing devices. Other than the external color change there is at least one internal update as well.The internal update comes in the form of some better QWERTY keyboard software, I wonder if that brings it closer to that

LG dropping new silver version of the Prada phone

With over 700,000 of these babies sold its no surprise they are trying something new to see how much longer they can capitalize on this single design, and they really are truly amazing devices. Other than the external color change there is at least one internal update as well.The internal update comes in the form of some better QWERTY keyboard software, I wonder if that brings it closer to that

Layouting Component Choices

Component Arrangement on Android is simple and we have more than one way to make the same design screen. we can use RelativeLayout, LinearLayout, or other layout. And we can combine two or more layout into one design screen.

For example, we want to desain screen as the image below:


The design screen can be expressed as below:

<?xml version="1.0" encoding="utf-8"?>
<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="fill_parent"
android:layout_height="fill_parent"
>
<TextView id="@+id/objLbl1"
android:layout_width="80sp"
android:layout_height="24sp"
android:text="Code"
/>
<EditText id="@+id/objTxt1"
android:layout_width="134sp"
android:layout_height="24sp"
android:layout_alignTop="@id/objLbl1"
android:layout_toRight="@id/objLbl1"
android:text="Edit 1"
android:singleLine="True"
/>
<TextView id="@+id/objLbl2"
android:layout_width="80sp"
android:layout_height="24sp"
android:layout_below="@id/objTxt1"
android:text="Name"
/>
<EditText id="@+id/objTxt2"
android:layout_width="134sp"
android:layout_height="24sp"
android:layout_alignTop="@id/objLbl2"
android:layout_below="@id/objTxt1"
android:layout_toRight="@id/objLbl1"
android:text="Edit 2"
android:singleLine="True"
/>
<Button id="@+id/objBtn1"
android:layout_width="80sp"
android:layout_height="24sp"
android:layout_below="@id/objTxt2"
android:text="Save"
/>
</RelativeLayout>

Or, your can replace with xml below:

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="fill_parent"
android:layout_height="fill_parent"
android:orientation="vertical"
>
<LinearLayout
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:orientation="horizontal"
>
<TextView id="@+id/objLbl1"
android:layout_width="80sp"
android:layout_height="24sp"
android:text="Code"
/>
<EditText id="@+id/objTxt1"
android:layout_width="134sp"
android:layout_height="24sp"
android:text="Edit 1"
android:singleLine="True"
/>
</LinearLayout>
<LinearLayout
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:orientation="horizontal"
>
<TextView id="@+id/objLbl2"
android:layout_width="80sp"
android:layout_height="24sp"
android:layout_below="@id/objTxt1"
android:text="Name"
/>
<EditText id="@+id/objTxt2"
android:layout_width="134sp"
android:layout_height="24sp"
android:text="Edit 2"
android:singleLine="True"
/>
</LinearLayout>
<LinearLayout
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:orientation="horizontal"
>

<Button id="@+id/objBtn1"
android:layout_width="80sp"
android:layout_height="24sp"
android:text="Save"
/>
</LinearLayout>
</LinearLayout>

Ok, have a nice try!

---

Do you want to learn more ?
Learning with sample code ?
Learning by Doing ?
Just Visit http://learncodes.googlepages.com/
and there is Android UI Design at there.

Who wants cocoa & s'mores?

It's been a busy few months. First we announced Android, then we released an early look of the Android SDK, and just last week we started accepting submissions for the Android Developer Challenge. Now that we've got things moving along, it's time to stop and smell the roses.

Our developers will be a huge part of Android's success, so we want to meet you, our colleagues. We're working on some events around the world that we hope to announce soon, but to kick things off, on the 23rd of January we'll be holding a Campfire about Android.

Join us for food, drinks, and great conversation! Come meet other developers as well as Googlers working on Android. Talk business, talk pleasure, or just hang out – it's up to you.

We'd love to see all of you there, but unfortunately space is limited. We've set up a registration page for you to sign up, so head on over and reserve your spot!

SoftBank 920SC Phone - Mobile for who love images

Softbank Mobile has released the PHOTOS 920SC slider phone that features two cameras - a 5-megapixel camera for picture taking and a 3-megapixel one for video conference. It further takes a stamp on the camera-phone market by including a xenon flash, 3X optical zoom, Bluetooth, IrDA, GPS, face recognition and auto focus capabilities. This will give its contemporaries, a run for their money.The

SoftBank 920SC Phone - Mobile for who love images

Softbank Mobile has released the PHOTOS 920SC slider phone that features two cameras - a 5-megapixel camera for picture taking and a 3-megapixel one for video conference. It further takes a stamp on the camera-phone market by including a xenon flash, 3X optical zoom, Bluetooth, IrDA, GPS, face recognition and auto focus capabilities. This will give its contemporaries, a run for their money.The

Beware of What You Read Online

I ran across an awful article on Wired magazine this morning posted by a gentlemen named Bruce Schneier. Apparently Mr. Schneier is some big wig CTO of a security services firm and author of some book that talks about security. In this article, Bruce is suggesting that your home WiFi network should be open to all and he attempted to talk down the risk by pretty much saying that you have a better chance of denying of any wrong doing by other people who have stolen your bandwidth because it is left "open" and to further support his argument, he claims that current encryption technology has its flaws, therefore its a pointless attempt to setup password encryption.

I am not a network/securities expert but I know that open networks are easy to hack and your identiy, login/password, personal files can easily be stolen. There may not be strangers driving around your house searching for your network to hack, but you never know what that neighbor's curious 12-year old may be up to. On the flip side of the argument, his suggestion of using other people's open network is equally as dangerous; your computer can also be hacked by stealing/jumping on other people's open WiFi.

I am pretty disappointed at Wired and Mr. Schneier at publishing this article and balatently asking folks not to protect their wireless networks. For a magazine of such wide reach and a voice of expertise to say this, its pretty irresponsible. The tone here is re-assuring the public that there is no need to be worried about personal identity over open WiFi... the question is, why take such risk and be concerned after you've been hacked?

See what others' think: 1, 2, 3