QuickZip 5.1 allow you to perform powerful archive operations over a wide range of archive types using a familiar explorer like interface.

I have added a numbers of improvements in Quick Zip 5.1.8

• UIScale – Change the size of all UI controls by holding Control key and press +/-/0 or Mousewheel up/down.
• PickDirectoryDialog – Extract function now shows the new dialog.
• Rewrite icon loading code – ExtraLargeand Jumbo Icon for most special directories is now displayed correctly.
• Archive/File now show correct last write time in gridview.
• Fixed a Typo in Progress dialog (CancelButton)

Autoupdate will be enabled in the next few days (A bug in 5.1.7 and 5.1.8 prevent it from working), as for now, you can download the latest version here :

Download link #1 (Netvigator.com)
Download link #2 (Quickzip.org)
Download link #3 (OverFiles – English)
Download link #3 (OverFiles – French)
Download link #4 (Frettts-Freeware – English)
Download link #4 (Frettts-Freeware – German)

Edit: 2010-09-03 :

If you have previous version of Quick Zip 5.1 installed, it will complain when installing.
Instead of uninstall and install, you can create a batch file with the following command :
msiexec /i quickzip51.msi REINSTALL=ALL REINSTALLMODE=vomus

Please check the previous post for software requirements.

FileList also support seven different viewmodes, sort using grid header, multi-select via dragging and able to update itself when the FileSystem is Changed.

I have updated FileExplorer to 0.8, with the following changes.

• Fixed crash in IDE (no longer fully load when in designmode)
• Added EntryFilter property to DirectoryTree and FileList
• Added OnDirectoryInvoked, OnFileInvoked and OnLinkInvoked property to FileList

I have also updated DirectoryInfoEx to 0.20, with the following changes.

• Fixed ShellProgressDialog still running after closed.
• Added LinkSummaryInformation in ExtraPropertiesProvider.

These projects require VS2010 or above to open.

You can download the control here, or read the article on CodeProject.

To allow control of what to list in FileList and DirectoryTree, e.g. to develop a custom PickDirectoryDialog, which file shouldn’t be listed on the FileList , I have updated these components to include EntryFilter and OnXXXInvoke actions.

EntryFilter (FileList and DirectoryTree)

[Flags]
public enum EntryType
{
    Special = 1 << 1,
    Directory = 1 << 2,
    File = 1 << 3,
    Link = 1 << 4
}

Both DirectoryTree and FileList have a dependency property named EntryFilter, which links to the DirectoryTreeViewModel.EntryFilter.

ExModel have a new function named MatchEntryFilter(), which accepts a EntryFilter, and returns whether the item should be listed.

EntryFilter allows user to specify the item to list, using the EntryType enum.

Noted that some directories or files can have multiple EntryTypes, e.g.

• Link files (file with an extension .lnk) = EntryType.File | EntryType.Link
• Most special directories (directory start with :: ) =  EntryType.Directory | EntryType.Special

In that case, matching any of them will get them listed.

OnDirectoryInvoke, OnLinkInvoke and OnFileInvoke actions (FileList only)

public enum CustomAction { Nothing, OpenFolderOrRun, OpenFolder, Run }

You can customize how the FileList react when a user double-click on a directory, link or file, by assign OnXXXInvoked with one of the properties above. OpenFolderOrRun applies to link, as links may be pointed to a directory or file.

public CustomAction DirectoryInvokedAction { get; set; }
public CustomAction FileInvokedAction { get; set; }
public CustomAction LinkInvokedAction { get; set; }

FileListViewModel have implemented the interface ISupportInvoke, which implements the above actions, they are linked to FileList’s OnXXXInvoke dependency properties. The static Invoking code is placed in ExViewModel, so any decedents, e.g. FileListItemViewModel, can use the following method to execute an Invoke action.

protected static void Expand(ISupportInvoke _rootModel, Action changeDirectory, ExModel embeddedModel)

QuickZip 5.1 allow you to perform powerful archive operations over a wide range of archive types using a familiar explorer like interface.

Unlike previous version, Quick Zip 5.1 don’t pack with a lot of features, here’s a list :

• Windows 7 Explorer like interface, even on Windows XP
• Open wide range of archives as folders, support drag and drop, and let you perform test, extract, delete and compress actions.

After a month of test, it should be stable enough for a release.

Download link #1 (Netvigator.com)
Download link #2 (Quickzip.org)
Download link #3 (Frettts-Freeware – English)
Download link #3 (Frettts-Freeware – German)

Quick Zip 5.1 requires Windows XP or above, and it requires WPF (.Net 3.5 or above), so if you are using Windows XP or Vista, you must have either of the following installed :

