You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The date put on either the fork to local event, or the event that causes it is wrong.
The following is an extract from the journal for Easy to Use
{
"type": "fork",
"site": "journal.hapgood.net",
"date": 1422837764365
},
{
"type": "edit",
"id": "12a33a7a00e14e8d",
"item": {
"type": "paragraph",
"id": "12a33a7a00e14e8d",
"text": "User-friendliness is generally described as being \"easy to use\"\" but in point of fact what most people mean by this is that it is easy to learn. These are not identical concepts, and it has been argued (by [[Alan Kay]], Doug Englebart, and others) that our desire for systems that are easy to learn sometimes results in systems that are hard to use. "
},
"site": "journal.hapgood.net",
"date": 1422837764359
},
{
"type": "fork",
"date": 1422837817266
},
which renders in the narrative chart as
the date for the fork event being after the edit event that triggered the save to local.
While the need to the fork to local is not until after the save to server has failed, it is placed before the edit in the journal - and so needs to be given a date just before the edit.
The text was updated successfully, but these errors were encountered:
The date put on either the fork to local event, or the event that causes it is wrong.
The following is an extract from the journal for Easy to Use
which renders in the narrative chart as
the date for the fork event being after the edit event that triggered the save to local.
While the need to the fork to local is not until after the save to server has failed, it is placed before the edit in the journal - and so needs to be given a date just before the edit.
The text was updated successfully, but these errors were encountered: