Re: [Sugar-devel] [IAEP] [SLOBS] [SLOB] GSoC mentor stipend motion

On 12 May 2016 at 10:52, Dave Crossland wrote: > On 12 May 2016 at 09:42, Walter Bender wrote: > >> As Adam has pointed out, this motion has failed to pass. It seems that >> there is some support of the idea of offering at least a portion of the >> GSoC

Re: [Sugar-devel] Fwd: GSOC

On Tue, May 17, 2016 at 4:44 PM, Ütkarsh Tiwari wrote: > I need to overwrite(delete) the existing object with a new object in > the Journal. > Can you explain your use case a bit more? Why is it not adequate to just modify the existing object? What is achieved by

Re: [Sugar-devel] Fwd: GSOC

I need to overwrite(delete) the existing object with a new object in the Journal. Thanks, Utkarsh Tiwari On 5/18/16, Sam Parkinson wrote: > If you make an activity, all of the journal interaction is handled by > the Journal. Maybe that would help you in this instance?

Re: [Sugar-devel] Fwd: GSOC

If you make an activity, all of the journal interaction is handled by the Journal. Maybe that would help you in this instance? On Wed, May 18, 2016 at 5:02 AM, Ütkarsh Tiwari wrote: Hi, How can we overwrite(contents) a specific object in Journal? Thanks,

Re: [Sugar-devel] Fwd: GSOC

Hi, How can we overwrite(contents) a specific object in Journal? Thanks, Utkarsh On 5/18/16, Ütkarsh Tiwari wrote: > Hi Tony, > In case if the user chooses to overwrite the > contents(code) of the existing project(already saved in Journal), > would

Re: [Sugar-devel] Fwd: GSOC

Hi Tony, In case if the user chooses to overwrite the contents(code) of the existing project(already saved in Journal), would you like to overwrite that Journal object or create a new object(overwritten- this might create duplicate names)? Thanks, Utkarsh Tiwari On 5/17/16, Walter

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

On Tue, May 17, 2016 at 12:35 PM, Dave Crossland wrote: > > On 17 May 2016 at 09:46, Walter Bender wrote: > >> we need to send out a clear description of what is expected of App >> developers ("transfer" their repos to sugarlabs) and how to manage issues

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

On 17 May 2016 at 11:44, Walter Bender wrote: > > On Tue, May 17, 2016 at 11:03 AM, Dave Crossland wrote: > >> >> On 3 April 2016 at 20:36, James Cameron wrote: >> >>> > >>> > Is wiki.sugarlabs.org used for tracking release engineering

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

On 17 May 2016 at 09:46, Walter Bender wrote: > we need to send out a clear description of what is expected of App > developers ("transfer" their repos to sugarlabs) and how to manage issues > once the switch-over has occurred.

Re: [Sugar-devel] Fwd: GSOC

I believe it defaults to ~/Documents (outside of sugar-build). -walter On Tue, May 17, 2016 at 10:48 AM, Ütkarsh Tiwari wrote: > Hi, > What is the location of the 'Journal/Documents' folder inside > sugar-build? > > Thanks, > Utkarsh Tiwari > > On 5/15/16, Tony

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

AFAIK, Martin is still the release manager. -walter On Tue, May 17, 2016 at 11:03 AM, Dave Crossland wrote: > > On 3 April 2016 at 20:36, James Cameron wrote: > >> > >> > Is wiki.sugarlabs.org used for tracking release engineering work? >> >> I'm not the

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

On 3 April 2016 at 20:36, James Cameron wrote: > > > > Is wiki.sugarlabs.org used for tracking release engineering work? > > I'm not the release engineer for Sugar, sorry. Who will manage the 0.110 release? https://wiki.sugarlabs.org/go/Development_Team/Contacts seems stale

Re: [Sugar-devel] Fwd: GSOC

Hi, What is the location of the 'Journal/Documents' folder inside sugar-build? Thanks, Utkarsh Tiwari On 5/15/16, Tony Anderson wrote: > Hi, Utkarsh > > I gave this version a trial. I think the integration is complete. The > next problems are left over from Richa

