Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

Thanks for this testing. You are showing some serious ambiguity in the core implementation of activity.py A return of True from can_close should end processing except write_file. Aside from user 'ctrl' + q or quit, the activity could be closed as a result of the end of the Sugar session by

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

As you may know, I submitted this feature for GSOC17. Along with Sebastian Silva, I worked as a mentor on this project. The feature was modeled on the way most document processors work. They offer the ability to save or save as the document. Save is used when the document has already been

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

That has happened to me when I wanted to change a title. I erased the title to write a new one and hit enter. This can easily happen on an XO where the trackpad can cause strange things to happen. I would have appreciated a warning. If the save as feature includes preventing a blank title

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

Closing PR#49 sounds like an advance. I am glad to hear that Utkarsh's problem has been fixed. Tony On 04/25/2017 02:12 PM, James Cameron wrote: I did, and have again. I reassert my statements; please be detailed if you have different data. On Tue, Apr 25, 2017 at 01:54:37PM +0800, Tony

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

I did, and have again. I reassert my statements; please be detailed if you have different data. On Tue, Apr 25, 2017 at 01:54:37PM +0800, Tony Anderson wrote: > See Browse PR#49 > > Tony > > On 04/25/2017 01:27 PM, James Cameron wrote: > >Your point wasn't clear, and it doesn't test out

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

See Browse PR#49 Tony On 04/25/2017 01:27 PM, James Cameron wrote: Your point wasn't clear, and it doesn't test out either. Browse-200 on Sugar 0.110 does not override the journal entry title if it has been set by the user, and Utkarsh's patch does not change that. There is a use case for

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

Your point wasn't clear, and it doesn't test out either. Browse-200 on Sugar 0.110 does not override the journal entry title if it has been set by the user, and Utkarsh's patch does not change that. There is a use case for giving a saved instance a title; which is where the title that would be

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

My point was clear. The fact that Browse overrides the user-supplied title of the saved state is not likely to be a problem in practice. It is hard to imagine a use case where a user wants to give a saved instance of Browse a specific name so that the urls collectively can be restored some

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

On Tue, Apr 25, 2017 at 09:28:00AM +0800, Tony Anderson wrote: > The page https://wiki.sugarlabs.org/go/Features/Save-As has been > edited to provide more information on the feature and to update it > to my understanding of the status. Thanks. > I am not sure that the issue with Browse is

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

The page https://wiki.sugarlabs.org/go/Features/Save-As has been edited to provide more information on the feature and to update it to my understanding of the status. I am not sure that the issue with Browse is relevant. Browse does not save a 'document' created by a user. It saves the urls

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

I am unfamiliar with the technical term 'momentum'. The request is clear, merge the changes with the master. This PR was developed as part of GSOC16 so any momentum, whatever that is, is the responsibility of the developers. The material progress needed is to test the PR with the current

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

Hi, Dave I suppose this discussion is valuable if it helps make folks aware of what is going on. On the school server, I have a tutorial sequence to introduce users to basic html5 and css. This is followed by a presentation based on the text Eloquent Javascript. For the html introduction,

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

On 15 July 2016 at 09:04, Tony Anderson wrote: > The screenshot was archaeological - a feature since removed from Sugar. > Ah yes, I see, from 0.90 which is very old. > I have not used any formal social science methodology (and really don't > plan to - my time at the

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

Hi, Dave The screenshot was archaeological - a feature since removed from Sugar. I have not used any formal social science methodology (and really don't plan to - my time at the deployments is limited and is focussed on introducing new capabilities which may be of use to the teachers and

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

On 15 July 2016 at 08:33, Tony Anderson wrote: > I think we all hope someone will attempt to work with and support our > users. I have a lot of experience over many years working > with deployments, but would not suggest anything I have done is definitive. > I understand

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

I think we all hope someone will attempt to work with and support our users. I have a lot of experience over many years working with deployments, but would not suggest anything I have done is definitive. This is a feature that my experience tells me is needed. I am trying to develop a training

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

On 15 July 2016 at 08:22, Tony Anderson wrote: > Sugar is frozen to decisions made several years ago. I think that's because there is no UX lead who is able to show through user studies that changes are good. ___ Sugar-devel

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

The default is, of course, no change. The user or deployment can change by the command line. As Martin Dengler has pointed out Sugar is frozen to decisions made several years ago. Tony On 07/15/2016 02:04 PM, Dave Crossland wrote: I think user testing can resolve such ux disagreements. A

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

I think user testing can resolve such ux disagreements. A setting to choose from both is not a wise design decision because there is still a question of which is default and how easy it is to set. Since Tony is advocating for a change, perhaps you could do a user test. Have you done one before?

Re: [Sugar-devel] [sugarlabs/sugar-toolkit-gtk3] Save As Popup (#327)

As you might expect, I totally disagree. First, by that time the damage has been done. Either the 'save as' option has been taken with a new object created or the 'resumed' document has been overwritten - as at present. This feature has two objectives: 1 - require Journal items to have