![]() ![]() This would trigger a switch back to space1 because the newly created Finder window converts to a tab, and that activates TotalFinder window living on space1. Let’s say the TotalFinder window is on space1, the user is working on space2 and for example clicks on the desktop to open a new folder. This caused problems in the case of having the TotalFinder window on a different space. Yeah, faster downloads for you and cheaper S3 bills for me :-) Want new windows always as tabs?įolks using the OSX Spaces feature were asking for better handling of new Finder windows.īy default TotalFinder turns new popping Finder windows into tabs of the last active TotalFinder window. Oh, maybe I should have added that the installer’s footprint is 3.4MB now, which is ~30% less than the previous 4.8MB. You know I hate cruft, especially in my own baby projects. Unfortunately I cannot present any visible progress here, but I personally feel much better now. This was also good excuse to refactor the whole XCode project into several smaller projects, solve dependencies, improve build scripts and clean things up. I understand the geek inside of you, so in the future I will write a separate technical article about how it works :-) You can then compile it on your own in case you want to be 100% sure about the kernel extensions on your system. This way when you happen to look into /System/Library/Extensions you won’t scare yourself to death by forgetting Echelon is simply something related to the peace-loving TotalFinder.Īnd by the way, if you are still scared please note that TotalFinder.kext is going to be also an open-source in a few days on GitHub. So I decided to rename it simply to TotalFinder.kext. ![]() ) A general project refactoring and Echelon renameĮchelon scares people too. Of course I will be glad to get some feedback/code reviews on this.Īnd as a side-effect I’ve learned how to rule the world with my own Scripting Additions. Don’t worry, I will open-source my solution in a few days on GitHub. But I’m using my own OSAX to do the Finder injection by default. TotalFinder.bundle is still a SIMBL plugin and you can run it with SIMBL if you want to play with ist. I was able to implement a future Finder version check like this: It does not need Agent and it is Snow Leopard only, so it turned out to be really easy (the plugin injector has less than 100LOC). Actually it does no good with Finder’s auto-restart and it has complicated my life in the past (I needed to prevent a continuous crashing scenario, for example) I don’t really need SIMBL’s Agent functionality.To sleep well at night I wanted to implement a future compatibility check for Finder.Testing compatibility and keeping up with Finder.app alone is quite enough work for me. I don’t want to depend on a component which may evolve.It should be ideally one-click experience. I want TotalFinder installation and uninstallation to be as seamless as possible.Is it really worth it to replace SIMBL with my own homebrew solution? And let’s be honest, the SIMBL homepage is not very welcoming to non-programmers. They will probably want to look at it and understand what it is. A user needs to install a separate program prior to TotalFinder. Running an installer is not much work, I know. The current version of SIMBL has one fundamental problem related to TotalFinder. TotalFinder probably would not be here today without SIMBL. All kudos to Mike Solomon who has been doing an awesome job on it for so many years. SIMBL is a great and well maintained software. The full changelog: TotalFinder loves SIMBL, but SIMBL scares people on the streets ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |