ffig explorer product roadmap

[petr-tik]

I want to outline my vision of ffig explorer and get your thoughts on this, so I can plan and implement GitHub issues accordingly.

Product

A web application served on the ffig.org site with 1 header file input window and automatically generated panes for bindings.

Use cases

Paste a C++ header file, choose which bindings you need, click a button -> view generated bindings side-by-side

Necessary work

API

Finish and deploy v0.1 of the API - deployment options discussed in #24

Front end

Add javascript to the ffig.org source. The JS will render text editor, send and receive XHR requests to the FFIG explorer api

Future use cases

Sharing URLs - future work - like compiler explorer

Necessary additions

Key-value storage for links -> header file + requested bindings

What do you think @jbcoe @ajbennieston? Am I missing something?