Hi Antoine! > >> What additional requirements do you have, that are not fulfilled by >> todays CRUD packages? >> > Two major requirements I can think of: > > The possibility to define how a relation is chosen/modified (having to > choose in a drop-down of 1000 items is stupid; I need e.g. some > autocomplete field based on some (supposedly unique) column of the > joined table).
Again I think, you use your own widget there, in both Catwalk 2 and RUM. However, you might consider it funny, that for me 1000 items might be on the safe side with drop down lists (if you can teach your users, how to use it): Just order them alphabetical and use "type ahead" in Firefox. Michael > The possibility to specify that a VARCHAR field is really an enum, and > to specify what labels (on the UI side) correspond to what values (on > the DB side). > > Then, of course, there's layout flexibility, custom validation, etc. > An useful CRUD package should be something else than a smart version > of phpmysql. > > Regards > > Antoine. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
