Totalfinder changelog11/22/2023 ![]() ![]() In the Chromium implementation every new tab has it’s content area realized as a NSView. It wasn’t clear to me how could I possibly do it. The next big task was to integrate tabs implementation with Finder. Tabs transplantation with Finders as child windows Kudos guys! By the way Alcor, the guy who invented Visor and QuickSilver, is also working on mac-specific features of Google Chrome. People working on it earned my full respect. I was really surprised how clean and well-documented the Chrome code is. I’d like to thank Google who made this all possible. After few evenings I’ve got working skeleton app with blank tabs. I’ve spent few days stripping dependencies and isolating functionality I needed. I took their main browser window implementation and also components implementing tabs and extracted them from the main project. I’ve studied briefly their codebase and it looked like a promising path to follow. Luckily enough, there is a great state-of-the-art open source tabs implementation in the Chromium project available. But I’m not afraid to search the internet and get deep into problems I happen to be exploring. I’m quite new to Cocoa and I’ve never implemented such a complex UI element in Cocoa before. Obviously this is a hard task, but so exciting. I had an idea of bringing tabs experience into Finder back in November 2009. Tabs gently ripped from Google Chrome project Enjoy it and look forward for the next release 0.9 which should finally include some new features.The next expiration date is set to Januand it will be probably maintenance release to iron out all problems introduced in this ground breaking update. And that is why we have a new uninstaller app which wraps this into a few straightforward clicks. This renders them unable to click the green “run” button to uninstall TotalFinder properly. Also, TotalFinder goes mainstream, and as you can imagine some people get shocked when they’re exposed to a raw applescript. And more improvementsĭrag & Drop respects system settings for springing delay. And don’t forget: the Activity Monitor is your friend. Report to me if you see anything unusual. I haven’t noticed any major memory leaks. Memory seemed to be returned to the system as expected. After a short TotalFinder session everything looked ok to me. Also, I did a brief investigation using XCode’s memory tools. Now I understand why have some people complained about TotalFinder slowing down their systems. But there was one really huge memory leak in the 0.8 release. Honestly I don’t have much time to hunt for memory leaks. But I don’t want to make this too complicated. Why? Some people want to be able to open classic Finder windows for some tasks while still having TotalFinder operate the rest of the windows. Right now, it is used only for the TimeMachine session, but it is a good foundation for future arbitrary switching of Finder windows between the classic and tab styles. To make TotalFinder windows play nice in TimeMachine, I needed to teach Finder windows how to switch from TotalFinder’s tab-style into the original frame-style and back. Anyway, this window-juggling was so confusing for TotalFinder that it usually crashed immediately after returning from TimeMachine or when the user tried to switch tabs. This working window is disposed of after returning from TimeMachine. The worst thing is that Finder creates an extra “working window” to render the stacked windows behind the main window (did you know these are clones?). Finder uses heavy CoreAnimation machinery for this and it broke visually with TotalFinder. You know, when entering TimeMachine, the active Finder window is animated and floats into the center of the screen for TimeMachine’s galaxy view. The full changelog: TotalFinder and TimeMachine ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |