prev Kozaneba Development Diary 2021-08-13
It was an image of extensibility by users, adding menus and processing with JS, but suddenly there was a bad idea of âturning and gaming backgroundâ.
I tried hard-coding it anyway.
- I found out that we need a mechanism to allow users to specify @keyframe, itâs annoying.
- reactjs - React how to specify animation @keyframes and classes locally - Stack Overflow
If the user changes the style
- Change the default style
- Change the style of a particular kozane or group There are two possible ways to If the objectâs style attribute is undefined, use the default one, or if it is a string, look for it in the style list by its name? I want a guard to ensure that the object entered by the user has the proper structure.
- Specifically, React.CSSProperties
Itâs going to cause users to fail and make errors.
- The current design doesnât give a detailed error message, it just registers on Sentry, but thatâs not right.
- Error messages should be communicated to the user during trial and error, and that shouldnât go into Sentry.
- On the other hand, you canât distinguish when a user script creates an inconsistent condition that results in an error after the fact.
Future Flow User testing is at a slow pace as my capacity is overflowing. First, implement the functionality you need for your own use, and then cover it with proper automated tests before including it in the tutorial. After all that is done, we will make the tutorial multilingual and create a user forum. Long-term goal is scalability by users
Iâm a little slammed with deadlines, so next week Iâll sit back, clean up the code, cover it with tests, and add explanations to the tutorials. There is no tutorial on how to view saved pages. Not good because the added stickies are placed at the origin in world coordinates. Important: I still donât think itâs a good idea to go the route of using the drag-drop API (the look and feel is very environment-dependent). The test itself has been created by trial and error and patchwork, so itâs chaotic. I want to make a user page. Need a list of places used in the past Placement of future expansion, etc. Iâd like to make a âof course you can use Scrapbox cards as small bills because theyâre DOMâ video as a catchy teaser at the right time.
The reason there is no tutorial on how to view a saved place is because there is no UI for that in the first place.
Clean up the test
- Itâs in integrations/movidea now.
- Why not just put the cleaned ones in kozaneba?
The tutorial was not initially intended to have titles on each page
- But as I wrote it, the title converged on a certain form
Tutorial Improvements Title. Table of Contents Number of pages to complete
- Now all the pages are being served in the denominator.
- It would even include additional content. Table of Contents
- Instead of starting the tutorial from the head.
- help menu
- I want to jump from the table of contents to the target page.
Test Improvement Dirty because of trial and error.
- A new way to write beautifully.
- Old and muddled writing style. Iâll speak at a workshop the week after next. I want to keep it clean.
drag and drop
- Change to a form that does not use the browserâs DragDropAPI
user page
- List of places created in the past
Organize with Kozaneba
- https://youtu.be/n0MLqfjpwlA
- I realized that the definition of âfunctions I need for my useâ was unclear.
- What do I need for my use?
- Not a tutorial improvement.
- I would like to have the ability to list the places we have created.
- The phenomenon of the size increasing when dragging is moderately stressful.
- Because it doesnât move to the position you want it to move to.
- I keep the original sticky note at the time of the split, but often want to replace it
- I think a replace button on the dialog would be nice.
Itâs more modest than the rotating gaming kozane, but it can now drag itself.
I thought that I must be confusing the world coordinate system with the screen coordinate system, and that if I separated vectors into âworld coordinate system vectorsâ and âscreen coordinate system vectorsâ and distinguished them by type, I should be able to find the bug of the mistake, so I added a type.
- It was a âbug in which a relative vector is converted to the world coordinate system by taking the difference between two absolute vectors in the screen coordinate system.
- In other words, we need four vector types: âworld absolute,â âworld relative,â âscreen absolute,â and âscreen relativeâ (wait
- And another value âCSS position (
{top, left})â (no!)
The groupâs stand-alone drag moved, well, easily.
- (This is because I wrote it so that it would work easily and not have the Kozane-specific offsets.)
However, the in/out decision for other objects while dragging doesnât work.
- mousemove does not cause mouseenter on div B at the back because div A is following at the very front.
- Asking on Twitter: when mousemove comes with div A, I want to detect that the mouse cursor is in div B below it, but I canât figure out how to do it.
-
Sheile: I havenât tried it, but if I add pointer-events: none; to div A at the timing of mousedown, I think I can get div Bâs I think I can get the mousemove event to fire.
-
However, it also prevents div Aâs mouseup event from being taken, so itâs tricky to handle when you let go of it. âŠ
- I see, you can ignore pointer events.
- The move and drag end of div A is taken by mousemove / mouseup of the innermost parent div, so itâs ok.
-
Context menu no longer appears. Selecting a range and moving appears to work okay, so Iâll do the test from here.
next Kozaneba Development Diary 2021-08-17
This page is auto-translated from /nishio/Kozanebaéçșæ„èš2021-08-16 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.