John Spackman

or some combination of "automatic rest" and "remote objects" (which was where I was going with qso but ran out of imagination 😊). It's interesting that this boils down to...

Yes, I agree. I did write a kind of event handling in server-objects but ended up only ever using it on the server side (and it's not straightforward). Just being...

**Psuedo-properties** - The description above is updated > or is there a provision for merging, e.g., if the two arrays are not the same size No, this is just about...

That looks really good! 👍 Does this mean that we would not have any instances of `qx.Class` any more? Or perhaps they would just be a meta data that wraps...

you're right sorry - that was a not-enough-coffee moment :)

## Properties and Async There's been a few discussions about properties and how to handle async values in getters and setters; this comment is to clarify and discuss some ideas...

> I'm guessing that your setXxx() method intended to return promise; at the end. Yes > We don't have that option. Now that we have an implementation that implements first-class...

I think that there are two issues this is boiling down to: (a) the return value of `setXxx` (and not `.xxx=value`), and (b) whether `.setXxx` resolves the promise it is...

> The synchronous setter, setXxx() can not return a value Ok > getters and setters are synchronous and do no magic other than when specifically requested, e.g., transform OK for...

WRT to the apply and event handler, the reason why a property (whether via a synchronous setter or async setter) would chain the promise is because you cannot have the...