We have a number of users spread across the globe that do editorial work on batches of text files. In order to homogenize the method for distribution and hence the general workflow, there is a project under development.? Part of the whole is a module, to be installed on Windows workstations (XP or Vista), that is capable of viewing, opening and extracting downloaded archived files to a specific hardcoded directory/subdirectory. The archived files are text files combined into packages and will be named accordingly in a unique manner. The purpose of the packaging is fundamentally part of the check-in/check-out system required by the workflow. Each package may contain at least one such file and usually more than two.
The project should be completed in C# (alternatively VB.NET will be considered).
## Deliverables
The modules workflow should be
1.? A list of files of a specific type in a specific folder on the user’s hard disk.
2.? The opportunity to select one or more of these files (packages).
3.? The selected packages must then be extracted into the individual files (contents) and to a specific folder.
4.? Once extracted the packages/archives must be deleted from their original location.
Further information
The UI design is inconsequential, should however adhere to usability standards as provided by major developers.
The format of the packages is as yet undefined. It is assumed that the easiest and most cost-effective method possible will be used (one example is CabPack to be found at <[login to view URL]>? Please note that the unpacking of whatever format is used must occur without any user input beyond the selection of the packages to be unpacked.)
The project/module should be completed in C# or [login to view URL] package/file selection should be as intuitive and clear as possible. For want of a better illustration, we envisage two list boxes, one with the folder contents and one with the selected items.
The extraction of the packages may be done in whatever fashion is adequate. Some of the text files are quite large.
Well documented and clearly formulated source code must be delivered in its entirety. We expect the code to be easily readable by intermediate C#/VB.NET developers.
Although not essential, it would be an added bonus if the project were developed in VisualStudio2005/2008 and delivered as a solution.
Should example text files be required, these can be made available.