[Kdenlive-devel] Fwd: relative paths in project files
dan at dennedy.org
Tue Nov 18 04:01:48 UTC 2008
On Mon, Nov 17, 2008 at 3:08 PM, Alberto Villa <villa.alberto at gmail.com> wrote:
> On Monday 17 November 2008 22:00:21 Dan Dennedy wrote:
>> Seems rather complicated and potentially frought with issues. I am not
>> opposed to it, and I try not to get too involved in kdenlive so I
>> don't get too spread out. However, when this has to be handed off to
>> rendering, then kdenlive might have to start using something other
>> than inigo because I will likely put it way down low on my prioritized
>> ToDo list simply based on the cost of complexity and effort for the
>> I have an idea.
> mh... seems subject to easy corruption... with md5 (and/or nepomuk, i'll
Of course, it will not help if someone drastically reorganizes files;
it only helps in the specific use case mentioned, which is definitely
short of the goals you propose.
> investigate on this 'cause i know really few) you can store absolute paths,
> and automatically (asking to user) update them if they change
> something like (on project open):
> "file not found, do you want to:
> - search automatically (you select a folder in a tree and kdenlive looks for a
> hash match)
> - search manually (you chose the file from a 'open file' dialog)
> - leave in the project unlinked (so you can use it as a placeholder, and also
> this other feature is easily done)
> - remove from the project (the actual behavior)"
> well, i'm not an english speaker, this is to let you know...
> would there be any problem with inigo this way? it seems quite easy to do...
Yes, this would not be permitted to be integrated into inigo because I
do not want to add the dependencies and UI; inigo needs to remain
simple and be able to run headless. But kdenlive is free to not use
inigo, the command line tool. The command line tool is minimal, and
all the power of inigo is still available in the libs, as demonstrated
More information about the Kdenlive