Git Product home page Git Product logo

peazip's People

Watchers

 avatar

peazip's Issues

[Windows 7] Allow non-nested context menus

Hi, Peazip is great, except I would really really like the ability to have 
non-nested context menu items, instead of having them all under the "PeaZip" 
context menu submenu.

I.e. when I right click on a .ZIP file I would like to be able to immediately 
choose "Extract here" or "Open with PeaZip" instead of having to go thru a 
submenu first.

Thanks!

Original issue reported on code.google.com by [email protected] on 7 Jan 2011 at 11:08

wrong folder selection in left pane

When user selects a folder in the left pane (left mouse button), and when the 
height of the main program window is not large enough to display all folders 
(vertical scroll bar used), another folder than the correct one is highlighted 
in the left pane.

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 1:15

Truncated menu text with non default windows theme

When using a 3rd party Windows 7 theme with non default font sizes >> 
http://zainadeel.deviantart.com/art/Shine-2-0-for-Windows-7-172671190
Menu text is cut off at the end.
Example image http://imgur.com/xFLt7.png

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 1:14

Support for .apk

It would be nice to be able to open apk archives, which is the format used for 
android apps..

7Zip already supports it

thanks !

Original issue reported on code.google.com by [email protected] on 12 Dec 2010 at 7:50

Auto start possible for all jobs

Request to auto-start jobs launched from context menu.
Currently archive creation jobs and "Extract..." wait for the user to click Ok 
(or press enter) to let time to modify the job definition (password, output, 
input, options...).

"Extract here" and "Extract here (to new folder)" jobs does not wait for user's 
confirmation.

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 3:46

Progress bar inaccurancy

The progress bar when job is running in graphic mode is not very accurate; if 
you want to have a real time report of the job's progress the native console 
mode is still the most detailed and accurate.

You can also select graphic + console mode in Options > Settings in order to 
have both a graphic interface to interact with the job and an accurate, real 
time report of ongoing operations in the console window.

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 12:32

Gtk-Warning cannot open display

What steps will reproduce the problem?
1. ./peazip -ext2to final_folder folder_file_to_dempress

What is the expected output? What do you see instead?
Is possible to work with peazip  without a gtk/Qt interface?

What version of the product are you using? On what operating system?
Suse 11
latest version of peazip

Thanks and best regards

Original issue reported on code.google.com by [email protected] on 8 Jan 2011 at 1:54

Archive browser needs to switch to flat mode for listing some out of standard archives

A few archiver utilities does not create entries for directories names while 
creating archives of various formats.

Browsing a such (mal)formed archive with PeaZip, the program will miss the 
directories name and so will not be able to display them, but still can launch 
jobs to correctly extract, list and test the archive, including the not 
displayed content.

The problem is avoided browsing those malformed archives in flat mode (clicking 
on the expand "+" icon or F6), or using basic or advanced filters. 
List/test/extract operation are not affected by the problem

From version 2.1, PeaZip auto-switches to flat view mode if it is able to 
detect this problem (which happens if no item is declared at the root level of 
the archive).

PeaZip 3.3. improves recognition of malformed archives and in those cases
automatically switches to flat mode (show all).
Also, the icon for toggling browse mode and flat mode was also added in
status bar area for better visibility of this feature.

This bug is also documented in program's FAQ

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 12:31

one single job window for multiple archive extract

doing a bulk extract of many archives in a folder results in a job progress 
popup window for each archive. With many archives it becomes very annoying as 
it constantly pops up over other programs even when peazip does not have focus 
(for each archive).

Fix>

Have one job window for the entire process with currently extracting archive 
progress shown.

Original issue reported on code.google.com by [email protected] on 5 Jan 2011 at 3:29

[Linux] cannot open files containing ' character

' character is used as quote in Unix command line.
PeaZip uses pipes to launch and monitor commands composed in the GUI of the 
program, so it cannot handle files containing command line's special 
characters, as ' is.
Windows is not affected by the problem because it's command line quote 
character " is not allowed in filenames.

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 1:10

Mac OSX version

Last update of Lazarus was the 0.9.28.x family, released in october 2009,
that marks support to Carbon as beta but does not resolve the issues I've
previously experienced in obtaining a satisfying build of PeaZip on OSX
platform.
Being no other Lazarus user I know of able to build the application for
OSX till now (not even the much more simple PeaLauncher for archive
extraction, with far simpler UI and no call to underlying crypto library),
I suspect it is, unfortunately, still early for an OSX port of that
application.

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 1:29

