Thanks for your answer... Yes, copying the source code will be the worse case but how about the future changes and improvements to these components? The change management will be a headache.
After all, why is it so? Almost all components are skinnable... why not these ones? Does this mean that one can not develop a complete new theme (just theme!) for all components of Android? One has to pack some specific components as well. FYI, AlertDialog's button-bar has the same problem. I had to make my own AlertDialog derived directly from Dialog and do all the tricks there. Dialog themes are not automatically affected by the theme you set in AndroidManifest.xml. Best Regards, Armond > -----Original Message----- > From: [email protected] [mailto:android- > [email protected]] On Behalf Of Yusuf Saib (T-Mobile USA) > Sent: Tuesday, September 08, 2009 11:49 PM > > > You could always roll you own skinnable version, borrowing from the > original source code. > > > Yusuf Saib > Android > ·T· · ·Mobile· stick together > The views, opinions and statements in this email are those of the > author solely in their individual capacity, and do not necessarily > represent those of T-Mobile USA, Inc. > > > > On Sep 8, 11:28 am, "Armond Avanes" <[email protected]> wrote: > > Hi Guys, > > > > Is it just me or Android theme-ing system does not allow to set a theme > for > > DatePicker and TimePicker? Searching "themes.xml" and "styles.xml" in > > Android source code (v1.5), I couldn't find anything related to these > two > > components! > > > > Aren't they really skinable? > > > > Cheersss, > > Armond > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
