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

Integrate platform-specific presentation customizations with the build process. #54

Open
a-laughlin opened this issue Feb 14, 2014 · 0 comments

Comments

@a-laughlin
Copy link
Contributor

Architecture:
The build process should know nothing about the presentation. That way we can eventually shift to a native Android UI by switching which presentation parts we use, without having to change the plugins themselves.

Utils folders:
Each type of plugin (e.g., forms) will get its own utils folder specific to each presentation platform. So there is an Angular form utils folder for displaying the form as HTML. It contains html partials, css, and js files. Eventually there will be an Android form utils folder for displaying the form in Android.

Plugin folders:
Each form plugin itself should only contain a happathon.json file which which references the form parts in the form-utils folder. (I need to finish changing all the references from "happathon" to "inside". This ticket needs to be updated also afterward).

How to integrate:
How to get the css and js to run without the build process knowing about them... placing it in the utils plugin's json config would work. I don't have a config json specced for utils plugins yet though. Need to create that.

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

No branches or pull requests

1 participant