- #Expandrive vs strongsync software#
- #Expandrive vs strongsync code#
- #Expandrive vs strongsync mac#
- #Expandrive vs strongsync windows#
Directory Opus has a very nice feature when renaming files inline: When opening a folder from Alfred I would like the option of opening it in the current tab, instead of creating a new tab.ģ. In icons view mode, pressing right arrow when you’re on the last item of a row should move to the first item on the next row.Ģ.
#Expandrive vs strongsync windows#
But coming from Directory Opus on Windows there are some things I really wish I could see in Forklift:ġ. Would more than love to help you with suggestions and ideas, if you need any help, please reach out.įorklift is a great piece of software. – ftp connections open up in a floating window rather than a pane – borrow this from total commander – backspace – to get out of the current folder Allow the right arrow and left arrow to move between columns, once on the first/last column would move the cursor to the beginning/end of the column
#Expandrive vs strongsync mac#
– have the files/folders in multiple columns (a la Total Commander, not the mac way) rather than just a long list of files. – sync preferences as well across devices (including shortcut keys) – sync FTP accounts via iCloud – iCloud should always be the preferred way for syncing for mac-only apps. – allow the use of function keys in Forklift – without having to change them in system preferences – Eltima’s Commander One does this and love this feature – focus on keyboard usage – ideally power users should be able to use Forklift just by using the keyboard That being said, here’s what’s very important (for me at least): Always ended up using ForkLift because Commander One is still very buggy. I’ve tested everything the mac universe had to offer best ones seem to be ForkLift and Eltima’s Commander One. It’s hands down, the best file manager, nothing comes close.
#Expandrive vs strongsync software#
Used to be a Windows guy 10 years ago and since my move to Mac there’s only one piece of software i miss every day. If you could add ONE feature to ForkLift 4, what would it be? Let us know in the comments which is the one, most important feature you definitely would like to see in ForkLift 4. We will make sure that this will be a fair offer. We will work out a fair concept this time too, where users won’t need to purchase ForkLift twice within a given period. In the past, we always introduced grace periods for the users who had bought ForkLift in the months before the release of the next major version. Users who need or want to buy ForkLift now should buy it now and shouldn’t postpone the purchase. Since we had announced that ForkLift 4 might come out in the spring, a lot of people asked if they should purchase ForkLift 3 now or wait until the new version comes out. ForkLift 4 will likely require a recent macOS version, but we hope that by the time ForkLift 4 comes out, this won’t be such a big issue. But unfortunately, using these modern implementations has its price too, and this price is the compatibility. It feels good and liberating to delete something old and unnecessary entirely or replace it with a much simpler solution. There is only one thing that can improve the app besides writing code, and that is deleting some unnecessary code.
#Expandrive vs strongsync code#
These new solutions are reducing the complexity of the code too. There are some new technologies and implementations (for example, SwiftUI) that we want to use in ForkLift 4, which would allow us to build a more robust and future proof app. If we want the code to stay relevant, then we have to change bigger parts of it, and it is better to change some of the core functions now, before the release, than a few months later on the live code. We want to create a solid foundation that we can later easily build on. The maintainability of the code will become even more significant now that we are switching to the new model of continuous development. A maintained, sustainable code is easier to work with, and it allows new functionality to grow. That is good for the developer and the users as well. That is a standard we have set for ourselves.
However, we are postponing the release of ForkLift 4 because we have decided to make a major overhaul once again.įirst and foremost, we want to add more new features to ForkLift 4 than planned so that we can call it a new major version with a clear conscience.Īlso, because of the complexity of ForkLift, we need to keep the code of ForkLift clean and sustainable. That was one of the reasons why we hoped that we could release ForkLift 4 in the spring. And we certainly didn’t want to completely rewrite the code as we did in the past major versions. We were planning to make fewer significant changes to ForkLift than in the previous major releases. In this last post, we also wrote that we were hoping to release ForkLift 4 in the spring of 2021. The feedback from our users has been overwhelmingly positive, which has strengthened our decision about the new pricing model. In one of our latest blog posts, we discussed our plans for the new business model for ForkLift 4.
0 kommentar(er)