• Microsoft .Net framework 3.5 (Larger download)
• Microsoft .Net framework 4.0 Client Profile (Smaller download, better performance)

Quick Zip 5.1 is translated into 4 languages, these translations are applied automatically.
Quick Zip 5.1 will Auto-Update itself every seven (7) days.

Information about how to translate Quick Zip 5.1 and a toggle to disable AutoUpdate  can be found in the About dialog.  (press F1 in main screen).

I have made some progress since last status update

• Aero glass – the transparent part in the top.  Also some updates to the breadcrumb so it fade when not active, and some XP related Theme updates (Breadcrumb align, GridView template)
• Notification bar – Improved design, also added a menu for Open directory, Restart and Remove from list.
• Improved warm start performance – mainly from Native image install, as well as optional .Net 4.0 client profile framework support.
• Overwrite dialog
• Multi-Window support, open new window when user open an archive in Explorer, reuse if specified directory already opened.
• Translation support – on Main window and Overwrite dialog.  Translation script can be downloaded here.
• Some misc updates
  • Address input box support autosuggest
  • Drop Action uses CopyExAWork
  • Improve Response speed for SelectAll/UnselectAll
  • Breadcrumb expander arrow border
  • Control-Backspace in Address input box now recognize archives

Uncompleted items that I can think of :

• Tabs – nice to have, not mandatory.
• Progress dialog – need some enhancements so it can pause and show the progress log.
• Bugfixes

The current version included only the most basic functions, the rest divided to three types :

• UI design – implemented, but haven’t decide how to put it on the user interface, e.g. Password support
• Not Implemented – because of time constraints, e.g. Scripting
• Obsoleted – functions that no one will ever use again, e.g. SFX.

FileExplorer includes two WPF controls, DirectoryTree and FileList.  Both support any normal/shell directory, background item loading, drag and drop, shell context menu, also refresh itself when the filesystem is changed.

FileList also support seven different viewmodes, sort using grid header, multi-select via dragging and able to update itself when the FileSystem is Changed.

I have updated FileExplorer to 0.7, with the following changes.

• Fixed a bug that caused wired thumbnail render.
• Fixed W7TreeViewItem Style, which enable hot track only over the text instead of the whole line.
• Fixed Virtual FileListItem retain selection state (IsSelected = true) after SelectAllCommand and User selecting another item (via Selection Helper).
• Fixed click on GridView Header recognize as drag start.
• For GridView, only support selection if drag occur inside the first column
• Drop operations now use WorkEx, which support custom progress dialog implementation and run in separate thread.
• OverwriteMode changes in DirectoryInfoEx 0.19.  (see below)

Before overwriting an existing file, CopyWork and other Works do raise a WorkOverwrite event, which is a property : Overwrite, to allow specify to continue overwrite (or not).  Currently this property is a boolean, where true is equal to overwrite.   To make the it more extendable, it is changed to OverwriteMode enum type.

public enum OverwriteMode { Ask, KeepOriginal, Replace };

You can download the control here, or read the article on CodeProject.
SelectionHelper 0.4 can be downloaded here.

Introduction

Work in DirectoryInfoEx(Ex) includes CopyWork, MoveWork, DeleteWork and ListWork, each Work will divide a work into smallest possible tasks and run them sequentially, thus possible to report progress and cancel.

DirectoryInfoExA (ExA), unlike Ex, support converting a shell item to another (e.g. an archive file (FileInfoEx) to archive directory (ArchiveInfoExA)), as well as creating one from nothing (e.g. BookmarkDirectory). It’s possible to implement the WorkExA using the method I used in Ex, but if I implement it in file based directory (especially archive directory), the performance become very slow, because the overhead for each archive-related action is great.

To overcome this problem, and to maintain computability with Ex a new Work implementation is developed :

Implementation

I reuse as much code as possible in ExA, so it benefits ExA every time a bug in Ex is reported and fixed.  So, WorkSpawnerExA inherited from WorkSpawner, and inherited all events and work spawning methods, with the following additions :

• WorkOverwrite/WorkList event does not support the new entries so WorkOverwriteExA/WorkListExA event is added.
• New overloads for SpawnCopyWork() is also added for new entries, it will construct the new CopyWorkExA instead of CopyWork, because all work is inherited from IWork, they can be used in the same way.
• SpawnCusomWork() method is added to deal with non copy operations (e.g. Test an archive)

CopyWorkExA

Compared with CopyWork, CopyWorkExA have to handle more situations, For examples :

