By the way; you can get your posts to this thread to show up in the ticket, but to do so, you have to go to the ticket (http://weblocks.lighthouseapp.com/projects/18897/tickets/60-re-login-as-subclass-of-quickform) and get a different recipient address from the bottom of the page.
Jan Rychter <[email protected]> writes: > a) is complete, e.g. you plug it into your site and you're good to go, Hmm; I'm using it on hfsbo.com. > b) does not assume it is a wall between two parts of the site, e.g. I > want a login widget to be displayed at all times or easily accessible > and once the user is logged in, the site just acts differently, walk-widgets is powerful enough to handle this, assuming that your walk-widgets implements the subwidgets-as-superset-of-children I've discussed, rather than just descending into widget-children. I just pass a GF `auth-changed!' in as the proc, and have various methods that respond, usually by dirtying widgets, sometimes by building a new single subwidget. > d) it can change into a user-info kind of widget, displaying the > user's information I think this ought to be done with flow-replacement rather than built-in to the widget. "Change into another widget" is what flow-replacement is good at. -- I write stuff at http://failex.blogspot.com/ now. But the post formatter and themes are terrible for sharing code, the primary content, so it might go away sooner or later. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" 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/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
