<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Wade,<br>
<br>
The current View Slides sends the whole slideshow in a Zip file over
the network. These slideshow Zip files can be 20-60 meg and I find
that sharing files of that size just doesn't work. Worse, if the
original file is still being shared it is impossible to resume a
document you have received by sharing without starting the whole
download over again. So I think my new idea makes a lot more sense,
and I'm thinking I can use code in Chat as an example to work from.<br>
<br>
I have moved both my repositories to gitorious:<br>
<br>
<a class="moz-txt-link-freetext" href="http://git.sugarlabs.org/projects/viewslides">http://git.sugarlabs.org/projects/viewslides</a><br>
<br>
<a class="moz-txt-link-freetext" href="http://git.sugarlabs.org/projects/readetexts">http://git.sugarlabs.org/projects/readetexts</a><br>
<br>
However, last night and this morning when I tried to do a git push to
the new repository I got this:<br>
<br>
[jim@localhost ~]$ cd olpc/readetexts/mainline/<br>
[jim@localhost mainline]$ ls<br>
activity NEWS ReadEtextsActivity.pyc setup.py<br>
locale po readtoolbar.py<br>
MANIFEST ReadEtextsActivity.py readtoolbar.pyc<br>
[jim@localhost mainline]$ git push origin master<br>
fatal: The remote end hung up unexpectedly<br>
<br>
This is on a machine where I have never done a git push before (I did
my development work on a different box). I created my SSH key and
published the public key in the account named jdsimmons, along with the
other public key from the other box. I just used ssh-keygen with no
parameters to generate the key, and gave it my passphrase when
prompted. I think this is all I did for the other box, but I can't
remember. So I don't know if this is my problem or something to do
with git.sugarlabs.org. If you or someone else can steer me in the
right direction I'd appreciate it.<br>
<br>
James Simmons<br>
<br>
<br>
Wade Brainerd wrote:
<blockquote
cite="mid:7087c32a0902021532m37f705d6l9520ec3d70ed2db3@mail.gmail.com"
type="cite">
<div class="gmail_quote">On Mon, Feb 2, 2009 at 6:10 PM, James
Simmons <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jim.simmons@walgreens.com">jim.simmons@walgreens.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Second,
now that I have this I want to perfect collaboration on my two<br>
Activities, Read Etexts and View Slides. Unfortunately, I am convinced<br>
that collaboration in View Slides that involves sending large Zip<br>
archives over the network is not and never will be practical. What I'm<br>
thinking about now is making the person "sharing" a slide show see only<br>
the image being viewed on the XO that has the full presentation. The<br>
master XO would page through the slides and those sharing would follow<br>
along. I'm not sure that's practical, either.</blockquote>
<div><br>
</div>
<div>I think sending one page at a time, and having the initiator
control the presentation is a great idea. Otherwise, you might as well
just send the document to everyone and have them open it up on their
own :)</div>
<div><br>
</div>
<div>Also, are you planning to move your repositories over to <a
moz-do-not-send="true" href="http://git.sugarlabs.org">git.sugarlabs.org</a>?
Most of the other activities are doing that now, and we have set up a
Sugar Labs ActivityTeam (<a moz-do-not-send="true"
href="http://wiki.sugarlabs.org/go/ActivityTeam">http://wiki.sugarlabs.org/go/ActivityTeam</a>)
to coordinate the process.</div>
<div><br>
</div>
<div>Best,</div>
<div>Wade</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
</blockquote>
<br>
</body>
</html>