for simplicity, I use Shell to represent real disk files/directory, and Archive to represent file/directory inside an archive (or other virtual folders).

• Shell —> Archive
  Create a list to copy, then add them to archive
• Archive  —> Shell
  Extract to temp directory, create a list to copy, then copy them one by one
• Shell —> Shell
  Create a list of files to copy, then copy them one by one
• Archive —> Archive
  Extract to temp directory, create a list to copy, then add them to archive

As you noticed, CopyWork is actually two tasks :

• Discover – Prepare a list of files to copy, then pass to next task
• Transfer – Copy the files to destination.

So the new CopyWorkExA is actually executing two task sequentially, and the tasks are defined as interface, namely, IDiscoverWork and ITransferWork.

The events (e.g. WorkOverwrite, WorkProgress, WorkMessage) raised by both Works are handled by it’s constructor, the CopyWorkExA.

Note: Actually CopyWorkExA is inherited from FileOperationWorkBase.  CopyWorkExA only instruct it to Copy.

IDiscoverWork

IDiscoverWork check and return entries inside one IFileInfoExA or IDirectoryInfoExA entry.

• SourceEntry – Specify an IFileSystemInfoExA to discover
• LookupSubdirs – Specify whether the IDiscoverWork should return the items in subdirectories.
• IsTempFiles – Whether the files returned is temporary files.
• DiscoveredEntries – The list of files found, noted that it is in Ex instead of ExA format, thus it must be files or directories in hard drive.
• DiscoveredEntriesBaseDirectory – The base directory of discovered files, ITransferWork uses IOTools.GetRelativePath(item, baseDirectory) to figure out the destination path name.
• DoWork() method – Start preparing the list.
• CleanUp() method – If the file IsTempFiles, CleanUp() method will remove those temp files.

ITransferWork

ITransferWork transfer a number of FileSystemInfoEx entries to a destination.

• PreferLookupSubDirs – Specify if the implementation of ITransferWork perefer to return only the top level entries, or all top level and sub level entries.
• SourceEntries – Specify the FileSystemInfoEx entries to transfer.
• SourceEntryBaseDirectory – Specify the base directory of SourceEntries, used to figure out the destination path of the file to transfer.
• Destination – Specify the IDirectoryInfoExA directory to transfer to.
• TransferMode – Specify Copy or Move.
• IsCleanupRequired – When TransferMode = Move, return whether IDiscoverWork.CleanUp() method should be called after transfer completed.

So CopyWorkExA actually does the following :

1. Generate a dummy TransferWork to figure if it PreferLookupSubDirs
2. For each entries to copy from, generate an IDiscoverWork, then start the generated works.
3. For each base directory returned from the IDiscoverWorks, generate an ITransferWork, then start the generated works.

The implementation of  WorkProviderLibrary, ITransferWork and IDiscoverWork will be discussed in the next article.

Further to the previous status update, I would like to update the progress. Completed Items

• Toolbar commands –  It’s completed, except it currently cannot display the message log when there’s an error, and only few commands is implemented (3 for archive, 1 for file), and it doesnt support encryption as well.
• DirectoryTree style – Directory Tree is updated so it looks similar than the one in Windows 7 File Explorer.
• Organize menu – New, Copy, Paste, Select All, Delete, Properties and Close.
• Open with menu – Screenshot here.
• Shortcut keys – Added some shortcut keys for DirectoryTree and FileList, e.g. Del for Delete, F2 for Rename, Ctrl+A for Un/SelectAll
• Shell Associate – A tool is written to associate Quick Zip 5.1 as the default program for several archives.
• Installer – Moved to Wix, but I have completed the file copy part only.

What is not completed :

• Translation – I will try to use Quick Zip 5.00 translation if possible.
• Tab – No Tab support is available now, prepared the design, will require another layer.
• Ngen – Automatically generate native image, native images are run much faster than Just-In-Time code.

Currently I am working on Translation support, and there’s a couple bugs that requires a fix.

FileExplorer includes two WPF controls, DirectoryTree and FileList.  Both support any normal/shell directory, background item loading, drag and drop, shell context menu, also refresh itself when the filesystem is changed.

FileList also support seven different viewmodes, sort using grid header, multi-select via dragging and able to update itself when the FileSystem is Changed.

I have updated FileExplorer to 0.6, with the following changes.

• Updated DirectoryTree Style so it match the style of FileList.
• Added a wide range of Commands (in SimpleRoutedCommand format, 6 for FileList, 2 for DirectoryTree and 6 for both), can be accessed by
  • calling FileList/DirectoryTree.Commands (In separate class to reduce the complexity of main control).
  • most of those commands are bound with a RoutedUICommands, like ApplicationCommands.SelectAll.
  • shortcut keys (e.g. F2 for rename)

  See FileList/DirectoryTree/SharedCommands.cs for details.

