<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<body text="#000000" bgcolor="#FFFFFF">
As you might expect, I totally disagree.<br>
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.<br>
This feature has two objectives:<br>
1 - require Journal items to have a name supplied by user<br>
2 - enable the user to choose whether to save the object as a
new one or to simply save the modified document. <br>
This proposal addresses neither objective.<br>
You are not going to change your point of view so the only solution
I can see is to provide a gsetting option so that users and
deployments can decide on how they want this to work. <br>
Re: the screenshot. Help me - as I remember this dialog was modal
and required an entry in the description area - leaving the title as
'Write activity' was ok.<br>
This was to implement Walter's desire that the description serve as
the message does in git.<br>
<div class="moz-cite-prefix">On 07/15/2016 04:36 AM, Sebastian Silva
<p>As promised here's a screenshot of Sugar 0.92's "save as"
alt="captura de pantalla de 2016-07-14 21-33-17"
<p>As per our meeting today I think Martin Dengler's proposal to
land the user in the Journal after quitting with focus on Object
Title would be a good solution.</p>
You are receiving this because you were mentioned.<br>
Reply to this email directly, <a moz-do-not-send="true"
it on GitHub</a>, or <a moz-do-not-send="true"
the thread</a>.<img moz-do-not-send="true" alt=""
<div itemscope="" itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope=""
<meta itemprop="name" content="View Pull Request">
<meta itemprop="description" content="View this Pull Request on