arelate / vangogh Goto Github PK

Current linear format has outgrown itself - we'll use 2.0 as an opportunity to break free from legacy and introduce new more structural data schema.

Details TBD.

ERROR - red, SUCCESS - green, WARNING - yellow

• remove svg and add fa.woff to the project
• split javascript files
• improve DLC section - create the list first then create DLC
• improve product files section - create the list first and avoid dupes
• show loading thumbnail for product images
• improve search
  -- block until we can be sure it's fluid
  -- don't reload the page, preserve search value and results on details <-> list transitions

When updating product files - need to make sure that any product files versions that are not current needs to be deleted, otherwise we'll keep adding files without removing (unless manually)

Currently name only, but shouldn't be a problem to add code as well

Also make this a component that download controller can use

Suspect cbdc5ec regressed this

https://www.gog.com/support/support_view/twostep_login_faq#en

Program.cs has accumulated too much special logic, need to refactor:

• abstract downloads from any other actions (through new download controller, that should be used for images, files, json data)
• register download tasks from product to allow reporting
• abstract all throttling logic to some controller
• unify reporting through event model
• all worker controllers would implement general interface and Program.cs just iterates over collection of workers, passing data as needed

Catch up with all latest code changes

• Parse all properties in JSON files
• Where we don't do fixup - serialize deserialized data and compare with raw source to highlight potential data schema changes (e.g. new properties we don't store yet)
• Start downloading https://api.gog.com/products/{{id}} data

Supporting partial downloads (partial as in "per chunk")
Concurrent downloads per chunks
Validation per chunk

Something I don't plan to fix, but want to capture details here. The way GOG does regionally priced products is creating separate products with different ids. There is Product entry for it that maps to ProductData and another one for GameDetails that has different id. To mitigate this for purposes of marking products owned, updated, wishlisted, etc. I've been using "bundles" where I bundle product and gamedetails object together (see Quake series as example). However this won't work for DLC currently as there is no good way to track DLC that is regionally priced (that means it's id would be different from ProductData id) and doesn't have id in GameDetails. Potentially I could use title comparison to understand whether this is owned, but I currently don't plan to do anything about it. Known product affected is Frozen Synapse: Red - and there is no real functional impact - files would be downloaded, DLC would be shown under Frozen Synapse (just without image or details, since I can't map this to ProductData).