Commit Graph
10 Commits
Author SHA1 Message Date
Thunderforge 375325ca94 * DATA: Changing YAML to Flathub style guide
With YAML being a very flexible format, it would be good to have some consistency with how it is formatted. Flathub is a pretty commonly used repository and has good YAML guidelines, so I think it's good to reflect them.
2020-04-04 17:36:23 -05:00
Thunderforge 73958c69d5 BUILD: Standardizing the variable names for parsing data
Fixes the following Codacy issues:

* Avoid variables with short names like `$a`. Configured minimum length is 3.
* Avoid unused local variables such as '$key'.
2020-04-03 13:47:28 +02:00
Thunderforge 3ca1160ca8 DATA: Removing $key to satisfy Codacy 2020-04-02 23:04:54 +02:00
Thunderforge 92a2c4cde0 DATA: Changing $a to $gameDemos to satisfy Codacy
Not sure why this wasn't flagging the old code, but whatever
2020-04-02 23:04:54 +02:00
Thunderforge 2f2a432581 DATA: Converting Game Demos page to YAML
Since it appears that #110 will require compatibility data to be changed from XML to YAML, I wanted to practice and change a simpler page from XML to YAML. If merged, I'm willing to convert other pages as well (e.g. Links, Press Articles, Screenshots, FAQs) as well
2020-04-02 23:04:54 +02:00
Matan Bareket 97262c4b2f WEB: Convert require statements to psr-4 style use statements 2019-01-22 19:49:58 -05:00
Matan Bareket 85328f2997 WEB: Use PSR-4 autoloading 2019-01-22 19:49:58 -05:00
Matan Bareket cfbeebb8dc WEB: Add namespaces to all PHP files 2019-01-22 19:49:58 -05:00
Matan Bareket 851bb41bb7 WEB: Auto-fix to PSR-2 standard 2019-01-22 19:49:58 -05:00
Eugene Sandulenko d429c48de0 Website rewrite from Fredrik Wendel
svn path=/web/trunk/; revision=40814
2009-05-23 18:45:30 +00:00