• Updated DirectoryInfoEx to 0.18.

DirectoryInfoEx and FileExplorer is released under LGPL license.
You can download the control here, or read the article on CodeProject.

Introduction

This article describe how to style the WPF TreeView so it looks like the one in Windows 7 File Explorer, I basically included 3 changes :

• Reduced indent spacing
• Full line selection indicator
• Auto fade expander arrows

How to use?

• Include W7TreeViewItem.xaml and W7TreeViewItemUtils.cs.
• Change the ItemContainerStyle of your TreeView.

<Setter Property="ItemContainerStyle">
  <Setter.Value>
    <Style TargetType="{x:Type TreeViewItem}"
           BasedOn="{StaticResource W7TreeViewItemStyle}">
    ...
  </Setter.Value>
</Setter>

• Enable W7TreeViewItemUtils.IsEnabled property for your TreeView, who will hook MouseEnter and MouseLeave event.

  W7TreeViewItemUtils.SetIsEnabled(this, true);

Reduced Indent Spacing

This is simple, all you need is to modify the ControlTemplate (You can look for it from MSDN, or use the “Edit a copy” function in Blend), You can find an ItemsPresenter inside the Template, which is used to list subitems, all you need is to change it’s Grid.Column to 0 (from 1), ColumnSpan to 3 (from 2) and set some Margin in the left side.

<ItemsPresenter x:Name="ItemsHost" Margin="8,0,0,0"
      Grid.Column="0" Grid.ColumnSpan="3" Grid.Row="1" />

Full line Selection Indicator

The default indicator occupy only the area of it’s contents, which in this case, icon and text, this is because the parent TreeViewItem occupy only that area, so changing the background doesnt work.

You may want to set HorizontalAlighment to Stretch, so the TreeViewItem occupy as much area as possible, it seems to work at first, but as you see above, subitems are placed in ItemsPresenter, and ItemsPresenter is allocated with a margin, which is 8 pts per level.

So the only way to deal with this is to use RenderTransform. Using RenderTransform you can change how it render, if I use ScaleTransform and set ScaleX to negative value, it will render from right to left (like a mirror).

Unlike LayoutTransform, RenderTransform affects the display only, so it wont change the size of the TreeView.

<Border Padding="{TemplateBinding Padding}" Grid.Column="0" Grid.ColumnSpan="3">
  <Grid x:Name="BdGrid" >
    <Grid.RowDefinitions>
      <RowDefinition MaxHeight="11"/>
      <RowDefinition/>
    </Grid.RowDefinitions>
    <Border x:Name="Bd" SnapsToDevicePixels="true"
            Background="{StaticResource SelectedBackgroundBrush}"  Grid.RowSpan="2"
            Visibility="Collapsed" BorderThickness="0,1" BorderBrush="#FFCCF0FF" />
    <Rectangle x:Name="BdUpperHighlight" Fill="#75FFFFFF" Visibility="Collapsed" />
    <Border x:Name="Bd2" SnapsToDevicePixels="true" ...Same as Bd... >
      <Border.RenderTransform>
        <TransformGroup>
          <ScaleTransform ScaleX="-2" />
        </TransformGroup>
      </Border.RenderTransform>
    </Border>
    <Rectangle x:Name="Bd2UpperHighlight" ...Same as BdUpperHighlight... >
      <Rectangle.RenderTransform>
        <TransformGroup>
          <ScaleTransform ScaleX="-2" />
        </TransformGroup>
      </Rectangle.RenderTransform>
    </Rectangle>
  </Grid>
</Border>

The UpperHighlight is found in above is required to make the upper part of the background look lighter (like Aero controls).

Auto fade Expander arrows

The expander arrow is only shown when the mouse cursor enter the TreeView (IsMouseOver), the expander then disappear slowly when cursor leave.

You cannot create a EventTrigger that intercept MouseEnterEvent from the TreeView, it can only intercept the item’s MouseEnterEvent, even you set TreeView.MouseEnterEvent.

So I created an attached property W7TreeViewItemUtils.IsEnabled, when set to true, will change another attached property W7TreeViewItemUtils.ArrowOpacity when mouse enter and leave the TreeView.   On the another side, ArrowOpacity is also bound by the TreeViewItem, so it will slowly disappear when TreeView’s ArrowOpacity is set from 1 to 0 using a DoubleAnimation.

The final product can be found in my FileExplorer article (0.6).