Click here to Skip to main content
15,885,365 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
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)?
Posted

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
 
Share this answer
 
Comments
Nelek 13-Nov-12 16:36pm    
Op answered to you and richard in solution 3
Sergey Alexandrovich Kryukov 13-Nov-12 17:32pm    
Thank you, Nelek.
I copied this post as a comment and removed the "solution", which I recommend to do in such cases.
--SA
Nelek 13-Nov-12 17:38pm    
You are welcome. I usually do it as well, but as it was for more comments I didn't want to repeat it. Next time I'll do as always and done ;)
Sergey Alexandrovich Kryukov 13-Nov-12 17:54pm    
This is great. Thanks again.
I notified Richard and warned OP against false solutions, it should help...
Cheers.
--SA
Sergey Alexandrovich Kryukov 13-Nov-12 17:27pm    
[OP commented:]

I am going to keep it together and add a 'table of contents' near the head of the article so folks can jump to the 'events', 'disk change notification', or 'file change notification' elements of the article, or read through the application notes and then into those other items.

Thanks for the suggestions guys.
If it's already complete in one part then post it and see what comments or suggestions you receive.
 
Share this answer
 
Comments
Sergey Alexandrovich Kryukov 13-Nov-12 17:31pm    
[OP commented:]

I am going to keep it together and add a 'table of contents' near the head of the article so folks can jump to the 'events', 'disk change notification', or 'file change notification' elements of the article, or read through the application notes and then into those other items. Thanks for the suggestions guys.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900