From 7173a9f0cf4dd5cb1f3f85ef44bd2acad89463d3 Mon Sep 17 00:00:00 2001 From: Stefan Hundhammer Date: Sun, 4 Jun 2017 15:38:33 +0200 Subject: [PATCH] Version bump and change log --- README.md | 175 +++++----------------------------------------- doc/DevHistory.md | 145 ++++++++++++++++++++++++++++++++++++++ src/Version.h | 2 +- 3 files changed, 164 insertions(+), 158 deletions(-) diff --git a/README.md b/README.md index b7d07ab3..164faeb1 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,7 @@ Target Platforms: Linux, BSD, Unix-like systems License: GPL V2 -Updated: 2017-05-31 +Updated: 2017-06-04 ## Overview @@ -65,7 +65,20 @@ _Full-size images and descriptions on the [Screenshots Page](https://github.com/ ## Latest News -**Latest stable release: V1.3** +**Latest stable release: V1.4** + +- 2017-06-04 **New stable release: V1.4** + + It's about time to ship all those latest changes. + +- 2017-06-04 Fixed problem with directories that have read, but not execute + permissions thanks to _slodki_: + + In that case, you'd get a warning in the log for every entry in such a + directory, and it would get the wrong icon (a locked folder) and null values + for all fields. Now checking for execute and read permission of the directory + in advance and not even trying to read any contents (because the values would + be bogus anyway). - 2017-05-31 Fixed [GitHub Issue #61](https://github.com/shundhammer/qdirstat/issues/61): Files and directories with UTF-8 special characters in the name not read @@ -192,164 +205,10 @@ correctly when built with Qt 4.x Beware that QSettings sorts the entries alphabetically, so the start is after the end (how philosophical...). - If there are graphics designers out there who want to tune this even more, - please send me the results (preferably with a screenshot). But please - remember that this effect should be kind of subtle, and the user should - clearly see the difference between a large file and a directory full of tiny - things that just don't get rendered because of the minimum tile size. - ------------------------ -- 2017-03-05 **New stable release: V1.3** - - It's about time to ship all those latest changes. - - -- 2017-02-27 Implemented [GitHub issue #30](https://github.com/shundhammer/qdirstat/issues/30): - - When hovering over a treemap tile, display the full path and the total size - of that element in the status bar. When the hover ends (when the mouse cursor - leaves the treemap tile), display the current selection again in the status - bar. - -- 2017-02-24 Improved logging: More secure and automatically log-rotating. - - QDirStat now uses its own log directory `/tmp/qdirstat-$USER` (where `$USER` - is your user name; the numeric user ID is now only used if the user name - cannot be obtained). It no longer keeps one single log file growing, but - starts a new one each time it is started. 3 old logs are kept; any older ones - are deleted. - - The permissions for that directory are set up in a pretty restrictive way - (0700, i.e. `rwx------`) when it is created. If it already exists, QDirStat - checks the owner and creates a new one with a random name if it is owned by - anyone else than the user who started QDirStat. - - [sh @ balrog] ~ 68 % ls -ld /tmp/qdirstat-sh - drwx------ 2 sh sh 4096 Feb 24 18:29 /tmp/qdirstat-sh - [sh @ balrog] ~ 69 % ls -l /tmp/qdirstat-sh - total 16 - -rw-rw-r-- 1 sh sh 2067 Feb 24 18:29 qdirstat-00.old - -rw-rw-r-- 1 sh sh 2067 Feb 24 18:07 qdirstat-01.old - -rw-rw-r-- 1 sh sh 2067 Feb 24 18:07 qdirstat-02.old - -rw-rw-r-- 1 sh sh 2067 Feb 24 18:29 qdirstat.log - - - For anybody regularly watching the log file this means they will now have to - use `tail -F qdirstat.log` rather than `tail -f` since the latter does not - realize when the file it watches is renamed and a new one is created under - the same name. - -- 2017-02-23 Fixed [GitHub issue #24](https://github.com/shundhammer/qdirstat/issues/24): - - During directory reading, subdirectories would get out of sync when opening - a tree branch. - - It looks like QDirStat's tree display was a bit too dynamic for the concepts - of the underlying Qt classes (QTreeView / QAbstractItemModel): During - reading, QDirStat would sort the tree by the number of pending read - jobs. That number is constantly changing, so the sort order would also - constantly need to change. This is very hard to do properly with the - limitations those underlying classes impose; basically it would require a - reset of all the data the QTreeView keeps, thus making it forget things like - its current scrollbar position or which tree branches were expanded or - collapsed. That would make the user interface pretty much unusable. - - So the fix for this is to not sort by read jobs, but by directory names - instead since they don't change all the time. The user can still sort by any - other column, but that sort is a momentary thing that might become invalid - moments later as data (accumulated sizes, number of child items) are - updated. Everybody please notice that **this is a known limitation** and any - complaints about that will flatly be rejected. The alternative would be to - not allow the user to sort at all during directory reading, and that is - certainly a lot less desirable. - - -- 2017-02-22 - - - @flurbius contributed a patch to switch the main window layout from tree - view above and treemap below to side-by-side (Menu _Treemap_ -> _Treemap as - Side Panel_). - - - Added new document [GitHub-Workflow.md](https://github.com/shundhammer/qdirstat/blob/master/doc/GitHub-Workflow.md) - explaining how to work with GitHub and Git to contribute to QDirStat. - -- 2017-02-20 Locating files by type from the _File Type Statistics_ window -![Locating FilesWindow](https://github.com/shundhammer/qdirstat/blob/master/screenshots/QDirStat-locating-file-types.png) - - You can now locate files with a specific filename extension directly: - - - You select a file type (a filename extension) in the "File Type Statistics" window. - - - You click "Locate" or you double-click the item. - - - The "Locate Files" window opens. - - - You click a directory there. - - - In the main window, the branch for that directory opens, and all matching - files are selected in the tree view and in the treemap. - - - You can now directly start cleanup actions for those files. - - See also [GitHub issue #48](https://github.com/shundhammer/qdirstat/issues/48). - - -- 2017-02-18 New document: [QDirStat for Servers](https://github.com/shundhammer/qdirstat/blob/master/doc/QDirStat-for-Servers.md) - describing how to use QDirStat and the `qdirstat-cache-writer` script on - headless (no X server, no X libs) servers. - -- 2017-02-17 _File Type Statistics_ window merged to Git master - - Latest screenshot: - - ![File Type Statistics Window Screenshot](https://github.com/shundhammer/qdirstat/blob/master/screenshots/QDirStat-file-type-stats.png) - - **Limitations:** - - Since filename extensions (suffixes) don't have as much semantics in - Linux/Unix systems as they do in Windows, many files are categorized as - "Other". This is a known limitation, but it's a limitation of the whole - concept of using suffixes to categorize files by type. And no, checking file - headers for magic byte sequences like the "file" command does is not an - option here; QDirStat would have to do that for (at least) all the 30,000+ - files typically listed under the "Other" category. So we'll have to live with - that limitation. - - Next thing to come: Locating files with a specific suffix from there. - See [GitHub issue #48](https://github.com/shundhammer/qdirstat/issues/48). - - -- 2017-02-12 Working on a _File Type Statistics_ window - - People who know WinDirStat inevitably want that _File Type_ view in QDirStat, - too. I was really reluctant to do that because I didn't quite see the point; - in WinDirStat, it serves mostly as a legend to the treemap colors since they - are constantly changing in WinDirStat: The file type that consumes most disk - space always gets color #1, the next-most color #2 etc., so it depends which - directory you scan what color each file type gets. In QDirStat, the colors - are stable; they are predefined and configurable in the _MIME Type - Categories_ configuration dialog. - - And as most of you probably know, filename extensions have a much stricter - meaning in Windows than on Linux/Unix systems; Linux people get very creative - when it comes to using dots in filenames. Sometimes those dots delimit a - filename's extension (suffix) from its base name, sometimes they are used for - entirely different purposes. - - Anyway, there was one user who was insistent enough to make me reconsider, - and I did some experimenting this weekend, and now we have an (albeit still - experimental) **File Type Statistics** view. So far, that code lives in a Git - branch, but I think it will stabilize in the next one or two weeks, so I will - merge it to Git master. - - - See the whole discussion with more screenshots at - [GitHub issue #45](https://github.com/shundhammer/qdirstat/issues/45) - - -- 2017-01-03 **New stable release: V1.2** +- 2017-03-05 **New stable release: V1.3** _See [DevHistory.md](https://github.com/shundhammer/qdirstat/blob/master/doc/DevHistory.md) for older entries._ @@ -360,6 +219,8 @@ for older entries._ This is just a rough summary. For more details, see [DevHistory.md](https://github.com/shundhammer/qdirstat/blob/master/doc/DevHistory.md) +- 2017-06-04 New stable release: V1.4 + - 2017-03-05 New stable release: V1.3 - 2017-01-03 New stable release: V1.2 diff --git a/doc/DevHistory.md b/doc/DevHistory.md index 34045c06..619c0cba 100644 --- a/doc/DevHistory.md +++ b/doc/DevHistory.md @@ -10,6 +10,151 @@ https://github.com/shundhammer/qdirstat/blob/master/README.md ## QDirStat History +- 2017-03-05 **New stable release: V1.3** + +- 2017-02-27 Implemented [GitHub issue #30](https://github.com/shundhammer/qdirstat/issues/30): + + When hovering over a treemap tile, display the full path and the total size + of that element in the status bar. When the hover ends (when the mouse cursor + leaves the treemap tile), display the current selection again in the status + bar. + +- 2017-02-24 Improved logging: More secure and automatically log-rotating. + + QDirStat now uses its own log directory `/tmp/qdirstat-$USER` (where `$USER` + is your user name; the numeric user ID is now only used if the user name + cannot be obtained). It no longer keeps one single log file growing, but + starts a new one each time it is started. 3 old logs are kept; any older ones + are deleted. + + The permissions for that directory are set up in a pretty restrictive way + (0700, i.e. `rwx------`) when it is created. If it already exists, QDirStat + checks the owner and creates a new one with a random name if it is owned by + anyone else than the user who started QDirStat. + + [sh @ balrog] ~ 68 % ls -ld /tmp/qdirstat-sh + drwx------ 2 sh sh 4096 Feb 24 18:29 /tmp/qdirstat-sh + [sh @ balrog] ~ 69 % ls -l /tmp/qdirstat-sh + total 16 + -rw-rw-r-- 1 sh sh 2067 Feb 24 18:29 qdirstat-00.old + -rw-rw-r-- 1 sh sh 2067 Feb 24 18:07 qdirstat-01.old + -rw-rw-r-- 1 sh sh 2067 Feb 24 18:07 qdirstat-02.old + -rw-rw-r-- 1 sh sh 2067 Feb 24 18:29 qdirstat.log + + + For anybody regularly watching the log file this means they will now have to + use `tail -F qdirstat.log` rather than `tail -f` since the latter does not + realize when the file it watches is renamed and a new one is created under + the same name. + +- 2017-02-23 Fixed [GitHub issue #24](https://github.com/shundhammer/qdirstat/issues/24): + + During directory reading, subdirectories would get out of sync when opening + a tree branch. + + It looks like QDirStat's tree display was a bit too dynamic for the concepts + of the underlying Qt classes (QTreeView / QAbstractItemModel): During + reading, QDirStat would sort the tree by the number of pending read + jobs. That number is constantly changing, so the sort order would also + constantly need to change. This is very hard to do properly with the + limitations those underlying classes impose; basically it would require a + reset of all the data the QTreeView keeps, thus making it forget things like + its current scrollbar position or which tree branches were expanded or + collapsed. That would make the user interface pretty much unusable. + + So the fix for this is to not sort by read jobs, but by directory names + instead since they don't change all the time. The user can still sort by any + other column, but that sort is a momentary thing that might become invalid + moments later as data (accumulated sizes, number of child items) are + updated. Everybody please notice that **this is a known limitation** and any + complaints about that will flatly be rejected. The alternative would be to + not allow the user to sort at all during directory reading, and that is + certainly a lot less desirable. + + +- 2017-02-22 + + - @flurbius contributed a patch to switch the main window layout from tree + view above and treemap below to side-by-side (Menu _Treemap_ -> _Treemap as + Side Panel_). + + - Added new document [GitHub-Workflow.md](https://github.com/shundhammer/qdirstat/blob/master/doc/GitHub-Workflow.md) + explaining how to work with GitHub and Git to contribute to QDirStat. + +- 2017-02-20 Locating files by type from the _File Type Statistics_ window + +![Locating FilesWindow](https://github.com/shundhammer/qdirstat/blob/master/screenshots/QDirStat-locating-file-types.png) + + You can now locate files with a specific filename extension directly: + + - You select a file type (a filename extension) in the "File Type Statistics" window. + + - You click "Locate" or you double-click the item. + + - The "Locate Files" window opens. + + - You click a directory there. + + - In the main window, the branch for that directory opens, and all matching + files are selected in the tree view and in the treemap. + + - You can now directly start cleanup actions for those files. + + See also [GitHub issue #48](https://github.com/shundhammer/qdirstat/issues/48). + + +- 2017-02-18 New document: [QDirStat for Servers](https://github.com/shundhammer/qdirstat/blob/master/doc/QDirStat-for-Servers.md) + describing how to use QDirStat and the `qdirstat-cache-writer` script on + headless (no X server, no X libs) servers. + +- 2017-02-17 _File Type Statistics_ window merged to Git master + + Latest screenshot: + + ![File Type Statistics Window Screenshot](https://github.com/shundhammer/qdirstat/blob/master/screenshots/QDirStat-file-type-stats.png) + + **Limitations:** + + Since filename extensions (suffixes) don't have as much semantics in + Linux/Unix systems as they do in Windows, many files are categorized as + "Other". This is a known limitation, but it's a limitation of the whole + concept of using suffixes to categorize files by type. And no, checking file + headers for magic byte sequences like the "file" command does is not an + option here; QDirStat would have to do that for (at least) all the 30,000+ + files typically listed under the "Other" category. So we'll have to live with + that limitation. + + Next thing to come: Locating files with a specific suffix from there. + See [GitHub issue #48](https://github.com/shundhammer/qdirstat/issues/48). + + +- 2017-02-12 Working on a _File Type Statistics_ window + + People who know WinDirStat inevitably want that _File Type_ view in QDirStat, + too. I was really reluctant to do that because I didn't quite see the point; + in WinDirStat, it serves mostly as a legend to the treemap colors since they + are constantly changing in WinDirStat: The file type that consumes most disk + space always gets color #1, the next-most color #2 etc., so it depends which + directory you scan what color each file type gets. In QDirStat, the colors + are stable; they are predefined and configurable in the _MIME Type + Categories_ configuration dialog. + + And as most of you probably know, filename extensions have a much stricter + meaning in Windows than on Linux/Unix systems; Linux people get very creative + when it comes to using dots in filenames. Sometimes those dots delimit a + filename's extension (suffix) from its base name, sometimes they are used for + entirely different purposes. + + Anyway, there was one user who was insistent enough to make me reconsider, + and I did some experimenting this weekend, and now we have an (albeit still + experimental) **File Type Statistics** view. So far, that code lives in a Git + branch, but I think it will stabilize in the next one or two weeks, so I will + merge it to Git master. + + + See the whole discussion with more screenshots at + [GitHub issue #45](https://github.com/shundhammer/qdirstat/issues/45) + - 2017-01-03 **New stable release: V1.2** diff --git a/src/Version.h b/src/Version.h index 8f137f8d..e8d5bbe8 100644 --- a/src/Version.h +++ b/src/Version.h @@ -9,6 +9,6 @@ #ifndef Version_h #define Version_h -#define QDIRSTAT_VERSION "1.3.01-git" +#define QDIRSTAT_VERSION "1.4" #endif // Version_h