What is the concept behind R.java?
In android R.java is used to provide access to resources defined in XML files.
To access the resource we need to invoke findViewById() method passing in the id of the resource to be fetched.
This is similar to Spring where beans are defined in a XML context and are fetched by using application context. context.getBean("beanId")
This provides loose coupling since the beans are defined externally and could be changed without making modifications to the code.
This has me confused. Though what Android does looks similar to spring, what advantage does it offer?
- What is the point of having an intermediate R.java anyway? Couldn't we just acquire resources directly from XML by use of a resource reader/application context. e.g.
findViewById("resourceId")- There isn't any loose coupling. Since references in R.java get auto-generated how could one delete a resource and put in a new one?
- What design pattern does it follow(if there is one)?
- Wouldn't it be better to have resources injected using IOC (like Roboguice)? Why did then google decide to give us such a wierd way of working with resources?
Pardon my ignorance. I'm a newbie Java developer trying too many things at once. :-) Thanks for all the feedback.
Answer
Biggest advantage is in Localization and Providing alternate resources for different screen sizes.
e.g you can have a String resource R.string.myname this could be a defined in english in /values-en/strings.xml and in spanish in /values-es/strings.xml
System will take care or picking up the right file depending on the locale you just need to use @string/myname in your layout file or R.string.myname in your code.
Similarly you could have two layout files for portrait and landscape defined in
res/layout/mylayout.xml
res/layout-land/mylayout.xml
In your code you will just specify R.layout.mylayout to inflate the layout. Resource manager picks up the file in layout-land if the device is in landscape mode.
Doing this manually would be a nightmare -- hence the need for R file