karl255 / tvz-bart Goto Github PK

For future reference:

All necessary info in one place: https://stackoverflow.com/questions/63425920/svelte-with-prettier-eslint

Also don't forget to restart eslint server in VSCode. Some VSCode settings might need to be adjusted too.

• ability to hide items in the timetable - identified not by id but by day of week, subject etc. (repeatable hide)
• setting to show hidden items - how else would the user unhide items?

• font

https://kit.svelte.dev/docs/load

Idea: use a store for the auto-save boolean and use that store in persistence stores too and when auto save is enabled again, flush unsaved changes.

• new content appearing (fetching new data for example) -> flash background slightly
• selected and previewed item effects

Device theme by default with overrides for both light and dark.

settings:

• preferred default department and semester
• overrides*
• exportable?

*added in the future

• API data parsing/tranforming that makes more sense

Use the https://homer.tvz.hr/CalendarJson/Semesters and https://homer.tvz.hr/CalendarJson/Departments endpoints.

• 1 event is replaced with 0 to N events

  • each new event can be additionally toggled
  • store in localStorage

• mark override events with an icon so the user is instantly aware that they're user-added

Move department and semester pickers to unused panel aside the timetable panel. Department picker should be a dropdown, semester picker should mostly stay the same.

• better follow the principle that one module should do only one thing

Currently they aren't refreshed when the current academic year changes.

• short info for new users - nothing advanced!
• use a slot in the CalendarItemInfo component for content shown when nothing is selected/previewed

Sometimes calendar items are positioned incorrectly in the calendar - only vertically.

• automatic - uses predefined hardcoded colors (about 8 should be enough)
• texturing for class type (regular, striped, dotted) (triage needed)

Schedule info sources:

• per department/semester (/CalendarJson)
• per subject (/CalendarJson/Predmet)
• per user (/CalendarJson/MojRaspored)

Allow custom schedule definitions. Eg. have a multiline text input that accepts a format like

calendar:PRIN-4
predmet:[id]
user:username:hash

Pros:

• very easy to parse

Cons:

• hard to implement different calendar source

of course this won't be the last one

• use Svelte's bindings and reactivity instead of function callbacks
• and more

• fetch entire semester at once and don't re-fetch
• only really necessary if many people use this - to not exceed Netlify's free tier serverless function limits

Abstract the whole page into a ScheduleViewer component. The component will handle timetable viewing, settings, week cycling... It will not handle schedule picking, that will rather come from the outside - through a prop. That prop might need to be a function (reactive closure) that takes params like weekStart.

• current academic year

• unsure (decide) - move selection of semester and department in there

• put in place of one of the ClassPeriodInfo displays

• instead of displaying the info somewhere, give the selected department/semester option a special style

Instead of using a single settings object and keep everything in there, have a generic "persistent store".

On hover and for selected item (hover overrides selected, default is none, can be deselected).