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 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 entire category of
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 wrote:
> On Mon, May 4, 2009 at 10:00 AM, Sundog wrote:
> > I have a highly rated app that simply... could... not... be...
> > writt
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 wrote:
> 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?
>
> Because there's no
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 o
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 wrote:
> Hello,
>
> could someone give a simple example to replace an AbsoluteLayout with
> Frame and Relative Layout ?
>
> Example :
> I ha
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 NO
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 wrote:
>
> Dianne, w
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, but
12 matches
Mail list logo
