Explanation of -c
-
Ah OK - already been through that one… :-)
-
should we?
-
Possibly. I think the information sent out with PACL (manual.txt) is very minimal. It might have been fine for version 4 when the functionality was much less but there’s too much guess work in using the options and how the options interact with each other.
e.g. “0 start as a low priority process”. OK, that’s fine, but then what? What causes the process to change priority? Is it up to the user to change the priority? Will it change priority automatically when the machine is less busy or more busy?
There’s not enough detials for the type of computer-literate user who will be using PACL. Maybe it just needs more detailed documentation.
-
it wont change priority, it will be started as lowest possible priority - started as in run as low priority…
-
we could convert manual.txt to wiki and then improve….
-
it wont change priority, it will be started as lowest possible priority - started as in run as low priority…
I understand that (maybe a bad example from me) but having compression options “0 - store” and “10 - store” without the “backwards compatibility” explanation you gave above is confusing.
manual.txt, wiki, pdf - doesn’t really matter how you present it so long as the information is available. It wouldn’t take much but it’s up to you on whether you think it’s worth it.
-
I understand that (maybe a bad example from me) but having compression options “0 - store” and “10 - store” without the “backwards compatibility” explanation you gave above is confusing.
manual.txt, wiki, pdf - doesn’t really matter how you present it so long as the information is available. It wouldn’t take much but it’s up to you on whether you think it’s worth it.
it is always worth it if our users request it :-)
-
so… what do we need to improve?
http://wiki.powerarchiver.com/en:help:pa_command_line_manual_pacl -
You’ve been busy :) Nice!
OK, it looks like you used the text from manual.txt as the basis of the wiki. Initially, I’d like to see a short explanation of each command and it’s capabilities\requirements at the top of the wiki so it’s the first thing you see in the wiki - sort of an expanded whatsnew.txt for each command - with links to the syntax of each command. Is there a reason why PAEXT is first. I’d have thought you compress then uncompress so PACOMP followed by PAEXT maybe?
(These are just my thoughts so anyone else please sound-off).
-
This post is deleted!