crazy idea: alias names for folders
Posted: 01 Apr 2026 09:47
This is maybe the most craziest idea, I have ever had so far.
I was thinking about keeping the paths short and still having folder names that are friendly for human readability.
My idea is to keep super short folder names on the file system level and then define easily human readable folder names in XY for display (eg. in file list, address bar etc., basically everywhere, where they are displayed / used).
I am not talking about Rapid Access Folders or similar, which are an alias / shortcut for a whole path.
Instead I am talking about individual folders on a per folder level.
The idea is a bit like how a professional DMS would work. System internal names for objects that never change and on top of these, display names for these objects. In XY's case, maybe the info of these easily human readable alias names could be saved somewhere in the windows file system? If not, then inside XYs databases.
Of course this idea would hugely affect almost every corner of XY, since all features that deal with file/folder paths should be able to support it. This would be a massive undertaking, almost like switching from VB to TB. And if not done right, it would mess up XY's UX more than it would help. So, I don't expect, not even hope, for anything. Still, before I kept it to myself, I thought, I just post it. Maybe it can trigger another simpler idea with someone else.
regards, auto
I was thinking about keeping the paths short and still having folder names that are friendly for human readability.
My idea is to keep super short folder names on the file system level and then define easily human readable folder names in XY for display (eg. in file list, address bar etc., basically everywhere, where they are displayed / used).
I am not talking about Rapid Access Folders or similar, which are an alias / shortcut for a whole path.
Instead I am talking about individual folders on a per folder level.
The idea is a bit like how a professional DMS would work. System internal names for objects that never change and on top of these, display names for these objects. In XY's case, maybe the info of these easily human readable alias names could be saved somewhere in the windows file system? If not, then inside XYs databases.
Of course this idea would hugely affect almost every corner of XY, since all features that deal with file/folder paths should be able to support it. This would be a massive undertaking, almost like switching from VB to TB. And if not done right, it would mess up XY's UX more than it would help. So, I don't expect, not even hope, for anything. Still, before I kept it to myself, I thought, I just post it. Maybe it can trigger another simpler idea with someone else.
regards, auto