Re: [Sugar-devel] Problem in sending email

2016-04-04 Thread Samuel Cantero
I have checked that someone has already processed your request. I guess Sebastian. Best regards, Samuel C. On Mon, Apr 4, 2016 at 4:18 AM, Samson Goddy wrote: > I just noticed that i can't send mail to the SLOB email address, sometimes > my mail get rejected by the Sugar-Dev list. I don't know

Re: [Sugar-devel] [DESIGN] Save as feature

2016-04-04 Thread Tony Anderson
Sadly, I am in a rush so haven't had a chance to follow this discussion in detail. An important point is that a user gives a name to a document by changing the text in the activity part of the toolbar. This can be done at any time. If this is done, the document should be save automatically as

Re: [Sugar-devel] [DESIGN] Save as feature

2016-04-04 Thread James Cameron
I agree, Sam. We've been through a save-as debate before. We need community consensus on function. There is no consensus yet. I won't be accepting this change into my OLPC branch unless there is a way to turn it off; because that's what I'd be doing on OLPC OS. It looks like this is a task wan

Re: [Sugar-devel] Need help with sugar-toolkit-gtk3

2016-04-04 Thread James Cameron
What about the call to datastore.create()? On Tue, Apr 05, 2016 at 02:26:42AM +0530, Utkarsh Tiwari wrote: > I did that. Even after disabling "datastore.write()" functions inside > activity.py ... the activity instance is stiil getting registered in > the Journal. > > Thanks, > Utkarsh Tiwari >

Re: [Sugar-devel] Need help with sugar-toolkit-gtk3

2016-04-04 Thread Utkarsh Tiwari
I did that. Even after disabling "datastore.write()" functions inside activity.py ... the activity instance is stiil getting registered in the Journal. Thanks, Utkarsh Tiwari On 4/5/16, James Cameron wrote: > Try this? > > When the shell (aka home view) starts a new instance of an activity, > it

Re: [Sugar-devel] [DESIGN] Save as feature

2016-04-04 Thread Sam Parkinson
Hi Utkarsh, I find the save as an interesting feature. From my knowledge, it was previously built into Sugar, however it was removed due to it annoying people. I don't know the exact reasoning, but here is what I think: * When does somebody quit and activity? Is it the right time to be as

Re: [Sugar-devel] Need help with sugar-toolkit-gtk3

2016-04-04 Thread James Cameron
Try this? When the shell (aka home view) starts a new instance of an activity, it calls the Activity.__init__() method, which calls _initialize_journal_object() method, which calls datastore.create(), followed by datastore.write(). On Mon, Apr 04, 2016 at 05:08:10PM +0530, Utkarsh Tiwari wrote: >

Re: [Sugar-devel] Issue tracking on Github?

2016-04-04 Thread Walter Bender
On Mon, Apr 4, 2016 at 10:08 AM, Dave Crossland wrote: > > Hi! > > On 4 April 2016 at 00:50, Devin Ulibarri wrote: > >> On 04/04/2016 12:35 AM, Dave Crossland wrote: >> > Here is why: >> > 1. Control. The community would be able to do what they wish with >> their >> > data. (the othe

Re: [Sugar-devel] Issue tracking on Github?

2016-04-04 Thread Dave Crossland
Hi! On 4 April 2016 at 00:50, Devin Ulibarri wrote: > On 04/04/2016 12:35 AM, Dave Crossland wrote: > > Here is why: > > 1. Control. The community would be able to do what they wish with > their > > data. (the other benefits really come from this one) > > > > > > Most of the data on

Re: [Sugar-devel] Need help with sugar-toolkit-gtk3

2016-04-04 Thread Utkarsh Tiwari
Hi, Whenever we start an activity from homeview, it gets registered in the Journal (through datastore.write()). I have inspected the activity.py file but there is someplace else besides activity.py where the datastore is being modified(activity instance is being added). I need to figure this o

Re: [Sugar-devel] Issue tracking on Github?

2016-04-04 Thread James Cameron
On Mon, Apr 04, 2016 at 12:48:15AM -0400, Dave Crossland wrote: > Hi Tony! > > On 3 April 2016 at 02:02, Tony Anderson wrote: > > You are proposing, appropriately, a new way to handle version > control for Sugar. > > I'm not sure about that :) I didn't intend to :)  >   > > There i