Freepine wrote: > For example, maybe we can introduce DI on some > selected root entities of aggregates, which I don't believe it will be > at the expense of a considerable performance hit. Sorry I couldn't give > more specific hints on concrete classes for I am not very familiar with > view or activity related Java classes.
You will note that neither Java-the-language nor "distros" like JavaSE offer DI built into the environment. Rather, DI is supplied by third-party JARs, whether it is Spring for general-purpose DI or the DI mechanisms offered by rich client frameworks. Hence, rather than trying to convince us that the core Android team ought to build DI into Android, why not build DI yourself? Code is more compelling than words in situations like this. -- Mark Murphy (a Commons Guy) http://commonsware.com Android Training on the Ranch! -- Mar 16-20, 2009 http://www.bignerdranch.com/schedule.shtml --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
