Age | Commit message (Collapse) | Author | |
---|---|---|---|
2024-03-19 | Definition Parser now consumes from the new Reader | Aki | |
Next steps are to move ParseUtils functionality to DefinitinoEx, sort things into the namespaces in this library, and then prepare it to handle overloading like nlohmann_json does. On the other side, it's time for starshatter::data. | |||
2024-03-07 | Added gtest to the project and a stub test for showcase | Aki | |
2024-03-06 | Limited uses of zlib to just ArchiveEx | Aki | |
This coincidentally fixes the issue with exceptions not getting caught correctly resulting in unexpected game/server terminations. | |||
2022-10-17 | Naively added components to install targets | Aki | |
2022-09-17 | Path normalization will now remove cwd from relative path | Aki | |
2022-09-16 | Fixed archive entry path on WIN32 | Aki | |
2022-09-11 | Replaced Datafile and StarsEx/Archive with dat and ArchiveEx | Aki | |
2022-09-11 | Archive Find is now case insensitive like originally | Aki | |
2022-09-11 | Added method to retrieve amount of entries in archive | Aki | |
2022-09-11 | Fixed WIN32 build of dat | Aki | |
There might be small differences between option handling and fnmatch vs. PathMatchSpecA, but that's understandable. | |||
2022-09-11 | Moved FilterFile around | Aki | |
2022-09-11 | Listing option now accepts pattern filtering like extract | Aki | |
2022-09-11 | Extracted fnmatch filtering to a higher-order func | Aki | |
2022-09-11 | dat will now extract all files if no patterns are provided | Aki | |
2022-09-11 | Fixed extracting files to current working directory | Aki | |
2022-09-11 | Fixed handling return value of create_directories | Aki | |
2022-09-11 | Implemented file extraction in dat utility | Aki | |
2022-09-11 | Extended dat update action with recursive behaviour | Aki | |
2022-08-20 | Added options to inspect archive content in dat utility | Aki | |
Old PrintX methods were replaced by higher order functions ForEachX that are intended to give slighly more granual control and move the responsibility of what actually happens to the user without introducing a whole iterator. | |||
2022-08-20 | Added stub of CLI utility for handling archives | Aki | |
This will eventually deprecate Datafile | |||
2022-08-20 | Merged on-demand Archive creation to constructor | Aki | |
2022-08-17 | Renamed ArchiveEx namespace | Aki | |
2022-08-17 | Hid Header definition from public archive header | Aki | |
2022-08-17 | Added function to create an empty archive | Aki | |
2022-08-11 | Renamed block map generation method | Aki | |
2022-08-11 | Renamed Insertion and Extraction methods | Aki | |
2022-08-11 | Code now consistently uses unique_ptr for arrays | Aki | |
Now, I realize this is a rather interesting choice. I want them to be consistent. In case of extraction the array gets released as part of the legacy interface. Because of this std::vector is out of question. All other cases could use it, but they all have the same start and purpose. Only that one differs and I don't like making it unique (pun intended). | |||
2022-08-11 | Implemented inserting entries into archive | Aki | |
2022-08-11 | Fixed null-terminated extraction | Aki | |
2022-08-09 | Added methods to inspect blocks in the archive | Aki | |
This actually yields predicted tendency to leave a single unused block at the start of the archive in case where directory starts to need more blocks and none of new files can fill it in. Interestingly it also shows a long sequence of unused blocks just before the directory that is right at the end of the archive. The cause for that can be pointed out in original implementation of FindDataBlocks method. | |||
2022-08-09 | Cleaned-up selected parts of newly added code | Aki | |
2022-08-08 | Added a functionality that enables extracting files by their path | Aki | |
2022-08-07 | Added method to expand stored files | Aki | |
2022-08-07 | Reimplemented part of archive format | Aki | |
This is getting reimplemented rather than refactor mostly in order to make clear which parts are needed for backwards compatiblity (reading-wise) and which are not. The current implementation has quite a number of quirks and potential failure points despite not being large. Understanding them is not worth it. |