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

UI Separation from backend #57

Open
dsolmann opened this issue Apr 15, 2020 · 3 comments
Open

UI Separation from backend #57

dsolmann opened this issue Apr 15, 2020 · 3 comments

Comments

@dsolmann
Copy link
Member

Sub issue: usable API to acquire UI's files and serve them.

@sidrus
Copy link
Collaborator

sidrus commented Apr 17, 2020

What are your thoughts on how we grab the UI? Do we want to just it as part of the post-build process and bundle that with the API or did you envision something else?

@dsolmann
Copy link
Member Author

dsolmann commented Apr 17, 2020

We could use something like this. For example, we have our mod folder (Telemachus). We can create there subfolder WebData and put there our default UI. For Houston & MKON we can create additional mods and distribute them just like any other mod.

@dsolmann
Copy link
Member Author

As for metadata file, I think should do smth like this:

<?xml version="1.0" encoding="utf-8"?>
<config>
  <string name="MODNAME">Houston</string>
  <string name="PROPOSED_URL">houston</string>
</config>

in web_config.xml (located in WebData folder)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants