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

App resource optimisation VS resource provision #135

Open
mvdandrieux opened this issue Aug 6, 2015 · 0 comments
Open

App resource optimisation VS resource provision #135

mvdandrieux opened this issue Aug 6, 2015 · 0 comments
Assignees
Milestone

Comments

@mvdandrieux
Copy link
Contributor

We have decided to store the main js resource of the sir trevor app outside of the system, as template files.

  • The goal is to prevent the ressource form loading in the front end when we only need to display the data of the field (and not the field itself)
  • The consequence is that the ressource is hence unreachable from the front-end (impossible to display the field, nor to bind it because one can't bind ressources in the template of the back-end from a template in the front-end.
  • The result is that you have to perform a nonsense-bind and store a strictly identical copy of the ressource a second time in the front end @sylvainfrigui

screen shot 2015-08-06 at 16 31 59

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

2 participants