Jorge Godoy schrieb:
I'm not impatient (otherwise I wouldn't be answering). All of his
questions
are answered without an API documentation.
http://docs.turbogears.org/1.0 -> "Widgets" -> "Introduction to Widgets"
http://trac.turbogears.org/wiki/DiveIntoWidgets
Sorry, that is not my idea of an "API documentation". These are mere usage
examples.
You don't need looking into the source code when there are docs about the
subject. The above two are just the two first I saw on the docs / wiki.
There's a lot more.
A title search for 'widget' returns:
1. 1.0/IntroductionToWidgets
2. 1.0/RemoteFormWidgetTutorial
3. 1.0/SimpleWidgetForm
4. 1.0/WidgetBrowser
5. 1.0/WidgetList
I wouldn't call that exactly "a lot", esp. since the last is only a list and
no. 2 is only about a special case.
What I miss is a documentation about, what widgets there are and what
parameters they take (including inherited ones) AND the type and semantics of
those parameters. Plus a description of the public methods of widgets that
should be used in:
a) the controller code
b) the widget templates
again with a description of the arguments.
That's what I would call an API documentation!
If the DocSprint happens, I will be happy to contribute in that direction.
Chris
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
