On 2/4/07, iain duncan <[EMAIL PROTECTED]> wrote:
>
>
> On Sun, 2007-04-02 at 19:52 -0500, Mark Ramm wrote:
> > I'd like to hear the specifics of what you think needs attention in
> > the TurboGears Documentation.
> >
> > On my list for most important Documentation issue right now is the
> > fact that we haven't been successful in getting API docs generated by
> > PythonDoc, or Epydoc.
> >
> > Beyond that, I think we could use some good "orientation"
> > documentation which provides the big picture overview.  Much like the
> > old Getting Started Guide did.
> >
> > And people always seem to need better Widget Documentation
> >
> > What else needs to be covered or covered better?
>
> I think one of the biggies right now is cleaning up the docs regarding
> differences between SA and SO, and I truly believe it is good for TG in
> the long run and a big strength of the platform to fully support both.
> SA is amazing, but also much harder for a new database programmer to
> wrap their heads around. And lots of web sites out there can be quite
> complex with really very minimal db needs, so I think it fills an
> important niche.
>
> I guess one area of confusion right now is what the role of the various
> mapper choices are. It would be great to have some form of unified api
> for the core components IMO, like being able to use identity with
> similar calls, so that if somebody starts using a tutorial on
> session/identities/widgets, whatever, they can count on it "just
> working" with nothing more than a difference in what they import.


huh? how can you have the same api for two totally different components?

Iain
>
>
> >
>

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