<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
The original idea in Sugar was to 'hide' the directory and file
model from users through the Journal. The effect of organizing files
into groups was to define tags as virtual directories in the fashion
of picasa.<br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 05/08/2016 12:11 PM, <a class="moz-txt-link-abbreviated" href="mailto:sam@sam.today">sam@sam.today</a>
wrote:<br>
</div>
<blockquote cite="mid:1462702310.1705.0@smtp.gmail.com" type="cite">Hi
All,
<div><br>
</div>
<div>This is a very interesting project, and is a *very large
change* to how we'll interact with the journal. *Please join
the design discourse*</div>
<div><br>
</div>
<div>I think that the idea of providing a way of sorting learning
into "mini-journals" is very helpful. Users can make a
mini-journal for a unit of work in school, an assignment/project
or a group activity that a teacher is running.</div>
<div><br>
</div>
<div>I think it is also quite natural. Currently the journal is
like one big box; you put everything in and search for it later.
Abhijit's proposal makes the journal into a collection of boxes
- one box for each project. I swear that you physically do this
in real life at times.</div>
<div><br>
</div>
<div>Another element of the proposal is forcing people to put
every activity in a mini-journal/"box". I think this is a nice
way to address journal clutter; you have a box of random stuff
for each project rather than a huge box with too much random
stuff.</div>
<div><br>
</div>
<div>The 2nd element of Abhijit's feature is the collaboration.
You can share your box with other people; useful for doing
group projects. Your friends can add photos, type more on the
"Report" write document, or whatever. I think that this makes
the collab system very conceptually simple for us as users.</div>
<div><br>
</div>
<div>Technically, the collab will be quite challenging. While
Sugar has a collab system when users are in activities ("online"
sync), there is not yet a system to sync when the users are not
active in the activity ("offline" sync). We can probably get a
system that works in good times (when every user is online and
connected), but I think that we will focus on adding conflict
resolution UI for when things get out of sync.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Sam</div>
<div><br>
On Thu, May 5, 2016 at 10:47 AM, Abhijit Patel
<a class="moz-txt-link-rfc2396E" href="mailto:abhisandhyasp.ap@gmail.com"><abhisandhyasp.ap@gmail.com></a> wrote:<br>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">Hi all,
<div>I will be working on the Journal-Rethink project
during GSoC'16. I would like to discuss with the
community regarding the designs and your expectations
from this project.</div>
<div><br>
</div>
<div>A brief description of project:</div>
<div><br>
</div>
<div>Focus -> enhance Journal such that students could
use it as a platform to do their project-work. <br>
</div>
<div><br>
</div>
<div>Major features that will be added are:</div>
<div><br>
</div>
<div>1. Shared mini-journal:</div>
<div><br>
</div>
<div>Present-> Sugar Journal shares only single
instance of an activity with a group of participants.</div>
<div><br>
</div>
<div>Idea-> creating one single instance (a
mini-journal) which has instances of all the activities
to be shared.<br>
</div>
<div><br>
</div>
<div>UI -> Journal contains list of projects
(mini-journals) in Projects List View [1]. Project [2]
contains a list of activities that are shared with the
same participants under the same project in the mini
journal.</div>
<div>
<div><br>
</div>
<div>Flow chart to explain the feature [3].</div>
<div>[1] <a moz-do-not-send="true"
href="http://wiki.sugarlabs.org/go/File:Project_Lists.png"
target="_blank">Project List View</a></div>
<div>[2] <a moz-do-not-send="true"
href="http://wiki.sugarlabs.org/go/File:Project_View.png"
target="_blank">Mini-Journal (project) View</a></div>
<div>[3] <a moz-do-not-send="true"
href="http://wiki.sugarlabs.org/go/File:Flow_chart_journal.png"
target="_blank">Flow-Chart</a></div>
<div><br>
</div>
<div>2. File Syncer System for mini-journal:</div>
<div><br>
</div>
<div>Use -> sync the files when the user does not
have the activity running. <br>
</div>
<div>
<div>Further use to alert the user for the changes
that occur in the state of shared activity by
implementing the alert tool. </div>
<div><br>
</div>
<div>UI -> A alert tool box with a palette box
which could be used as an indication of new
notifications or alerts that will be prompted when
the state of shared activity changes.</div>
</div>
<div><br>
</div>
<div>Other features are like</div>
<div> -> Icon View for Journal, </div>
<div> -> "Add new entry" tool,</div>
<div> -> Integrating chat activity in mini-journal.</div>
<div><br>
</div>
<div>More details about the project are in my proposal
[4].</div>
<div>Any suggestions or advice regarding the design or
any other aspects of the project are welcomed :)<br>
</div>
<div><br>
</div>
<div>[4] <a moz-do-not-send="true"
href="https://www.docdroid.net/hbalTLC/1458885012-journal-rethink-proposal.pdf.html"
target="_blank">Journal-Rethink-Proposal</a><br>
</div>
<div><br>
</div>
<div>Best Regards,</div>
<div>Abhijit.</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Sugar-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>