Closed frankrousseau closed 10 years ago
Hi,
do you mind about implementing angular app ? I already made that with some jquery, by lazyness, fact is, i think it does not fit well the problem. So i d like to switch to angular, but it s much more heavier, so how do you think ?
In terms of transport i d like to setup a socket, seems more suitable than webservice.
Finally, i think server side templating, deserve badly the capabilities of targeted environments (extreme low latency, when not a local setup). So i d like to avoid it.
Whatever technology you use for the frontend, you need one entry point that requires some kind of templating. Moreover, I think we shouldn't put too much options in the UI too early. So I would suggest that we stay on server side rendering until we find a really good use case that requires a single page for the dashboard.
I found a solution. I use an index.html from the asset folder as an entry point. From there we can serve js that build the page. Communicating through a websocket would be better but actually I use a simple get request to know which data to load. I will open another issue about that subject.
HTML code should be extracted from the Javascript code.