Christopher Arndt <[EMAIL PROTECTED]> writes:
Sorry, that is not my idea of an "API documentation". These are mere usage
examples.
I didn't say they were API. Let me repeat: "without an API documentation".
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.
If you restrict yourself to the wiki then there isn't a lot. :-) Search the
archives here and you'll see a lot more of resources and examples. There are
blogs with recipes, notes, etc.
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.
Have you looked at the toolbox?
That's what I would call an API documentation!
I'd ask for a few more things such as what can be overriden, how, etc.
If the DocSprint happens, I will be happy to contribute in that direction.
Go for it! But remember that ToscaWidgets will become the standard.
--
Jorge Godoy <[EMAIL PROTECTED]>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
