pascalstockert / yolol Goto Github PK

Currently in dark-mode the background-color of the library remains light.

Maybe think about lightening the background-color in light-mode (lower the brightness-differences between layers)

When chipwait is <0, the chip will no longer interpret any lines, which means the user cannot change chipwait.

• Need editable output fields

Strip the text to it's bare minimum and assure proper line breakage.

Regular form-input with ng-material's snackbar to display errors or successes

Landing page:
"A pre-requisite page, what people should know going into it and what they hope to learn from the program."

• Battle_wrath

Chapter 2
"Chapter 2 is a bit of a break down of how YOLOL is in the game, how they might come across it (Yolol chips, displays, how the yolol chip functions and how it relates to the web-page built editor.)"

• Battle_wrath

Update the design using Figma rather than XD

-[ ] Separate section for globals
-[ ] Separate section for local vars
-[ ] Max entries for both = 5 => Scroll: auto;
-[ ] Make values scrollable on overflow

The default css for ng-material unfortunately adds basic styling to text-elements and the like, leading to weirdly positioned text.

GraphCMS has an easier query-structure while providing the possibility of up to 5 users per project for the same price as Prismic - 0€.

Following this would be optimizing requests for tutorial-pages as there's a hard-cap at 1 mil.
Solution: LocalStorage

• Set up GraphCMS project
• Integrate GraphCMS API with repo
• Rewrite cms.service.ts and adapt routing accordingly
• Save already visited routes in LocalStorage/ Search for already saved versions on route change

Description

Headers are behaving like fixed elements when scrolling - only changing position when a scroll is concluded.

Possible fixes

Two possible ways of adjusting behavior:

1. Make headers normal scrolling DOM elements
2. Make headers fixed to the top of the screen

Include a dropdown in the settings for selection of the syntax highlighting - including VScode-yolol and YOLIDE

Headlines should have more pacing on top to increase readability of the texts.

Doing a string pre decrementation should remove the first character not the last one.
Expected behaviour:

input = "Hello World!"
--input -- input should be equal to "ello World!"

Nav-buttons & on-site links

VSC-Yolol might be nice but isn't as "hands-on" as Yoloxide. Not everyone has access to the closed pre-alpha as well, making the ingame-YOLOL a not so accessible alternative.

For ingame-YOLOL take screenshots of chips in ship-editor

For VSC-YOLOL take a glimpse at: https://marketplace.visualstudio.com/items?itemName=dbaumgarten.vscode-yolol

Sometimes darkmode is not regained when reloading the page. This bug was introduced together with the automatic setting of darkmode through the system's perferred color-setting.

Possible fix:
Remove check for preferred colors

Currently errors thrown from Yazur are causing the editor to be stuck upon interpreting.

Expected behavior:
Skip each line containing errors upon interpreting.

On Chapter 5 the "Next chapter" button is missing.

Presumably on Yazur's side of things

Keep track of issues in the issues section & automatically post progress updates :D

This will be fixed by adapting the new style dictated by Figma-Mockup

As the current state of this repository cannot be compiled with latest Angular, re-setup the project with recent Angular-Dependencies and other 3rd-party libs. While copying components make sure to check for optimizations, bugs and the like.

• Setup vanilla Angular
• Install updated dependencies and libraries
• Copy components, services and pipes

After this is done, other issues can be adressed.

"One little thingy I notice; it'd be nice to have an idea of what each chapter is about from the "chapters" dropdown"

• Senkii

Tooltips from Angular Material are not working as intended - looking for a fix. It's not too big of a deal so removing them might be a valid solution.

Currently the cookie-notice's background-color remains light.

Example:

Description

The elements if the footer don't behave nicely when displayed on mobile.

Characters not included in the language spec break the code snippets
After typing \n:

Steps to recreate:

• Type "adsfasdf" in line 1
• press return to get to line 2
• type "adsfasdf" in line 2
• click after the end of line one
• press return

may work with text other than "adsfasdf" however, this is untested :)

Expected:
new empty line at line 2 & old line 2 moved to line 3

Things like != and == might get confusing for people who have never dealt with code before.

• Add button to toggle ligatures for snippets
• Save selection of ligatures to IndexedDB