Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client/Server structure using API #80

Open
Tracked by #5527 ...
teolemon opened this issue May 2, 2015 · 1 comment
Open
Tracked by #5527 ...

Client/Server structure using API #80

teolemon opened this issue May 2, 2015 · 1 comment
Labels
API Refactor API Issues related to the Open Food Facts API. More specific labels exist & should be used (API WRITE…) refactor

Comments

@teolemon
Copy link
Member

teolemon commented May 2, 2015

What

Product Opener should move step by step to a client/server structure where the HTML templates, CSS and Javascript is separated from the back (Perl files) and communicates with it using a REST API.

Part of

@teolemon teolemon added the API Issues related to the Open Food Facts API. More specific labels exist & should be used (API WRITE…) label May 3, 2015
@teolemon teolemon modified the milestone: API May 12, 2016
@teolemon teolemon added API Issues related to the Open Food Facts API. More specific labels exist & should be used (API WRITE…) and removed API Issues related to the Open Food Facts API. More specific labels exist & should be used (API WRITE…) labels Dec 11, 2016
@teolemon
Copy link
Member Author

Open Food Facts Explorer by @VaiTon is an attempt at solving this issue: https://github.com/openfoodfacts/openfoodfacts-explorer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Refactor API Issues related to the Open Food Facts API. More specific labels exist & should be used (API WRITE…) refactor
Projects
Status: To discuss and validate
Development

No branches or pull requests

2 participants