Re: [Sugar-devel] Sugar-On-The-Ground features

Tony, my hosting service is suddenly on an RBL so my email is not making it to the list could you reply to the list for my to keep the record in the archives going please. > On May 17, 2016 at 9:20 AM Tony Anderson wrote: > > > Hi, Jerry > > You raise some interesting

Re: [Sugar-devel] Beautiful Soup

Hi, I have resolved the issues which I had been facing with prettifying the code on display(webconsole) as well as inside the user's .html file! Will soon share the xo as soon as I fix the other mentioned issues. Thanks, Utkarsh On 5/17/16, Sam Parkinson wrote: >

Re: [Sugar-devel] [GSOC] Font Editor Next Steps

On 17 May 2016 at 10:22, Lionel Laské wrote: > it take me lot of time to ensure first that it make sense to run videos in > a browser on the XO-1. > That it was possible is very encouraging :D ___ Sugar-devel mailing list

Re: [Sugar-devel] [GSOC] Font Editor Next Steps

2016-05-17 3:10 GMT+02:00 Dave Crossland : > > I have concerns about the performance of sugar-web apps, especially on > XO-1s. My understanding is that one of the main engineering concerns that > OLPC Australia people had with Sugar was the delay in upgrading Browse to > webkit2;

Re: [Sugar-devel] Sugar-On-The-Ground features

Hi, Jerry You raise some interesting points. Thanks for confirming that ejabberd still requires registration. How would an xo connect to different servers for backup and for ejabberd? What might be useful is that the client is automatically registered for ejabberd at connection but only

[Sugar-devel] [ASLO] Release HelloWeb-3

Activity Homepage: http://activities.sugarlabs.org/addon/4791 Sugar Platform: 0.82 - 0.104 Download Now: http://activities.sugarlabs.org/downloads/file/29243/helloweb-3.xo Release notes: Removes some unused files. Corrects problem with stop button. Sugar Labs Activities

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

+1 for migrating. But... I think we need to send out a clear description of what is expected of App developers ("transfer" their repos to sugarlabs) and how to manage issues once the switch-over has occurred. -walter On Mon, May 16, 2016 at 11:13 PM, Dave Crossland wrote: > Hi >

Re: [Sugar-devel] Sugar-On-The-Ground features

Hi, Jerry You want the url to be something like http://communityserver or http://server1? I think that should be easy to do. Wouldn't registration naturally use the hostname given at install time? Ds_backup uses the name from registration which is shown in the control panel network. I was

Re: [Sugar-devel] Sugar-On-The-Ground features

Would be nice to be able to alter the url/dns_name of the server machine that is offering the backup from within the client as not to rely on the only hardcoded 'schoolserver' dns_name that registration provides. As myself and others have said the original XS model wants to run everything and that

Re: [Sugar-devel] Sugar-On-The-Ground features

Hi, Jerry I am not sure how ds_backup is connected to webservices. Tony On 05/17/2016 02:15 PM, Jerry Vonau wrote: Only once ds-backup-client is modified to fit into the webservices framework and its settings can be viewed/modified from within sugar-cp-backup or the webservices applet. Just

Re: [Sugar-devel] Sugar-On-The-Ground features

Only once ds-backup-client is modified to fit into the webservices framework and its settings can be viewed/modified from within sugar-cp-backup or the webservices applet. Just my 'loonie's'[1] worth, Jerry 1. https://en.wikipedia.org/wiki/Loonie > On May 17, 2016 at 6:42 AM Tony Anderson

Re: [Sugar-devel] Sugar-On-The-Ground features

Hi, Sebastian So what I assume James Cameron means when he says backup is not part of Sugar is that: sugar-cp-backup-0.106.0-1.fc18.noarch is and ds-backup-client-0.106.0.1.fc18.noarch is not. Perhaps, the package should be renamed: sugar-ds-backup-client-0.106.0.1.fc18.noarch Tony On

Re: [Sugar-devel] Beautiful Soup

Tony, given that the fiddle can't even preserve line breaks when saving, there are only 2 reasons that this could be happening: 1. You are building on a horrible base 2. You have built a horrible thing Maybe you should start over and use a simple Python activity? My simple prototype that I

Re: [Sugar-devel] Beautiful Soup

Hi, Sebastian Which, at the end of the day, is what we are doing now. Tony On 05/17/2016 01:18 PM, Sebastian Silva wrote: El 17/05/16 a las 06:06, Tony Anderson escribió: How then do we maintain the contributions from GSOC participants since virtually all of them leave the community at the

Re: [Sugar-devel] Beautiful Soup

El 17/05/16 a las 06:06, Tony Anderson escribió: > How then do we maintain the contributions from GSOC participants since > virtually all of them leave the community at the > end of the summer to meet their obligations for school or work? Presumably, we merge them, or fail them. :-)

Re: [Sugar-devel] Beautiful Soup

Hi, Sebastian How then do we maintain the contributions from GSOC participants since virtually all of them leave the community at the end of the summer to meet their obligations for school or work? Tony On 05/17/2016 12:49 PM, Sebastian Silva wrote: El 17/05/16 a las 04:39, Tony Anderson

Re: [Sugar-devel] Sugar-On-The-Ground features

El 17/05/16 a las 04:36, Tony Anderson escribió: > This 'OLPC OS' is a recent invention. I still consider what is > installed on an XO as Sugar (or a Fedora remix). Tony, Please don't use different terminology as everyone else. If you please go into your XO and type `rpm -qa | grep sugar`

Re: [Sugar-devel] Beautiful Soup

El 17/05/16 a las 04:39, Tony Anderson escribió: > Do you consider maintenance by the community a problem? I don't think there is such a thing except for stuff everyone uses or cares for. The point is Ms. Richa Sehgal is not maintaining this fiddle. Other such tools are properly maintained, and

Re: [Sugar-devel] Process for updating help.sugarlabs.org

Version is here: https://github.com/godiard/help-activity/blob/master/source/conf.py#L51 Then, you need regenerate the html https://help.sugarlabs.org/how_to_help.html On Tue, May 17, 2016 at 1:21 AM, Dave Crossland wrote: > > Hi! > > https://help.sugarlabs.org is v0.106, so I

Re: [Sugar-devel] Sugar-On-The-Ground features

Hi, Sebastian Exactly. Tony On 05/17/2016 11:00 AM, Sebastian Silva wrote: El 17/05/16 a las 01:52, Tony Anderson escribió: As always a good programmer implements a feature and makes it available for use. If it is a good design it will be adopted. In contributing to a free software

Re: [Sugar-devel] Sugar-On-The-Ground features

Hi, Sebastian Agreed. This includes the screenshot feature as well. Tony On 05/17/2016 11:02 AM, Sebastian Silva wrote: El 17/05/16 a las 01:33, Tony Anderson escribió: The home view implementation suffers heavily from the default naming in the Journal which the 'save as' feature addresses.

Re: [Sugar-devel] Sugar-On-The-Ground features

