Changes

This has some interesting implications.

This has some interesting implications.

* Sugar code doesn't have to keep a .xol and a Library directory in sync, installing and uninstalling the lattr

* Sugar code doesn't have to keep a .xol and a Library directory in sync, installing and uninstalling the latter as .xols are opened and erased.

* The file system ensures uniqueness of content bundles

* The file system determines if a content bundle conflicts with another.

* Instead of making web pages telling readers how great some content is, they can view it for themselves before they download.

* Instead of making web pages telling readers how great some content is, they can view it for themselves before they download.

* Some collections have an index.html that does a meta http-equiv refresh to a path in file:///home/olpc/Library , this won't work (and I think breaks anyway in other Sugar environments)

* Some collections have an index.html that does a meta http-equiv refresh to a path in file:///home/olpc/Library , this won't work (and I think breaks anyway in other Sugar environments)

* Some collections (Biology, NatureImages, TranslationDictionary) reference a /usr/share/library-common/css/master.css).  This won't work if you browse them remotely.

* Some collections (Biology, NatureImages, TranslationDictionary) reference a /usr/share/library-common/css/master.css).  This won't work if you browse them remotely.

* I don't know what the performance implications are.  I know Firefox 3.6 has additional performance boosts as Mozilla moved more files into a single runtime .jar file.

* I don't know what the performance implications are.  I know Firefox 3.6 has additional performance boosts as Mozilla moved more files into a single runtime .jar file.