Hi Karl

I haven't read it all very closely, but it seems that you've done a
marvellous job.

I think you should add a link to the installation guide
(http://www.turbogears.org/download/) to the start of the tutorial.
That might be of great assistance to any potential newcomers to TG
(linked from Digg or similar places).

I also think we should consider porting all our docs to SQLAlchemy as
that seems to be The Future(tm) of TurboGears :)

That is not very important though, but I think we should make it a
policy for the 1.1 docs :)

In any case, good job

Regards,
Mikkel

On 12 Nov., 08:29, "Karl Guertin" <[EMAIL PROTECTED]> wrote:
> After two months worth of comments, I've rewritten the 20 minute wiki 
> tutorial.
>
> http://docs.turbogears.org/1.0/Wiki20/Page1
>
> The primary enhancement is that I've added contextual lines in the
> examples, which will hopefully reduce the confusion over where to
> insert stuff.
>
> Since nobody is going to get through a written tutorial in 20 minutes,
> I've taken the opportunity to expand the explanations to provide some
> background information and links to places where you can find more
> information on topics the tutorial glosses over. I've tried to take
> special care to explain more exotic Python constructs to language
> newcomers, as we do seem to be getting a number trying to work through
> the tutorial.
>
> Finally, I've modified the ajax portion to use MochiKit's connect()
> functionality to demonstrate proper technique. Remember folks, setting
> onclick attributes is not good style and killing my "open in new tab"
> middle click annoys me greatly.
> 
> All the best,
> Karl


--~--~---------~--~----~------------~-------~--~----~
 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to