> 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! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
