Right, and unlike some of the other posters who seemed to have a slight more agitated tone, I really tried to emphasize that I want to get on board with respect to this particular issue. I'm not complaining about AbsoluteLayout's deprecation at all, I just want to write my code correctly, and if AbsoluteLayout is not the recommended way to place one view at an arbitrary location on top of another view, I was just wondering what *is* the recommended way. I was getting confused because some places said FrameLayout and RelativeLayout were the solution, but other places were very clear that they weren't the best solution. I had also seen the suggestions of rolling a layout manager on my own...I was just...a little unsteady about that.
I'll look into making my own layout manager. Please consider how confusing this is for those of us not already in the know. For example, I would assume this consists of writing my own layout class, something akin to AbsoluteLayout or LinearLayout, etc. The funny thing, which I find very confusing, is that none of those are actually subclasses of Layout! They subclass ViewGroup, while Layout is some other class which doesn't seem to have any direct connection to the existing Layouts. Thus my impending confusion. I'll do some research on layout managers on my own first, the pointer in that direction was sufficient, thank you...I'm just asking that you please realize the apparent discrepancy in terminology which I find confusing. Cheers! On May 13, 11:05 pm, Romain Guy <[email protected]> wrote: > Again, AbsoluteLayout was deprecated to encourage developers to use > "real" layout managers. AbsoluteLayout just won't work with other > screen resolutions and densities. Like Dianne said, it won't go away > but we want you guys to think very hard before using it. It is (most > of the time) bad practice and will only come back to haunt you in the > future. > > > > On Wed, May 13, 2009 at 11:00 PM, Mark Murphy <[email protected]> wrote: > > >> I believe I have politely and thoroughly stated my question. Anyone > >> have an answer? > > > Everybody, even to an extent the core Android team folk on this list, is > > contributing answers on a volunteer basis. Lots of questions get asked > > here that do not get answered, for any number of reasons. > > > Also, bear in mind that you sent your question less than 24 hours ago. Not > > everybody monitors this list continuously. If you need answers in that > > short of a timeframe, hire a consultant. > > > I have watched your thread since its inception. I did not reply at first, > > because you seemed set on having a core Android team member answer, and I > > am not such a person. However, since your focus now seems to be on getting > > some sort of answer from anyone, here's my take on it: > > >>> > I have seen a number of threads discussing the deprecation > >>> ofAbsoluteLayout. I'm a little fearful of reading third-party blogs > >>> > that suggest solutions to the deprecation because in some discussion > >>> > threads the Google employees have explicitly said the blogs contain > >>> > misunderstandings or inaccuracies. > > > According to Ms. Hackborn's most recent(?) post on the topic, while > > AbsoluteLayout is deprecated, it is not going away. Strategically, I > > suppose that means no new code should be built that relies upon > > AbsoluteLayout, but there is no need for a massive rush to the exits to > > abandon AbsoluteLayout for existing code. > > > Personally, if I were in your shoes, I would aim to eliminate my > > dependency on AbsoluteLayout in the next few months. Note that "eliminate > > the dependency on AbsoluteLayout" could be simply a mental bookmark that, > > should AbsoluteLayout ever be truly removed from the platform, that you > > will be willing and able to maintain AbsoluteLayout yourself, based on the > > last implementation found in the Android open source project. > > > But, again, Ms. Hackborn has indicated AbsoluteLayout is not going away, > > and so you may elect to not worry about this issue in the near term. > > >>> > So, I need to know how to implement my app's behavior > >>> withoutAbsoluteLayout. I would greatly appreciate any input people > >>> might > >>> > have, especially the real pros, the Android dev team who, by > >>> > deprecatingAbsoluteLayout, must have a clear picture in their heads > >>> > of how to reorganize code to be up-to-date to achieve the same > >>> > functionality. Romain Guy, Diane Hackborn, I'm looking your > >>> > direction. :-) > > > I believe both of them, in related threads, indicated that the solution is > > to create your own layout manager, rather than use AbsoluteLayout or > > RelativeLayout or any of the other built-in ones. > > > Unfortunately, I am unaware of any tutorials on exactly how to do this. > > You can probably examine the source of some of the existing layout > > managers to see how they do what they do. > > > -- > > Mark Murphy (a Commons Guy) > >http://commonsware.com > > _The Busy Coder's Guide to Android Development_ Version 2.0 Available! > > -- > Romain Guy > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time > to provide private support. All such questions should be posted on > public forums, where I and others can see and answer them --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
