Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Date on fork to local entiries in the journal #134

Open
paul90 opened this issue Sep 11, 2015 · 0 comments
Open

Date on fork to local entiries in the journal #134

paul90 opened this issue Sep 11, 2015 · 0 comments

Comments

@paul90
Copy link
Member

paul90 commented Sep 11, 2015

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
screen shot 2015-09-11 at 18 07 37
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant