| <harts...@osafoundation.org> |
n class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Sun, 12 Apr, 21:12 |
| <harts...@osafoundation.org> |
n class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Sun, 12 Apr, 21:12 |
| <p...@prescod.net> |
2019;t necessarily tabbed out of the Notes field
- yet.)&lt;br/&gt;
</span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Tue, 14 Feb, 14:14 |
| Parlante |
t;/span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Sat, 09 Apr, 03:30 |
| Parlante |
t;/span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Sat, 09 Apr, 03:30 |
| b...@code-bear.com |
lt;/span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Sat, 13 Sep, 09:29 |
| b...@code-bear.com |
lt;/span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Sat, 13 Sep, 09:29 |
| b...@code-bear.com |
lt;/span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Sat, 13 Sep, 09:29 |
| b...@code-bear.com |
lt;/span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Sat, 13 Sep, 09:29 |
| ch...@osafoundation.org> |
span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Sun, 11 Oct, 21:18 |
| fairwi...@eastlink.ca |
;/span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Sat, 14 Jun, 16:51 |
| h...@osafoundation.org> |
p;lt;/b&gt; and just sent the Reply to me, not to Amy. &lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;I receive the email Reply from Carol in both my Chandler and
</span><span class="rem">-my email client.&lt;br/&gt;
</span><span class="add">+my email client.&lt;br&gt;
</span><span class="cx"> &lt;ul&gt;
&lt;li&gt;In Chandler, the Reply appears as a new Item in the All and
</span><span class="rem">-Mail app areas.&lt;br/&gt;
</span><span class="add">+Mail app areas.&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
&lt;li&gt;The &lt;b&gt;Communication&lt;/b&gt; stamp shows that the Reply is an
inbound unread email.&lt;/li&gt;
</span><span class="lines">@@ -401,156 +403,156 @@
</span><span class="cx"> &lt;li&gt;Carol replies again with oops, another suggestion. This second
Reply appears
in the All and Mail app areas as another new Item, just like the first
</span><span class="rem">-Reply.&lt;br/&gt;
</span><span class="add">+Reply.&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
&lt;li&gt;I return to the original invitation Item, either in a summary
table view or on the Calendar.
</span><span class="rem">-The Communication stamp still displays the Invitation&amp;#x2019;s &amp;#x2018;Sent
-status&amp;#x2019; in the mark-up bar.&lt;/li&gt;
- &lt;li&gt;I edit the Item to add in Carol&amp;#x2019;s suggestions.
</span><span class="add">+The Communication stamp still displays the Invitation&amp;#8217;s &amp;#8216;Sent
+status&amp;#8217; in the mark-up bar.&lt;/li&gt;
+ &lt;li&gt;I edit the Item to add in Carol&amp;#8217;s suggestions.
</span><span class="cx"> &lt;ul&gt;
&lt;li&gt;As soon as I make any changes, the &lt;b&gt;Send&lt;/b&gt; button
</span><span class="rem">- re-activates from its formerly disabled state and changes
- to &lt;b&gt;Update&lt;/b&gt;. I can hit &lt;b&gt;Update&lt;/b&gt;
- to send out the item again with the information. (Ideally, the
- &lt;b&gt;Update&lt;/b&gt; button activates as soon as the user makes an edit by
- typing in new text or deleting old text. However, we&amp;#x2019;re aware
- there are limitations wrt when changes to the Detail View are
- committed. What we&amp;#x2019;d like to avoid is the situation where users
- have edited the Notes field and are looking to send out the
- Update, but haven&amp;#x2019;t necessarily tabbed out of the Notes field
- yet.)&lt;br/&gt;
</span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Fri, 10 Mar, 08:39 |
| isse |
wrt when changes to the Detail View are
- committed. What we&amp;#x2019;d like to avoid is the situation where users
- have edited the Notes field and are looking to send out the
- Update, but haven&amp;#x2019;t necessarily tabbed out of the Notes field
- yet.)&lt;br/&gt;
</span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Sun, 13 Nov, 20:15 |
| itch...@osafoundation.org> |
&gt;
- to send out the item again with the information. (Ideally, the
- &lt;b&gt;Update&lt;/b&gt; button activates as soon as the user makes an edit by
- typing in new text or deleting old text. However, we&amp;#x2019;re aware
- there are limitations wrt when changes to the Detail View are
- committed. What we&amp;#x2019;d like to avoid is the situation where users
- have edited the Notes field and are looking to send out the
- Update, but haven&amp;#x2019;t necessarily tabbed out of the Notes field
- yet.)&lt;br/&gt;
</span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Sun, 17 Jun, 07:05 |
| itch...@osafoundation.org> |
&gt;
- to send out the item again with the information. (Ideally, the
- &lt;b&gt;Update&lt;/b&gt; button activates as soon as the user makes an edit by
- typing in new text or deleting old text. However, we&amp;#x2019;re aware
- there are limitations wrt when changes to the Detail View are
- committed. What we&amp;#x2019;d like to avoid is the situation where users
- have edited the Notes field and are looking to send out the
- Update, but haven&amp;#x2019;t necessarily tabbed out of the Notes field
- yet.)&lt;br/&gt;
</span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Wed, 25 May, 07:48 |
| ja...@wordzoo.com |
br/&gt;
</span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Thu, 24 Apr, 14:24 |
| ja...@wordzoo.com |
br/&gt;
</span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Thu, 24 Apr, 14:24 |
| ja...@wordzoo.com |
br/&gt;
</span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Thu, 24 Apr, 14:24 |
| ja...@wordzoo.com |
br/&gt;
</span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Thu, 24 Apr, 14:24 |
| ja...@wordzoo.com |
br/&gt;
</span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Thu, 24 Apr, 14:24 |
| ja...@wordzoo.com |
br/&gt;
</span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Item.Nil
+ return Nil
if copyFn is None:
copyFn = copyOther
@@ -1446,7 +1491,7 @@
for name in self._references.keys():
policy = (deletePolicy or
self.getAttributeAspect(name, 'deletePolicy',
- default='remove'))
+ False, None, 'remove'))
if policy == 'cascade':
value = self._references._getRef(name)
if value is not None:
@@ -1455,7 +1500,7 @@
else:
sName = property(fget = __getName,
fset = rename,
doc =
|
Thu, 24 Apr, 14:24 |
| m.@osafoundation.org> |
the Calendar.
</span><span class="rem">-The Communication stamp still displays the Invitation&amp;#x2019;s &amp;#x2018;Sent
-status&amp;#x2019; in the mark-up bar.&lt;/li&gt;
- &lt;li&gt;I edit the Item to add in Carol&amp;#x2019;s suggestions.
</span><span class="add">+The Communication stamp still displays the Invitation&amp;#8217;s &amp;#8216;Sent
+status&amp;#8217; in the mark-up bar.&lt;/li&gt;
+ &lt;li&gt;I edit the Item to add in Carol&amp;#8217;s suggestions.
</span><span class="cx"> &lt;ul&gt;
&lt;li&gt;As soon as I make any changes, the &lt;b&gt;Send&lt;/b&gt; button
</span><span class="rem">- re-activates from its formerly disabled state and changes
- to &lt;b&gt;Update&lt;/b&gt;. I can hit &lt;b&gt;Update&lt;/b&gt;
- to send out the item again with the information. (Ideally, the
- &lt;b&gt;Update&lt;/b&gt; button activates as soon as the user makes an edit by
- typing in new text or deleting old text. However, we&amp;#x2019;re aware
- there are limitations wrt when changes to the Detail View are
- committed. What we&amp;#x2019;d like to avoid is the situation where users
- have edited the Notes field and are looking to send out the
- Update, but haven&amp;#x2019;t necessarily tabbed out of the Notes field
- yet.)&lt;br/&gt;
</span><span class="add">+re-activates from its formerly disabled state and changes to &lt;b&gt;Update&lt;/b&gt;.
+I can hit &lt;b&gt;Update&lt;/b&gt; to send out the item again with the
+information. (Ideally, the &lt;b&gt;Update&lt;/b&gt; button activates as soon as
+the user makes an edit by typing in new text or deleting old text.
+However, we&amp;#8217;re aware there are limitations wrt when changes to the
+Detail View are committed. What we&amp;#8217;d like to avoid is the situation
+where users have edited the Notes field and are looking to send out the
+Update, but haven&amp;#8217;t necessarily tabbed out of the Notes field yet.)&lt;br&gt;
</span><span class="cx"> &lt;/li&gt;
</span><span class="rem">- &lt;li&gt;Once I make an edit, the Detail View displays &amp;#x201c;updated by me&amp;#x201d;
- under the From: and To: fields (see storyboards).&lt;/li&gt;
</span><span class="add">+ &lt;li&gt;Once I make an edit, the Detail Vo ma. Unstamping items is the
</span><span class="rem">-equivalent of &#x2018;Removing the item&#x2019; from the Task list or Calendar, which
</span><span class="add">+equivalent of &#8216;Removing the item&#8217; from the Task list or Calendar, which
</span><span class="cx"> in turn removes any Task or Calendar specific attributes from the item.
</span><span class="rem">-Unstamping does not imply splitting the item into separate Items. <br/>
</span><span class="add">+Unstamping does not imply splitting the item into separate Items. <br>
</span><span class="cx"> </p>
<p>The workflow is as follows: I receive an email. I put it on the
calendar and
added it to a task list. If I unstamp this Item as a communication, we
will
</span><span class="rem">-make no attempt to preserve the &#x2018;communication-ness&#x2019; of the Item as a
-separate Item. Instead, we assume that the user just doesn&#x2019;t need to
</span><span class="add">+make no attempt to preserve the &#8216;communication-ness&#8217; of the Item as a
+separate 'user' Item. Instead, we assume that the user just doesn&#8217;t
+need to
</span><span class="cx"> keep the
</span><span class="rem">-communication information anymore. Unstamping the &#x2018;communication-ness&#x2019;
</span><span class="add">+communication information anymore. Unstamping the &#8216;communication-ness&#8217;
</span><span class="cx"> of an item is the equivalent of what people do when they copy and paste
event information from an email to an event on their calendar and then
</span><span class="rem">-delete the email. Similarly, we can think of unstamping &#x2018;task-ness&#x2019; or
-&#x2018;calendar-ness&#x2019; as
-taking the event off the task list and the calendar.
</span><span class="add">+delete the email. Similarly, we can think of unstamping &#8216;task-ness&#8217; or
+&#8216;calendar-ness&#8217; as
+taking the event off the task list and the calendar.<br>
</span><span class="cx"> </p>
</span><span class="add">+<p>If I am in a Kind-specific App area (e.g. Mail, Tasks, Calendar) and
+I unstamp an Item, such that it no longer belongs in that App area, the
+Item should be removed immediately removed from the summary pane, just
+as if I had selected the Item and then removed it with the
+Edit&gt;&gt;Remove menu item. For example, if I am in the Calendar view
+and I am looking at an Event stamped as a Communication, when I
+unstamp the Item thereby 'Removing it from the Calendar', the event
+fields disappear from the detail
+view (e.g. location, all-day checkbox, date/time, timezone, event
+status, recurref view._logItem(self):
self._status |= dirty
@@ -1363,7 +1408,7 @@
None, copyOther)
return otherCopy
else:
- return Ite |