tsquare opened this issue on Feb 17, 2011 · 138 posts
Keith posted Thu, 03 March 2011 at 2:37 PM
To use another post of mine from that 4 year old thread I mentioned before, I suggested something like this:
Quote - ReadMe
Merchant
ProductName folder
product readme files
Runtime
Geometries
Merchant
ProductName
product obj files
Libraries
Regular library folders
Merchant
ProductName
product files
AddOn folders*
Textures
Merchant
ProductName
product textures
AddOn folders*
For the AddOn folders (marked by asterisks), what I mean are merchant addons to an existing product. For example, if I made mats and textures for the Daz Morphing Fantasy Dress and sold them, my texture directory layout might look something like this:Pose
MATs
DAZ
MorphingFantasyDress
KeithsAmazingMFDTextures
DAZ
Clothing (if organized like this, otherwise move stuff up a level by removing this one)
MorphingFantasyDress
KeithsAmazingMFDDoing it this way means it's a lot easier to find things. I know all the MAT files from everyone making stuff for the MFD will be in the MFD directory structure. If I want to move the dress from, say, the V3 runtime to a dedicated DAZ clothing runtime, it's easy to find all the files and the add-on products that I've bought.
At the time I suggested this, someone pointed out that they'd hate the structure the way I did it, and that's fair enough because that sort of thing was personal preference. What I was getting at, though, is that it isn't trying to create a folder structure that would make everyone happy, which is an impossibility, but one that's consistent, so that if and when I want to reorganize things to suit my preferences, I know where they can be found as a default in a newly unzipped/installed file.
The single biggest pain in the ass with the wildly individual structures in product distribution is the textures folder.