TG2 doc questions

[iain duncan]

Ok, I'm leaping in and trying to get this thing going.

Two questions:

- can someone give me write access to the the TG2 rough docs so I can
make corrections as I go?

- First doc question: Do we need to install the pylons dev version in
order to run TG2? If so, why? The first page of TG2 doc says we should
do that without explaining why.

Thanks
Iain

[iain duncan]

On Fri, 2007-14-12 at 12:07 -0800, iain duncan wrote:
> Ok, I'm leaping in and trying to get this thing going.
>
> Two questions:
>
> - can someone give me write access to the the TG2 rough docs so I can
> make corrections as I go?

Oops, I see I already have it! Sorry, thought that was locked down to
prevent spam.

>
> - First doc question: Do we need to install the pylons dev version in
> order to run TG2? If so, why? The first page of TG2 doc says we should
> do that without explaining why.

I'm finding the layout of the tg2 docs a little weird, and I'd like to
make some edits to help new users. Should I check here first or is there
somewhere I can stick a rough copy?

One thought I had is that maybe the first docs should also talk about
doing the install in a virtualenv as probably that is what most people
would want for mucking about with dev versions. Thoughts?

Iain

[Mark Ramm]

> > - First doc question: Do we need to install the pylons dev version in
> > order to run TG2? If so, why? The first page of TG2 doc says we should
> > do that without explaining why.

TG2 currently depends on features not in any released pylons version
(in particular we use an expose/decorated controller, which was added
just for TG2).

We also use the WebOb version of Pylons, which makes the
request/response stuff more intuitive for TurboGears users.

> I'm finding the layout of the tg2 docs a little weird, and I'd like to
> make some edits to help new users. Should I check here first or is there
> somewhere I can stick a rough copy?

Those docs are very rough, they were just thrown up there durring
sprints, so that things weren't being developed with no documentation.
But very liitle (ok none) thought was put into arranging them in a
useful way. So feel free to do anything you want.

> One thought I had is that maybe the first docs should also talk about
> doing the install in a virtualenv as probably that is what most people
> would want for mucking about with dev versions. Thoughts?

I'm all for adding a doc that uses virtualenv, it sounds like a good
idea to me. I do want to provide users with the option of just
installing if that's what they want to do.

--Mark