For what is worth, we (which mostly means Mariana) are putting a lot of effort on porting our apps to use Pylons (and I've been bugging the list with a few questions :-). A few comments from that perspective:
On 1/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
(...)
1. Hosting possibilities - not to many... ---------------------------------------------
(...) That is not an issue for us (we host things on our machines here, blablabla). But I understand our situation is not common.
2. Documentation -------------------------------------------- More docs and in a more friendly layout. In Django to start working with databases user needs to check two pages - "Creating models", "The database API " which explain in a nice way how to use that part of the framework. For this example a Pylons only SQLAlchemy tutorial would be required (how to add,edit,delete,search, how to make complex queries, how to create models). The docs layout could be like django/djangoo book - explain one feature at a time, no SQLAlchemy + Myghty + Helpers + FooSomething at once. Lolish examples with print's are very good for learning. Move tips from mailing list to the site.
Well, this is actually interesting. When we started (about 9 months ago?), one of the reasons we decided to go with Pylons was that it looked like the docs were actually better and the info easier to find (yes, we did look at TG and Django, among several others). We haven't really compared again after we plunged into Pylons. However, yes, certainly the docs can be very much improved (e.g., just in the last couple of days, Mariana has found a solution to a problem not from a Pylons doc, but from a Ruby on Rails doc, and extrapolating from there). (I just read Mike Orr's comments; I see his points, but to those of us who are not really web-based apps. hackers the situation can sometimes be _very_ frustrating. That said, though, we still think Pylons is really awesome).
3. Promotion ------------------------------------------- Django writes a book, Django on PyCon, everyone talks about Django ;) There is a lot of small and bigger Django apps (Check google code). Pylons can also use some more aggressive promotion - if someone wants to make a CMS app and ask about it on the mailing lists - no Zope but "use Pylons"... Blog about Pylons, new tutorials, new events (like new hosting company etc.) put them on aggregates like python planet. Try to digg them.
Our moving to pylons is far from complete, but (some of) our stuff is here: https://launchpad.net/asterias-pylons Best, R.
>
-- Ramon Diaz-Uriarte Statistical Computing Team Structural Biology and Biocomputing Programme Spanish National Cancer Centre (CNIO) http://ligarto.org/rdiaz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
