![]() ![]() Even in the past, there have been so many times when Windows explorer crashed while copying files, thus aborting the entire process. But if you’re a power user, or even if you’ve used the other options out there, you’d know what I’m talking about. Most people won’t find much fault with the default Windows file explorer, it is simple to use and gets the job done. Even third-party Windows File Explorer alternatives are way ahead, in terms of features at least. Meanwhile, the world has moved on and so have the explorers on alternative operating systems. Yet, when it comes to the Windows File Explorer, All Microsoft has managed to do is change its name a few times and add a ribbon bar that’s kind of useful, at times. Windows 10 has brought countless new features and changed just as much without changing too much. ![]() It seems the software giant has finally woken up from its slumber. Windows has never been gaining new features as fast as it is with Windows 10. Native file handling can be done by editing the wine registry but obviously that's a chore compared to our file assosciations.Microsoft’s desktop operating system is on an exciting path these days. I'm going to explore that more later because it means XYplorer could be used to navigate to a file and then it hands over the file handling (pdf, video, audio, etc.) to the UNIX native program. In theory, you could write a shell script that regexes out the drive letter to make the path legal. usr/bin/vlc) but the file path that is fed to the executable is corrupt (it contains the Windows drive letter which is not accepted in UNIX). They work by themselves and Xy is able to launch native UNIX applications from their full path (e.g. Custom File Assosciations are somewhat broken. When search hits folders owned by root XY locks up. sorting 5000 items on name in my home folder took around 5 seconds. (wine performance) search result sorting slows down considerably when a lot of items are involved. disk space indication for root partition is slightly different from "df" return value (within 1% accurate) Essentially that means that Xyplorer as access to /bin/bash which in turn allows you to do anything on the UNIX side of things from within xy Most promissing so far is that run() is able to start native UNIX applications. It's difficult to test because most of them are to do with file handling and don't deal well with wineprefix yet. + scripting: At the moment most of my scripts work. Image preview can be a bit slow when switching between images (not instant, more like 1 second) + quick file preview (including mouse down blow up for images). + right click menu XYPLORER features (To clipboard, Rename Special, etc.) + move or copying files works usin xycopy but only by using ctrl+c ctrl+V I never run wine as root so that behavior seems normal to me. Can't view /root or other root access only locations. + access to the UNIX file system is respecting permissions as far as I can see. + disk space indication for wine PREFIX partition is correct (on my system WINEPREFIX sits on another partition than root I did some digging around and this is what I have thus far: XY is obviously a Windows file manager but I have to say: There is absolutely NOTHING on unix that even comes within a thousand kilometers of XY when it comes to GUI file management. When I'm done I will write an appreview on WineDB. 40k wrote:I'm doing some more testing today to see what works and what not.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |