For starters, its important to understand a few things about the Parallax Network filing system, and to understand that its NOT a mistake, and im NOT looking for another content management setup or file structure. The short version is, at any point in time, the same piece of content exists in 4 locations, per office:
1. Server "In Use" Libraries (gets used by us when modeling day in and day out)
2. Server "Packaged for Client Distribution" Libraries (containerized in their own subdirectories, organized differently, and dont get touched, except for QA/QC)
3. Server "Teams" locations (versions (sometimes) edited for clients needs, in a directory structure emulating clients offices, for QA/QC post distribution)
4. On our machines C Drives, sync'd at login from location 1. When we travel, our machines auto-path to location 4, versus auto-pathing to location 1 when were in the office.
OCCASIONALLY (a couple of times a year) when i am rushing, i forget that i had the machine in "Travel mode" because i was visiting a client, and i open some content and edit it, thinking im in Location 1, and im on the C drive (Location 4). Then when i dock at the office, the one-way content sync eradicates what i did on my local hard drive.
Stupid problem, really. Well, i did it last night. Worked for a few hours in the Prlx Template, and it was gone this morning. Checked my Journal, and sure enough.... I had opened the local template like a moron.
Well, John Pierson wasnt having any of that. He whipped this up in short order. Basically, it has a config file, and i can give it any number of Root Directories, and RGB colors i want it to show when im in each directory. So the ribbon turns color, if im in a certain place. I made the local library (the one i shouldnt be editing) stay "Obnoxious Red (255,0,0)) so i go blind if i try to do something stupid.
Its in Alpha testing, now. hehehehehe
EDIT: BOOOOOO. We cant attach GIF's here? WTF?
https://goo.gl/dZ2f35
1. Server "In Use" Libraries (gets used by us when modeling day in and day out)
2. Server "Packaged for Client Distribution" Libraries (containerized in their own subdirectories, organized differently, and dont get touched, except for QA/QC)
3. Server "Teams" locations (versions (sometimes) edited for clients needs, in a directory structure emulating clients offices, for QA/QC post distribution)
4. On our machines C Drives, sync'd at login from location 1. When we travel, our machines auto-path to location 4, versus auto-pathing to location 1 when were in the office.
OCCASIONALLY (a couple of times a year) when i am rushing, i forget that i had the machine in "Travel mode" because i was visiting a client, and i open some content and edit it, thinking im in Location 1, and im on the C drive (Location 4). Then when i dock at the office, the one-way content sync eradicates what i did on my local hard drive.
Stupid problem, really. Well, i did it last night. Worked for a few hours in the Prlx Template, and it was gone this morning. Checked my Journal, and sure enough.... I had opened the local template like a moron.
Well, John Pierson wasnt having any of that. He whipped this up in short order. Basically, it has a config file, and i can give it any number of Root Directories, and RGB colors i want it to show when im in each directory. So the ribbon turns color, if im in a certain place. I made the local library (the one i shouldnt be editing) stay "Obnoxious Red (255,0,0)) so i go blind if i try to do something stupid.
Its in Alpha testing, now. hehehehehe
EDIT: BOOOOOO. We cant attach GIF's here? WTF?
https://goo.gl/dZ2f35
Attached Files
Comment