Widgets look interesting, but I must confess that I don't understand
them.
A little on my background.
I develop CAD/CAM apps for a living. I create web applications to
support my development efforts. These websites help me:
- manage a project
- document a project
- document best practices
- ...
I have a base understanding of HTML, and understand the Java servlet
model.
I have been using python as my scripting language of choice since 94
(It was perl before that). Python has increated my development
productivity, and twisted serves as the backbone of our internal
compute grid.
My background is probably similary to a large set of people that would
leverage turboGears to improve their productivity in their non-web day
jobs.
I have been through the TurboGears tutorial and am very happy with what
I have seen. After getting a grasp of the basics, I would like to take
my web applications to the next level, but I am having trouble with the
format of the documentation for the advanced turbogears functionality.
I may be out of the norm, but recipe-based docuementation works very
well for me.
The documentation that has worked best for me provides the following:
- Concept being presents
- Name of concept (so it can be refered to at a later time)
- screen shot(s) of effect ( I am a visual person)
- known uses of concept
- turboGears recipe to implement effect (if more screen shots were
added to 20 minute wikki, the format would be perfect for me).
- similer effects (see also)
I like the 20 minute wiki approach as a start point, Maybe the recipes
could add functionality to the wiki?
I am really enjoying turbogears, I am stuck making the jump to
1) widgets
2) mochikit
3) createing/using AJAX widgets
4) ....
Thanks for the great project, the current documentation is very good,
and necessary. It just seems like there may be a better way to move
someone through the learning curve of the advanced TurboGears-specific
features.
Thanks,
Mike
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.11.53.63 with SMTP id b63mr124828cwa;
Mon, 22 May 2006 07:33:21 -0700 (PDT)
X-Google-Token: 3BFh1AwAAADiS5WaBrWvWrU7bDBY-qlF
Received: from 216.196.246.230 by j55g2000cwa.googlegroups.com with HTTP;
Mon, 22 May 2006 14:33:21 +0000 (UTC)
From: "Michael Schneider" <[EMAIL PROTECTED]>
To: "TurboGears" <[email protected]>
Subject: Widgets For Beginers Request
Date: Mon, 22 May 2006 07:33:21 -0700
Message-ID: <[EMAIL PROTECTED]>
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.3)
Gecko/20060426 Firefox/1.5.0.3,gzip(gfe),gzip(gfe)
Mime-Version: 1.0
Content-Type: text/plain
Widgets look interesting, but I must confess that I don't understand
them.
A little on my background.
I develop CAD/CAM apps for a living. I create web applications to
support my development efforts. These websites help me:
- manage a project
- document a project
- document best practices
- ...
I have a base understanding of HTML, and understand the Java servlet
model.
I have been using python as my scripting language of choice since 94
(It was perl before that). Python has increated my development
productivity, and twisted serves as the backbone of our internal
compute grid.
My background is probably similary to a large set of people that would
leverage turboGears to improve their productivity in their non-web day
jobs.
I have been through the TurboGears tutorial and am very happy with what
I have seen. After getting a grasp of the basics, I would like to take
my web applications to the next level, but I am having trouble with the
format of the documentation for the advanced turbogears functionality.
I may be out of the norm, but recipe-based docuementation works very
well for me.
The documentation that has worked best for me provides the following:
- Concept being presents
- Name of concept (so it can be refered to at a later time)
- screen shot(s) of effect ( I am a visual person)
- known uses of concept
- turboGears recipe to implement effect (if more screen shots were
added to 20 minute wikki, the format would be perfect for me).
- similer effects (see also)
I like the 20 minute wiki approach as a start point, Maybe the recipes
could add functionality to the wiki?
I am really enjoying turbogears, I am stuck making the jump to
1) widgets
2) mochikit
3) createing/using AJAX widgets
4) ....
Thanks for the great project, the current documentation is very good,
and necessary. It just seems like there may be a better way to move
someone through the learning curve of the advanced TurboGears-specific
features.
Thanks,
Mike
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
