Windows users can do that with shortcuts on the desktop. You can also have quick launchers for explorer locations in Windows.
This conversation is bit difficult as you apparently haven't used Magellan2 ever and aren't familiar with terms and behaviour of it. So, we're getting misconceptions on almost every point, because you try to adapt terms in Windows/Linux features.
Double clicking in desktop meant that you'll get device list window opened whenever you double click any empty point at desktop. With device list you get quick access to any mounted volume or any defined assign. So, predefined shortcuts won't do the same thing as they don't automatically adapt with removable media and changing mounts/assigns. Not to talk about getting it opened anywhere when visible screen area changes with opened windows etc.
You can also do this or even choose to use Webdav instead. (Quick how to if you're really interested)
On Magellan2 ftp isn't statical mounting or mapping. It's more like comprehensive ftp client integrated in the file manager. You don't have to keep sites mounted longer than you need them at the moment. It has good addressbook with versatile per site options. I for example have around 130 sites defined on it (ok I used to trade a bit). You can integrate site opening easily everywhere in the program. And you can open new sites just by typing the url in the lister's location string. File management functions adapt to ftp use and for example file attributes etc work differently than on standard Amiga filesystems, but still you handle everything same way no matter if it's ftp or local dir. You also can see on site messages etc. So it's good compromize between separate ftp client and mounted ftp.
But it's only providing basic functionality - playing a better than VGA video, copying a DVD or anything requiring buffering is going to take a long time.
Those aren't filemanager's issues. It depends of on what system you are using it and what external programs you configure in the manager etc. Of course it's not limited to only low end machines even if it _can_ be used. I use Magellan2 with 1.5GHz Mac mini and 1GB memory and it's extremely fast.
Ubuntu provided button swapping functionality for single double etc. You can even change the handiness of the mouse and I suspect Windows also allows this.
It wasn't at all about button swapping. It was about configuring the program to do different things when you click file with different ways.
Like if you double click a jpeg image, it opens it on certain viewer. And if you right click it, you get more features to open it on editors or whatever. Or how it is processed when you drag&drop it on other location. Or if you double click it with control or some other qualifier key pressed. It can be made to open yet different programs or even make it to do some image processing events automatically for it then or whatever your imagination allows.
All can be configured easily and you can even define configurations for certain file type groups. For example some functions are available for all images, but then some more detailed functions just for png images etc.
but when it comes down to getting a modern workload done fast (converting DVDs, preparing multiple GBs of files for an MP3 player, streaming HD video etc) I'd rather do it with that machine!
Magellan2 is just perfect for those! Aren't we talking about the program, not the platform you run it?
As mentioned it's great to see things like "Very configureable startmenus" (on Windows - toolbars, Gnome probably has the same)
On Windows they aren't that configurable for the user. You can't have total control of them in same way. And how they are consistent and cooperative with other components of the system.
"Very comprehensive function editor" (on Gnome perl, python etc etc all industry standards, and at a push can install Rexx too) etc come to Amiga OS. I'm in no doubt the last point is good specifically for the Amiga file managment as compared to using perl but I really wouldn't want to have to learn a proprietry(?) new function editor just to manipulate files automatically based on decisions.
Again some misconception with terms. On dopus function editor is used to tell what program does on certain event. It's basic methods and options selected on the event. Those scripting languages are options what function editor then tells to execute. So they're deeper level things and I didn't mean them. Everyone knows what they can be used then.
In function editor you can define what commands (internal, amigados, workbench, script, arexx) are executed in what order and what data is provided to them. Do they need some output options, do they need to be executed asynchronously, do they need more data with different type of requesters (string, secure string, file/dir requester etc), what info of the files or environment are given etc etc. It just gives you possibilities to do everything you can imagine without needing to think any external tricks or scripting language knowledge etc.
And this function editor is used for all actions like those filetype definitions, startmenus, hotkeys, automatic script launching, button banks, lister functions, pulldown system menus etc, giving the consistency I've mentioned earlier for the whole system.
we've found newer and somewhat better ways of doing the same things which are available in other OS but I'm very happy that this sort of stuff is getting open sourced on the Amiga.
I haven't found anything similar although I've used lots of different systems for my work and fun.
