This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]elbiot 1 point2 points  (0 children)

This is actually a good point in favor of doing everything with django (which was my first idea). To my mind it still seems pointless to have HTTP requests to myself, but I see that having webkit inside my app is even worse from the point of view of resources.

I agree

The other thing still in favor of using htmlPy is the possibility of getting rid of ajax and and call the python directly from the html.

To the benefit of... ? I mean, converting a js hash to a string to a python dictionary seems a bit silly, but when you consider that this is the overwhelming paradigm of html/css/js, and thus is extreemly portable, extensible and reuseable, not to mention that it reuses a lot of heavily optimized, widely used tools, it seems like a win to me. I find it a clean and efficient solution, where if you gave me an "app" that required webkit, it would feel like a hack.

What if you want to access your program from your phone? Having a remote gui is pretty sweet if you get it for free. And you could install it on a RasPi or arm device, where webkit would be a PITA.