i really like the structuring approach of #94 and thought of doing that until I saw you already did it. However a suggestion, low-prio since the use will not notice it (hopefully):
You can use ng-route to split the page into several small files which might be easier for maintainance and merges.
I can also send a PR along, but I dont want to make the dev to master merge more complicated and will await that one.
There are also a lot of nice how-tos for routing e.g. here.
Hi,
i really like the structuring approach of #94 and thought of doing that until I saw you already did it. However a suggestion, low-prio since the use will not notice it (hopefully):
You can use ng-route to split the page into several small files which might be easier for maintainance and merges. I can also send a PR along, but I dont want to make the dev to master merge more complicated and will await that one.
There are also a lot of nice how-tos for routing e.g. here.