I read the other discussion about the Processing temporary files, but have some separate observations and questions.
I have been using Processing for 3 months now and have thousands of these files. Space is not the issue but the burden on the file system and the amount of time it adds to the work of compiling a program. The directory names found in
users\...\appdata\local\temp
are obtuse. For example:
graphics1a31191575365824121temp
while the contents of this folder is simply:
graphics1a.java
The Processing IDE should provide some options for managing this fileset, including the ability to specify where to place the files (current location is seemingly a poor choice), an age limit (days to keep before deletion), and grouping (high level directory structure by sketch name), separating the random number from the sketch name (graphisc1a_nnn), and using the standard suffix of 'tmp' so system provided functions can find them than handle deletion.
In appdata\local\temp, the files are not in a directory that is easily identifiable with Processing. I would suggest
appdata\local\temp\Processing
which makes them easier to identify and find so you don't have them intermingled with files/directories from other applications.
By the way, I have cleaned out several gigabytes of these so space can be an issue as well.
Just what purpose do these directories and files serve? Are there other such repositories on my disk drive for Processing? Why aren't they deleted when the run command has completed?
I have been using Processing for 3 months now and have thousands of these files. Space is not the issue but the burden on the file system and the amount of time it adds to the work of compiling a program. The directory names found in
users\...\appdata\local\temp
are obtuse. For example:
graphics1a31191575365824121temp
while the contents of this folder is simply:
graphics1a.java
The Processing IDE should provide some options for managing this fileset, including the ability to specify where to place the files (current location is seemingly a poor choice), an age limit (days to keep before deletion), and grouping (high level directory structure by sketch name), separating the random number from the sketch name (graphisc1a_nnn), and using the standard suffix of 'tmp' so system provided functions can find them than handle deletion.
In appdata\local\temp, the files are not in a directory that is easily identifiable with Processing. I would suggest
appdata\local\temp\Processing
which makes them easier to identify and find so you don't have them intermingled with files/directories from other applications.
By the way, I have cleaned out several gigabytes of these so space can be an issue as well.
Just what purpose do these directories and files serve? Are there other such repositories on my disk drive for Processing? Why aren't they deleted when the run command has completed?
1
