Zippie! - A simple archiving tool. banner

Zippie! - A simple archiving tool.

4 devlogs
11h 2m 7s

Zippie is a simple archiving/unarchiving tool for linux with inspiration taken from macOS' "archiving tool" in that it's out of the way and simply works.

Zippie will be essentially a wrapper for CLI tools, however its' tools will also be comple…

Zippie is a simple archiving/unarchiving tool for linux with inspiration taken from macOS’ “archiving tool” in that it’s out of the way and simply works.

Zippie will be essentially a wrapper for CLI tools, however its’ tools will also be completely customizable via a simple config file which will allow you to add whatever files you want by simply writing the command to archive or unarchive them.

koy

I was going to wait until the project was working before posting this devlog. That is not the case.

After a while of adding the lookup part of the parse function and refactoring a few things I encountered an error: the lifetime of a variable ended while it was being created. this took about three hours to solve :sob and in the end it was just me ending the value assignment with .split(), which modifies the variable in place and thus trips the compiler into thinking data was lost (I think).

And that wasn’t the end, I later wanted to commit my changes to GitHub and then realised that I haven’t moved from the master branch, which I forgot to remove from being the default on my system before starting this project. I have almost lost 90% of my progress trying to move everything but I got it sorted and now the default branch on my system and remote are both ‘main’ sighs now I have to figure out why my command are going out in the wrong format. wish me well.

have a nice 365 days,
with love,
–Koy💜

P.s. for the shipwrights, I’m sorry that I can never find anything to add as the attachment. I hope this doesn’t create a problem. (I know I’m not making it any better by adding this as the attachment but still my code doesn’t even work rn 😭😭)

Attachment
0
koy

This was a hard one. essentially all I did was parsing, which isn’t a lot, but I am still learning and honestly I’m proud of it. since the last devlog I decided to add the TOML crate instead of completely parsing it myself, and now I have reached the point where I can look it up in a hashmap (that is inside of another hashmap) . the next devlog should be the last :p

btw in case anyone actually wants to use this I will keep maintaining it for at least a while because I’m going to use it lol

With much love, –Koy

Attachment
Attachment
0
koy

in this devlog I made the logic to make/read the config file to a string, excluding placement for now.

I am starting to realise this project is not that great for logging and my inability to properly code doesn’t help either.

Anyway I decided to use TOML for the configs, though I will be dynamically parsing it into a hasmap of hashmaps. I think the next devlog will take more time (help I have nothing to show what do I do)

Attachment
0
koy

Until now I focused on getting a POC so that I will actually complete this project. Yes I have a problem, why do you ask?

Anyway until now I have a program that gets a file as input from CLI, parses it and finally unzips it because that was the easiest for me to test.
this also means there is nothing interesting for me to show so here’s a picture of rustc screaming at me (T.T)

Tomorrow I will start working on the config parsing :))
Good night!!! (if it’s night time lol)

Attachment
0