Option to remember all custom compression settings, overriding format, level and method defaults

PeaZip is currently set to remember last used compression level and method
for each format, but other custom options (dictionary, word, passes, solid
block size) will be remembered only for the current session (or until the
archive type is changed).
This current behavior is meant to start each compression level with its
default settings, which are balanced to give an efficient speed/compression
ratio for most data structures.
Some custom settings may in example lead to better result on some file
types and worse on other ones, or increase memory usage or computing time
without reasonable improvement in compression ratio, so I gave priority to
remember default settings for each compression level as originally intended
by Igor Pavlov who developed the 7z backend, without the need of users to
remember them to manually change back to defaults.

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 1:45

[Win 7] Ask for admin rights if needed

What steps will reproduce the problem?
1. Open an archive
2. Choose for extraction a folder such as Program files
3. The program says it doesn't have admin rights, he should try to elevate the 
rights instead (UAC prompt)

Windows 7 64 bit, it should be the same also on Windows Vista

Original issue reported on code.google.com by adecorte on 3 Feb 2011 at 3:20

Extraction without recreating the full parent path tree

Currently both "Extract" and "Extract without paths" extraction options works 
exactly as in the command line version of the 7z backend binary (from 7-Zip 
project), so:
- "Extract" will rebuild the path as it is saved in the archive
- "Extract without paths" will extract all files in the same specified output 
path

An intermediate option of extracting a subfolder without recreating the full 
parent path cannot be performed by 7z executable; it would require either 
expanding the functions of 7-Zip's 7z or some second pass workaround to locate 
and move the extracted output, which is a less good solution since it will work 
from the GUI but will not work the same way if the job is saved and launched as 
batch.

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 3:22

nautilus script for multiple archive extract

add nautilus scripts to "extract all here" on a folder so that peazip extracts 
all the archives in the folder to the same folder in one operation.
(currently the "extract here" script produces errors saying can not decompress 
folder)

also have "extract all here" option for when multiple archives are selected in 
nautilus so each of the selected archives are extracted to current directory in 
one operation. (currently it only works for the first archive)

Original issue reported on code.google.com by [email protected] on 5 Jan 2011 at 3:38

Checksum/hash display in tree format

Currently checksum and hash of files are displayed in a tabular view (that can 
be saved as tab separated text), one proposal to make it more readable onscreen 
is a tree:

MyDummyFile.txt
->Adler32 : AAAAAAAAAA
-> CRC16 : BBBBBBBBBBBB
-> CRC32 : CCCCCCCCCCCC
-> SHA1 : XXXXXXXXXXXXX
-> MD5 : YYYYYYYY
-> ...

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 1:54

Stop drag and drop operation from rebuilding entire path tree

The drag and drop operation in Windows is a bit annoying. 

If I select one file from a subfolder within an archive, and drag it to a 
specific directory, the whole file path is recreated.

For instance, if an archive has the following:

folder1/
folder1/subfolder1/
folder1/subfolder1/subfolder2/readme.txt

and I drag / drop readme.txt onto my desktop, I end up with the following 
created on my desktop:

folder1/subfolder1/subfolder2/readme.txt

instead of just readme.txt

Tested on Windows 7 x86

Original issue reported on code.google.com by [email protected] on 16 Dec 2010 at 2:29

  • Merged into: #30

[Windows] custom drag and drop implementation

Advantages and disadvantages of PeaZip's custom drag and drop implementation 
are discussed in documentation:
http://peazip.sourceforge.net/peazip-more.html

In short, PeaZip can only get the path from the open file explorer window (or 
from the desktop), not from objects (folders) inside the explorer's window 
itself.

The advantage in avoiding the Windows' integrated drag and drop mechanisms
is that the files can be moved directly to the output path, while Windows'
drag and drop needs to copy the files to the system's TEMP folder first.
This is an exceptionally bad idea for file handling applications like
file/archive managers (in fact, issues implicit in this mechanism are a
recurring source of complaints in forums of similar applications running
under Windows), because:
- if the target directory is on a different partition than the system's
TEMP, the process will take double time
- if the system's partition has not enough free space, the Windows' drag
and drop will fail
- the system's TEMP folder can have different security policies than the
intended output directory

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 1:06

Please add a menu item to unzip autodetecting sub-folder

In the menu options for unzipping there is:

* Unzip here
* Unzip in sub-folder

But, what I really need is what KDE offers in it's file browser:

* Unzip, autodetect subfolder

This means that if the archive contains only a single directory with all the 
stuff inside it, then unzip here.

