Skip to content
This repository has been archived by the owner on Nov 10, 2017. It is now read-only.

Should we remove angular? #15

Open
groovecoder opened this issue May 21, 2015 · 1 comment
Open

Should we remove angular? #15

groovecoder opened this issue May 21, 2015 · 1 comment

Comments

@groovecoder
Copy link
Contributor

If we eventually integrate this with MDN systems, we may want to use plain django/jinja templates without angular. Is there a compelling value that Angular gives us over django/jinja templates for the purpose of reports?

@peterbe
Copy link
Contributor

peterbe commented May 22, 2015

The intention was to use it as a "pjax" solution. I.e. you load some report and any click from there would just load different content within the main div, keeping the header & footer static throughout.

Also, perhaps the central place where you chose analysis plugin/report and/or you sign in can be a regular django template thing and the individual plugins/reports can be little fat-client javascript apps.

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

No branches or pull requests

2 participants