On 4/14/06, Steve Bergman <[EMAIL PROTECTED]> wrote: > > I have just started a really simple project that I think is suitable > for FastData and FastData alone, if I can get everything looking like I > want. > > Two questions. > > 1. According to > http://trac.turbogears.org/turbogears/wiki/ListWidgetFromForeignKey , I > can use something like: > > def _get_form_option_value(self): > # This lets turbogears know what to use for the option element > value. > # Could this also be used to populate the DataGrid? > return self.name > > in my model to get the auto-generated drop downs for foreign keys to > show the values I want. However, this does not seem to work. I still > get the ugly <Classname 1 name="whatever"> format.
That recipe references r458, and we're now over 1100. FastData has support for foreign keys, but it doesn't have the particular customization you've mentioned. http://trac.turbogears.org/turbogears/browser/projects/FastData/trunk/tgfastdata/formmaker.py > 2. Where is the proper place to apply CSS to the fastdata template? It > does not seem to inherit from master.kid, and editing its default > template in place seems like a bad idea. Is there some mechanism to > specify my own custom template? This is probably the #1 problem with FastData, and the biggest reason it's not a part of the core at this point. Kid and/or TurboGears need some additional functionality before you'll really have stylistic control over a FastData app. Kid would need to be able to specify extends at render time or TG needs template override capability. TG will get template overrides in 1.1 for sure. Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
