Features/Save-As

Summary

Add a setting for a Save-As dialog to interrupt the activity Stop workflow if a name has not been set for the journal entry.

Owner

• Name: Utkarsh Tiwari
• Email: Utkarsh Tiwari <iamutkarshtiwari@gmail.com>

Current status

• Targeted release: 0.112
• Last updated: 24th April 2017
• Percentage of completion: 80%

Detailed Description

• add a setting save-as,
• when an activity stop button is pressed, and the journal entry has not been named, and when save-as is set, prompt for the name,
• fix any activities that are broken by the change,
• also backport to GTK+ 2 toolkit,

Benefit to Sugar

What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?

Force rather than passively encourage reflection.

Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.

Requested by Tony Anderson.

Scope

What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?

• GSettings schema, see https://github.com/sugarlabs/sugar/pull/750,
• GTK+ 3 toolkit activity stop flow, see https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/327,
• GTK+ 2 toolkit activity stop flow, see https://github.com/sugarlabs/sugar-toolkit/pull/4,
• Help activity [documentation], not started,
• Browse activity [identified regression], see https://github.com/sugarlabs/browse-activity/pull/49,

UI Design

Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.

Direct impact on work flow. A visual mockup is in https://github.com/sugarlabs/sugar-toolkit/pull/4

How To Test

Features/Save-As/Testing

User Experience

If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.

A save-as dialog will appear if the journal entry is not named.

Dependencies

What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?

No dependencies.

Contingency Plan

None necessary, revert to previous release behaviour.

Documentation

Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.

Release Notes

The Sugar Release Notes inform end-users about what is new in the release. An Example is 0.84/Notes. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.

Comments and Discussion

• Link to the discussion of this feature on lists.sugarlabs.org
• See the discussion tab for this feature.