Many classes don't have an actual implementation yet. The plan is to create stubs until you can compile cleanly so we know what actually needs to work, then we try to get it to work. We've only recently received a report that one large app finally compiles so we are just starting in on getting things to run. We can use all the help we can get.
OK, I see.
Royale solve the problem how to show a PopUp, etc ... and mx/spark is a
layer (emulation) over the Royale and not directly from the browser (this
was already solved by Royale).
It's good. Less fragmentation.
Then, I need to get familiar with Royale first and beads, etc ... that are
all new for me, before thinking in go thru mx/spark and who to implement a
few missing pieces.