Given the annoying behaviour of the bundle that seems like a good idea. But I did like the idea of integrating the pdf with the browser library stuff.
The idea was to distribute school manuals in pdf, each as a xol bundle and have the children download that. Before trying the procedure, I expected that once downloaded, the manuals would show up in the browser and clicking on a name would start the reader. No fuss. Philippe ------ The trouble with common sense is that it is so uncommon. <Anonymous> On Sunday 05 October 2008 13:03:51 Gary C Martin wrote: > On 5 Oct 2008, at 17:48, Walter Bender wrote: > > You should only need an index.html file that points to your PDF. > > > > <html> > > <meta http-equiv="refresh" > > content="0;url=file:///home/olpc/Library/[bundle name]/[PDF > > name].pdf"> > > </html> > > > > In the library/library.info file, there should be an activity_start > > entry as per: > > > > activity_start = index.html > > > > In theory, make_index.py reads this line from the info file when > > generating its index. > > Philippe, why not just distribute the pdf, as a pdf? What benefit is > there in making a single pdf into Library bundle (unless you're just > testing the process)? > > I must admit to not liking some of the old Library content, much of > it Browse just copies into the Journal, then you have to resume the > new pdf entry with Read, if you forget something is a pdf and have > already viewed it, you end up with multiple copies in the Journal. > Seems a bit backwards to me, I guess it makes the Library interface a > zip archive utility for installing pdfs into the Journal. > > Apologies if you were just testing the bundle process. > > --Gary _______________________________________________ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar