Boil an egg app - step by step (step 2 – Layouts)

-

 

    After doing part 1, it’s time for coding – let’s write down the layouts used:

layouts

it’s easy to see that we have only a single layout, however – we have two:

main_layout

splash_layout

the splash layout is pretty much a nifty way to show the user something that will make him a bit excited, it’s not mandatory, but it’s really nice.

let’s review the splash screen and the main layout screen, the 2 files can be found at:

https://www.dropbox.com/sh/cieiqif3lpzip2n/gC0jqfrBR6

Basically it’s a single LinearLayout containing an ImageView with the src directed to a png file in the drawables directory called splash.

let’s review the main_layout layout:

damn! seems like a complicated layout – no, it’s not – being a long xml doesn’t make it complicated, it just means it has a lot of views.

lines 8-44 : header, intro text, and label for choosing an egg

lines 46-150 : basically the layouts for choosing an egg size buttons, buttons for choosing egg type and the start/reset buttons.

lines 152-180: the label and the TextView for the actual timer.

copy it and try to run just to follow the components using the designer, you’ll see it’s very simple.

on the next post, we’ll cover the Java parts.

Comments

Post a Comment

Popular posts from this blog

Spinner VS AutoCompleteTextView

-
Image
       We’ve all been in a situation where we needed to show a list of some sort, a list which should be triggered by a user interaction (click, tap, etc..) A list is simple enough, probably even a spinner if we don’t want to spend that much screen real-estate on showing a list which the user clicks once and probably doesn’t need to see it after that. A spinner can be a real bug once there are too much entries for the user to choose from, how much is too much? that’s a good question – probably it differs from user to user, and probably this will have some performance issues with areal large number of entries, you cannot scroll forever to find what you’re looking for. A simple solutions for the problems mentioned above is an AutoCompleteTextView. it’s a control which is basically a combination of a TextView, EditText, and a Spinner all wrapped up in a single easy to use and configurable control. let’s see how it’s done:   first, in the layout file, create an AutoCompleteTextView
Read more

How to update UI from a different thread

-
     Google has set it’s tone on some tough guidelines for developing android apps, basically there aren’t any strict rules but one very easy to misunderstand. there is a single Thread which is called the “main” thread, or “UI thread” on some places. this is the thread which is in charge on the views and interaction with the users gestures. based on the guidelines of any mobile platform at the moment, all the work that shouldn’t be done on the main thread should be done on background thread. this can be achieved in many ways, you can use AsyncTask, Or A Handler, Or a simple thread with an implementation of the   run() method within the declaration of the runnable. ok, so if I’m pulling some server data, or performing long calculations, pulling stuff from or to the Sqlite database I’ll probably use an AsyncTask. but let’s say for instance that I want to simply update the UI once every couple of seconds (update a TextView or an ImageView’s content etc..), here’s a simple example of i
Read more

Utilizing Http response cache

-
     A typical mobile application will probably consume some resources from a web server using http requests. This repeated task has some drawbacks: Bandwidth has a cost, polling the same data over and over again results in a waste of user’s quota. the responsiveness and user experience is compromised once the user keeps waiting for data. If the requested data hasn’t changed on the server, then there’s no reason for us to fetch it. Of course, local caching of data is a must, but we also need to be able to refresh the data if it has changed on the server. A simple solution which comes out of the box for API 4+ is http response caching. Http response caching is a mechanism which enables us as developers to save a footprint of the response utilizing the abilities of the Http protocol. Basically, is holds a simple cache of the response which can be defined and enabled in code, and it prevents from fetching unchanged data from the server which was already fetched and processed into t
Read more