Update: The compiler isn't assigning private access getters to the Watchers, but it is assigning it to the Bindings, so I made changes to the Binding code in FlexJS to deal with it and things seem to be working. Maybe we will find a reason to put the getters on the Watchers some day.
Any volunteers to refactor the binding classes onto a base class with subclasses? There is lots of shared/duplicate code in each of the binding implementations. Thanks, -Alex On 10/4/16, 4:14 PM, "Alex Harui" <aha...@adobe.com> wrote: > > >On 10/4/16, 2:03 PM, "OK" <p...@olafkrueger.net> wrote: > >>Hi Greg, >> >> >>Greg Dove wrote >>> I suspect it might work with ViewDataBinding but perhaps not the other >>> Binding types yet. >> >>Hmmm, I've just tested it and it seems to me that's the same behaviour >>with >>ViewDataBinding: >>Public works, private not. > >I'm looking into it. The compiler is not doing the right thing... > >> >> >>Greg Dove wrote >>> I can work on this by early next week if no-one else gets to it first. >> >>Would be great but please don't get me wrong: >>I highly appreciate any effort but I don't expect it as a matter of >>course. >>I sometimes struggle with myself to post an issue or not cause it might >>waste lots of people time if I'm doing soemthing wrong or if you guys >>have >>it on the list anyway. > >I don't know how often you decide not to post, but IMO, traffic isn't too >high yet. If you are doing something wrong, we need to identify that and >document it at least in email because others will probably end up in the >same hole. The only list we have is what is in JIRA. If it isn't in >there, feel free to add your issue. > >New committers should make sure they are subscribed to >iss...@flex.apache.org since some JIRA traffic only goes there. I'd like >to establish a protocol where you only assign yourself an issue when you >about to start working on it. That way we can hopefully avoid duplication >of effort. > >Thanks, >-Alex >
