Your answer is Specificity
Specificity is a mechanism within the CSS cascade that aids conflict resolution
Basically it determines preference of CSS styles, over and above the cascading nature of stylesheets
Order of Precedence of Specificity:
| Type | Specificity |
|---|---|
| Inline Style | Highest |
| Highest Number of #id selectors | Wins |
| Highest number of class, attribute and pseudo selectors | Wins |
| Highest Number of element selectors | Wins |
Check available android platforms
android list targets
Start a Project
android create project --target <target_id> --name <appName>
target_id – is the target available in android list targets
Build the project
ant debug
you may need to install apache ant
Compile?
adb install bin/Package_Name-debug.apk
Emulate (Need a virtual device manager)
android avd
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren’t special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one– and preferably only one –obvious way to do it.
Although that way may not be obvious at first unless you’re Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it’s a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea — let’s do more of those!
Source: python.org