"Anyway, you do not need to like me to like web2py and vice versa. "
Let me clarify that I have absolutely no problem with you, I just wanted to "tell" the impression that an external user may have reading some discussions through some forum. I've expressed those critics because I think that web2py is an excellent project and I think that a potential new user that is looking for informations that stumbles onto these "flames" can obtain a false impression that "slow down" the spread of web2py. The fact that I bought your book and I have decided to write those criticisms on web2py users group is the clearest demonstration that I am really convinced of the quality of web2py. If I thought that your words where just "spam" I would not be here right now. I think web2py should be promoted in other ways and I assure you that personally, when I'll have more confidence with this framework, I will write an article (in Italian) on my blog. For the other "concerns" I would love to see implemented in web2py the features of Django admin interface specified at point 2, I hope yuo will implement some of those feature in future versions of web2py, this is the reason why I've explained it. :-) Thank you. On 23 Ott, 16:05, mdipierro <mdipie...@cs.depaul.edu> wrote: > I agree with everything you say except one. > > I do not act like a spammer (defined as someone who sends unsolicited > bulk messages). I just respond to every post online mentioning web2py > and to posts asking generic information about Python Web Frameworks, > in particular to correct false statements made by other people. When I > made an incorrect statement (and I have) I have corrected it and > apologized publicly for it. > > In this process I have learned that some users of other frameworks are > sensitive people and do not like comparisons (this is how you do it in > XXX and this is how you do in YYY). In the academic environment this > kind of comparisons are normal and welcomed. This is something I have > done (and you have done it too in your post, right?), that has caused > some irritation and disproportionate retaliation and more spreading of > false rumors. I try not do this anymore because I like and respect > those other frameworks as I like and respect their users, and I do not > want to have them against me or web2py. > > So, since you asked, I apologize to you again. > > Anyway, you do not need to like me to like web2py and vice versa. > > I am happy to have you here and we will be happy to answer any > question you may have. > > Massimo > > On Oct 23, 5:02 am, Doxaliber <salingro...@gmail.com> wrote: > > > Hello everybody, > > > yesterday I've bought on Lulu the Book on web2py. I've a good > > experience with Django and I want to share my first impressions on > > Web2py that, I think, have some positives and some negatives respect > > to Django. > > > The cons: > > 1) ORM maybe it's more powerful than the Django one but it's less > > immediate. For example: > > > class Author(models.Model): > > first_name = models.CharField(max_length=30) > > last_name = models.CharField(max_length=40) > > > class Book(models.Model): > > title = models.CharField(max_length=100) > > authors = models.ManyToManyField(Author) > > publisher = models.ForeignKey(Publisher) > > publication_date = models.DateField() > > > is easier to understand and to remember than the web2py version. Also > > relationships on Django are more easier to remember. > > > 2) Django admin interface is more powerful. I think that it can be > > used on production environments (and it is!) and it is more > > customizable than the web2py one. Django interface have also a goodies > > that I think is really useful: when you have a form with a select from > > a foreignkey there is a link (with a plus) that allows the user to add > > an element to the related table! I also like the design of forms that > > belongs on many to many relationships. I also think that overall > > design of admin interface is more beautiful than web2py admin > > interface.http://graffletopia.com/images/previews/362/original.jpg > > > 3) Documentation: Django have great documentation! The Django book is > > fantastic and it's free. Web2py documentation is poor. I've bought the > > web2py book for desperation and mine seems more an act of faith than a > > reasoned choice! :-D > > > 4) Massimo Di Pierro sometimes act like a spammer! :-D Some time ago I > > was searching informations about web2py, some review, some points of > > view. Well, everywhere there was Massimo Di Pierro saying how good is > > his framework! I think this attitude makes a bad impression to those > > who want to try to use web2py. I hope that Di Pierro will apologize me > > for this, mine are just observations made for good purposes. > > > The cons (for now!): > > 1) SQLFORM > > 2) CRUD > > 3) AUTH system > > > That's all for now. I hope that the criticisms set out here can help > > improve web2py. I apologize in advance for my bad English. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
