Activities/View Slides - Revision history

Chimosky: Change Bugs link and source code link to Github.

2021-08-07T14:54:24Z

Change Bugs link and source code link to Github.

← Older revision		Revision as of 10:54, 7 August 2021
Line 90:		Line 90:

	* Document sharing is reliable but slow. Currently it uses Tubes to copy a file from one computer to another. When using Gabble the file is Base 64 encoded and sent using a method that has a lot of overhead, which is necessary because the two computers might be on different networks and have to deal with with firewalls and the like. You can minimize the problem by shrinking your images with "mogrify" as described above. This not only improves document sharing, it also improves performance and dramatically cuts down on disk space usage, which is vitally important on the XO!		* Document sharing is reliable but slow. Currently it uses Tubes to copy a file from one computer to another. When using Gabble the file is Base 64 encoded and sent using a method that has a lot of overhead, which is necessary because the two computers might be on different networks and have to deal with with firewalls and the like. You can minimize the problem by shrinking your images with "mogrify" as described above. This not only improves document sharing, it also improves performance and dramatically cuts down on disk space usage, which is vitally important on the XO!
	* [~~http~~://~~bugs~~.sugarlabs~~.org~~/~~query?component=View+Slides&col=id&col=summary&col=component&col=type&col=status&col=priority&col=milestone&col=time&col=changetime&order=priority Sugar Labs trac tickets~~]		* [https://github.com/sugarlabs/viewslides/issues Github Issues]

	== Source ==		== Source ==

	* ~~http~~://~~git~~.sugarlabs~~.org/projects~~/viewslides		* [https://github.com/sugarlabs/viewslides Github]
	* [http://activities.sugarlabs.org/en-US/sugar/addon/4039 ASLO page]		* [http://activities.sugarlabs.org/en-US/sugar/addon/4039 ASLO page]

RafaelOrtiz: /* Source */

2011-01-28T04:21:25Z

Source

← Older revision		Revision as of 00:21, 28 January 2011
Line 95:		Line 95:

	* http://git.sugarlabs.org/projects/viewslides		* http://git.sugarlabs.org/projects/viewslides
	* [http://activities.sugarlabs.org/en-US/sugar/addon/4039 ~~Sugar Activity Library~~ page]		* [http://activities.sugarlabs.org/en-US/sugar/addon/4039 ASLO page]

Patrol: moved Walter is a wanker 7/View Slides to Activities/View Slides over redirect: revert

2010-02-24T01:38:53Z

moved Walter is a wanker 7/View Slides to Activities/View Slides over redirect: revert

← Older revision	Revision as of 21:38, 23 February 2010
(No difference)

Page move vandal: moved Activities/View Slides to Walter is a wanker 7/View Slides: Walter is a wanker

2010-02-24T00:18:36Z

moved Activities/View Slides to Walter is a wanker 7/View Slides: Walter is a wanker

← Older revision		Revision as of 20:18, 23 February 2010
(No difference)

Patrol: moved Anal bleaching 14/View Slides to Activities/View Slides over redirect: revert

2010-02-21T22:40:00Z

moved Anal bleaching 14/View Slides to Activities/View Slides over redirect: revert

← Older revision		Revision as of 18:40, 21 February 2010
(No difference)

Anal bleaching: moved Activities/View Slides to Anal bleaching 14/View Slides: Anal bleaching

2010-02-21T22:21:46Z

moved Activities/View Slides to Anal bleaching 14/View Slides: Anal bleaching

← Older revision	Revision as of 18:21, 21 February 2010
(No difference)

FGrose at 22:01, 10 October 2009

2009-10-10T22:01:38Z

← Older revision		Revision as of 18:01, 10 October 2009
Line 1:		Line 1:
			<noinclude>{{TOCright}}[[Category:Activities\|View Slides]]</noinclude>
	== Description & Goals==		== Description & Goals==

Line 89:		Line 90:

	* Document sharing is reliable but slow. Currently it uses Tubes to copy a file from one computer to another. When using Gabble the file is Base 64 encoded and sent using a method that has a lot of overhead, which is necessary because the two computers might be on different networks and have to deal with with firewalls and the like. You can minimize the problem by shrinking your images with "mogrify" as described above. This not only improves document sharing, it also improves performance and dramatically cuts down on disk space usage, which is vitally important on the XO!		* Document sharing is reliable but slow. Currently it uses Tubes to copy a file from one computer to another. When using Gabble the file is Base 64 encoded and sent using a method that has a lot of overhead, which is necessary because the two computers might be on different networks and have to deal with with firewalls and the like. You can minimize the problem by shrinking your images with "mogrify" as described above. This not only improves document sharing, it also improves performance and dramatically cuts down on disk space usage, which is vitally important on the XO!
			* [http://bugs.sugarlabs.org/query?component=View+Slides&col=id&col=summary&col=component&col=type&col=status&col=priority&col=milestone&col=time&col=changetime&order=priority Sugar Labs trac tickets]

	== Source ==		== Source ==

	http://git.sugarlabs.org/projects/viewslides		* http://git.sugarlabs.org/projects/viewslides
			* [http://activities.sugarlabs.org/en-US/sugar/addon/4039 Sugar Activity Library page]
	[~~[Category~~:~~Activities]~~]

Jdsimmons: /* Description & Goals */

2009-07-17T14:24:37Z

Description & Goals

← Older revision		Revision as of 10:24, 17 July 2009
Line 8:		Line 8:

	Just like Read Etexts has advantages over using PDFs with the core Read activity, View Slides has the potential to be easier to use and perform better for books composed of scanned page images than core Read is with scanned page images converted to PDFs. With PDFs of scanned page images there is often a lag before a page image becomes visible, and moving from page to page can be awkward because there is a point where you see the bottom of one page and the top of the next, rather than cleanly moving from one page to the next. Getting a full page image to appear in the screen is difficult; with View Slides it is easy and automatic.		Just like Read Etexts has advantages over using PDFs with the core Read activity, View Slides has the potential to be easier to use and perform better for books composed of scanned page images than core Read is with scanned page images converted to PDFs. With PDFs of scanned page images there is often a lag before a page image becomes visible, and moving from page to page can be awkward because there is a point where you see the bottom of one page and the top of the next, rather than cleanly moving from one page to the next. Getting a full page image to appear in the screen is difficult; with View Slides it is easy and automatic.

			You can compare Read with PDF to View Slides by downloading the book "Jack and the Giants" from the Internet Archive in PDF format, then downloading the zipped image format I have created. Links to both are in the sections below.

			In the future the core Read Activity will be able to read zipped image files also, but judging from my experience doing that with evince (which Read uses code from) View Slides should still give you a better experience.

			The latest version of Read has excellent support for the Deja Vu format, which is also available from the Internet Archive. This format is especially designed to compress scanned book pages more than JPEG can without losing image quality. This format, like PDF, is available from the Internet Archive and may be the format to beat for scanned books.

	== Creating Slide Collections ==		== Creating Slide Collections ==

Jdsimmons: /* Optimizing Image File Sizes */

2009-07-17T14:11:47Z

Optimizing Image File Sizes

← Older revision		Revision as of 10:11, 17 July 2009
Line 46:		Line 46:
	zip JackAndTheGiants *.jpg		zip JackAndTheGiants *.jpg

	The original archive was about 40 megabytes, my new one was about 6 megabytes.		The original archive was about 40 megabytes, my new one was about 6 megabytes. You can download it [http://people.sugarlabs.org/~jdsimmons/JackAndTheGiants.zip here].

	If your files are in a supported format already then there is no need to convert them. Use display to see how they fit on the screen of a computer running at 1024x768. If they seem to be twice as tall as the screen then you can run this command to shrink them down by 50% and overwrite the original files:		If your files are in a supported format already then there is no need to convert them. Use display to see how they fit on the screen of a computer running at 1024x768. If they seem to be twice as tall as the screen then you can run this command to shrink them down by 50% and overwrite the original files:

Jdsimmons: /* Bugs */

2009-07-15T15:52:58Z

Bugs

← Older revision		Revision as of 11:52, 15 July 2009
Line 82:		Line 82:
	== Bugs ==		== Bugs ==

	* When you exit the activity it should save the current page number and resume on that page number when you resume the activity. This actually works, but because of a known bug in Journal (which has been fixed in the next version of Sugar) the page number meta data does not persist after a reboot. Also, the page number cannot be saved when the images are loaded from an SD card or USB drive. These devices don't have the same support for metadata as the Journal does.
	* Document sharing is reliable but slow. Currently it uses Tubes to copy a file from one computer to another. When using Gabble the file is Base 64 encoded and sent using a method that has a lot of overhead, which is necessary because the two computers might be on different networks and have to deal with with firewalls and the like. You can minimize the problem by shrinking your images with "mogrify" as described above. This not only improves document sharing, it also improves performance and dramatically cuts down on disk space usage, which is vitally important on the XO!		* Document sharing is reliable but slow. Currently it uses Tubes to copy a file from one computer to another. When using Gabble the file is Base 64 encoded and sent using a method that has a lot of overhead, which is necessary because the two computers might be on different networks and have to deal with with firewalls and the like. You can minimize the problem by shrinking your images with "mogrify" as described above. This not only improves document sharing, it also improves performance and dramatically cuts down on disk space usage, which is vitally important on the XO!