You are browsing as a guest. Sign up (or log in) to start making projects!

Jinsu

@Jinsu

Joined June 1st, 2026

  • 4Devlogs
  • 5Projects
  • 0Ships
  • 0Votes
I do somewhat cool stuff
Open comments for this post

1h 33m 1s logged

Today I started building the first real feature for SmoothActions: Copy All Code Blocks.
The goal was simple — click a button in the extension popup and instantly grab every code example from any webpage. ( ̄y▽ ̄)╭ Ohohoho…..

What I built
I wired up the popup UI and wrote the first version of the script that searches the page for and elements. The popup could run scripts on the active tab, and the alert showed up correctly.

The problem
When I tested it on MDN, it didn’t copy the code examples.
Instead, it copied random labels like:

Code
for
condition
continue
break
At first I thought the selector was wrong, but the real issue was that MDN doesn’t use normal or tags for its examples. Some code is inside custom containers, some inside shadow DOM, and some duplicated in the sidebar.

The fix
I rewrote the feature to:

scan normal and blocks

scan MDN‑specific classes like .notranslate and .language-js

scan inside shadow DOM elements

return all code blocks as one combined string

Once I injected the script properly using chrome.scripting.executeScript with a separate file, everything worked. The extension now successfully copies all code examples from the MDN Loops & Iteration page. o(  ̄ ▽ ̄)ブ pluh…

Today I started building the first real feature for SmoothActions: Copy All Code Blocks.
The goal was simple — click a button in the extension popup and instantly grab every code example from any webpage. ( ̄y▽ ̄)╭ Ohohoho…..

What I built
I wired up the popup UI and wrote the first version of the script that searches the page for and elements. The popup could run scripts on the active tab, and the alert showed up correctly.

The problem
When I tested it on MDN, it didn’t copy the code examples.
Instead, it copied random labels like:

Code
for
condition
continue
break
At first I thought the selector was wrong, but the real issue was that MDN doesn’t use normal or tags for its examples. Some code is inside custom containers, some inside shadow DOM, and some duplicated in the sidebar.

The fix
I rewrote the feature to:

scan normal and blocks

scan MDN‑specific classes like .notranslate and .language-js

scan inside shadow DOM elements

return all code blocks as one combined string

Once I injected the script properly using chrome.scripting.executeScript with a separate file, everything worked. The extension now successfully copies all code examples from the MDN Loops & Iteration page. o(  ̄ ▽ ̄)ブ pluh…

Replying to @Jinsu

0
4
Open comments for this post

1h 7m 30s logged

Ok ive ditched the idea of making this a game buut here is the complete info of the project so far. this Interactive 3D map of the lunar south polar region for Artemis III planning, built with Three.js.Features
Terrain (LOLA / GRAIL) — 256×256 polar stereographic grid (~560 km across) synthesized from LOLA DEM crater profiles and GRAIL Bouguer anomaly patterns
Ice & PSRs — Permanently shadowed region proxy from depth and crater geometry (Diviner / LOLA PSR catalog behavior)
Lighting — Adjustable sun azimuth; illumination from lunar obliquity (~1.5°) and local slope
Landing zones — Nine NASA Artemis III candidate regions (Oct 2024) with labels and footprint rings This demo embeds synthesized elevation (not full-resolution LOLA tiles) so it runs offline
Sources:
NASA Artemis III landing region update (Oct 2024)
LRO LOLA, Diviner, LROC
GRAIL gravity models
GIS-MCDM landing site study (Nobile Rim 2 / DM2)

Ok ive ditched the idea of making this a game buut here is the complete info of the project so far. this Interactive 3D map of the lunar south polar region for Artemis III planning, built with Three.js.Features
Terrain (LOLA / GRAIL) — 256×256 polar stereographic grid (~560 km across) synthesized from LOLA DEM crater profiles and GRAIL Bouguer anomaly patterns
Ice & PSRs — Permanently shadowed region proxy from depth and crater geometry (Diviner / LOLA PSR catalog behavior)
Lighting — Adjustable sun azimuth; illumination from lunar obliquity (~1.5°) and local slope
Landing zones — Nine NASA Artemis III candidate regions (Oct 2024) with labels and footprint rings This demo embeds synthesized elevation (not full-resolution LOLA tiles) so it runs offline
Sources:
NASA Artemis III landing region update (Oct 2024)
LRO LOLA, Diviner, LROC
GRAIL gravity models
GIS-MCDM landing site study (Nobile Rim 2 / DM2)

Replying to @Jinsu

0
2
Open comments for this post

1h 11m 50s logged

Turning this into a game?

I’ve been making a few models and animations in Blender and Scratch to turn this into a cool game. Like maybe an exploration game with LORE!!! So here is the character I’ve been designing. Also, I decided to call the game Orbitrack.

Turning this into a game?

I’ve been making a few models and animations in Blender and Scratch to turn this into a cool game. Like maybe an exploration game with LORE!!! So here is the character I’ve been designing. Also, I decided to call the game Orbitrack.

Replying to @Jinsu

0
3

Followers

Loading…