See Compatibility Zoom. Only since Android 3.2, though.
But I think you're better off fixing your fundamental problem, which is an
inflexible layout.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
I have an iPhone app that needs conversion to Android ASAP.
And just plain (attempts of) ports/conversions of iPhone apps into Android
apps don't work. You will get a lousy rating on the Market. No one will use
it or want to use it.
And using an AbsoluteLayout to do so, is setting yourself up
Am I a naughty boy for wanting to use AbsoluteLayout?
Not if you need it... do you *really* need it or will RelativeLayout work
better?
Here is a good article discussing this topic...
http://developer.android.com/resources/articles/layout-tricks-efficiency.html
Also, is there a way to make
Once you publish the app on the Android Market you will get complaints
from people who have devices with other screen resolutions. Then you
can go back to Eclipse and see exactly where the problems are since
those classes are crossed out.
To prevent these complaints read
Drag and drop can be implemented without AbsoluteLayout. You can see
how in Launcher's source code at source.android.com
(packages/apps/Launcher.)
On Sat, Jun 13, 2009 at 7:59 PM, Mooretisgregory.mo...@lifeaware.net wrote:
I noticed that AbsoluteLayout is deprecated in the latest SDK.
Dianne, with all due respect, I'm with Mark on this one.
The only reasonable thing for a developer to do at this point is
abandon the deprecated classes as quickly as possible. Google's track
record with Android releases proves that they can and will spin on a
dime without giving much notice as
check out my simple example at http://developreality.blogspot.com/
it's my blog, and i have a post on doing just that...
good luck
On May 4, 5:34 am, 6real xirgon...@gmail.com wrote:
Hello,
could someone give a simple example to replace an AbsoluteLayout with
Frame and Relative Layout ?
Your blog post is full of misunderstandings. First of all, using
margins *does* work for what you want with a FrameLayout. You used a
LinearLayout and as a result your views are much bigger than they need
to be and it's probably much more expensive that it needs to be.
Second of all, you should
I'll say again: we are not going to remove AbsoluteLayout from a future
release, but we strongly discourage people from using it.
If you choose to not believe me, you are welcome to, but I am not
responsible for you making that decision.
On Mon, May 4, 2009 at 1:00 PM, Mike
Thanks for the input, I am very new at this UI thing so it makes sense
that there are some mistakes there, however, I have tried basing my
directions on trial and error and answers I got in this group, for
example, the use of framelayout was recommended in this group and
that's why I tried it,
Great thinking here.
I have a highly rated app that simply... could... not... be...
written... without AbsoluteLayout, no matter whose Java sensibilities
it steps on. I guess Android's doing so well with apps that it can
afford to shut down an entire category of games.
Oh well. Glad I got it in
Sundog wrote:
I have a highly rated app that simply... could... not... be...
written... without AbsoluteLayout
Hogwash!
AbsoluteLayout is written in Java. You can find it on Google Code Search.
Ergo, it is possible to create an application that works exactly as
yours does that does not use
On Mon, May 4, 2009 at 10:00 AM, Sundog sunns...@gmail.com wrote:
I have a highly rated app that simply... could... not... be...
written... without AbsoluteLayout, no matter whose Java sensibilities
it steps on. I guess Android's doing so well with apps that it can
afford to shut down an
I managed to overcome it - take a look at
http://developreality.blogspot.com/2009/05/overcoming-absolutelayout-deprecation.html
On May 4, 3:16 pm, Dianne Hackborn hack...@android.com wrote:
On Mon, May 4, 2009 at 10:00 AM, Sundog sunns...@gmail.com wrote:
I have a highly rated app that
Dianne Hackborn wrote:
Did AbsoluteLayout disappear from 1.5? No. Are you unable to write 1.5
apps using it? No. Have we ever said we have any plan to completely
remove it at any point in the future? No.
AbsoluteLayout is flagged as deprecated in Android 1.5. As far as we out
here are
On Mon, May 4, 2009 at 12:36 PM, Mark Murphy mmur...@commonsware.comwrote:
AbsoluteLayout is flagged as deprecated in Android 1.5. As far as we out
here are concerned, that means we gotta abandon the class or clone and
maintain our own copy, and do either of those very very quickly.
Why?
Dianne Hackborn wrote:
We've said repeatedly that we won't be (intentionally) breaking old
applications. Removing a major API like this would be a huge breakage.
It won't happen.
Good to know! In other projects, flagging something as deprecated means
it is going bye-bye within a release or
17 matches
Mail list logo
