I was thinking to check it by default only when using a single file compressor *and* having multiple files in list, while leave it unchecked by default when using archiving formats (or when a single file is in input list). However, the defaults of that options will need be quite flexible, i.e. In this way using the option would be something like creating a solid archive (first archive, then compress) but replacing the native metainformation of the selected format (7z, zip, paq, pea.) with tar ones, hich would be very welcome in Unix environments because tar format metainformation about object are a long time estabilished standard for that enviroment and other software and scripts which exists for it. I like this idea! But as something like "TAR before" for single file compressors ONLY.I also started with this idea, but I tended to shift toward allowing it for all formats. However, despising those issues that prevented me to consider UHARC support in peaZip before, I'll try to get more information and to conduce more tests on this that seem to be a very interesting and promising format. Moreover it's not open source and I was not able to find a Linux version, so I would have to let it unsupported in Linux version of PeaZip, that would not be very elegant. However, in "Default options" you can set 7z and PAQ* to use native console based interface, so you will see the native progress indicator of each LovePimple thank you for have suggested to me this very interesting forum about UHARC unfortunately I don't know if I may redistribute it in PeaZip like I do with 7z and PAQ*, that is a key requisite for including it, the license state it's free for non commercial use and I really don't know how it's intended to be redistributed by third parts. Unfortunately for the moment I designed the graphic wrapper around back-end applications as monothread so I cannot display pipe output until the application (in this case PAQ*) has ended. so I forgot to make it optional! But however what you suggest is a good idea and I think I'll add an option to turn off the popup in next version of the Black_Fox The confirmation popup (when using console interface for applications) was initially intened to be optional, but then I really liked it since I could launch many very long jobs at once and then, when I come back, see exit codes for each one. bat, truning it in a full functional script (I know for advanced uer it's a less than meaningful issue since he/she will just open the file and copy/paste the command line). I choose to keep separated job_definition and job_log information because job definition may contain password (if encryption is used) so it should be handled with more care than job log information another reason is that it's a little simpler to understand how to use job definition information if it's not mixed to other content, basically a Windows user, in example, could just rename it in. It is an open-source software and can be legally downloaded and distributed for free.Hi, thank you a lot for the interest and the comments about Fallon tgz) and as a portable package that does not need to be installed and the system does not change. PeaZip is released under the LGPL for Windows and Linux as an installation package (Windows installer, Deb, RPM, Slackware. PeaZip has its own archive format, called PEA, which supports compression, multi-archive creation and flexible tools for encryption and integrity checking.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |