In any event I have managed to achieve what I want without using the XML > method - by playing around with some of the class methods. The key methods > for making it work were setGravity(), > SetHorizontalGravity(),setVerticalGravity(),setLayoutParams() and > setPadding(). The text in the TextView (the initial list of items) kept > disappearing so I accessed it using getChildAt() and then set the layout > for it as well as the padding and font size. > That sounds like a whole lot of work and a royal PITA... I highly recommend defining layouts in XML. I've never had to deal with stuff like that.
Thanks, Justin Anderson MagouyaWare Developer http://sites.google.com/site/magouyaware On Wed, Sep 5, 2012 at 5:30 AM, Larry Meadors <larry.mead...@gmail.com>wrote: > Get used to the xml, really. You'll kick yourself if you coffee it all in > Java. > On Sep 4, 2012 11:37 PM, "Ravin" <rperi...@yahoo.com> wrote: > >> Thanks for the insight Justin - yes it feels strange to use XML for me >> - should try getting used to it. In any event I have managed to achieve >> what I want without using the XML method - by playing around with some of >> the class methods. The key methods for making it work were setGravity(), >> SetHorizontalGravity(),setVerticalGravity(),setLayoutParams() and >> setPadding(). The text in the TextView (the initial list of items) kept >> disappearing so I accessed it using getChildAt() and then set the layout >> for it as well as the padding and font size. >> >> On Tuesday, September 4, 2012 9:52:50 AM UTC-7, MagouyaWare wrote: >>> >>> Thanks for the replies. I will try what laminina has suggested. No I'm >>>> not opposed to specifying the layout in XML - I guess since any s/w I have >>>> written in the past for other GUI based systems such as WIndows has been >>>> based on instantiating objects at runtime I have been avoiding the XML >>>> layout method. I will try that too as an alternative. >>>> >>> >>> I had hesitations using XML when I first started developing for Android >>> but now I find that it is many times easier in most cases. Doing UI in >>> code now is the exception rather than the norm for me now... >>> >>> Thanks, >>> Justin Anderson >>> MagouyaWare Developer >>> http://sites.google.com/site/**magouyaware<http://sites.google.com/site/magouyaware> >>> >>> >>> On Tue, Sep 4, 2012 at 10:43 AM, Ravin <rper...@yahoo.com> wrote: >>> >>>> Thanks for the replies. I will try what laminina has suggested. No I'm >>>> not opposed to specifying the layout in XML - I guess since any s/w I have >>>> written in the past for other GUI based systems such as WIndows has been >>>> based on instantiating objects at runtime I have been avoiding the XML >>>> layout method. I will try that too as an alternative. >>> >>> >>> -- >> You received this message because you are subscribed to the Google >> Groups "Android Developers" group. >> To post to this group, send email to android-developers@googlegroups.com >> To unsubscribe from this group, send email to >> android-developers+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/android-developers?hl=en > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
