Talk:Features/Content support: Difference between revisions
→Browse can handle content bundles directly: new section |
|||
| Line 67: | Line 67: | ||
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 | * 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 | * 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. | ||
There are limitations to this: | |||
* 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. | ||
-- [[User:Skierpage|Skierpage]] 06:40, 4 September 2010 (EDT) | |||