Ticket #151 (new task)

Opened 10 years ago

Last modified 10 years ago

xuvtools: [wishlist] "projectfilename" contains an absolute path

Reported by: ne704 [niko@… Owned by: emmenlau
Priority: minor Milestone:
Component: xuvtools Version:
Keywords: xuvtools, projectfiles Cc: developers@…


currently, the xuv-projectfiles (plain-text format) contain an absolute path for the key "projectfilename"

is this really necessary? since #141 has been fixed, directories containing images and projectfiles can be moved around and opening the very same projectfile from a different location works without any problems. so the question is, do we need to write the "projectfilename"-key into the file at all, or is this just because the plain-text projectfile is merely a dump of all internal variables?

I'm happy with being told we leave the situation as-is, but I didn't want to retain the topic, since this is IMHO a bit confusing...

Change History

Changed 10 years ago by emmenlau

Its a valid (and good) point you are raising here. The key "projectfilename" is only in the project file for historic reasons. I think it would make sense to remove it from the project file!

Concept idea (as a reminder for myself):  http://www.xuvtools.org/doku.php?id=devel:project_files#how_loading_and_storing_works. There is an idea outlined how to remove "projectfilename" and other keys.

Note: See TracTickets for help on using tickets.