More "compressed" format?

[Progress1]

Internal database format use fixed length size to store file names etc. What about something like csv structure? (separated with ; ) Why? i just create whole disk catalog and has ~400mb. Due a lot of empty space it has big size. But divided structure can have ~40mb.

Solution: in Format settings add radio button: Ident (like now, will be default) and csv (or something like that). You just need add some auto detection at the start to identify right catalog format.

[tiglat]

Thank you for idea. I will take it into account. Unfortunately I am very busy. This feature will require enough big time.

By the way I would like to clarify the initial idea behind the current design. Fixed length size format is used to make the output file readable by human. The output file could be printed as well. The last point probably is not actual any more. But possibility to read file in any simple text viewer I think still useful.

Anyway I understand you request. Today number of files on our disks are increased significantly, so we need another approach to work with file lists.

[Progress1]

Yes, therefore we keep it on the user selection. If user want human readable catalog -> he will use default setting. If user want just create small size catalog for archiving and don't care about readability, printing -> uses csv. Also csv is readable by excel so user can process these data in own way later. Or even more compressed format after applying csv format we can add another zip layer over it (.zlst extension) and plugin do decompression in memory automatically -> just another idea for far far future :)