About Store Forum Documentation Contact
Donations:
309$/mo



Post Reply 
Plain (not encoded) filename mode
Author Message
takashi Offline
Member

Post: #1
Plain (not encoded) filename mode
Hi,

Is there any plan to support plain (not encoded) filename mode? This mode would be very useful when teams handle a lot of file. It is critical to us. If it takes time and cost, let me know by private message.

Thanks,
Takashi
06-24-2016 04:20 AM
Find all posts by this user Quote this message in a reply
Esenthel Online
Administrator

Post: #2
RE: Plain (not encoded) filename mode
Could you please explain more?

The filenames for project elements are taken from UID of the element.
Since UID is a binary data of 16 bytes, it must be converted into some filename-compatible form.
06-25-2016 01:50 AM
Find all posts by this user Quote this message in a reply
Zervox Offline
Silver Supporter

Post: #3
RE: Plain (not encoded) filename mode
Most likely he means to ask is storing and handling the files in the traditional way like it was done in 1.0.
06-25-2016 12:16 PM
Find all posts by this user Quote this message in a reply
takashi Offline
Member

Post: #4
RE: Plain (not encoded) filename mode
I'm afraid but I don't know it was done in 1.0...
I suppose that current UID base filename would have some advantage in EE.
However, in case of my team, plain (not UID based) filename is prefered.
The reasons are as below.

1. It's difficult to find a file in Windows' Explorer or MacOS's Finder.

2. When svn dectects conflict, it's hard to know which file caused conflict.

Therefore, UID based filenames mode is required for my team.
Is it possible to provide the mode in option?
06-27-2016 02:45 AM
Find all posts by this user Quote this message in a reply
Esenthel Online
Administrator

Post: #5
RE: Plain (not encoded) filename mode
Hi Takashi,

Thank you for the feature request, however:
-this task would take a very long time to make
-it's a complex task
-if implemented, then once a project element is renamed, or placed into another folder, then all existing references to it would be broken, unless asset path fixup functionality is included, however that is a slow operation for big projects

From my perspective it seems more sensible if I would develop my own SVN-like solution, that would work based on existing UID-encoded filenames, however that's a very long and complex task as well.

So for now I prefer to work on other tasks.

Thank you very much
07-01-2016 03:05 AM
Find all posts by this user Quote this message in a reply
Post Reply