Hey everyone, I am looking for options and feedback.
I have wanted to change the "temp" directory structure for a long time
now but I have not because a lot of people may have door configurations that need to be updated.
For example: If you have a door with a command line that is the "old"
way of doing things where you use the TEMP directory and %3 or %N to
point to the path where the door files are then you'd need to change it:
OLD: c:\doors\mydoor.exe c:\mystic\temp%3\door.sys
NEW c:\doors\mydoor.exe %Pdoor.sys
If you use an asshole design door like LORD where you have to set up the drop file path for each individual node within its configuration, then you'd need to update those as well. I only know of LORD that does this but there may be others.
My question is: How many people would have a huge problem with me doing this change? I may not do it for a while or at all I just wanted to get
a feeling of opinions.
I have wanted to change the "temp" directory structure for a long time
now but I have not because a lot of people may have door configurations that need to be updated.
1. Its cleaner. Alongside these changes there will only be a single TEMP
directory and all other directories will be included as a
subdirectory:
OLD: \mystic\temp1\ \mystic\temp2\ \mystic\tempmis\
NEW: \mystic\temp\1\ \mystic\temp\2\ mystic\temp\mis\
So you'd no longer have 23420 temp directories in c:\mystic just
one.
2, Option to put TEMP in a ram disk or other location for distributions that run on slow media. This will increase performance in some areas on those devices at the expense of needing memory for the RAM disk.
My question is: How many people would have a huge problem with me doing this change? I may not do it for a while or at all I just wanted to get
a feeling of opinions.
On 02-16-19 14:32, g00r00 wrote to All <=-
Hey everyone, I am looking for options and feedback.
I have wanted to change the "temp" directory structure for a long time
now but I have not because a lot of people may have door configurations that need to be updated.
On 02-17-19 17:26, Avon wrote to g00r00 <=-
2, Option to put TEMP in a ram disk or other location for distributions that run on slow media. This will increase performance in some areas on those devices at the expense of needing memory for the RAM disk.
I personally wouldn't be using that.
On 16 Feb 2019 at 02:32p, g00r00 pondered and said...
I have wanted to change the "temp" directory structure for a long tim now but I have not because a lot of people may have door configuratio that need to be updated.
I think with respect to doors running them stand alone on a BBS is declining with the rise of the door servers many now use. I still run several as standalone on Agency and others using the same games do for
the inter-bbs BRE for Zone 21... that said I agree it's time to move and standardise this to a single directory.
1. Its cleaner. Alongside these changes there will only be a single
directory and all other directories will be included as a subdirectory:
OLD: \mystic\temp1\ \mystic\temp2\ \mystic\tempmis\
NEW: \mystic\temp\1\ \mystic\temp\2\ mystic\temp\mis\
So you'd no longer have 23420 temp directories in c:\mystic just one.
I support this.
2, Option to put TEMP in a ram disk or other location for distributio that run on slow media. This will increase performance in some areas those devices at the expense of needing memory for the RAM disk.
I personally wouldn't be using that.
My question is: How many people would have a huge problem with me doi this change? I may not do it for a while or at all I just wanted to a feeling of opinions.
Yep suggest you do this and make it a fixed thing of any alphas for 1.13 once 1.12 is out.
Better to let folks know that 1.12 respects the current state of play
then make changes for 1.13
Perhaps 1.13 can roll in some of the other standardised directories
beeing mooted for Mystic 2.0 but please merge the concept into 1.0
rather than force us to pick up a whole new UI etc. that was in the 2.0 demo.
better to move ideas across from 2.0 into the 1.0 branch IMHO :)
Hope that helps.
Hey everyone, I am looking for options and feedback.
Yep, totally agree with everything Avon says here... this would
definitely be a good change. How difficult would it be to put some sort
of parser in so the update would leave current systems as they are, and
Assuming I understand what you're asking for, this will not be an option, sorry. :(
The goal of these changes are to simplify the directory structure to make it easier to move Mystic to different drives and root directory names as well as to reduce the number of directories and configuration options.
If I tried to build some old and new way thing it would take what is already too complex and make it more difficult to work with than it already is.
g00r00 wrote to All <=-
My question is: How many people would have a huge problem with me doing this change? I may not do it for a while or at all I just wanted to
get a feeling of opinions.
The reason for the change is for a couple of reasons:
1. Its cleaner. Alongside these changes there will only be a single
TEMP
directory and all other directories will be included as a
subdirectory:
OLD: \mystic\temp1\ \mystic\temp2\ \mystic\tempmis\
NEW: \mystic\temp\1\ \mystic\temp\2\ mystic\temp\mis\
So you'd no longer have 23420 temp directories in c:\mystic just
one.
It would be cleaner. If I did use the actual directory location in any door data lines, it would get me off my butt to get them fixed. :)
It would be cleaner. If I did use the actual directory location in an door data lines, it would get me off my butt to get them fixed. :)
so in a way it's going to help you burn calories and become the man you want to be :)
Such a change will break the original MRC python client. But I'm sure a coordinated rollout of an updated client would solve the issue.
Also, I know that several of my MPL apps use the user's temp directory
for stuff. I think I use the CfgTempPath variable. I assume that under the new plan, the variable will point to the proper directory, yes? If
so, then I don't think that my apps will break because of it.
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 31 |
Nodes: | 8 (0 / 8) |
Uptime: | 204:27:12 |
Calls: | 2,083 |
Calls today: | 1 |
Files: | 11,139 |
Messages: | 948,040 |