Re: Fixture files
Posted: 25 May 2009, 14:27
Thinking out loud:
Current situation: Fixture creator asks the user what the new filename should be.
New situation: Fixture creator generates the file name (and if needed the path) with the known values of the fixture. Corresponding to the new file naming convention that we are thinking about here.
Brand and Model are available in Fixture creator, Mode could be added, as for version.
Then no one has to "learn" those rules, they just have to be implemented in the Fixture creator and if applicable FreeStyler needs an adaption that it can find those files.
Ofcourse there are the already existing fixture profiles that does not meet the new file naming convention. So there needs to be a one time "conversion".
Or just leave it so and make FreeStyler compatible with both types.
So my suggestion would be:
Fixture creator:
- Add fields like mode and fixtureversion and fileversion
- When the user clicks "save" then Fixture creator generates the filename all by himself, but still asks the user if that filename is okay. The user should be able to change it whenever and for whatever reason.
FreeStyler:
- If needed change the routines to look for the fixture files. Search through nesting directories.
About the filenaming itself:
Onge said: manufacturer_model_version/revision_mode_fixture_file_version
I thinks its better to do: manufacturer/model_version/mode_fixture_file_version or manufacturer/model_version_mode_fixture_file_version
On behalf of getting too much directories and to much mess, but maintaining some kind of overview I'd vote for the last one:
manufacturer/model_version_mode_fixture_file_version
Last note:
If this new technique gets implemented somehow, FreeStyler must not (never) rely on the filenames itself.
So if someone makes a file: Martin_MAC600_x_Mode1_1.0 in the Martin path, that someone can rename the file to whatever.pff, place it in some other fixture file directory, then still FreeStyler has to find the file correctly, regardless of its name and path.
So this naming convention we are talking about here should only be helping us "people" to quickly see what file it is and what it is for.
FreeStyler works this way at the moment, it does not matter how the file is named, as long as its in the right path, it works. It should stay that way. So only a slight adaption can be made. Make FreeStyler to iterate through subdirectories to see all the files there.
Current situation: Fixture creator asks the user what the new filename should be.
New situation: Fixture creator generates the file name (and if needed the path) with the known values of the fixture. Corresponding to the new file naming convention that we are thinking about here.
Brand and Model are available in Fixture creator, Mode could be added, as for version.
Then no one has to "learn" those rules, they just have to be implemented in the Fixture creator and if applicable FreeStyler needs an adaption that it can find those files.
Ofcourse there are the already existing fixture profiles that does not meet the new file naming convention. So there needs to be a one time "conversion".
Or just leave it so and make FreeStyler compatible with both types.
So my suggestion would be:
Fixture creator:
- Add fields like mode and fixtureversion and fileversion
- When the user clicks "save" then Fixture creator generates the filename all by himself, but still asks the user if that filename is okay. The user should be able to change it whenever and for whatever reason.
FreeStyler:
- If needed change the routines to look for the fixture files. Search through nesting directories.
About the filenaming itself:
Onge said: manufacturer_model_version/revision_mode_fixture_file_version
I thinks its better to do: manufacturer/model_version/mode_fixture_file_version or manufacturer/model_version_mode_fixture_file_version
On behalf of getting too much directories and to much mess, but maintaining some kind of overview I'd vote for the last one:
manufacturer/model_version_mode_fixture_file_version
Last note:
If this new technique gets implemented somehow, FreeStyler must not (never) rely on the filenames itself.
So if someone makes a file: Martin_MAC600_x_Mode1_1.0 in the Martin path, that someone can rename the file to whatever.pff, place it in some other fixture file directory, then still FreeStyler has to find the file correctly, regardless of its name and path.
So this naming convention we are talking about here should only be helping us "people" to quickly see what file it is and what it is for.
FreeStyler works this way at the moment, it does not matter how the file is named, as long as its in the right path, it works. It should stay that way. So only a slight adaption can be made. Make FreeStyler to iterate through subdirectories to see all the files there.