I think the idea here is the same as was behind "SessionConfig" in dbsprockets.
That is, there is a standard set of data you expect to retrieve for a given generated widget, be it a set of data to populate drop-downs, or a jsonified stream to populate an autocomplete field. If there is a way we can make this data retrievable and customizable, we will have a win. -chris On Jul 16, 3:11 pm, Alberto Valverde <[EMAIL PROTECTED]> wrote: > Felix Schwarz wrote: > > Thanks for your excellent explanation. > > > As I may need something like dbsprockets/dbmechanic/rum in the near > > future, I'm interested in Elixir support. Does rum currently support > > Elixir? If not, any estimations when basic support is coming? > > Elixir should be usable already, pass the entities in a list as "models" > to the repositoryfactory when initializing RumApp (like in the example) > and pass elixir's session as 'session_factory'. I haven't really tested > it, but it should work...> And another very critical issue to me: Currently > you use drop down > > menus to select referenced objects. I have an app with quite a few > > users (>> 10,000) so I can't use drop down menus there. Any chance to > > select them by ID together with AJAX to get a label for this id? > > It's not implemented yet but it will be, all the infrastructure to > support it is there but there's still many things to do before I get > into any heavy client side coding, hopefully it'll be ready before gsoc > ends. > > Alberto --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
