prev Kozaneba Development Diary 2021-08-26
I think it would be easier to introduce an arrow layer in the forefront. Braces are good for object layers.
- Better not to split into separate objects.
- Custom Styles.
Relationships between multiple boxes
- It can be easily drawn once the location of the box is determined. What if you can draw an arrow against an arrow?
- Circular references can occur.
Groups are also ārelationships among multiple boxesā in
- The bounding box of the child element is calculated first to determine its own position.
I was thinking about the arrows, but itās not too difficult if you completely make the arrows a layer to be written afterwards. in that case
-
You canāt put a kozane on top of an arrow because the arrow is always the frontmost surface.
-
Arrows cannot be drawn against arrows because arrows are a different kind of object from āboxesā such as kozane and groups become
-
Perhaps Iām unconsciously choosing the left way because Iām using the Kozane method from the state of paper stickies with no āgrouping functionā etc.
-
On the other hand, as a new feature, āNow you can group stickies in a way that paper stickies couldnāt!ā will appeal to people who started using it after seeing it, so they will unconsciously choose the right way to do it.
-
You can āmake it bigger,ā which was not available on paper stickies!
-
You can use a large space inexhaustibly and arrange them in a way that was difficult with paper stickies!
- Hmmm, this looks like it could be put back together.
- But if you give the link to someone else, and then put it back into a mode where people who know the link can edit it, of course they can.
- Is that okay with you?
Google Spreadsheet
- The link for view is the same as the link for edit.
- The screen I opened at the time of the view is still in readonly, but when I reopen it, I can write on it.
Hmmm, so itās the same shape I was trying to create, is that right?
- I thought it would be better to have separate view and write links and be able to turn them on and off separately, but I guess it works fine in most cases without such a feature.
Cases where the current design causes problems
- After publishing a link to a view, there is no way to add a writer if you want to.
- Reverting back to EDIT could result in unexpected people being promoted to WRITER.
- This is because the specification says that āthe person who edits is promoted to writer and has write permission even after being returned to view.
- In the first place, it is unlikely that you will need to add a WRITER since it is basically intended for personal use.
- Iād like to have āreceive the UID and add itā or āissue a separate invite link to add it to writer while in view modeā.
- Just the latter.
- Reverting back to EDIT could result in unexpected people being promoted to WRITER.
Lead-only sharing is now available! You can share Kozaneba Kanban directly instead of images!
-
There is still no function to show the image when it is posted to Twitter or other sites.
-
-
With create and delete copies, if you accidentally share something you shouldnāt show, you can just copy it and delete the original one. Oh, you didnāt create an error process for when something you tried to open is not there.
-
Oh, and I havenāt finished supporting touch events yet, so anyone who opens the link on a smartphone canāt do anything.
- In the future, I would like to see a flow of āadd handwritten kozaneā, āhandwrite in the opened dialogā, and ābecome Gyazo kozaneā.
To the front of the group when opened Even when 4 cards are added, the small group margin makes it difficult to select them. GyazoGIF Kozane
There is no flow line for people who have received the lead-only share to go to the home page to view the tutorial.
- If you click on the name of the service, you will be taken to the top page or So when I open a read-only share on my other device, I canāt edit it because Iām not logged in, but I canāt log in because itās not editable and I donāt get the cloud save menu either.
I use the split menu a lot, but I almost always Replace.
- If it is possible to clone a clicked Kozane, there is no need to use āAddā and āReplaceā.
- split, add = clone, edit
- split, replace = edit
Huh? I see, the reason I had trouble using images from Gyazo in Regroup was because it was in Canvas, and if I simply paste it as an img, thereās no problem?
- If you want to make Scrapbox Kozane, you need Gyazo loading function after all
- The DOM is different in this area, and I think itās making the problem too difficult to do with user extensions.
ts
export const id_to_dom = (id: string, offset: TOffset) => {
const item = get_item(getGlobal(), id);
if (item.type === "kozane") {
return <Kozane value={item} offset={offset} key={id} data-testid={id} />;
} else if (item.type === "group") {
return <Group value={item} offset={offset} key={id} data-testid={id} />;
}
return null;
};Itās like adding Gyazo and Scrapbox here.
- Rather than making it look like a complete system, it would be better to keep it to a minimum that serves the intended function, and if users want to tweak the look, they can do so with extensions.
- In general, when you go with a perfect match to the original, itās not even a āfamiliar lookā for people who are tweaking with UserCSS.
- I guess Iāll just have to go with the minimum implementation that will serve the functionā¦
- Maybe itās just about 2 or 3 times the size of this oneā¦
- (of) good appearance
It looks done, butā¦
-
Cannot drag and drop
-
Cannot select a range
-
Bounding box calculation is not yet implemented, so space key kills it.
This page is auto-translated from /nishio/Kozanebaéēŗę„čØ2021-08-27 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.