Feature: Option to not auto-background

[GoogleCodeExporter]

This is to request a new feature. I would like for there to be a setting in 
kirikae to make it so 
even I I have Backgrounder installed, kirikae doesn't background programs when 
switching 
apps. For 95% of my apps, it's not useful to background them, and just wastes 
memory. 
Ideally, kirikae would preserve an app's existing backgound state, and also 
would respect 
Backgrounder's Always-enabled list and background those apps, but not 
background other 
apps. Thank you.   

Original issue reported on code.google.com by adamje...@gmail.com on 19 Oct 2009 at 9:04

[GoogleCodeExporter]

An option like this would work great if a new switch appeared beside running 
apps in kirikae.  This switch 
would toggle backgrounding off or on.  It could be a user preference whether 
the toggle would be set to 
on or off by default. Additionally, if this system of switches was implemented, 
another option users should 
be given would be to have kirikae remember the state of the switch switch for 
each app from the last time 
it was run, therefor, remembering how you like your apps to run on an app to 
app basis.  

Original comment by hprid...@gmail.com on 22 Oct 2009 at 3:35

[GoogleCodeExporter]

A potential work around would be to black list every app in backgrounder except 
the
ones that you want to white list. Kirikae's method of hooking into the 
backgrounder
does seem to obey backgrounder's black and white lists.

Original comment by robert.n...@gmail.com on 7 Dec 2009 at 5:08

[GoogleCodeExporter]

I want the same functionality. I thought a "thumb tack" by the active app would 
be a helpful motif. It could 
be "tacked" if kirake were going to keep the app open and "untacked" if not 
(preferably the default tack 
state would be based on backgrounder's setting...or maybe kirake can have its 
own settings for each 
app).  The user could tap the tack to toggle its state.

now that I have kirake as my main launcher (as it includes a springboard 
tab--brilliant!),I find most of the 
time I am simply going to close my app and select another. So if the CURRENT 
app were at the bottom 
of the screen and it were easy to close and throw me in springboard, that would 
be great!

POTENTIAL SOLUTION: maybe the current app could be clearly different from 
others, being at the 
bottom separate from the "list," having the "tack" so user can quickly choose 
whether the app should 
remain open, the standard X for closing (which, like ALL OTHER X's on the 
screen, would close the app 
but stay in kirake!), AND having a little "bomb" icon (which would close the 
app and return to 
springboard). That would allow the user to do all the things s/he might want to 
do with the active app, 
AND eliminate the need for a separate two lines "Home Screen" and 
"SpringBoard"! So we would just 
have a special place for active app and its control, and a list of other active 
apps--clean!

I would donate AGAIN for this kind of functionality ;) 

Original comment by dr.aar...@gmail.com on 29 Dec 2009 at 6:52

[GoogleCodeExporter]

PS: the problem with springboard tab is that everything I 
launch there is necessarily backgrounded. The "tack" 
metaphor would make it unnecessary for kirake to assume 
that I would want anything i launch to stay backgrounded!

Perhaps there could be 3 states for the tack: untacked, 
tacked, and "lock" tacked (meaning I want this app to stay 
open not only now, but whenever it's launched). This would 
integrate control of the app in its current state as well as 
specifying the selection of "always-background" in a single 
interface!  

Original comment by dr.aar...@gmail.com on 29 Dec 2009 at 7:08

[GoogleCodeExporter]

I had another idea about how to make this interface simple and effective:

* The active app will still be at the bottom, in larger text than apps listed as
running in the background...
* On the right will be a small "x" just like all the other "x"s (clicking it 
closes
the active app without leaving kirikae)
* On the left is a big red "X" (rather like a Windows XP close button, or it 
could be
like a Mac close button of course :)). Clicking that will close the active app 
and
Kirikae (meaning, this is a shortcut to simply closing the app and returning to 
your
springboard, which is the default action the home button would do anyway!). 

It should be clear that the little "x"s are different from the big red
"X"...Alternatively, the graphic could be a little wider, showing a red "X" and 
an
arrow to a thumbnail of the springboard! So the graphic would be saying "close 
and
return to springboard"

Hope you'll consider this :)

Original comment by dr.aar...@gmail.com on 29 Dec 2009 at 10:22