DarkBlue schrieb: > The documentation also needs to give a better understanding > for the widget browser. The widget browser says source code and > template and I believe many a new user is fooled that what is there > can be copy pasted into the own kid file or controller. Only to find > out it does not work that way.
There is a page for the widget browser on the wiki [1]. And yes, it is too short, partly misleading [2] and the language style could be better. After this page has been improved a bit, a "Help" link could be added to the widget browser template that points to this page. Patches anyone? Chris [1] http://docs.turbogears.org/1.0/WidgetBrowser [2] e.g. for the "Source Code" tag it says, "The Python code needed to invoke the widget.", but you can't normally just take the code and include it in your controller, because it is specific to how the widget browser works. It might be enough to just clarify that this is the source code of the example and not that of the widget itself. A usage example would be better placed in the description anyway, IMO. Also, it should be made clear that the tab "Template" shows the template that is used to *build* the widget and not the code that the user should insert into his page template to *display* the widget. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
