I am uploading my first attempt at a project article and I would appreciate some advice.
The project is a mature bulk/batch file renamer. It contains code to sense when a drive is mounted or dismounted so that the drive list is always up to date. It also contains a 'file(s) changed' sensing class to keep that display list up to date. It has a better user interface and more choices on prefix, suffix, infix with add, delete, and replace values supplied by the user. It also has a preview column next to the 'current' column so you can see the effects before you execute.
I am currently writing an article covering the entire project with not a lot about the fairly mundane code for spinning through a file list and changing the names. Instead I have spent more time explaining the processes for sensing drive and file changes and then how to create, raise, and consume async events.
My question is should I split this up and write shorter, concentrated articles on sensing drive changes, sensing file changes, and how to create and utilize events, or should I keep it as a whole (or all of the above)?
I would prefer to read in one source. You are not limited by the volume. In the article content and table of content, divide the article in two distinct parts: on the utility and the technologies, and in the second part, write sub-division of handling of drive and file changes. This is up to you though, but in all cases, preserve cross-reference between different parts very clearly.—SA
If it's already complete in one part then post it and see what comments or suggestions you receive.
This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)