Skip to content

jreeee/awccccpp

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

15 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Disclaimer: this project is neither affiliated with AniList nor AWC

Disclaimer 2: This is currently in a non-functional state as i am working on building up the structure first

awccccpp / aw4cpp

aw4cpp (AWC Challenge Checker C++) is a redesign of my older project awccc.

goal

similar to awccc, aw4cpp aims to help you fill out AWC Challenges by adding dates and checking if chosen entries fit their given requirement. additionally i want to implement a overview that displays the progress for all ongoing challenges.

why rewrite and not fix the old app?

awccc is written in Python and was more like a proof of concept than a proper application, with that the overall design of the app more or less hacked together. while it generally works there are some big limitations e.g. it being rather slow, checking only card-links, and a couple more.

with aw4cpp i want to design my software properly and have a fast and reliable tool for my challenging endeavours.

dependencies

to work properly, (lib)curl is needed

(and a working internet connection at least initially)

this app includes two libraries:

both can be found in ext/ and are not submodules.

json because it can be used as header-only

curlpp as i had to change the include in curlpp/include/curlpp/Form.hpp from <utilspp/clone_ptr.hpp> to "../utilspp/clone_ptr.hpp" for it to compile and other stuff that breaks with new libcurl versions like CURLOPT_CLOSEPOLICY

build

i plan to include executables when this is in a better shape...

$ mkdir build && cd build
$ make 

next steps

now that i have the first steps for the general structure, coming up are:

prio

  • have it build on linux and windows (idk about mac)
  • storing a basic config with the username
  • creating a list of all (currently available) challenges
  • retrieving the users anime list (for now just the "Completed")
  • retrieve the created challenge posts
  • simple CLI interface that shows the progress for challenges based on entries added (and completed)
  • set up proper chaching for all the data required

soon

  • figure out license stuff
  • retrieving and parsing the completed challenges from awc.moe
  • create a ruleset for all (available) challenges
  • modify a challenge post by adding all the dates

at some point

  • parse challenge posts and check with challenge rules
  • parse reqs and check with AL
  • generate a overview of all challenges, similar to the gist i use mb with html and a bit nicer

endgoal

  • can automatically backfill challenges
  • can recommend stuff for reqs

About

Trying to redesign & rewrite awccc in c++

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages