android Programming Glossary: coupling
Best way to accomplish inter-activity communication in an Android TabHost application http://stackoverflow.com/questions/1162659/best-way-to-accomplish-inter-activity-communication-in-an-android-tabhost-applic getParent .getNearbyMatches This adds an element of strong coupling that I'm not entirely thrilled with but from a performance standpoint..
Android - Tabs, MapView, activities within tabs http://stackoverflow.com/questions/1590340/android-tabs-mapview-activities-within-tabs Map and in the individual lists. We really like the loose coupling this provides us we just give a VIEW command and the URI to.. try to switch out the views etc. etc. as well as strongly coupling our program in a way we don't want. Any suggestions on a way.. try to switch out the views etc. etc. as well as strongly coupling our program in a way we don't want. This doesn't follow at all..
Communicate with Activity from Service (LocalService) - Android Best Practices http://stackoverflow.com/questions/4908267/communicate-with-activity-from-service-localservice-android-best-practices I wouldn't. Use the loosest possible coupling you can stand. Hence on average aim for the command pattern..
Android Performance - 'Avoid Internal Getters/Setters' http://stackoverflow.com/questions/6716442/android-performance-avoid-internal-getters-setters other areas e.g. preserving encapsulation reducing harmful coupling making your code more maintainable and so on. So it is generally..
Android: How to declare global variables? http://stackoverflow.com/questions/708012/android-how-to-declare-global-variables abstract or interface classes Inability to subclass High coupling across the application difficult to modify Difficult to test..
Best way to accomplish inter-activity communication in an Android TabHost application http://stackoverflow.com/questions/1162659/best-way-to-accomplish-inter-activity-communication-in-an-android-tabhost-applic custom function in the parent activity like so MainActivity getParent .getNearbyMatches This adds an element of strong coupling that I'm not entirely thrilled with but from a performance standpoint it's much better than it was. I appreciate the answers..
Android - Tabs, MapView, activities within tabs http://stackoverflow.com/questions/1590340/android-tabs-mapview-activities-within-tabs shows the object. The same mechanism is at work both in the Map and in the individual lists. We really like the loose coupling this provides us we just give a VIEW command and the URI to the person place event and it automatically brings us to the.. to do a LOT of housekeeping to intercept all the back events try to switch out the views etc. etc. as well as strongly coupling our program in a way we don't want. Any suggestions on a way forward would be extremely appreciated. We're new to Android.. to do a LOT of housekeeping to intercept all the back events try to switch out the views etc. etc. as well as strongly coupling our program in a way we don't want. This doesn't follow at all from what you wrote previously. Your back events will not..
Communicate with Activity from Service (LocalService) - Android Best Practices http://stackoverflow.com/questions/4908267/communicate-with-activity-from-service-localservice-android-best-practices http developer.android.com reference android app Service.html#LocalServiceSample I wouldn't. Use the loosest possible coupling you can stand. Hence on average aim for the command pattern with startService instead of the binding pattern with bindService..
Android Performance - 'Avoid Internal Getters/Setters' http://stackoverflow.com/questions/6716442/android-performance-avoid-internal-getters-setters case the getters and setters have significant benefits in other areas e.g. preserving encapsulation reducing harmful coupling making your code more maintainable and so on. So it is generally regarded as best practice to use getters and setters despite..
Android: How to declare global variables? http://stackoverflow.com/questions/708012/android-how-to-declare-global-variables as stolen from the StackExchange link Inability to use abstract or interface classes Inability to subclass High coupling across the application difficult to modify Difficult to test can't fake mock in unit tests Difficult to parallelize in the..
|