The Following User Says Thank You to Mentalist Traceur For This Useful Post: | ||
|
2011-09-08
, 12:59
|
|
Posts: 238 |
Thanked: 291 times |
Joined on Mar 2010
@ London, UK
|
#12
|
|
2011-09-08
, 14:21
|
Posts: 20 |
Thanked: 19 times |
Joined on Nov 2009
|
#13
|
|
2011-09-08
, 14:36
|
|
Posts: 770 |
Thanked: 558 times |
Joined on Mar 2010
@ Abidjan
|
#14
|
/usr/share/hildon-desktop/transitions.ini, on the bottom of this file you can add a row (if its not allready there) like this:
blacklist = appname1 appname2
or
whitelist = appname1 appname2
example "whitelist = osso-browser" or "blacklist = mediaplayer"
|
2011-09-08
, 15:07
|
|
Posts: 323 |
Thanked: 189 times |
Joined on Oct 2010
@ Brazil
|
#15
|
|
2011-09-11
, 13:10
|
|
Posts: 254 |
Thanked: 146 times |
Joined on Dec 2010
@ Antwerp Belgium
|
#16
|
/usr/share/hildon-desktop/transitions.ini, on the bottom of this file you can add a row (if its not allready there) like this:
blacklist = appname1 appname2
or
whitelist = appname1 appname2
example "whitelist = osso-browser" or "blacklist = mediaplayer"
|
2011-09-16
, 08:26
|
|
Posts: 548 |
Thanked: 562 times |
Joined on Aug 2011
@ Germany
|
#17
|
|
2011-09-22
, 18:48
|
|
Posts: 254 |
Thanked: 146 times |
Joined on Dec 2010
@ Antwerp Belgium
|
#18
|
I can't open the transitions.ini with leafpad or vim it doesnt show me anything??
The Following 2 Users Say Thank You to peter2p For This Useful Post: | ||
|
2011-09-26
, 16:57
|
Posts: 3,328 |
Thanked: 4,476 times |
Joined on May 2011
@ Poland
|
#19
|
|
2011-12-26
, 18:49
|
Posts: 24 |
Thanked: 5 times |
Joined on Feb 2010
|
#20
|
Anyway, back to the main point, I can understand the want for a completely unified interface, but I don't personally like a status menu applet (I really like my status menu as is, and I already hate organizing the priorities of my applets to get the optimal access to the menu options I want at any given time, adding another guaranteed-to-always-be-there system applet would just mean more fiddling... possibly every CSSU install.). At least, please make it disable-able, or uninstallable in the settings. (There really is a need to watch that you don't push too much out through the CSSU, or if you do, don't cross link them to be completely dependent on each other, preventing uninstallation.
At the same time, can't it just be put in the normal repositories, instead of being pushed with the CSSU, and at the worst, make it depend on the CSSU metapackage if it absolutely has to have some elements of the CSSU present?