If it contains more then 1 file, then unzip inside a new subdirectory.

This is very useful, because 95% of the archives provide all files inside a 
single directory and 5% provide a mix of files in the root.

So if I use unzip in subdirectory, I will almost always get a too deep 
directory tree, which is annoying.

If I use unzip here, sometimes I will gets lots of files which get mixed with 
my own files so it is very annoying and hard to undo the action.

Also no button should be need to be pressed to really unzip. I already told the 
UI to unzip, so just unzip =) No extra confirmation should be necessary.

thanks!

Original issue reported on code.google.com by [email protected] on 30 Nov 2010 at 9:51

  • Merged into: #21

[Vista and older systems] improve context menu

Microsoft introduced a new, more efficient, method to create cascaded
context menu in Windows 7, that is now recommended over the older COM
method implemented in Vista and older MS systems.
PeaZip supports the new cascading menu standard, but still not the old one.

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 3:20

Copy files from within archives

First of all, I've switched to PeaZip a while ago and I think it's an excellent 
archive manager.

One thing that has been bothering me is the ability to copy specific files from 
within archives without extracting the whole archive. I know you can preview 
and open with right click or ctrl + alt + o.

But what if you implement a ctrl + c (Copy) on selected files and when ctrl + v 
is clicked on a destination folder, it simply extracts those files there.

If that would conflict with Windows own shortcut mapping, then another shortcut 
would be fine.

I really find it hindering to have to go through the extraction process to get 
a couple of files from within an archive.

Original issue reported on code.google.com by [email protected] on 26 Nov 2010 at 11:01

Delete original files after being archived or extracted

Request for an option for deleting original files after being added to an 
archive; now it is up to the user to manually delete original files after being 
archived.
(I currently declined this feature as it is quite dangerous and I prefer 
destructive operations to be logically isolated as much as possible for users, 
so the deletion being logically independent and performed as a separate action 
rather being concatenated with another job)

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 2:59

[Linux] Extracting from p7zip backend does not set file permissions

The problem is known to p7zip's team, i.e. 
http://sourceforge.net/tracker/index.php?func=detail&aid=1065668&group_id=111810
&atid=660496

