Hi,

> 1) Only show parameters that belong directly to the widget, not to its
> > base classes
> Done. The new WidgetBrowser eggs separates both kinds (inherited and
> 'local'). Now the GUI needs the ability to hide the inherited ones until
> the user wants to drill them, working on it...


Ok, I've just committed a change adding a "param_doc_cutoff" parameter to
widgets. Not sure it's 100% what we want, but it definitely helps for now.


> > possible though; I can always recode)
> > 2) Pick up documentation in the params dict (perhaps this isn't
> I've opened ticket #4 for it.


Ok, I've committed a fix.

With these two in place, I can pretty nice autogenerated API docs, so I've
started tidying up the docstrings for tw.dynforms. Shouldn't be much more
work now to get some decent doco :-)

Paul

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" 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-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to