Yes, the plays will be shown concurrently, as well as the role parts. The reason why right now it doesn't behave that way is because of the table we are using to display the sequence. It was too confusing to display concurrent activities in the table.
That is why we are now working in a javascript tree (like the one LORS uses). It will be more easy to "navigate" inside the course using the tree. We are basing our development on the CopperCore tree, so when we finish with that, both of them should have pretty much the same behavior. Besides, with the table there was no sense to have into account the properties like "is-visible", or the sequence-type of the activity structures, but with the tree those properties will be interpreted/treated as they should.
BTW, we had a discussion about the learning-objects issue and we misunderstood the spec, so that will be fixed soon and commited this week.
Regards
