The idea of signals is to provide a standard way to communicate data between widgets, it's database work mostly. The signals class in google code is just "a case of use", This class is going to by a little more dynamic.. the idea is to get a mapping of all the elements of the site on the database to be able to relate one object to other, I've thinking on a self relational table for this, the signal class should be able to get any SA model and use it, for storing data of any other widget that can't use standard ones.
Those standard signals should be enough for the majority of widgets, providing data in different ways. They can return SA iter objects, list, dic, an some other will do for sure. Maybe the terminology I'm using is a little cumbersome for something that for sure you already know ! Thanks ! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
