5 pointsby milst7 months ago2 comments
  • mdp20217 months ago
    Suggestions:

    -- Improve the timeline marks for readability (use one row with a rounded scale - ...700, 800, 900, 1000, 1100... - and another row for the shown events - ...711, 960, 1112...; ditch the comma and the "CE/BCE". Or, create visualization options).

    -- Also improve text readability - event titles should not overlap.

    -- Avoid page layout jerks when clicking on items (depending e.g. on amount of rows in the "event description" box.

    -- Add granularity of details ("most important events" vs "important events" vs "interesting events"...).

    -- Add a mode in which all the "description" texts are listed in a table (instead of being constrained in a box, one at a time).

    ...

    Very good job.

    • mdp20217 months ago
      Update:

      -- the «Let's explore the fascinating history [etc.], from its early beginnings to the next era. I'll create a timeline to illustrate the key events». Is fully redundant

      • milst7 months ago
        True, and it says that almost every time... I'll do some prompting to stop that
      • milst7 months ago
        updated the 'overview' generation
    • milst7 months ago
      thanks! Any ideas on how to get around overlapping titles? Was thinking maybe truncate with ellipses like "Some long titl..." but often there are too many events too close together for that to make a difference
      • JamesHist7 months ago
        I feel your pain on the overlapping titles. When creating a timeline application, there's usually only a short time between 'let's connect to Wikidata' and needing to deal with live label clustering and deconfliction.
      • mdp20217 months ago
        A first idea could be, if you are using "nowrap", to have two event title rows. So it could be, top to bottom: event_year, event_rowabove, event_rowbelow, event_bullet, rounded_years.
  • optinghost7 months ago
    interesting