On itchio/itch@f9251ed | https://github.com/leafo/itchio-app/blob/f9251ed9a789e6c332223ddfc743abdf902457be/itchioapi.cpp#L78

New code gives compile error:
<itchioapi.cpp:78: error: no matching function for call to 'Game::fromJson(QJsonObject)'>

@MScottMcBee

After downloading a game the "Download" button should turn into a "Run" button. For the initial release we'll try to guess which file needs to be run, but I think in the long term the game developers should be required to provide a manifest file on itch.io site that instructs the app on how to start a game for certain platforms.

The logic could be simple like:

• If the downloaded file is an executable, execute it
• If the downloaded file is an archive, extract it
  • Search for an executable in the archive, if there is only one, run it
  • If there are multiple executables, present user with choice to pick one. Remember choice.

This doesn't really take into account games have their own installers. I think for the initial release it's okay to just run the installer, and then the user is responsible for running the installed game afterwards.

We also need to figure out to extract files reliably cross platform, does this mean bundling a zip binary with the installation? What about other formats? Should we require archives to be zip?

As of #12 a basic system tray icon is there for keeping the application running in the background.

The system tray should be used for notifications of events as they are added:

• System notification when a new version of a game is out
• System notification when a download finishes
• System notification when library updates

As more screens are added menu entries should be added to the context menu on the tray icon to navigate to those screens directly.

It would be nice to have a way to browse the collections you've created, and then download the games in them. Then will let you bring any free games you're interested in into the app.

If you buy a new game on the site the app should update it's cached list automatically (and possibly show a notification in the system tray #3)

There are a few ways to do this, some sort of persistent socket connection. Or polling. I think polling is fine because it requires no new services on the backend. It doesn't need to be real time, maybe once every minute?

Game downloading needs to be coded. For the initial release it will be done over HTTP. There should be a simple progress bar. If a download fails, then it must be canceled and started over. Files should be downloaded to QStandardPaths::​writableLocation and a manifest file should be written.

By default the user shouldn't have to pick which file is downloaded. An API call for the game's files is done, then if there is just 1 file that matches the platform it will be downloaded. If there are multiple files for the given platform, or there are no files for the platform then a file can be manually chosen by the user.

To download a given file, an API call is made with the file's ID and an expiring URL is returned.

Games can optionally have install instructions written as text provided by the developer. We could show these after the download completes?

None of these APIs exist yet, I'll post them here with docs as they become available.

Right now the app only shows games that you have purchased or been gifted. itch.io makes the destinction between purchases/gifts vs download keys that have been claimed. Here's a new API call, very similar to my-owned-keys, that returns owned keys.

I'm thinking for simplicity we'll keep the distinction in the app, and just have a new tab for claimed keys.

GET /api/1/:api_key/my-claimed-keys

{  
  claimed_keys:[  
    {  
      updated_at:"2014-04-14 18:32:30",
      id:24234,
      downloads:0,
      game_id:3,
      created_at:"2014-04-14 18:25:16",
      game:{  
        p_android:false,
        id:3,
        p_osx:true,
        min_price:0,
        created_at:"2013-03-03 23:02:14",
        published_at:"2013-03-03 23:02:14",
        p_windows:true,
        url:"http://leafo.itch.io/x-moon",
        title:"X-Moon",
        cover_url:"http://img.itch.io/aW1hZ2UvMy8xODM3LnBuZw==/315x250%23/y2uYQI.png",
        short_text:"Humans have been colonizing planets. It's time to stop them!",
        type:"default",
        p_linux:true,
        user:{  
          url:"http://leafo.itch.io",
          username:"leafo",
          id:1,
          cover_url:"http://img.itch.io/aW1hZ2UyL3VzZXIvMS8zODEzNi5wbmc=/100x100%23/fsSoF5.png"
        }
      }
    }
  ]
}

This is mainly directed at @Zetsaika

So I think this project got off to a good start, but as I learned more of QT I started to realize that the cost of not being familiar with the platform is quite high. I'm worried that it's going to be really difficult to get this finished an polished on QT. And even if we do get it out, it will be difficult to maintain.

I'm considering transitioning over to nw.js or electron to build the app.

This would mean abandoning all the code we have and starting fresh.

The advantages are: a familiar platform, html/css/js, and the potential to reuse styles and assets already built on the main site.

The disadvantages are abandoning the work we've done. And potentially something with a bigger binary size and more memory usage.

I don't mind putting aside what I've coded, but @Zetsaika has also written a lot.

Tell me what you think.

Right now, itchio-app has no license at all, which generally means that default copyright laws apply and people can't do anything with the code. This is probably not what you want.

Please consider choosing an appropriate free software license and denoting the license in the source tree by:

• Adding a LICENSE / COPYING text file to the project's root
• Mentioning the license by name in the README.md
• Ideally adding copyright / license information header comments to each source file

Thanks.

Need to fetch owned games from user's library with an API call that returns the games on this page: http://itch.io/my-purchases

Post screenshots of other downloading apps (game or non-game related) for ideas and inspiration in the comments please
#1 brought some visual updates to what's already coded, but I figure some thought should go into designing the various dialogs both visually and how the user interacts with them. Here are the following views that are planned (so far) and the corresponding page on the site.

• Log in http://itch.io/login
• My collections http://itch.io/my-collections - #9
• Game listing http://itch.io/my-purchases - #6
• Game files http://leafo.itch.io/boyfriend-simulator-feed-my-boyfriend/download/4nZiJ9C72U21B8dQ5IZMeya9xn94446G1pq96Cny
• Application settings - for controlling things mentioned in #5

Each one of these doesn't necessarily have to be a separate screen but should minimally be incorporated somehow.

We need scripts to download dependencies to 'Project Folder/dependencies. See: 49d1186

• Windows
• Linux
• Mac

-- old --

Following the site style, i got the free Lato font, http://www.latofonts.com/lato-free-fonts/ for use in the app. But, i am not really sure how to put it in the project.

Should we just put a link in the readme for people who would like to work on the app to get? Put it in the repo along with the license file(open font license)?

I am not really familiar with this situation.

cc @leafo

After you've downloaded a game, you should be given the option to update the game if new files become available. This is going to be tricky because itch.io currently doesn't have versioning for files uploaded. But, it could be as simple as just looking to see if there are uploads with ID's greater than what was there at the time of the download for the given platform.

When a game is updatable the UI should show it, and it should give you an option to update. The same logic for game downloading can be done to find the file to download (but it can exclude files that have already been downloaded) #4

Before this app is deployed, there really should be a proper login API call that accepts encrypted user info.

Things like game cover should be put in a cache to prevent server overuse.

An abstraction on top of QSettings should be made with methods for common actions for saved data:

• Logging in, the API key should be cached into user settings, password does not need to be stored
• Whether to automatically check for updates
• Whether to show desktop notifications

A settings dialog will probably need to be created with a few toggles.