On Jan 15, 7:19 pm, Niklas Hambüchen <[email protected]> wrote: > All your problems are just the result of the fact that Turbogears > documentation sucks.
With a bit of experience in organization I'm always cautious to push the blame to one aspect alone. One crucial question might be: Do TG developers really want the framework to become _popular_ (not only efficient, powerful or elegant)? > I guess that TG's documentation is bad because TG is just an > accumulation of projects with some sugar on top, not a full-blown > from-scratch project that needs a completely new documentation It might not need a "completely new" documentation. What's happening now (in the albeit few pages I focused on) is that the docs _repeat_ other docs and themselves (thus somehow violating the DRY claim) and produce some chaos along the way. It might often be better to delete a paragraph and point to another site/page instead. > So I'd propose that if you get your TG up running (it might be worth the > effort), write a new straightforward documentation page on how you did > it, see if it reproducible and covers the cases the other docs did, and > then delete the non-working ones. Yes, I have that in mind. Yesterday evening I watched TV with my girl friend, chewed cheese- balls, and then decided to try a Django install with the laptop on my knees; this was successful after one hour or so. The first success experience comes quite fast (with Debian): http://docs.djangoproject.com/en/dev/intro/install/ .. and continues with setting up the first project structure and serving it with: python manage.py runserver 0.0.0.0:8000 ( http://docs.djangoproject.com/en/dev/intro/tutorial01/ ) So far it's close to what we did with paster in TG. Now I looked into the index to get apache-wsgi running, and found: http://docs.djangoproject.com/en/dev/howto/deployment/modwsgi/ This way I had the django "welcome" served via apache-wsgi in 20 minutes. What they do is telling you (almost) only what you need to get running, and then pointing to a place if you you want to learn more _at the end_: http://code.google.com/p/modwsgi/wiki/IntegrationWithDjango This is (again) full of remarks, variants, deprecated stuff ("if you have a version before x do this, if it's newer than y, you can omit that .. "); but that's not Djangos problem anymore. What both pages leave out completely is the virtual environment stuff, and I just don't (yet) understand if this needs to be understood for TG or not. So a similar strategy might work for TG, but I'd ask experienced developers join me on that. This ML also seems not to be a good place to discuss these details - maybe there is a TG wiki for works like this (including a discussion module)? / Bernd -- You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en.