p7zip is a port of 7z, which is a Windows based archiving utility, and the tar 
implementation on 7z (and consequently p7zip) does not currently support 
restoring Unix files permissions (resets them to tar's standard defaults).

The workaround suggested from p7zip's author is to use p7zip up to 
decompression, and perform the final untar step with the tar implementation 
which is featured by default in Linux distributions.

I'll let this bug report open hoping to improve support for restoring Unix's 
file permission in future.


Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 12:48

[Windows] Translate context menu items

Context menu entries are currently in English only, as they are created by the 
setup package (or the system integration tool) that is in English only, and not 
by the application that is localized.

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 3:11

Graphic confirmation dialog in case existing files are found

Currently a common graphic dialog for asking about overwriting or skipping 
existing files when extracting is not featured by PeaZip.

PeaZip acts as frontend for various compression/extraction engines, its
behavior is usually determinate by policies rather than requiring user's
interaction.

In case of existing files are found, the action to take is determined in 
"Naming policy" submenu in the dropdown on the right of extraction button (also 
available in extraction panel, the second dropdown in "format options").
In this way it is possible to set a policy for existing files: skip
(default), auto rename extracted files, auto rename existing files,
overwrite, ask.

The last policy allows to give interactive feedback in the extraction's engine 
console.
In the extraction console it is possible a very flexible and granular
interaction, so under some aspects it is even preferable to the usual graphic 
confirmation dialog used by many applications in this case.

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 3:40

Delete unfinished archives

Request for an option to delete automatically unfinished archives if the job is 
stopped by the user or due to an error.
Currently in those cases the unfinished archive is let available for being 
inspected or manually deleted by the user.

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 3:25

[Linux, Qt version, some distributions] Missing "x" button

On some Linux distributions, due to partial incompatibilities of Qt versions 
running on the machine and the one used to build the application, the "x" 
button is not shown in the Qt version of PeaZip.
Anyway the application can quit from main menu with File > Quit (or Ctrl+Q).
For distributions maintainers: compiling the application with the right Qt 
bindings version for the target Linux distribution should fix the problem.

GTK2 version is not affected.


Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 12:42

Password Protection at Individual-File Level Not at Archive-File Level

Hello, I'm using PeaZip 3.6 on Windows 7 32-bit

My issue is that the password protection is not implemented at the 
archive-level, but is implemented at the individual-file-level within the 
archive-file.

What steps will reproduce the problem?

1. Create a zip file with some files and specify a password

Now unzip the file with Extract Here (in new Folder) and similar context menus. 
It prompts for archive password and extracts files as expected.

A. Now try same zip file and use context menu "Extract..." - opens interface 
without prompting for password - should prompt for password. 

B. If set directory location and click OK, does not prompt for password and 
will place zero-byte files in directory and then produce error report that 
decryption failed. 

*** Allowing a user without passwords to see filenames is still a security 
breach, even though they can't open zero-byte files. Filenames still provide 
insight into contents/purpose of a 'protected' archive file and may help 
provide enough insights that could be used to crack the archive password. 

2. Add some files to an existing password protected file, allows addition of 
files without prompting for password. New files added are added without 
password.

* a protected archive shouldn't be modified without supplying the password

3. There are other less-critical glitches in the GUI due to the 
individual-file-level password approach that would be cleaned up with the 
archive-level password approach.  For example, files with different passwords 
can be in one archive, when you extract that archive through a method that 
prompts for a password, PeaZip unzips the files with the password supplied but 
the other files with different password are unzipped as zero-byte files because 
the password doesn't match - if you prompt for the first password, why not 
prompt for subsequent passwords? Archive-level passwords clean up these loose 
strings in the app logic.


I believe the vast majority of users would expect the password behavior to be 
at the archive-file level and not individual-file level within the archive. The 
app would be more usable for more people and therefore adopted/used long-term 
by more users if the default support was archive-level passwords. File-level 
passwords within the archive should be considered an advanced option that could 
still be supported by the app through an advanced options tab/feature, but 
should not be the default behavior of a zip program.  

Even if individual-file level password is desired/intended by the app 
developers (then please add archive-level passwords as an 'advanced' option!), 
there are still some holes to plug like not extracting zero-byte filenames that 
reveal naming conventions and insights into the archive contents or opening the 
archive in the PeaZip browser, displaying the filenames. The app could prompt 
for passwords during extraction rather than erroring out and creating zero-byte 
files. The option to Encrypt the filenames within the archive file isn't 
supported by some major formats like ZIP so that isn't a suitable reason to 
overlook these issues.


Please update the app to have default archive-level passwords, aside from this 
it is a great application - Thanks!

Original issue reported on code.google.com by [email protected] on 12 Jan 2011 at 12:37

Extracting .tar.* archives

I am quite irritated each time I extract a tar.gz and it just goes to a regular 
.tar file, which I have to perform another extract step.
This is the same with tar.bz files.
To solve this, I recommend just doing extension checkes - if it's tar.* then 
peazip should know that it's a two step extraction.  If you're afraid this 
would cause some issues, add a new behaviour called "full extract" or something 
like that so the normal extract behaviour is not affected.

Original issue reported on code.google.com by [email protected] on 8 Jan 2011 at 4:18

  • Merged into: #35

Asm blocks cannot be compiled on Linux x86_64

What steps will reproduce the problem?
1. Build project Pea, PeaLauncher or PeaZip

Lots of errors 'Asm: 16 or 32 Bit references not supported'

PeaZip 3.6 - compiling on Slackware64 13.1 using FPC 2.4.0 and Lazarus 0.9.28.2


Original issue reported on code.google.com by [email protected] on 10 Jan 2011 at 4:39

Support editing files inside archives

Editing files inside archives is currently not supported.
The way to update archives (if the format is write-supported) is currently to 
add modified files to the archive, that has by default "update" parameter.
Files can currently be added only to root level of the archive.

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 1:49

[ZPAQ]

ZPAQ support is still experimental both on Windows and Linux, due to the 
difficult syntax of the executable.
On Linux platform there are still difficulties for passing the needed delimiter 
characters to the command.


Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 12:39

[XP, TweakUI] custom desktop path

If the desktop path cannot be recovered by standard Windows API, i.e. because 
customised by some third parts applications, PeaZip can be set to use any 
folder the users wants as desktop, overriding the automatic detection of the 
desktop path; it can be selected in Options> Settings > Desktop.

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 12:51

Support for more achive formats, add here requests

Please add here formats you would like to be supported by PeaZip.
Ideal candidates are not encumbered by patents and have working Open Source 
implementation both of compressor and extractor.
Preference goes to cross-platform implementations, in order to keep PeaZip for 
Windows and for Linux as similar as possible in terms of supported formats.

Original issue reported on code.google.com by [email protected] on 19 Nov 2010 at 1:27

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.