Timeline for Javascript based application controller in Javascript-less environments
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 20, 2014 at 13:57 | comment | added | SPI | Thanks for the list. From what I gather, the best way to go about this is to extend the backend to allow callbacks from a JavaScript based restful API. With a little tweaking of the configuration file that controls the back-ends application controller, I will be able to make it respond to the API calls with responses encoded in JSON. | |
| May 20, 2014 at 13:16 | comment | added | Greg Burghardt | There are many JavaScript frameworks out there: en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks and sporto.github.io/blog/2013/04/12/… | |
| May 20, 2014 at 7:30 | comment | added | SPI | I should have mentioned that I was speaking in regards to web-sites with a moderate-to-large scale. While plugging in JavaScript here and there in different views is not a bad idea for smaller projects, doing so for larger ones is setting yourself up for doom in terms of maintainability. Server Sided Code is easy to structure with an MVC + a controller pattern of your choice. The best way to complement it with structured JavaScript has me at sixes though. | |
| May 19, 2014 at 18:59 | history | answered | Greg Burghardt | CC BY-SA 3.0 |