Thread: Testers wanted - archiving tool.

Actually I want to stay up working. I just made one more minor modification to it: I noticed while archiving it throws out a list of what it's about to add before it adds them, which is a bit misleading plus you couldn't tell whereabouts it was with progress. Now it's like extraction, I.E. lists the files as it processes them.

Same linky as before.

Tragically Poor Excuse for an Update

It's just ticked over midnight here and the only thing keeping my eyes open is the sound of RHCP up full blast ( headphones of course ).

I've just added an extremely preliminary, disgustingly crappy GUI. Ignore it all except the "Creation" mode button and the two associated edit boxes ( nothing else works ). Oh no, I lie, the "Enable Large Files" checkbox works ( it throws you a warning if you create with it checked ) but actually doesn't do anything because I've just remembered, I left out the call to flip the flag. God darn it.

Anyway, run it, laugh at it, laugh at me. I'll be back in a few hours ( like 9 ). Tomorrow I'm almost certainly going to do the GUI again from scratch anyways.

'luka, out.

Well if you're not doing anything else, sure, MFC it. I'd like to see code for that too ( I will get a copy of the source code, right? ) since I should start learning MFC.

Quick Update

Now you don't have to worry about directories - when it finds one it omits it instead of trying to add it like a file. Go forth and archive your desktops!
Oh and I've removed the GUI - we're back to a command prompt

long live the command prompt!

I'll be testing more of it this afternoon.

Then I've got some extra work to do. At the moment it takes a path to a directory and sucks up every file inside it. I'll get the creation function to accept a vector of std::string's and load each file from the path specified in each element instead.

I'll post up here when I'm done ( or catch you on MSN ).

Well this can be done several ways. We can create a temp folder in the app folder and use that as the archive folder. This means I must copy the contents of each file into that folder which is probably not the fastest solution.

Or I can write the output of what belongs in a file to a temporary text file. Ill pass the text file filename to your code and you can simply read in each line, open the files, add to archive buffer, and write out final buffer when done. When you return from your CreateArchiveFromFile() function I'll delete the text file.

The best approach would be for you to stick your code into a DLL and I'll load it dynamically with LoadLibrary() and then use GetProcAddress() to get pointers to your functions. That way if you want to change how you implement the archiving you just change the DLL and it won't break the front end GUI.

Then to install the 'patched' DLL you simply use Setup and Deployment wizard and use your DLL file as the main output. This will effectively replace the DLL that was installed previously with the new DLL. It also ensures that people have the latest code updates for your program yet also ensuring them you are not writing ten zillion dlls on their drive.

Well I finished the new CreateArchive() which now accepts a vector of std::string's. I'll write another function, ParseFileList() which'll read the temp text file and add each line ( filename ) to a vector and pass it onto CreateArchive().

I'll DLL it now and email you the header.

Hmm gimmie a day to go over this, it's a mess.
Plus for reasons unbeknowest to me, it's only outputting the .lib and .exp, no .dll. I'll start a new project ( this was a SUBSYSTEM:CONSOLE till I switched it and it doesn't seem to like it much ).