desktops as overlay

[GoogleCodeExporter]

Type a detailed description about your request
basically copy quickdesk app, and add more desktops to it.
use double tap in home to put the same desktops (default home or another 
number) or a totally different desktop set in Overlay to the current open app, 
without going to Desktop that are in background or leaving the app.

Attach mock-ups/screenshots if you can.
http://www.appbrain.com/app/sg.ruqqq.quickdesk

Original issue reported on code.google.com by BUGabu...@gmail.com on 1 Sep 2010 at 12:21

[GoogleCodeExporter]

I love this idea, @BUGabundo, did you also contact the quickdesk developer? 
Maybe he/she/they could implement more 'screens' into quickdesk.

Original comment by b...@bdeferme.net on 1 Sep 2010 at 12:42

[GoogleCodeExporter]

I'd like to see something very light, like the 4-6 most used apps. Laucher Pro 
Beta does this quite well, you just stay a bit longer on the home button (it 
does vibrate two times) and you see your last 6 launched apps.

Ah, and arrange the icons in a quarter circular way, so can easily reach with 
the thumb. See the attachment for a rough sketch.

Original comment by mathias....@gmail.com on 1 Sep 2010 at 4:08

Attachments:

• device.jpg

[GoogleCodeExporter]

mathias please file another bug for that and stop spamming mine :P
we already have awesome control of last open apps in CM

Original comment by BUGabu...@gmail.com on 1 Sep 2010 at 10:46

[GoogleCodeExporter]

I like the idea Mathias presented, merged with yours, BUG... a quick overlay 
that's customizable similar to quickdesk, built into the launcher itself...

Original comment by phaseburn@phaseburn.net on 1 Sep 2010 at 10:54

[GoogleCodeExporter]

@BUGabundo
I'm sorry … it was mainly an _idea_ how to arrange the icons (for lazy 
thumbs). I agree the input about the last used apps is redundant. IMO android 
is lacking of "fancy" design … ;-)

Original comment by mathias....@gmail.com on 2 Sep 2010 at 5:57

[GoogleCodeExporter]

Big problem: memory.

Each android app is limited to a small chunk of ram... users with 7 desktop 
screens filled with widgets (even with density hacks, more columns, rows, 
shirtcuts,etc) usually suffer OOM fcs....

Now imagine if we add inside the same app another X "overlay" screens to the 
user....

Option 1: Destroy all the "real" launcher's memory (widgets, etc) each time the 
user leave the app so we have memory to possibly open the "overlayed" launcher. 
So returning to the real launcher will reload it from scratch....

Option 2: Similar than the previous one but just release all the "real" 
launcher memory if the user loads the "overlayed" one... So opening the 
overlayed one would be slow as hell.

Option 3: Make the "overlayed" launcher very limited/trimmed down so it doesn't 
hog memory.

Option 4: make it into a separate app. Or even better, use already other great 
apps like powerstrip/quickdesk.

So..... you know.

Original comment by ander...@gmail.com on 2 Sep 2010 at 11:53

• Added labels: Priority-Low

[GoogleCodeExporter]

What if it's not necessarily a whole new overlay?  Is there a way to take 
advantage of the resources already in memory for the launcher and just, for 
example, open our desktop but in an overlay mode where it doesn't quit the 
current app?

Or, for example, the ability to open your app drawer in an overlay with a long 
press of the search button or double tap home or whatever.

If that's possible then that's where it would be advantageous to use an ADW 
implentation of overlays as opposed to just using quickdesk or whatever because 
it would actually conserve memory.

That app drawer accessible from anywhere sounds pretty cool, actually.  I don't 
use quickdesk because it's too slow to pull up on my myTouch 3G.  But I do 
"keep home in memory" and if it's possible to take advantage of those resources 
then I think this could be a brilliant feature.

But if it's not possible to use the already allocated resources then I really 
don't think there's a reason to pull these features into ADW.

Original comment by mtt.ml...@gmail.com on 4 Sep 2010 at 12:31

[GoogleCodeExporter]

> open our desktop but in an overlay mode where it doesn't quit the current app

YES YES YES 
thats what i'm asking too (sure would be nice to be able to choose another 
desktop

Original comment by BUGabu...@gmail.com on 4 Sep 2010 at 1:25

[GoogleCodeExporter]

Issue 129 has been merged into this issue.

Original comment by JAguirre1231 on 4 Sep 2010 at 11:24

[GoogleCodeExporter]

Integrate the Visual Task Switcher in features ADW.Launcher will improve 
usability a lot.

Original comment by salsich...@gmail.com on 8 Sep 2010 at 6:14

[GoogleCodeExporter]

I agree with comment 10

Original comment by fpadi...@gmail.com on 9 Sep 2010 at 3:40

[GoogleCodeExporter]

It seems to me that this could be accomplished be making it so that pressing 
the back button while on the homescreen would take to the last loaded app -- 
i.e. I'm in an app, press home, then press back to go right back to that app.

Original comment by charlton...@gmail.com on 21 Oct 2010 at 12:46

[GoogleCodeExporter]

Issues 269 and 270 ("Option to allow Home button to always open default screen" 
and "Back button bindings") would effectively implement this functionally, if 
not aesthetically. To implement it aesthetically, 269, 270, and a "make home 
screen transparent" (dunno how possible that is :) and possibly a "open home 
screen X" binding (for people who want to have Home do one thing and 
double-Home or long-press search to do another) would definitely cover it all. 
Though it wouldn't be quite as pretty as something just stuck in a corner, I 
think it would get as much use.

BTW, to make clear to some of the requestors, it's unlikely that ADW can bind 
to anything other than Home, double/triple/etc-Home, and long-press Search. 
Long-pressing Home is handled by the Android OS, and that little 6-icon popup 
described as "in Launcher Pro Beta" is in fact Android, not Launcher Pro Beta.

Original comment by dbhar...@gmail.com on 21 Dec 2010 at 1:00