We are pondering a few changes in the Learning Design player in .LRN (package imsld) that I'd like to share with the rest of the community, specially with Gustaf. I also have a question about dependencies.
As of now, the player receives a Unit of Learning (zip file with material and and arbitrarily complex choreography of activities) and creates different "runs" or enactments of such unit. Until now, the resources (for the purpose of this discussion, HTML files) were stored in the CR. This hinders significantly the possibility of making small adjustments to the material. We're thinking on things such fixing typos, rewriting a paragraph, changing an image, etc.
The idea we implemented in a prototype (currently in HEAD) is to import all these resources in Xowiki when the UoL is loaded and allow the teaching staff to manipulate them through the Xowiki interface. We also have a variety of new scenarios in which students also edit and modify other resources, but they are irrelevant for the discussion.
The two issues that we encounter are:
1) If following this path, Imsld will have a strong dependency (as pointed by Gustaf and Emmanuelle) on Xowiki. The alternative would be make imsld sensitive to the presence of Xowiki and fall back to its previous behavior and using CR. What are the consequences if we opt for using only xowiki?
2) Resources are shown by the player through the use of 3 iframes: activity tree, environment and activity text. The last one is rendered using the xowiki interface, but it contains the main-site header and additional information that we would like to hide. Any suggestions on how to achieve such thing cleverly? I think the issue is how to use the functionality to edit pages but embedded in a more complex page (thus ruling the header/tail unnecessary).
Any feedback would be greatly appreciated.