I cannot thank you enough for your efforts on this. The beta is working for me (I have SIP disabled so I can continue to use Total Finder as well). So far so good- hotkey switching between Spaces is working fine, no graphical issues so far.
Really- I think I speak for us all when I say how grateful we are that you continue to plug away at this despite it looking like an uphill battle. If there are specific things that we can do to help test or give you other information, please just let us know.
No problem - I find it hard to live without grid spaces, so Iāll continue with it as far as I can. It was a great relief to find a way to get it going!
Feedback is very helpful, please do continue to let me know how it works for you.
What a pleasant surprise, Iām so happy to have the grid back! Thank you, Stephen!
As for your ārelease notesā:
You can get this functionality back if you use a program such as BetterTouchTool or MagicPrefs, etc. to assign trackpad gestures to fire off keystrokes you set in TotalSpaces to swipe between spaces.
I wouldnāt call anything that Iāve seen a āserious UI/graphical glitchā - just little tiny bits of jankiness that I probably wouldnāt even have noticed if you hadnāt said anything. Super easy to ignore, no big deal.
Totally understandable, but Iām so glad you seem to have had cracked the rewritten-in-Swift Dock.app!
I havenāt found anything yet, but I will report back if I do.
^
Again, thank you SO much for keeping this aliveā¦ I would have totally understood if you just abandoned ship on this one, but it makes me hopeful to know you are as attached to grid spaces as many of us are.
I was wondering if you could look into fixing transitions? Itās currently broken for me. The only reason I bought the app was to avoid the animation for switching spaces.
I have installed TS 2.3.1 on beta 6 but have the same problem as mentioned above with TS telling me I need ā16 desktops and I have 16 desktopsā and no grid overview.
I have installed TS without turning off system security is this OK or do I need to turn it off?
Yes, unfortunately if you want to run TotalSpaces on El Capitan you will need to turn off System Integrity Protection. See at the bottom of this post for how to do that: http://blog.binaryage.com/el-capitan-update/
Thanks Stephen not very keen to do that so perhaps will wait and see what develops. Really disappointed as TS and TF are my most used and precious apps. Thanks for all you are doing really appreciated.
For those of you with 2.3.1 installed, thereās some breakage in beta 7 [10.11 Beta (15A263e)] - Iām on the case, itās probably fixable pretty quickly.
Apple developer and corp. employee here (marketing), todays latest release (DP7 15A263e) no longer has the option to disable āSIPā (aka ārootlessā) from Recovery. Itās been removed. Opening terminal, running ācsrutil statusā (w/o quotes) states SIP status as enabled, however it lists the following as ādisabledā under āConfiguration:ā
Apple Internal
kext Signing
Filesystem Protection
Debugging Restrictions
Dtrace Restrictions
NVRAM Protection
Essentially, most is disabled however SIP remains enabled. The latest version of TotalSpaces worked perfectly with DP6 and SIP disabled. Many of us (aka internal employees) are divided on this issue as EUās should have a more clear path of understanding and enabling/disabling this security measure. This will prove especially difficult for third party developers, however based on what we have āheardā, this may be a āpushā in nudging developers who do not use the OS X MAS in doing so as to circumvent these new measures. Internal documents suggests Apple may lower their current 30% MAS āfeeā to 15% in order to encourage MAS sales, discourage pirating, while also increasing long term profits by having more applications run through Appleās system. I am speaking frankly as this matter has created a rift within various internal 'circles" and would implore third party developers to contact Apple regarding this matter. Many of us do not want Apple to enforce an āall or nothingā approach to distributing non-Apple applications under the guise of improved security.
The more consumers and developers who contact Apple regarding this matter, the better the odds that this may change before GM/consumer release.
Thank you for posting the information. However, Iām curious about your comments regarding the MAS. My understanding is that an app like Total Spaces would not be accepted there because it is affecting system components and the fundamental use of the application would prevent it from being distributed there. Even if it were, what development options would be available for restoring its functionality that it would not have otherwise?
The more consumers and developers who contact Apple regarding this matter, the better the odds that this may change before GM/consumer release.
How? How do we contact apple through a non-blackhole mechanism?
Iām a user - not a developer. Probably classified as a power user.
SIP wonāt let me fix parts of the OS that I need fixed. ie, bash. Sure, I know why you wont distribute bash4. but I require /bin/bash to be bash4.
If I, as the owner and operator of my computer, donāt have access to read and write /, macos will no longer be usable for me. One of the major reasons Iāve seen such great growth in OSX adoption (vs bsd/linux on the desktop) is the unix-like (bsd, even better) userland with a functional gui and strong application developer ecosystem. If you break that, youāll lose those of us who use it daily and require our tools and system to be able to be modified to suite our needs.
As for the MAS (mac app store?) - Iām against any push to drive developers there. I try very hard to avoid purchases through the app store, not because itās evil but because apple pushes so hard to make everyone use it, with the clear goal of shutting out the true independents (and open source). That, and apple neuters what app store software can do, AND takes a cut of the developers payment.
Donāt kill your customers and dont kill your developers and innovators, apple.
Rant off. For the moment.
ā¦david (osx user since 10.0 betas - though I was running them on unsupported 604eāsā¦well, 10.1 anyway)
Dire emergency recovery: hit Shift-Ctrl-Alt-Cmd-Space and wait 5 seconds. This will write a sample to ~/sample.txt, and will restart Dock. If your UI appears to completely freeze then do this and send me the sample file. Iām not expecting it to, but this has been useful to me during development.
Still some UI glitches in exiting the grid, I have a good plan to fix it, but itāll take a while.
Yes, as you describe, turning off SIP from the Recovery GUI now results in this āunsupported configurationā. Itās clearly unfinished. (But TS2 2.3.2 does work.)
More generally, TS2 is not app store material; it would never pass sandboxing for one thing. The only way I can see it living on is if injecting signed code is allowed, or we could have a usable way for users allow that for a single specific app.
As I have said before we canāt reasonably ask our users to turn off general security protections, even if they are more fine grained (although that might help a bit).
I suspect, for the case of TF and TS2, the official view is that allowing apps to inject code is a threat to system stability even if the apps are from good and not bad actors, so I donāt hold out too much hope of prevailing.
But I take the point, it may be that the more that contact apple the better the chances of change here.
All good questions. Appleās end game is to push for appās they approve via the MAS. If an app gets into system [root] settings, they wonāt approve it. Using SIP will deny its use, thus forming an end game. Either the developer abides by set rules via the MAS (OS X Mac App Store) or the app/developer folds.
As Apple takes 15% off Apple Music profits, they are following suit with the Developer Revamp (15% instead of 30%). Instead of paying $99/year for separate iOS and OS X development accounts, $99/year will cover both to encourage more developers to use Appleās conduit. The potential increase in app sales would outweigh the 15% Apple decrease in revenue and possibly may surpass sales by ālocking downā system resources for the sake of improved security. Itās a win/win.
Since the MASās release, overall sales havenāt lived up to internal expectations. Many developers have come forward along with research/figures to support the fact the profits arenāt as impressive as many assume. Thus many developers push their apps independently (and via the MAS if approved) in order to bolster sales. Top ten āPaid Forā¦ā doesnāt necessarily mean the developer is making decent, or even reasonable, profits. Itās a bit of a misnomer.
Marketing has been developing methods to entice developers to utilize the MAS. SIP and lowering Appleās percentage being two convenient means, many others are on the table. Additionally, aside from boasting YOY records compared to iOS sales, it would allow Apple more control over what appās are approved as OS X engineering has sidelined proposed core system features that some developers have already implemented. This is mostly frustrating as unforeseen applications made it difficult to implement similar/exact key components into OS X. As OS X is a tightly integrated system, one key feature that depends on another which is either available third party and/or via MAS (approved without foresight) has resulted in sidelining many projects. Cannot name it for obvious reasons but some will know it, one app in particular that adds an iOS style panel similar to Notification Center resulted in engineering placing this feature on hold. This OS X feature was to be integrated with iOS devices akin to Handoff and Continuity.
There are many reasons for Appleās desire to better control third party appās running in OS X. As they have no direct [legal] control regarding non MAS third party applications (including pirated apps), which may result in security comprises to OS X feature integration and lower than expected MAS sales, SIP and possibly locking out third party application installations may be the steps towards these goals. Currently, allowing apps downloaded from the MAS is the default setting in OS X. That may change once Apple formulates an enticing prospect for such developers to utilize their system, thereby lessening possible outrage.
Again, this is all hearsay and I never wrote this and I love your app.
Everything seems to be working with ver. 2.3.2. Iām on 10.11 public beta 5 and recovery update 2. Thank you for this update!
Question: Can you offer this version for sale to the public even if it does not meet Apple requirements?
If it requires users to turn off general security protections then we probably canāt sell it. But as long as I can make it work Iāll make it available for download.
