I just checked in a refactoring of the way otrunk learner data code is 
saved through Sail.
I committed a change similar to this a few weeks ago.  This new change 
goes even further and in the process cleaned up some of the old code.  
It gets the code closer to supporting pluggable learner data persistence 
implementations. 

Before using this new code in a classroom, please verify that learner 
data is:
- getting loaded in
- getting saved back to the server
- getting saved to the local disk at regular intervals. 

You can test the last one by:
-- making changes
-- waiting a 2 minutes (every minute a file is saved to the local disk, 
so that file should include your changes)
-- force quitting the application  (this prevents your changes from 
being sent to the sds)
-- startup the application again (this will upload your changes saved 
locally, then download a file that should include those changes)
-- check for your changes.

There are currently 4 ways OTrunk and Sail can be integrated:
- Standard curnit with OTrunkStep - this is a typical Wise 2.5 or Wise 
3.0 curnit that has an OTrunkStep
- SailOTViewer - this is used by DIY.  It starts up the OTrunk view 
system to display an otml file.  It is used by UDL, CAPA, and ITSI
- OTrunkCurnit - this is used by PasOTrunk.  It starts up OTrunk and 
uses the controller system to create Pas objects similar to how 
XMLEncoder was used before.
- OTrunkCurnit with OTrunkStep - this is a special case of PasOTrunk 
that has an OTrunkStep inside.  The OTrunkStep starts up the view system 
to display the target object of the OTrunkStep.

I tested my changes with the first 2 ways, because they are used in 
production.  I believe my changes will not break the OTrunkCurnit stuff, 
but it should be tested too.

The projects affected by the changes are:
otrunk, sail-otrunk, pas-otrunk

The otrunk-jackrabbit project will be broken until I get it updated to 
use the new refactoring.

Scott

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"SAIL-Dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/SAIL-Dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to