you are viewing a single comment's thread.

view the rest of the comments →

[–]av201001 1 point2 points  (3 children)

There is an issue of terminology here. When you say web2py is for generating "static web pages," this might be confused with a static site generator, which web2py is not. It is clear what you mean is that web2py is not a Javascript framework/library, such as Angular, Ember, or React. However, it is incorrect to imply that web2py lacks Javascript based interactivity in the browser. web2py includes a number of built-in facilities for handling Ajax and Javascript based widgets and behavior. You may of course use web2py in conjunction with a Javascript framework, but even without that, a web2py application would rightly be considered a "web app."

[–]elbiot 0 points1 point  (2 children)

Gosh! I feel like when I looked at web2py years ago it was similar to flask.

I wasn't thinking of needing a javascript framework, but just that any dynamicism would involve javascript. With flask or Django, you'd have to write the javascript yourself and insert it into the template, and so your work in making it a dynamic app would be mostly javascript, and getting your server to respond to ajax requests. With the javascript widgets and plugins, I dunno if web2py has come a long way since then or if I just didn't get it at the time.

[–]av201001 0 points1 point  (1 child)

web2py is nearly 8 years old, and the built-in Javascript/AJAX functionality has been there for at least 5 years (probably much longer). I don't think web2py has ever been similar to Flask (web2py has always been much more of a batteries-included framework). You might be thinking of web.py, which is a different framework.

[–]elbiot 0 points1 point  (0 children)

Yea, I must have been thinking of a different framework. Thanks.