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

Third-Party Support: WIPI #84

Open
XerTheSquirrel opened this issue Jul 1, 2020 · 0 comments
Open

Third-Party Support: WIPI #84

XerTheSquirrel opened this issue Jul 1, 2020 · 0 comments
Labels
api An API compatibility Compatibility Issues third-party-api Third-Party API
Milestone

Comments

@XerTheSquirrel
Copy link
Member

XerTheSquirrel commented Jul 1, 2020

WIPI documentation:

Most of this stuff seems to only have stayed in Korea, so virtually everything that exists is only in Korean.

Note that WIPI uses something called JLets, which are like MIDlets but completely proprietary with this API. There are also CLets but those are out of scope for this. A customized JLet launcher would have to be used because there are no manifests for the applications and otherwise.

Some documents:

@XerTheSquirrel XerTheSquirrel added compatibility Compatibility Issues api An API third-party-api Third-Party API labels Jul 1, 2020
@XerTheSquirrel XerTheSquirrel added this to To do in Version 0.6.0 (Dev 0.5.0) via automation Jul 1, 2020
@XerTheSquirrel XerTheSquirrel added this to the Version 0.6.0 milestone Jul 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api An API compatibility Compatibility Issues third-party-api Third-Party API
Projects
Development

No branches or pull requests

1 participant