claunia/SabreTools
1
0
Fork 0
mirror of https://github.com/claunia/SabreTools.git synced 2025-12-16 19:14:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

[README.1ST] Clarity

Browse Source
This commit is contained in:
Matt Nadareski
2017-05-04 09:31:25 -07:00
parent 7316931271
commit c68e6dbc8d
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
SabreTools.Library/README.1ST
View File

@@ -15,20 +15,20 @@ Table of Contents
** Section 1.0 - Introduction and History ** Section 1.0 - Introduction and History
*** History of the Project
Hello and welcome to the latest release of SabreTools! We are happy that you Hello and welcome to the latest release of SabreTools! We are happy that you
chose to use our software for your DAT management needs. But what exactly is chose to use our software for your DAT management needs. But what exactly is
SabreTools? How did it get started? Why is it named so weirdly? Why should we SabreTools? How did it get started? Why is it named so weirdly? Why should we
care? Well, the first two can be answered, though the last one is up to you. care? Well, the first two can be answered, though the last one is up to you.
*** History of the Project
SabreTools has its roots in an internal tool developed by RomShepherd member SabreTools has its roots in an internal tool developed by RomShepherd member
The Wizard of DATz (WoD). The aim of the PHP-based program was to collate data The Wizard of DATz (WoD). The aim of the PHP-based program was to collate data
from multiple sources and create new DAT files for custom sources as well as from multiple sources and create new DAT files for custom sources as well as
DAT files that have duplicate data removed, called merged DATs. WoD maintained DAT files that have duplicate data removed, called merged DATs. WoD maintained
this software and used it to create near-monthly releases for quite a while. this software and used it to create near-monthly releases for quite a while.
Around the middle-end of 2015, WoD announced that they would be taking a break Around the middle-end of 2016, WoD announced that they would be taking a break
from the process of creating and releasing new files. A couple of months went from the process of creating and releasing new files. A couple of months went
by with no information. Finally, WoD finally told the community that they would by with no information. Finally, WoD finally told the community that they would
no longer be able to maintain either the project or the software involved, no longer be able to maintain either the project or the software involved,
@@ -47,7 +47,7 @@ Numerous other features and pages were added over the next month, progressing
toward more a more mature codebase. DAT parsing ended up being the main barrier toward more a more mature codebase. DAT parsing ended up being the main barrier
during that time, leading to many frustrations. RomVault was used as the basis during that time, leading to many frustrations. RomVault was used as the basis
for DAT parsing quality, leading to a mock rivalry and darksabre76 dubbing it for DAT parsing quality, leading to a mock rivalry and darksabre76 dubbing it
"project nemesis" of wizzardRedux. These have long since been cleared up but the "project nemesis" of WoD Redux. These have long since been cleared up but the
rivalry still stands. This original project can be found at rivalry still stands. This original project can be found at
https://github.com/SabreTools/wizzardRedux. https://github.com/SabreTools/wizzardRedux.
@@ -61,7 +61,8 @@ out as the first official release. Pretty soon, this got even more support than
the web version and soon became the main focus. For a while, code parity between the web version and soon became the main focus. For a while, code parity between
the two versions was attempted. It became quickly apparent that the desktop the two versions was attempted. It became quickly apparent that the desktop
version was going to be the better option due to the higher accessiblity and version was going to be the better option due to the higher accessiblity and
willingness to be tested. willingness to be tested. This project is currently hosted at
https://github.com/SabreTools/SabreTools.
Development accelerated, soon leaving the PHP version in the dust. Once the Development accelerated, soon leaving the PHP version in the dust. Once the
basics were implemented, more features were requested, including better merging basics were implemented, more features were requested, including better merging