Hi, Sebastian It is not a hack - it has been part of Sugar since 0.84 (before there was even a remix and before there were git repositories). AFAIK, it has not been updated in years. This 'OLPC OS' is a recent invention. I still consider what is installed on an XO as Sugar (or a Fedora

Re: [Sugar-devel] Beautiful Soup

Do you consider maintenance by the community a problem? Tony On 05/17/2016 10:56 AM, Sebastian Silva wrote: El 17/05/16 a las 02:01, Tony Anderson escribió: What do you mean by upstream? I meant a fiddle that is maintained by somebody else (upstream). .

Re: [Sugar-devel] Sugar-On-The-Ground features

El 17/05/16 a las 01:33, Tony Anderson escribió: > The home view > implementation suffers heavily from the default naming in the Journal > which the 'save as' feature > addresses. I agree here, let's land the save as feature first then. :-) ___

Re: [Sugar-devel] Sugar-On-The-Ground features

El 17/05/16 a las 01:45, Tony Anderson escribió: > If you want an rsync solution, that is what is currently implemented > in Sugar (although > James Cameron claims this is not part of Sugar). It is distributed in > the 13.2.5 release. As far as I understand, that is a hack, and not part of

Re: [Sugar-devel] Sugar-On-The-Ground features

El 17/05/16 a las 01:52, Tony Anderson escribió: > As always a good programmer implements a feature and makes it > available for > use. If it is a good design it will be adopted. In contributing to a free software project, a good contributor will update the feature until it is adopted. I have

Re: [Sugar-devel] Beautiful Soup

El 17/05/16 a las 02:01, Tony Anderson escribió: > > What do you mean by upstream? I meant a fiddle that is maintained by somebody else (upstream). ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org

Re: [Sugar-devel] [GSOC] Font Editor Next Steps

> But I realised after posting this reasoning that sugar-web makes it > possible to package a JS app for the Sugar desktop, so the addressable > market is actually the same for JS and Py based Activities. > It's exactly my thought. Since Sugar 0.100 it's easy to create Sugar activity using

Re: [Sugar-devel] Extracting fiddle information from an html file

Hi, Utkarsh This feature will require some work - not just from pretty-printing. Consider an html file: hello h1 { text-align:center; } My title console.log($('h1').text()) When this file is extracted. The css panel should show the content. The html panel should

Re: [Sugar-devel] Beautiful Soup

Hi, Sebastian What do you mean by upstream? Tony On 05/17/2016 07:59 AM, Sebastian Silva wrote: Looking at that code, I have to wonder the same thing as Dave... having an upstream /fiddle /would look much cleaner IMHO. El 17/05/16 a las 00:49, Ütkarsh Tiwari escribió: Checkout the

Re: [Sugar-devel] Beautiful Soup

Hi, Yash I think this is an example with the problem of carrying on design discussions on a public forum. The 'save' feature saves an html file correctly with no line feeds. This makes looking at the file in a text editor (such as gedit) difficult. BeautifulSoup is already installed in Sugar

Re: [Sugar-devel] Beautiful Soup

Hi, Dave This capability was developed during GSOC 15 but has not been released. There is no effort to write the fiddler part, the problem is to integrate it with Browse so it can be used. Tony On 05/17/2016 04:00 AM, Dave Crossland wrote: Hi Kindly, I'm confused about this js fiddler

Re: [Sugar-devel] Sugar-On-The-Ground features

Hi, Sebastian As always a good programmer implements a feature and makes it available for use. If it is a good design it will be adopted. If not, the community will be more aware of the opportunity and may come up with a more successful approach. It is very easy to discuss a new feature and

Re: [Sugar-devel] Sugar-On-The-Ground features

Hi, Sebastian I assume you mean you have not tried the feature. It is implemented by Sugar but is, of course, meaningless without a server. I am not sure what you mean by generalized. Registration establishes the directory on the server for the rsync backup and creates a public/private key to

Re: [Sugar-devel] Sugar-On-The-Ground features

Hi, Sebastian The design assumption is a server using xsce6 (CentOS). Naturally, there are many ways to build a LAMP stack and large deployments such as Uruguay, Peru, and others may have their own solution (e.g. Rwanda has its own as well). What I said was that Sugar and the school server

Re: [Sugar-devel] Sugar-On-The-Ground features

Hi Sebastian, Manash is implementing this feature. Tony On 05/17/2016 07:50 AM, Sebastian Silva wrote: >The design discussion on the backup is at >https://wiki.sugarlabs.org/go/Sugar-server_Journal_backup. So who will work on this, Utkarsh or Manash?

Re: [Sugar-devel] Sugar-On-The-Ground features

Sebastian I think we are discussing too many independent issues together. I overstated the 'reverse'. I believe Sugar can still be distributed with a default of 'resume' from the home view. However, a gsetting configuration could allow deployments and users to select the resume new as

Re: [Sugar-devel] Beautiful Soup

Looking at that code, I have to wonder the same thing as Dave... having an upstream /fiddle /would look much cleaner IMHO.// El 17/05/16 a las 00:49, Ütkarsh Tiwari escribió: > > Checkout the web-console.py file for the relevant extraction code. >