New Idea To Export and Backup X17 Project Files Within The Project Manager?

[VHampton]

On 6/5/2025 at 2:21 PM, Renerabbitt said:

I disagree, updating a template has never been easier. dragging and dropping is a dream. duplicating a complexed linked layout template is super easy. navigating to my projects is faster...like way faster. versioning is faster.
On the flip side, team collab is way more convoluted in project management

 

inadvertently yes. Huge number of support calls on broken links from people who do not understand where texture files are stored and search for and why renaming a file breaks a linked layout

I see your point, Renne — and you make a good case for the benefits. For someone building out from scratch or looking for a faster way to manage templates and versions, I can see how the new system shines.

That said, I still like my own setup — maybe it’s just old habits. Honestly, this feels a bit like being asked to drive on the left side of the road when you’re so used to the right. We’re still getting to the same destination; it just feels unfamiliar.

[Steve_Nyhof]

After having several offline discussions, I remain liking the idea of a backup and/or trigger to auto export the .caproj file. However, there is an issue of how many files would be exported with the file, or if there would be options as to what by default might be part of that export. I do not have answers to how it would all work, but I remain believing that more can be done to automate these files so that how we work with out file systems can continue to be used. 

 

There are ways to dig into existing backups and chief software files to gain access to some of these files, and a more advanced tech can if they want work in this way. I am trying to approach this from a common user, but again, there are things that could cause issues, or future issues with the ongoing development of a cloud type system.

[Renerabbitt]

29 minutes ago, Steve_Nyhof said:

There are ways to dig into existing backups and chief software files to gain access to some of these files, and a more advanced tech can if they want work in this way. I am trying to approach this from a common user, but again, there are things that could cause issues, or future issues with the ongoing development of a cloud type system.

So the way I see this working:
Backup File Manager. It offers to overwrite an old backup or not. If overwriting, then everything is exported, with no option to circumvent. I think this would keep the support calls from coming in about potential lost data from overwriting in conjunction with the second part
Do not overwrite data
Then it lists what data has changed since the last backup, and you can hit select all found, similar to the current dialog box for setting object eyedropper properties.
this export is only the things you selected, and again, has no option to overwrite a full backup

Next tricky part is figuring out how it distinguishes itself with its file name...how the heck do you, the end user, know what the heck is in this backup? Maybe it just asks you to name the backup upon export?