- 1 Status
- 2 Administration
- 3 Resources
- 4 Specifications
- 5 Notes
- 6 Tasks
I'm still thinking about and working on simchar, I wouldn't say this is complete yet. I'll probably change the character set somewhat before I'm done and have a 'recommended release' that I use to implement my 'unconfusable codes' (development of the characters for use in 'unconfusable codes' being the point of the simchar software).
Delfiles is pretty much baked. I don't have any real plans to change it in any way. It's a simple little thing that just does its simple little job which it's doing just fine for me at the moment.
People who have contributed to this project. Newest on top.
Copyright 2012, Contributors.
Licensed under the New BSD license.
The repository can be browsed online:
The latest stable released version of the code is available via Subversion from:
Or if you want the latest version for development purposes:
In the functional specification we describe what the project does.
The jj5-win project is broken into discrete 'utilities'. Each utility does something different, but all utilities in the project are available in the same way. Basically a utility has a command in the 'bin' folder that runs the command interactively. Some utilities also have installers for configuring the utility to be available as part of the Windows Shell, available via Windows Explorer context menus for instance. Generally you should put the 'bin' folder in your %PATH% environment variable and then you can run utility commands from the command line by invoking them with their name, e.g., 'simchar' or 'delfiles'. Documentation for each utility is provided separately and each utility is essentially a subproject.
The simchar utility helps work with ASCII characters that are similar in various ways. For instance characters that look similar, or sound similar. Also characters that aren't as common and thus people might not know a name for, such as hat '^' or tilde '~' or pipe/vertical-bar '|' or hash/pound/number '#'.
The intent of simchar is to find sets of characters that will not be confusing to users. The idea being that numbers encoded in such character sets will result in less confusion and less mistakes and therefore aid in higher productivity.
See simchar technicalities for technical information about how simchar works.
Run the simchar help command for syntax and available commands, e.g.:
C:\Documents and Settings\jj5>simchar help simchar: show's similar and distinct ASCII characters. Syntax: simchar OPERATION OPERATION: read, for characters that are safe to read. hear, for characters that are safe to hear. know, for characters people probably know. safe, for characters that are readable, hearable and known. code, for characters that can be used for codes.
The idea with delfiles is that you give it a path to a directory and it will go through the entire subtree deleting any files (but not directories) that it finds. So you can clear out all the files in a subtree and leave the directory structure in-tact.
I use delfiles when I'm upgrading a Subversion working copy with a new vendor drop. For example, say I download a new release of MediaWiki. I have the web directory of the jjwiki project checked out into a working copy in C:\Inetpub\wwwroot\jjwiki\web. I run delfiles on C:\Inetpub\wwwroot\jjwiki\web and it clears out all the files from the working copy. I then copy the latest files from the MediaWiki tarball into C:\Inetpub\wwwroot\jjwiki\web and the files are restored with the latest copy. But any files that have been removed from the latest version of MediaWiki will also now be missing from the working copy. So when I checkin the working copy TortoiseSVN will figure out that the missing files are to be deleted from the repository, new files are to be added, updated files to be updated, and anything else stays the same.
Pretty handy, huh?
See notes for implementers for installation/configuration instructions.
See delfiles technicalities for technical information about how delfiles works.
Once delfiles is correctly installed on your system you run it by right-clicking on a directory in Windows Explorer and selecting "Delete Files" from the context menu. However, if you don't install it, you can still run it from the command-line by running bin/delfiles.cmd and passing the folder you want to delete all the files from as the first argument.
This utility lists files in the current directory or any subfolders and sorts them according to their file size. Handy for finding big files on your system.
In the technical specification we describe how the project works.
The jj5-win system contains a 'bin' folder which comprises the interface to all jj5-win software. Basically each jj5-win utility should have a corresponding cmd/bat/exe file in the 'bin' folder that acts as the interface to that component. For example the interface to the 'simchar' utility is bin/simchar.cmd, and the interface to the 'delfiles' utility is bin/delfiles.cmd. The commands in the bin folder are assumed to be interactive, that is they are are assumed to have been run by a user from the command-line.
Generally the interactive command scripts do some minor processing of input and then defer the processing to a non-interactive command file in the utility's subfolder. For instance the interactive bin/simchar.cmd command defers processing to the non-interactive command email@example.com, and the interactive bin/delfiles.cmd command defers processing to the non-interactive command firstname.lastname@example.org. As you can see each jj5-win utility typically has a subfolder in the 'bin' directory named after the utility, e.g. bin/simchar/ for simchar and bin/delfiles/ for delfiles. This is called the "utility folder" and that is generally where the bulk of a utility's software is found.
The convention I use for interactive vs. non-interactive scripts is that a non-interactive script is named with a leading '@' character. Non-interactive scripts exit the command processor with an error level whereas interactive scripts do not exit the command processor, rather they just report to the user via stdout and pause on error.
Some "non-interactive" scripts still interact with the user. For example the non-interactive @delfiles.cmd script will still popup a message box asking the user to confirm that they really want to delete all of their files. I have no need for a truly non-interactive version of @delfiles.cmd so I haven't implemented one. If you really want a version of this utility that doesn't confirm that you want to delete all of your files then feel free to patch your own copy of the code. I'm crazy, but I'm not that crazy.
Note: it might be curious to some of you that having been a programmer focused predominantly on Microsoft technology for over twelve years that my Windows utility scripts project only has two utilities in it. I mean, what have I been doing for the last twelve years!? Well, that's a good question. The answer is that I have hundreds of Windows utility scripts that I've written, but they have all been managed in my company's private repository. Only as of 2012 have I finally got the infrastructure in place to begin sharing my code. As I have the need to write more Windows utility scripts in the future I think you can feel assured that they will generally be implemented as components of this jj5-win project. Another thing to bear in mind is that personally and professionally I have spent the last four or so years moving away from Microsoft technology towards open-source alternatives such as Linux. Thus my jj5-bin project, which is the complement of this jj5-win project, where I keep my Linux utility scripts, is already considerably more feature rich than jj5-win. I expect I will continue to get more work done for my Linux jj5-bin project than I do for my jj5-win project, but I'm still a pretty big fan of Windows (XP, I ain't upgrading) on the desktop so my involvement with Microsoft technologies isn't over yet, thus, I will have call to implement a Windows utility from time to time.
The delfiles utility can be run from the command-line passing the path of the folder you want to delete all files from as the first argument to bin/delfiles.cmd. The delfiles utility can also be installed so that a folder context menu "Delete Files" is available in Windows Explorer. To install delfiles you run the bin/delfiles/install.cmd script which will generate a VB script file that will configure your Windows registry with appropriate values for specifying the folder shell context menu item. The VB script installer defers to the RegWrite interface available on the WScript.Shell ActiveX component and writes a registry entry for delfiles into "HKCR\Folder\Shell\Delete Files". After creating and running the VBS installer the install.cmd script deletes the VBS file and cleans up after itself. I guess it's a bit dodgy that the installer just works out of the current directory rather than %TEMP% or %USERPROFILE% and if I cared enough about that I would fix it. :P
The delfiles installer defers processing of the specified folder to the non-interactive command email@example.com, thus you will see a cmd.exe window popup when you run Delete Files from Windows Explorer. If you wanted to you could probably change this easily enough so that the delfiles.js script was run directly in wscript.exe from the context menu and then there would be no such cmd.exe window visible during processing. Again, if I cared enough about this I would fix it. :P
Notes for implementers
If you are interested in incorporating this software into your project, here's what you need to know.
Firstly, feel free to ask questions if something is unclear or missing.
Secondly, at the moment there is no downloadable tarball/zip file, nor is there an installer. To get the software you need to grab it from svn.
On my systems I have a 'util' folder in G:\data\util. The 'util' folder is a Windows share also called 'util'. I map the 'util' folder to the U: drive with the following command:
net use u: \\bender-xp\util
Note: in this case my machine name is 'bender-xp', you would use the name of your own computer if you were following my standard. Note also that it's not important where the 'util' share is actually located, it doesn't need to be in G:\data\util as long as wherever it is it is shared as 'util'.
Now I have a U: drive. In the U: drive I create a folder called 'jj5-win'. I right-click on that folder and use TortoiseSVN to checkout the latest stable release of jj5-win from Subversion:
I then edit the %PATH% environment variable, by clicking through:
Start -> Right-click My Computer -> Properties -> Advanced -> Environment Variables -> System Variables -> Path -> Edit
Then in the "Variable value:" textbox prepend the text:
If you have any cmd.exe windows open you will need to close them and reopen them to get the new value of the %PATH% variable. Your path will now include the jj5-win commands.
After you have installed jj5-win you can install delfiles. When delfiles is installed it will add a context menu item called "Delete Files" to folder context menus in Windows Explorer. To install delfiles run:
Be careful with this command because it can delete all your files!
Notes for developers
If you're interested in contributing to this software, here's what you need to know:
For security reasons write access to jjrepo is only available for John. It's basically my private repository. If you'd like to hack on projects where you do have checkin permissions on the Subversion repository, along with infrastructure for running your code, then why not head over to ProgClub and register?
Configuring a development environment
I keep my source code on a partition mounted on the K: drive, which I call my KODE drive. Cheesy, huh?
I keep my jj5.net projects in:
So I create a folder in the 'jj5.net' folder called 'jj5-win'. I.e.:
I then use TortoiseSVN to checkout the jj5-win trunk, being:
That's pretty much it. Because I have a 'production' version of jj5-win installed on my development environment per the instructions in addition to the development code if I want to run the development version of my code I need to change directory into the development jj5-win/bin folder before running a command, e.g.:
cd /d K:\jj5.net\jj5-win\bin
If you run an installer from the development working copy, such as jj5-win/bin/delfiles/install.cmd, then your system will be configured to run the development version of your code. If you did this and then later wanted to revert your setup back to using the production version of the code then you would run the corresponding installer from the production folder, e.g. U:\jj5-win\bin\delfiles\install.cmd.
Releasing a stable version
Releases of jj5-win can only be done by John. To do a release run the jjrepo-release script from either empathy or orac. E.g.:
jj5@orac:~$ jjrepo-release jj5-win
After you've done a release don't forget to update the release notes.
Release notes are (supposed to be) added after notable releases are made. New release notes are added to the bottom of the release notes section and have a level 3 title based on the release date.
Things to do, in rough order of priority:
- Simchar coding.
- Add a 'long' classification for characters that take a long time to say, e.g. '!' as 'exclamation point' or '?' as 'question mark'.
- Add a 'case' operation to simchar for characters that aren't confusable in either upper or lower case.
Stuff that's done. Latest stuff goes on the bottom of the list.