Kozaneba Development Diary 2022-05-26
- Kozaneba Development Diary 2021-12-10
- Kozaneba Development Diary 2022-03-18
- Kozaneba Development Diary 2022-03-24
from [/villagepump/workroom 2022/05/26](https://scrapbox.io/villagepump/workroom 2022/05/26).
13:00
13:25 Pomodoro beginsπ .
A: Isn't it possible to import Kozaneba's UserScript like Scrapbox? That too from Scrapbox. I'll give it a try.
It is not enough to just write import in UserScript.
import "https://scrapbox.io/api/code/nishio/Kozaneba%E3%81%AEUserScript/script.js";Cannot use import statement outside a module- Hmmm... I'm currently realizing UserScript by reading from LocalStorage and eval'ing, but that doesn't mean I can't import.
- Oops, if you put in UserScript that causes serious errors, it dies on startup so you can't reach the edit screen (terrible).
- I deleted it in the developer tools, but that's not good.
dynamic import is not allowed due to CORS restrictions
Even if you replace the header on the server only for URLs you import directly, if you import code from another page from the code placed in Scrapbox, it will die there, so you won't be very happy anyway.
If you want to do it, you need a mechanism to collect all the files with dependencies in the form of a scrapbox-bundler or something like that.
- ServiceWorkerγ§θ§£ζ±Ίγ§γγγ
- ServiceWorker: A service that can intercept all HTTP requests, including
fetchand<img>, and do whatever it wants. - Now, if you replace
https://scrapbox.io/api/code/to fetch on the server, you can play around with all theimportsor whatever. - Real world example: Swdev: true no bundle frontend
- Import is intercepted and bundled locally and returned.
- ServiceWorker: A service that can intercept all HTTP requests, including
- I see.
- hijack
- ServiceWorkerγ§θ§£ζ±Ίγ§γγγ
When you save the UserScript, it says Saved on the console, but it should be on the screen.
Breakdown on improving appearance with 4 minutes remaining
- The button enclosure line is gone.
- Help is available from the hatena icon on the status bar in the lower left corner, but ordinary users do not notice it, so a help button is placed in the upper right corner.
- Only the arrow heads are 100% opaque.
- Needs a major refactor, no real harm in use, so we left it alone, but it looks bad, so we'll improve it.
- Arrowheads for nested groups may be misaligned.
- Reproduction conditions are not clear
13:58 π
Help is available from the hatena icon on the status bar in the lower left corner, but ordinary users don't notice it, so a help button is placed in the upper right corner.
- 10min I added a help button.
The button enclosure line is gone.
- 21min
- CSS Specificity issue, DevMenu is an ID, but buttons added by user scripts are classes, so they did not have enough priority
- Two minutes left, commit, close tab and prepare for next
- I pushed it.
- Notes of Concern :
WARNING in ./node_modules/@progfay/scrapbox-parser/esm/parse.js
Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from '/Users/nishio/kozaneba/node_modules/@progfay/scrapbox-parser/src/parse.ts' file: Error: ENOENT: no such file or directory, open '/Users/nishio/kozaneba/node_modules/@progfay/scrapbox-parser/src/parse.ts'
14:00
- 14:32 π
Only the arrow heads are 100% opaque.
- before
- I see, to begin with, the current code has two steps: "draw a line" and "add an arrow head if necessary".
- It's bracketed out because the drawing of the arrow heads is common regardless of the type of line, but it's wrong that they're separated on the time axis.
- Initially, it was loosely coupled, which was fine, but it was ruined when the specification to match transparency was added.
- It should have been separated lexically and integrated with drawing a line on the time axis with a function call.
- 8 minutes remaining
- One step further β
15:00
break
- The head of the translucent arrow overlaps and darkens because of the overlapping translucent lines.
- To solve this problem, it is necessary to change the current structure that treats the object as a unit of "line" and create a layer that treats it as a unit of "object composed of several lines".
- I wonder if we can do it in one pomodoro, we should commit at the moment anyway.
15:07 π
- Fix bugs and commit
- I introduced the SVG g element.
- I think we can do this.
- Perfect!
- I'd like to tweak the relationship between distance and density a bit more.
- Let's commit so far for now β .
- Modified to make the change in intensity continuous β .
- fixed `Failed to parse source map` - `.env`: `GENERATE_SOURCEMAP=false` - [javascript - Failed to parse source map - Stack Overflow](https://stackoverflow.com/questions/70599784/failed-to-parse-source-map) - I've confirmed that the Netlify deployment is successful, I'll have to write release notes.
17:20 π
- /kozaneba-forum-jp/release-noteUpdated both in Japanese and English
- We sought ways to reproduce the problem for the next fix.
- Condition to reproduce the problem, nesting is not required, but it seems to write arrows for groups.
- I guess I better make a test case for Cypress first.
18:35 I'll continue development tomorrow.
- I saw "Anki" above and suddenly came up with the idea of turning oblique strategy into Anki.
- By declaring what I'm going to do today at the beginning of the page, I've prevented myself from getting sidetracked and starting to do Anki.
19:00
- 7:25 p.m. I feel sleepy after dinner.
22:00
- 23:00 I woke up.
- 23:18 π
This page is auto-translated from /nishio/KozanebaιηΊζ₯θ¨2022-05-26 using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I'm very happy to spread my thought to non-Japanese readers.