Dependencies solver

[founder]

Organization changes from time to time, but the dependencies of Scribus and Openshot files are a terrible obstacle changing organization.

For example there is

archieve/special.videos/2021-05-27 solar with pictures SLA and OSP files.

I would like to move this to

internet/gemini.pege.org/video/2021-05-27 solar

but dependencies make this very complicate.
There are about 50 such project folders to move.

What about a software checking all SLA and OSP files in the whole file system for dependencies
and solving rename and move problems?

[AdmFubar]

i dont see what these dependencies  are. can you provide more details?

[MrB]

Have you tried File->Collect For Output?

[AdmFubar]

Have you tried File->Collect For Output?

I still think this should be the default way (or at least user settable) to save scribus projects.

[Nermander]

If you have a lot of images that are used in several different projects it would cause tons of duplicates.

But an option to "link" or "save (copy) in project" would maybe be useful.

There is also the picture manager, maybe it could get some improvements to replace paths in several documents at the same time?

I would probably rather look at using sed on the Scribus documents to replace paths (I assume they are in clear text in the documents).

[a.l.e]

many moons ago, i did a feature request for allowing such use cases...

https://bugs.scribus.net/view.php?id=9056

it would help, if somebody could make a good formal proposal that considers all options, use cases, and edge cases : - )

[PatJr]

+1 on the picture manager, I've never got that to work

[AdmFubar]

many moons ago, i did a feature request for allowing such use cases...

https://bugs.scribus.net/view.php?id=9056

it would help, if somebody could make a good formal proposal that considers all options, use cases, and edge cases : - )

Essentially it is there with the collect for output, Prolly need a lil tweaking to make it work remotely.

Nermander :
"If you have a lot of images that are used in several different projects it would cause tons of duplicates."

I have the equivalent  of a super computer on my desktop. Lots of storage(it is cheap these days). this isnt the days of 8bit machines and floppy disks.

[Nermander]

But the issue is that if you for example use a logo in your publications, you may want each document to use the same source so if you edit the logo it will be updated in all publications. If you have done Collect for output, you would have to update every copy, which is a lot more work.

[AdmFubar]

A minor issue. I search and replace with copy it easily. And if you have so many documents to update then one should prolly be using another method of creating them.

(also why I want this as optional.)