On 2/2/06, Randall <[EMAIL PROTECTED]> wrote: > > I was using the fastdata.DataController to do some CRUD with > User/Group/Permission data. I was pleasantly suprised by the > configurability and the new join_widget and fk_widget. With a little > more polish, DataController could be useful for the majority of CRUD > applications.
That's good to hear! Hopefully, I'm not breaking things too badly with the refactoring I'm doing. I do think the widget API is going to look quite streamlined and easier-to-subclass when I finish. (The next commit will actually have quite a bit of cleanup in it.) > For the column_widget_fk_col and join_widget_related_join, the data is > displayed using unicode(object_ instance), which is ugly. Maybe it's > just stepping stone, but I think there should be a way to specify a > column to use to display the object. Maybe something similar to > form_order or somthing defined in sqlmeta like sqlmeta.display_field = > 'name'. I'd like to hear opinions on if and how this would be done. This was discussed either in a ticket or on the list... Here was the thinking: just giving a column name isn't good enough. (Consider a table with last name, first name and middle initial). Of course, you can use a property instead. But, what I was figuring was that what we're really angling for when you're displaying that is the human-understandable form of that particular object. And that's what __unicode__ or __str__ are all about, right? Kevin
