You are not logged in.
Pages: 1
ReNamer 6.9 has been released!
Most notable changes from the user’s point of view:
Implemented rule comments. This was one of the most requested features. Rule comments are editable via the rules context menu and visible in the Statement column. See the demo screenshots below.
Added a dialog for manually entering file paths for renaming. Useful when you have a list of paths as plain text.
Added Dutch and Traditional Chinese (Taiwan) translations.
Various efficiency improvements.
Complex rules can be difficult to read...
Now, nicely commented by you!
Full list of changes:
* Implemented rule comments, editable via rules context menu.
* Enhanced storage path resolution with new path tags and handling of multiple path tags.
* Major code refactoring to improve automation and unit testing capabilities.
* Decoupled renaming rules from the visual components.
* Refactored renaming rule structures and management operations.
* Refactored file signature structures and management operations.
* Added a dialog for manually entering file paths for renaming.
* Added various unit tests, including unit tests for some renaming rules.
* Remove all files more efficiently than one-by-one when all files match the clearing criteria.
* Efficiency improvements for files table clearing operations.
* Efficiency improvements for performing shell actions on files.
* Added "How to translate" link to the Languages menu.
* Find application language file independently of the executable file name.
* Perform a fast clearing of files tables when closing the application.
* Converted action buttons in the Pascal Script window to a toolbar. Better handling of long localized text.
* Changed the Z-order of controls in the Delete rule window. Avoid awkward overlapping with long localized text.
* Forbid the use of empty folder when creating preset links. Avoid an error.
* Added Dutch language file.
* Added Traditional Chinese (Taiwan) language file. Thanks to 冰霧神域.
* Updated French language file.
* Updated Chinese Simplified language file. Thanks to WanderMax.
* Updated German language file. Thanks to Kevin Scheitler.
* Updated Serbian language file. Thanks to Никола Алексић.
* Updated Russian language file.
* Internal refactoring.
Offline
Color me impressed!
(incredibly so, I must say...)
I have been using version 5 for so long that I had forgotten to check how much this program had evolved.
It really shows how much effort Dennis has been making into further developing the product.
I believe it's really (really!) worth buying now, even if it costs more than half of what I spend on food each month... I promise I'll start saving money just for this purpose.
Congratulations, Dennis! (Really nice job )
Offline
Color me impressed!
(incredibly so, I must say...)
It is great to know, especially coming from a long time user!
Offline
Visiting the forum after a hiatus of 4 years!
It's great to see this is going strong as ever!
In this layout, the same Statement column represents either the composed rule or the comment; which is a little unintuitive. Instead, can we have Comment as a separate column, and then a column-management feature that allows the user to show/hide columns, and change their sequence?
Let the user right-click in the column header and trigger the column-manager dialog.
He should be able to drag and drop the columns to change their sequence.
Offline
Visiting the forum after a hiatus of 4 years!
Glad to see you back here!
All your suggestions about the Comment column and column management features in general are right on the spot. This is all planned, along dozens, if not hundreds, of other features and improvements.
Offline
6.9.0.3 Beta
Added unit tests
Please, what does that means?
Was is that, was is that good for?
Is that for us users or more an program internal thing?
Read the *WIKI* for HELP + MANUAL + Tips&Tricks.
If ReNamer had helped you, please *DONATE* to Denis or buy a PRO license. (Read *Lite vs Pro*)
Offline
History wrote:6.9.0.3 Beta
Added unit testsPlease, what does that means?
Was is that, was is that good for?
Is that for us users or more an program internal thing?
This is an internal feature, it doesn't have any direct effect for the user.
Unit tests ensure that future changes to the code base or the development environment don't have an undesired effect. These tests are executed as part of the development workflow. Unit tests provide a layer of testing, in addition to the functional testing, which increases the chances of detecting issues/bugs earlier.
The indirect effect for the user is, hopefully, a better long term experience.
Offline
Pages: 1