risonakamo / anigen4 Goto Github PK

even when it says something like "winter 2020" sometimes it is confusing what date range that actually is, since the seasons themselves are not any official range

pass result of the chart input box component up and use it to do things.

load the text input results, navigate to the chart page, render the chart page based on the inputs

so the current chart can be switched quickly. but, saved inputs should be a convenience thing, not something to depend on. if the intention is to quickly compare certain seasons, then that's what the image output is for, or making multiple tabs?

have the chart input box's getvalue return the actual result using the text input, instead of the example input.

basically, finalising getvalue function

anilist link placeholder should example links

or "generate" "generate chart"

• maybe use router? it pretty much needs to be a whole new page
• where will image output be?

• have name of chart as a separate input

• provide a choosable number of columns, change width based on that value

get google fonts onto page

• button also needs to perform parsing of chart input
  • needs to be able to execute this function before performing the navigation
• needs to be able to send data to the chart page element

• maybe also include name and id

• test if it works without internet
  • mhtml works without internet, images work as well
• test if buttons are on the page, if this breaks it
  • ideally, what should the buttons do if they were to appear on the page?
    • probably should just do nothing
  • probably won't have any buttons on the page at all
• title of the page (both when saving and in the tab bar when the html is opened) should be correct
  • filename
  • tab name
  • see what happens when the filename is changed from the tab name, does it change the tab name? basically, is the tab name actually the title element or is the name of the file?
  • looks like the title is preserved. so we want to make sure to set the title correctly, should be the title set by the user

try having description of what the field should be above it? could also try placeholder, at least for title

to go back to input page

maybe give it min height?

and containers for shows falling under the show header

• multiline scrolling input for shows
• larger input line for title

• maybe yaml or json, with fields to specify name and other future options
• maybe drag in to load?

• one item per line, invalid lines are excluded

comma, or maybe dot, or small vertical line?