Skip to content
RePod edited this page May 9, 2016 · 16 revisions

PSDLE is a JavaScript... something.
It does a lot of great things to enhance the download list.

Have you read the Enhanced Filtering page to fully utilize PSDLE's filtering options?

Why JavaScript?

  • Portable
    • Anything that can access the store and execute JavaScript will most likely be able to run PSDLE.
    • Theoretically the consoles themselves too, if they could access the store from their respective browsers.
  • Scalable
    • The Userscript (Greasemonkey/etc) and Chrome extension use the exact same code.
  • Web-oriented
    • Leveraging jQuery and the store's environment makes everything easy.
    • There's less of a security risk since PSDLE does not need login info or unfamiliar web browsers/programs.

Some Personal Coding Restrictions

  • No data saved, be it cookies or local storage.
    • A lot of neat things could be achieved by storing information, such as quicker Catalog lookups or personal settings persisting between sessions. I do not want to ever facilitate or imagine being responsible for a security flaw involving them.
  • No external resource/URL fetching.
    • Simple: only use what the store provides and provides itself. While even more neat things could be achieved, such as fetching Metacritic scores, inlining YouTube videos, or fetching staff information, I don't want to be held responsible or even considered such when problems about security arise.

The good thing about these coding restrictions, however, is they're quality of life for and against users. What is lacked in exciting features is made up for in peace of mind knowing PSDLE does its thing while not compromising itself.