I'm starting to work with TurboGears again, and am enjoying the fact that several widgets have been included with TurboGears.
However, I find it difficult to find the code for any given widget when I want to explore a widget's code to find out how to use it and how it works. I haven't found any consistency in the naming conventions for widgets included with Turbogears For example... turbogears.widgets.big_widgets is not at all descriptive of the types of widgets contained therein (CalendarDatePicker et al, AutoCompleteField, LinkRemoteFunction, RemoteForm, AjaxGrid) It would be much more useful from a code-browsing-by-someone-who-didn't-write-the-widgets-code point of view if there were turbogears.widgets.calendar, .autocomplete, .linkremote, .remoteform, .ajaxgrid modules to contain the Python side of all of these widgets. The first thing that came to mind was "well, maybe since these are big, they are lazy-loaded in case they aren't used." But turbogears.widgets.__init__ does an "import *" (yuck!) of big_widgets along with everything else, so lazy-loading isn't the case here. Are there any plans to clean up the module naming conventions? I'm also confused by the split between turbogears/static/js/widget.js and the turbogears/widgets/static directory. Thanks! - Matthew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
