Definite need for a Cupcake SDK & release details.

by Romain Guy » Fri, 03 Apr 2009 16:17:03 GMT


Sponsored Links
  did not say otherwise but the best I can do right now is guide you
and help you solve your issue.

We are aware of what you're saying and we understand. Repeating it
over and over will not, unfortunately, make things happen differently.
Believe it or not, we heard you the first time. (And we were even
smart enough to think about it ourselves ;-))

I cannot, at the moment, give you more information about the SDK but
we're working hard on having one available as soon as possible.

On Fri, Apr 3, 2009 at 1:12 AM, Al Sutton <a...@funkyandroid.com> wrote:



--
Romain Guy
Android framework engineer
romain...@android.com

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

--~--~---------~--~----~------------~-------~--~----~



Definite need for a Cupcake SDK & release details.

by Al Sutton » Fri, 03 Apr 2009 16:47:43 GMT


  appreciate the responses you've given and understand you're giving it your
best efforts, but from this side of the fence we've see no movement and no
solid commitment. Surely it's not too much to ask for a nightly build of the
SDK and/or emulator images to be posted somewhere?, I'd do it myself if I
thought that my bandwidth bill wouldn't hit the roof.

Al.

-----Original Message-----
From: android-developers@googlegroups.com
[mailto:android-develop...@googlegroups.com] On Behalf Of Romain Guy
Sent: 03 April 2009 09:17
To: android-developers@googlegroups.com
Subject: [android-developers] Re: Definite need for a Cupcake SDK & release
details.


I did not say otherwise but the best I can do right now is guide you and
help you solve your issue.

We are aware of what you're saying and we understand. Repeating it over and
over will not, unfortunately, make things happen differently.
Believe it or not, we heard you the first time. (And we were even smart
enough to think about it ourselves ;-))

I cannot, at the moment, give you more information about the SDK but we're
working hard on having one available as soon as possible.

On Fri, Apr 3, 2009 at 1:12 AM, Al Sutton <a...@funkyandroid.com> wrote:
networking up.
cupcake.
cupcake.



--
Romain Guy
Android framework engineer
romain...@android.com

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




--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Definite need for a Cupcake SDK & release details.

by Mariano Kamp » Fri, 03 Apr 2009 17:01:02 GMT


 ey Al,
I actually think the keyboard layout has a nice curve to it ;-) You should
sell it as a feature.

Cheers,
Mariano

On Fri, Apr 3, 2009 at 9:58 AM, Romain Guy <romain...@google.com> wrote:


--~--~---------~--~----~------------~-------~--~----~



Definite need for a Cupcake SDK & release details.

by Al Sutton » Fri, 03 Apr 2009 17:06:15 GMT


 t's only when you scale the image down to the size of the G1 screen do you
see that although it may look nice it's really not usable so it'd guarantee
a few unpleasant comments :).

Al.

---

* Written an Android App? - List it at http://andappstore.com/ *

======
Funky Android Limited is registered in England & Wales with the
company number 6741909. The registered head office is Kemp House,
152-160 City Road, London, EC1V 2NX, UK.

The views expressed in this email are those of the author and not
necessarily those of Funky Android Limited, it's associates, or it's
subsidiaries.





_____

From: android-developers@googlegroups.com
[mailto:android-develop...@googlegroups.com] On Behalf Of Mariano Kamp
Sent: 03 April 2009 10:01
To: android-developers@googlegroups.com
Subject: [android-developers] Re: Definite need for a Cupcake SDK & release
details.


Hey Al,

I actually think the keyboard layout has a nice curve to it ;-) You should
sell it as a feature.

Cheers,
Mariano

On Fri, Apr 3, 2009 at 9:58 AM, Romain Guy <romain...@google.com> wrote:



The layout is actually working.

However, Cupcake has new assets for buttons (and other widgets) and it
happens that the minimum width of the buttons has changed. I don't
know how you set up your layout but it looks like you were relying on
that minimum size to get all the buttons aligned (which would be bad
since such a layout would break anyway on devices with different
resolutions and/or densities, but that's another topic.)


On Fri, Apr 3, 2009 at 12:50 AM, Al Sutton <a...@funkyandroid.com> wrote:
companies
people
distributors
ahead



--

Romain Guy
Android framework engineer
romain...@android.com

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









--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. Displaying already existing activities

Hello everyone,

I am trying to display activities that were already created but are
currently in the background. The problem is that I use startActivity
or startSubActivity from the current activity to display them, which
will create a new instance of the background activity. When calling
finish on this new instance, I would want all instances of that
activity to be closed, which is not the case. I could use
launchMode="singleInstance" in the manifest file, but I don't like how
the transition is done between different activities (i.e., when
starting a new activity from my single instance one, an empty screen
is displayed, then the single instance activity is displayed again for
a couple of seconds, then the new (map) activity is shown -- this only
happens when displaying a map activity). If I don't use single
instance on my original activity, the transition is done smoothly.

I tried using an approach mentioned in a previous thread, where I
first have to get the task id for the activity and use that when
trying to bring it to the foreground, but I get the same task id for
every activity that I create. Single instance would have solved that
also, but as mentioned above, I dislike the screen transition
process.

It would have been nice to be able to get a list of all existing
(background) activities and close them manually, but I don't think
it's possible.

If I call finish() write after I start a new activity, an intermediate
screen appears before showing the new activity, which I dislike also.
I am implementing the whole onActivityResult concept, but this goes to
waits (at least in my case) when more than one instance of an activity
is running, since I want all instances to be closed when one is.
Hence, exiting the application has become more cumbersome.

How can I solve this problem?

Thank you,
Mihai
--~--~---------~--~----~------------~-------~--~----~

2. Cross-fading?

Does the audio subsystem support cross-fading, or at least offer
sufficient features to implement it gracefully?
--~--~---------~--~----~------------~-------~--~----~

3. Logcat stopped working

4. Discussion on media-sample-apps

5. Updating View in a SimpleCursorAdapter

6. Notepad exercise1 - error on import line com.google.provider

7. Porting android on hardware