iteloo/storytown

An online teaching portal for language teachers and students written in Elm/Haskell

storytown's Issues

Doesn't support SEO

Story page still showing bogus translations

Translation splitting only works for Chinese characters

Currently splitting each character, even if they are Latin alphabets.

Split translations don't highlight together on hover

No way to show overflowing part of translations

Several options here:

• separate zoom box activated on click/hover
• scrolling text (haha!)
• shrink text

Left-align split translations

Warn when leaving edit page without saving

Invalid URL crashes app

Text can be clicked even when audio isn't loaded

css name clashes

Marked text shifts text to the right

incorrect width for top-level translation due to bootstrap interference

Password not hashed

incorrect width for top-level translation due to bootstrap interference

Add ellipses to split translations

Need to measure width using port

Translations span trailing spaces

Possible fixes:

1. move spaces out before rendering
2. move spaces out when parsing

(2) is cleaner, but may result in problems when measuring widths, due to space collapsing behaviours in css.

Translation splitting algorithms doesn't take into account the side paddings

We can import the padding lengths from MyCss.elm, but we'd need to convert between px and the "unitless" values. Is this conversion device independent?

Encrypt traffic to Heroku Postgres

Split lines with no words have no height

Add in a space?

Translation granularity not persisted

Currently I'm only storing the source text on server.

A few options to implement this:

1. store the entire Collapsable on a per user basis
2. store the sequence of zipper movements to recreate state

In (1), if the story is edited, the user will continue having the old version. We can provide the option to let them upgrade the story, at the cost of possibly resetting the granularity levels. At some point we can minimize this disturbance by using a tree diff.
In (2), we need to load the correct version from the server to apply the zipper movements. Otherwise the result will be undefined.

In either setup we will need some sort of versioning of the stories.

Break paragraphs into lines, not each sentence

Collapse "button" doesn't span the entire width of the parent

Saving of stories should be disallowed if no changes

translation tree animations doesn't work smoothly

Spacing between words are wrong

We want

• spaces optional and collapsed in source text
• spaces stripped in translation blocks
• spaces preserved in rendered original text

Login session not working

Did session tokens break again?

Expand and Collapse always updates first sentence

Long translations pushes original text apart, causing line overflow.

Because the line breaks are measured without the translations.

Navbar dropdown doesn't close when clicking outside the menu

Rerecording audio doesn't delete old file off s3

Currently, S3 files are created as soon as a sentence is recorded, so the deletion must also happen in the client as well.

Alternatively, we can only submit audio to S3 upon saving the story. In this case, we can also let the server take care of the deletion.

Translations merely duplicated to each broken line

Translation divs/spans need to be top-aligned

Create separate S3 bucket for production

`AnimationFrame` events received even after formatting is done

User redirected to login page even when visiting public pages

Right now an API call to get the logged-in user is enforced on app launch, and authentication error is handled the same way as any other API call – by redirecting to the login page.

We can treat this call as a special call bypassing the default error handler.

Add uniform network error handling on client

Add audio-text syncing for story page

Working before. Need to upgrade to TransView

Show session status on right of nav bar

• if logged in, show username
• if not logged in, show login and sign up buttons

Colour translation blocks to visually aid distinguishing blocks

We have two options:

1. Computed dynamically, at the time of expansion and collapsing. We will only need a total of 3 colours. Also, we are able to make colour distribution as uniform as possible.
2. Precompute colours for all the levels before rendering for the first time. This is less confusing for the user as the colours won't randomly change as they expand and collapse translations. However, this will probably require way more colours, but exactly how many?

Hovering doesn't highlight expand/collapse buttons on other lines

Line breaking doesn't break words in terminal blocks

Blob still gets sent to S3 even if microphone is broken

Zippers forget expanded blocks

Because the context doesn't store this information. We need it when using zippers to update nodes in the tree.

Remove tiny gaps between marked text during audio-text sync

Redirect http traffic to https

Requires checking for X-FORWARD-PROTO header on Heroku, since proxy communicates with dynos using http only.

Logging out doesn't clear session data

Clearing Http-Only cookies require a call to the server.
A cleaner solution is to store a loggedIn flag in the client, and keep the current cookie setup.

Collapse button pushes lines below away

Stories with empty sentences can be saved

Add empty source to parser error

Line breaking algorithm sometimes measures incorrect widths if span gets broken across lines

Line breaks aren't re-calculated when window resizes

Subscribe to window resize events and format again.