File Share Activity

0 views
Skip to first unread message

Justin Lewis

unread,
Dec 11, 2009, 11:30:57 PM12/11/09
to sugar...@lists.sugarlabs.org, fileshar...@googlegroups.com
Hey members of sugar-devel,

Just wanted to let you know that I have been working on a file
share activity and is now in a testable state.

It is still under development, but I figured I would share it with
everyone and see what you all think.

The activity can be found on on the sugarlabs wiki.

Please feel free to check it out.  Let me know if you have any
suggestions, bugs or other feedback.



Justin Lewis

Tomeu Vizoso

unread,
Dec 12, 2009, 8:21:54 AM12/12/09
to Justin Lewis, sugar-devel, fileshareactivity
Would you like for people in Uruguay to test it? 0.84 and later Sugar
releases have file transfer in the journal, but most OLPC machines are
stuck with 0.82 for the time being.

Btw, are you the author of Bundle or is it another Lewis?

http://dev.laptop.org/git/activities/bundleactivity/

Regards,

Tomeu
> _______________________________________________
> Sugar-devel mailing list
> Sugar...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>



--
«Sugar Labs is anyone who participates in improving and using Sugar.
What Sugar Labs does is determined by the participants.» - David
Farning

Justin Lewis

unread,
Dec 12, 2009, 11:17:46 AM12/12/09
to fileshar...@googlegroups.com, sugar-devel
I am not the author of Bundle.  If people would like to test it, fine by me.  This was written mainly to get some sort of file transfer system on the olpc.  Another reason is on the 84, it seems you have to pick a file and send it to a specific user, where this system lets you pick files and then send them to anyone who has joined.

I have not had much testing with it yet so if they would like to test it, that would be great.  I still have a few things I need to work on, but any feedback would be great.


Justin Lewis



--

You received this message because you are subscribed to the Google Groups "FileShareActivity" group.
To post to this group, send email to fileshar...@googlegroups.com.
To unsubscribe from this group, send email to fileshareactiv...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fileshareactivity?hl=en.



Gary C Martin

unread,
Dec 12, 2009, 1:28:40 PM12/12/09
to Justin Lewis, fileshar...@googlegroups.com, sugar-devel
Hi Justin,

On 12 Dec 2009, at 16:17, Justin Lewis wrote:

> I am not the author of Bundle. If people would like to test it, fine by me. This was written mainly to get some sort of file transfer system on the olpc. Another reason is on the 84, it seems you have to pick a file and send it to a specific user, where this system lets you pick files and then send them to anyone who has joined.

+1!

Being able to publish a number of items for download is a very useful feature (imagine a teacher sharing several resources for a specific class lesson). Thanks for stepping up to do this. There has been talk on Journal at some future point providing something similar, but to be honest a really clean/simple/robust activity would be better, why?

1). Journal could be kept clean and simple instead of trying to overload it with multiple types of sharing features (technically possible, but the design will just get more and more unusable until it looks like a Microsoft office product).

2). As a separate activity it can be developed out side of the Sucrose development/release cycle and team.

3) As a separate activity it can be used by folks not running the latest and greatest version of Sugar (think a generation of hundreds of thousands of kids who use 0.82, and perhaps only ever will).

> I have not had much testing with it yet so if they would like to test it, that would be great. I still have a few things I need to work on, but any feedback would be great.

I'll try and give it some testing, I might have some UI/design type feedback as well if that's OK with you? ;-)

Couple of quick questions:

- Is it possible to create your git repository on http://git.sugarlabs.org/ or is it already somewhere public?

- You named your bundle FileShare-2009-12-11.xo, I'd just go with FileShare-1.xo to stick with current convention, and start bumping up the version integer for each new release from now on (that way Sugar will happily upgrade a previous version correctly).

Thanks again for having a go at tackling this one!

Regards,
--Gary

P.S. I think Tomeu mentioned the Bundle activity (I never saw it correctly working when I tested), as there could be a workflow where basically a zip of a bunch of Journal entries could be created by an Activity, and then transferred in one go as a single compressed file (or perhaps in chunks like a torrent). Your File Share activity could potentially subsume this workflow, or do something similar i.e. could provide "Download All" as the primary button that would trigger a downloading of a single zip of everything; then have little download buttons next to each file if folks want to get just a few (and avoid the need for users to have to select file rows and click on a separate download button). Sorry just rambling, only looked at your screen shot so far ;-)

Wade Brainerd

unread,
Dec 12, 2009, 1:40:50 PM12/12/09
to Gary C Martin, Justin Lewis, sugar-devel, fileshar...@googlegroups.com
+1 from me too, for all of Gary's reasons. Looking forward to
checking the activity out.

-Wade

Justin Lewis

unread,
Dec 12, 2009, 8:56:11 PM12/12/09
to fileshar...@googlegroups.com, sugar-devel
Thanks for the feedback Gary.


> - Is it possible to create your git repository on http://git.sugarlabs.org/ or is it already somewhere public?

Yep, it is currently on Gitorious
(http://gitorious.org/jlew/xo-file-distro). I can move it to
git.sugarlabs.org if that would be better for everyone in the sugar
community.

> - You named your bundle FileShare-2009-12-11.xo, I'd just go with FileShare-1.xo to stick with current convention, and start bumping up the version integer for each new release from now on (that way Sugar will happily upgrade a previous version correctly).

Ok, I'll do that next time I release a build.

I will try to put download buttons next to each file and convert my
current download button into a download all (I think I will still have
it download all the files as separate objects but have it download
them all automatically to keep the system simple).

And feel free to any UI/design feedback as well. This is my first use
of gtk, so if you have any suggestions, please let me know.


Justin Lewis


On Sat, Dec 12, 2009 at 1:28 PM, Gary C Martin <ga...@garycmartin.com> wrote:
>

Aleksey Lim

unread,
Dec 12, 2009, 9:18:11 PM12/12/09
to Gary C Martin, Justin Lewis, sugar-devel, fileshar...@googlegroups.com
On Sat, Dec 12, 2009 at 06:28:40PM +0000, Gary C Martin wrote:
> Hi Justin,
>
> On 12 Dec 2009, at 16:17, Justin Lewis wrote:
>
> > I am not the author of Bundle. If people would like to test it, fine by me. This was written mainly to get some sort of file transfer system on the olpc. Another reason is on the 84, it seems you have to pick a file and send it to a specific user, where this system lets you pick files and then send them to anyone who has joined.
>
> +1!
>
> Being able to publish a number of items for download is a very useful feature (imagine a teacher sharing several resources for a specific class lesson). Thanks for stepping up to do this. There has been talk on Journal at some future point providing something similar, but to be honest a really clean/simple/robust activity would be better, why?
>
> 1). Journal could be kept clean and simple instead of trying to overload it with multiple types of sharing features (technically possible, but the design will just get more and more unusable until it looks like a Microsoft office product).

Well, maybe I wasn't so clear in that question, but the final target of
Journal Plugins was 1) technical, make core development process more
flexible and 2) social, encourage non core developers to experiment with
Journal.

And I see what people think about this proposal - fat journal
application. At the end I wasn't sure that plugins should work in shell
process. One of consequence of 1) is having some kind of shell
integration. That could be very useful if activities like that, will be
more integrated to the shell UI e.g. this activity will behave like
"regular" GUI downloader, so needs at least notification area
integration from shell(or so).

I'm going to rename "Journal Plugins" feature to "Shell UI
integration"..

--
Aleksey

Aleksey Lim

unread,
Dec 12, 2009, 9:21:07 PM12/12/09
to Gary C Martin, Justin Lewis, sugar-devel, fileshar...@googlegroups.com
..and making my thoughts more clear :)

On Sat, Dec 12, 2009 at 06:28:40PM +0000, Gary C Martin wrote:
> 2). As a separate activity it can be developed out side of the Sucrose development/release cycle and team.

that was another reason for Plugins proposal(now Shell Integration API)

> 3) As a separate activity it can be used by folks not running the latest and greatest version of Sugar (think a generation of hundreds of thousands of kids who use 0.82, and perhaps only ever will).

as well

--
Aleksey

Gary C Martin

unread,
Dec 13, 2009, 11:44:41 PM12/13/09
to Justin Lewis, fileshar...@googlegroups.com, sugar-devel
Hi Justin,

On 13 Dec 2009, at 01:56, Justin Lewis wrote:

> Thanks for the feedback Gary.
>
>> - Is it possible to create your git repository on http://git.sugarlabs.org/ or is it already somewhere public?
>
> Yep, it is currently on Gitorious
> (http://gitorious.org/jlew/xo-file-distro). I can move it to
> git.sugarlabs.org if that would be better for everyone in the sugar
> community.

Thanks, that rep's fine for me if that's where you're already set-up to work :-)

>> - You named your bundle FileShare-2009-12-11.xo, I'd just go with FileShare-1.xo to stick with current convention, and start bumping up the version integer for each new release from now on (that way Sugar will happily upgrade a previous version correctly).
>
> Ok, I'll do that next time I release a build.
>
> I will try to put download buttons next to each file and convert my
> current download button into a download all (I think I will still have
> it download all the files as separate objects but have it download
> them all automatically to keep the system simple).

Cool. Will keep an eye out for your next build!

> And feel free to any UI/design feedback as well. This is my first use
> of gtk, so if you have any suggestions, please let me know.

Yea, gtk is still a huge amorphous blob of unexpected classes and methods to me as well, the only way I get by is with constant reference to the class documentation, poking through other people's code, and living by what wits I have :-) Took me the best part of half a day just to work out how to add an optional scrollbar to a text label widget!

Regards,
--Gary

> Justin Lewis
>
>
> On Sat, Dec 12, 2009 at 1:28 PM, Gary C Martin <ga...@garycmartin.com> wrote:
>>
>> Hi Justin,
>>
>> On 12 Dec 2009, at 16:17, Justin Lewis wrote:
>>
>>> I am not the author of Bundle. If people would like to test it, fine by me. This was written mainly to get some sort of file transfer system on the olpc. Another reason is on the 84, it seems you have to pick a file and send it to a specific user, where this system lets you pick files and then send them to anyone who has joined.
>>
>> +1!
>>
>> Being able to publish a number of items for download is a very useful feature (imagine a teacher sharing several resources for a specific class lesson). Thanks for stepping up to do this. There has been talk on Journal at some future point providing something similar, but to be honest a really clean/simple/robust activity would be better, why?
>>
>> 1). Journal could be kept clean and simple instead of trying to overload it with multiple types of sharing features (technically possible, but the design will just get more and more unusable until it looks like a Microsoft office product).
>>
>> 2). As a separate activity it can be developed out side of the Sucrose development/release cycle and team.
>>
>> 3) As a separate activity it can be used by folks not running the latest and greatest version of Sugar (think a generation of hundreds of thousands of kids who use 0.82, and perhaps only ever will).
>>
>>> I have not had much testing with it yet so if they would like to test it, that would be great. I still have a few things I need to work on, but any feedback would be great.
>>
>> I'll try and give it some testing, I might have some UI/design type feedback as well if that's OK with you? ;-)
>>
>> Couple of quick questions:
>>
>> - Is it possible to create your git repository on http://git.sugarlabs.org/ or is it already somewhere public?
>>
>> - You named your bundle FileShare-2009-12-11.xo, I'd just go with FileShare-1.xo to stick with current convention, and start bumping up the version integer for each new release from now on (that way Sugar will happily upgrade a previous version correctly).
>>
>> Thanks again for having a go at tackling this one!
>>
>> Regards,
>> --Gary
>>
>> P.S. I think Tomeu mentioned the Bundle activity (I never saw it correctly working when I tested), as there could be a workflow where basically a zip of a bunch of Journal entries could be created by an Activity, and then transferred in one go as a single compressed file (or perhaps in chunks like a torrent). Your File Share activity could potentially subsume this workflow, or do something similar i.e. could provide "Download All" as the primary button that would trigger a downloading of a single zip of everything; then have little download buttons next to each file if folks want to get just a few (and avoid the need for users to have to select file rows and click on a separate download button). Sorry just rambling, only looked at your screen shot so far ;-)
>>
>> --
>>
>> You received this message because you are subscribed to the Google Groups "FileShareActivity" group.
>> To post to this group, send email to fileshar...@googlegroups.com.
>> To unsubscribe from this group, send email to fileshareactiv...@googlegroups.com.
>> For more options, visit this group at http://groups.google.com/group/fileshareactivity?hl=en.
>>
>>
Reply all
Reply to author
Forward
0 new messages