Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>-- EDIT --+</p> <p>Yeah, right after I posted I realized I was heavy on comparison of frameworks but light on suggested solutions to your problem (i.e. existing appliances). I think that Django probably has more matured addins/apps. That being said, crafting your own blog in web2py (a simple blog) is probably only a little harder than configuring one for another framework. </p> <p>There is the wordpressclone appliance: <a href="http://web2py.com/appliances/default/show/36" rel="nofollow noreferrer">http://web2py.com/appliances/default/show/36</a> (you can extract existing wordpress data and get it in here, i'm pretty sure there's a WP export and an import function on this appliance)</p> <p>There is an e-store (haven't used it): <a href="http://web2py.com/appliances/default/show/24" rel="nofollow noreferrer">http://web2py.com/appliances/default/show/24</a></p> <p>There is KPax CMS, as you said, but i think this one might be out of date, unless it was updated recently. The integration between these should be possible, you can share sessions across apps and I think if you have the same auth_user db, it should work.</p> <p>I would try installing these and see if they are close to meeting your needs -- especially KPax since I'm not sure the state it's in.</p> <p>-- END EDIT --</p> <p>Both Django and Web2py are very good frameworks in my opinion. I think you would be happy with either. That being said, having not used frameworks I would say to with web2py, unless you NEED certain modules that only exist in the django world. Web2py probably has a little more gradual learning curve. Also, it can do RSS out of the box, there's a screencast somewhere showing how to create a blog app in about 5 minutes (including comments), and the community is (usually) very responsive. I don't think there is anything that web2py can do that django can't (except DB migrations -- but i think you can make django do them with some 3rd party code), or vice versa.</p> <p>Django favors a "explicit is better than implicit" development methodology, which requires to you import various modules and doesn't have all the "magic" of web2py. Using django, you will be more aware of exactly what is going on under the hood. The django templating language is easy to learn and provides a lot of functionality for common markup tasks. Their is a LOT of documentation, a larger user-base and tons of 3rd party modules/plugins/whatever.</p> <p>Web2py favors a "everything should have a default" approach, and enables to to focus on the big picture without getting bogged down by the minutia of web development. I'm not saying this is in contrast to django, but rather that web2py is very strong on this point. It allows you to rapidly develop applications, and takes the headache out of things like updating a table schema (i.e. it does database migrations). I also prefer web2py's templating language to django's, as it allows pure python and does not require one to learn a separate templating language at all. </p> <p>I think both frameworks have decent internationalization/localization features. I'm not sure if Django's is still under development or not? Web2py's is easy to use, but I think you might have to provide a lot of the translations yourself. </p> <p>As for the lack of replies on the web2py list, maybe it's because this topic is becoming more and more frequent? I'm not sure. You could ask people on the web2py freenode channel.</p> <p>Also, definitely check out this link:</p> <p><a href="https://stackoverflow.com/questions/4352428/django-vs-web2py-for-a-beginner-developer">Django vs web2py for a beginner developer</a></p> <p>The first response is from the lead developer of web2py, but I think he makes a fairly balanced comparison. </p> <p>Also, the previous thread includes a link to here (the good and bad of web2py):</p> <p><a href="http://www.mengu.net/post/django-vs-web2py" rel="nofollow noreferrer">http://www.mengu.net/post/django-vs-web2py</a></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload