Voltage Spike
05-03-2004, 10:48 AM
I think the following improvements could be made to the handling of file <Path> elements in iSiloX for the Mac OS:
Relative Path Names: I do not like the fact that moving my documents (and the corresponding .ixl files) to another location, or renaming the hard drive, results in invalidation of the iSiloX files. Note that iSiloXC allows relative path names.
(Functional) Long Filename Support: Long file names seem to be truncated into some sort of hash of a shorter file name (e.g., "Stephen_R_Donaldson_-#62A83.txt"). These special names make editing the .ixl file by hand very difficult. Furthermore, modifying the source document requires that I remove and re-add the source file since it's hashed file name changes. Note that iSiloXC allows relative path names.
Standard Path Seperators: The graphical client uses the ':' character as a path seperator. I would prefer that it use the '/' character (even on the Windows client) so that the files are more portable. Note that iSiloXC allows the use of '/' as a path seperator.
If you are good at recognizing patterns, you might notice that iSiloXC behaves as I want it to. :) Great! I would just like to see the graphical client move forward, as well.
My guess is that all three deficiencies are due to its support for the old Mac OS version 8 and 9, while the command-line client does not have that limitation. While I am pretty certain that is the case, that doesn't mean I have to like it. ;)
Relative Path Names: I do not like the fact that moving my documents (and the corresponding .ixl files) to another location, or renaming the hard drive, results in invalidation of the iSiloX files. Note that iSiloXC allows relative path names.
(Functional) Long Filename Support: Long file names seem to be truncated into some sort of hash of a shorter file name (e.g., "Stephen_R_Donaldson_-#62A83.txt"). These special names make editing the .ixl file by hand very difficult. Furthermore, modifying the source document requires that I remove and re-add the source file since it's hashed file name changes. Note that iSiloXC allows relative path names.
Standard Path Seperators: The graphical client uses the ':' character as a path seperator. I would prefer that it use the '/' character (even on the Windows client) so that the files are more portable. Note that iSiloXC allows the use of '/' as a path seperator.
If you are good at recognizing patterns, you might notice that iSiloXC behaves as I want it to. :) Great! I would just like to see the graphical client move forward, as well.
My guess is that all three deficiencies are due to its support for the old Mac OS version 8 and 9, while the command-line client does not have that limitation. While I am pretty certain that is the case, that doesn't mean I have to like it. ;)