Open GoogleCodeExporter opened 9 years ago
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
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:
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
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 phaseb...@phaseburn.net
on 1 Sep 2010 at 10:54
@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
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
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.mllns@gmail.com
on 4 Sep 2010 at 12:31
> 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
Issue 129 has been merged into this issue.
Original comment by JAguirre1231
on 4 Sep 2010 at 11:24
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
I agree with comment 10
Original comment by fpadi...@gmail.com
on 9 Sep 2010 at 3:40
Original issue reported on code.google.com by
BUGabu...@gmail.com
on 1 Sep 2010 at 12:21