Hi Alex, El jue., 14 mar. 2019 a las 19:28, Alex Harui (<[email protected]>) escribió:
> Hi Carlos, > > IMO: > > -Everything you mentioned does or should generate events. > ok > -In theory some view bead or MXML document is in charge of displaying > validation errors (the validators themselves are hopefully not displaying > the errors, just returning a status or dispatching an event). That view > bead or MXML document should be listening for the appropriate events > still not, but I hope to refactor this someday > > I think the trick is how some view or MXML can get events from other UI > widgets. I don't think there is a single strategy for that so it would be > interesting to see various strategies implemented (hopefully as beads) to > capture appropriate events. Similar to LayoutNotificationBead, some bead > could be added that watches a component for an event and forwards it to a > central bead on the app. Another bead might watch the central bead and > clear the validation errors. > just committed a solution that works. Let me know what you think about it. If is what you recommend or not. Just take into account that for now validation bead has baked the visualization for now until I can refactor that. In the solution: * NavigationActionNotifier : listen for change or click events and creates " navigationAction" that bubbles to main app view * CleanValidationErrors : is in main app view and listen for " navigationAction" and dispatch "cleanValidationErrors" that Jewel Validator nows to destroy all error tips Thanks Carlos > > Just an idea, > -Alex > > -- > Carlos Rovira > http://about.me/carlosrovira > > > >
