That's also why I want to add a mongoDB backend. (as well)
I am also thinking of moving the Views completely to javascript (ejs would probably be my choice then).
That would result in a client <--JSON --> Server <--- JSON ---> Database
szenario. Which looks pretty clean, at least to me.
It looks nice but it's hard to trust a web framework with such a jumbled home page. I know it has absolutely nothing to do with the backend abilities of PoW but if you want people to make websites with your technology you should probably set the example with a really cool website.
Sorry to be negative, I am not putting down the framework.
No problem, I just took the standard Bootstrap layout.
But right, the red info box is a little heavy weight. But I like to point out that this is not meant to be production ready, yet.
Anyway I am not a Designer.
I like my blog template, though ;)
Seems interesting. Has ways to go until production ready, but even so I think there's potential here. I'm not sure I dig the "wheels" branding because long term it can cause people to maybe needlessly view this in comparison to RoR, with this being a pure Python based architecture and not a straight port.
15 comments
[ 3.7 ms ] story [ 44.2 ms ] threadhttps://news.ycombinator.com/item?id=4377328
See the Github development page for more.
https://github.com/pythononwheels/pow_devel/commits/beta1_au...
http://cfwheels.org/
https://pypi.python.org/pypi/wheel/
http://www.youtube.com/watch?v=3nOTeDhZ1lc&feature=youtu...
But my main point was to have a fluent workflow.
That's also why I want to add a mongoDB backend. (as well) I am also thinking of moving the Views completely to javascript (ejs would probably be my choice then).
That would result in a client <--JSON --> Server <--- JSON ---> Database szenario. Which looks pretty clean, at least to me.
Sorry to be negative, I am not putting down the framework.
Anyway I am not a Designer. I like my blog template, though ;)