|
47734
|
thestarsirius by @zenia | Stardance
|
zenia
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: thestarsirius by @zenia | Stardance
|
1792526013.2324376
|
1793130813.2324376
|
|
1957
|
Untitled project by @zengblade | Stardance
|
zengblade
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @zengblade | Stardance
|
1792670040.944844
|
1793274840.944844
|
|
51499
|
My own site! by @zen7 | Stardance
|
zen7
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @zen7 | Stardance
|
1792673385.0214627
|
1793278185.0214627
|
|
5836
|
zWork Browser Control by @zemu | Stardance
|
zemu
|
1
|
42.25
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-23T14:43:46Z", "hours": 24.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made zWork Everything was challenging, mainly harness engineering. The browser feature was relatively straightforward. I’m proud of the extensiveness or comprehensiveness of this project, and the scale at which it worked. To fully test my app, you should probably install the app, as well as the extension. There is a limited web demo at app.tryzwork.app which doesnt really have any features. More info is available in the readmes.", "repo": "https://github.com/Ryz3nPlayZ/zbctl", "demo": "https://github.com/Ryz3nPlayZ/zWork/releases"}]...
|
[{"post_id": 77432, "ts": "202 [{"post_id": 77432, "ts": "2026-10-06T23:48:07Z", "hours": 15.72, "text": "any click that changed DOM used to take about 3s now it takes about 200ms. I also added back the extension GUI because sometimes its confusing without it. also to save tokens from agent context windows, content.js no longer creates a brand new fat snapshot of the entire page."}, {"post_id": 52033, "ts": "2026-08-22T02:13:23Z", "hours": 2.5278, "text": "updated readme because i needed to"}, {"post_id": 33339, "ts": "2026-07-23T05:02:08Z", "hours": 5.2228, "text": "I benchmarked zWork (desktop ai agent made by me) using zbctl (extension) to test its new browser use abilities. ive used the prompt in the picture below. the model answered all but one correct. the google form used to “benchmark” the model was: https://docs.google.com/forms/d/e/1FAIpQLSfHyJDMoOuDENsrrTmFsGtoDfe-9RRhlB2SDkKgYQlAAXOvhg/viewform the form included a variety of answer types, including radio and dropdowns. this is by no means a final polished product, but is certainly a good proof of concept. I will continue working on zWork and improve the harness to also improve the models tool calling and accuracy. Thanks guys"}, {"post_id": 17862, "ts": "2026-06-28T20:02:34Z", "hours": 12.9517, "text": "i tested zbctl using zWork (the agent im working on) as well as using claude code. initially there wasnt an endpoint for claude code, but claude code made one by itself. to make things fair, both harnesses were wired up to use deepseek-v4-pro as the model, and after testing the same prompt and same task, claude code basically won. my harness zWork needs a lot of work, but thats a bit besides the point. The zbctl bridge extension works."}, {"post_id": 5930, "ts": "2026-06-09T22:11:43Z", "hours": 2.2767, "text": "i made a desktop agent (still in development) now im making a browser extension to let it attach onto browser sessions that users are already signed in on. Cool stuff: Push-based DOM snapshots (MutationObserver auto-detects page changes) Stable element IDs via WeakMap (same element always has same ID) Works with Gmail, Google Forms, real sessions Tab management: switch, open, close specific tabs File upload/download support Technical stuff: Python FastAPI daemon (port 8788) Manifest V3 Chrome extension Content script walks DOM → structured JSON 200ms debounce for settle detection, 3s hard cap Biggest limitation: Cross-origin iframes blocked by browser security. Can’t interact with YouTube embeds, payment forms, etc. But handles ~80% of normal browsing fine. right now it does work"}, {"post_id": 2549, "ts": "2026-06-05T02:52:17Z", "hours": 3.9786, "text": "magic"}]...
|
Title: zWork Browser Control by @zemu | Stardance
Title: zWork Browser Control by @zemu | Stardance
Devlogs:
magic
i made a desktop agent (still in development) now im making a browser extension to let it attach onto browser sessions that users are already signed in on. Cool stuff: Push-based DOM snapshots (MutationObserver auto-detects page changes) Stable element IDs via WeakMap (same element always has same ID) Works with Gmail, Google Forms, real sessions Tab management: switch, open, close specific tabs File upload/download support Technical stuff: Python FastAPI daemon (port 8788) Manifest V3 Chrome extension Content script walks DOM → structured JSON 200ms debounce for settle detection, 3s hard cap Biggest limitation: Cross-origin iframes blocked by browser security. Can’t interact with YouTube embeds, payment forms, etc. But handles ~80% of normal browsing fine. right now it does work
i tested zbctl using zWork (the agent im working on) as well as using claude code. initially there wasnt an endpoint for claude code, but claude code made one by itself. to make things fair, both harnesses were wired up to use deepseek-v4-pro as the model, and after testing the same prompt and same task, claude code basically won. my harness zWork needs a lot of work, but thats a bit besides the point. The zbctl bridge extension works.
I benchmarked zWork (desktop ai agent made by me) using zbctl (extension) to test its new browser use abilities. ive used the prompt in the picture below. the model answered all but one correct. the google form used to “benchmark” the model was: https://docs.google.com/forms/d/e/1FAIpQLSfHyJDMoOuDENsrrTmFsGtoDfe-9RRhlB2SDkKgYQlAAXOvhg/viewform the form included a variety of answer types, including radio and dropdowns. this is by no means a final polished product, but is certainly a good proof of concept. I will continue working on zWork and improve the harness to also improve the models tool calling and accuracy. Thanks guys
updated readme because i needed to
any click that changed DOM used to take about 3s now it takes about 200ms. I also added back the extension GUI because sometimes its confusing without it. also to save tokens from agent context windows, content.js no longer creates a brand new fat snapshot of the entire page.
Ships:
I made zWork Everything was challenging, mainly harness engineering. The browser feature was relatively straightforward. I’m proud of the extensiveness or comprehensiveness of this project, and the scale at which it worked. To fully test my app, you should probably install the app, as well as the extension. There is a limited web demo at app.tryzwork.app which doesnt really have any features. More info is available in the readmes....
|
1792972347.397626
|
1793058747.397626
|
|
9808
|
aero-deuce by @zemu | Stardance
|
zemu
|
1
|
10.0
|
174
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-08T02:18:32Z", "hours": 10.0, "multiplier": 17.74, "payout": 174, "blessing": "neutral", "text": "I made Aero-Deuce, a 12-billion parameter AI language model that runs locally on consumer hardware. It’s an instruction-following chatbot fine-tuned and post-trained from Google’s Gemma 4 12B using a technique called QLoRA with the Muon optimizer. It’s a relatively new approach that applies matrix orthogonalization to keep the training efficient. The whole model was trained on 30,000 instruction-following examples across 2,000 steps, going from a loss of 3.82 down to 0.57. The final model is exported in three formats: a GGUF file (~7GB) that works with anything supporting llama.cpp (LM Studio, Ollama, GPT4All), an MLX version optimized for Apple Silicon, and the raw LoRA adapter for anyone who wants to merge it or fine-tune further. I also built a live API endpoint on Modal with streaming support, so anyone can chat with it through a web interface. It's named \"Aero-Deuce\" because deuce means two, and this is my second attempt at LLMs, my first being a 300m custom model with some weird architecture, and I didn't have the funds to get that one off the ground. The most challenging part was the training pipeline itself. I started on Modal with spot GPUs, which meant my training kept getting preempted. I had to build robust checkpoint resumption just to survive it. Then I switched to Lightning AI for the second half. The base model uses a \"unified\" architecture (gemma4_unified) that most tooling didn't support — PEFT didn't recognize it, MLX couldn't run it, so I had to manually strip multimodal weights, rename parameter keys, and patch configs to make it work everywhere. Exporting to GGUF required building llama.cpp from source. The HuggingFace uploads stalled repeatedly. There were a lot of nights where nothing worked and I had to dig through error logs at 2am. I'm proud that it actually works end to end. A 12B model that you can download as a single 7GB file and run on a MacBook Air — that's real. The training converged well, the model follows instructions properly, it identifies itself as Aero-Deuce instead of claiming to be Gemma. I built the entire pipeline from scratch: data loading with loss masking, the Muon optimizer implementation, dual-optimizer parameter partitioning, checkpoint resumption, the export pipeline, and the inference API. It's not a notebook tutorial — it's a real system. To test it: go to the live demo at https://aero-deuce-lander.vercel.app, or download the GGUF from huggingface.co/ZeZZm/aero-deuce-GGUF and open it in LM Studio or GPT4All. If you're on a Mac, you can run pip install mlx-lm and use python -m mlx_lm.generate --model ZeZZm/aero-deuce-MLX --prompt \"anything\". The code is at github.com/Ryz3nPlayZ/aero-deuce. Everything is Apache 2.0. Thanks!", "repo": "https://github.com/Ryz3nPlayZ/aero-deuce", "demo": "https://aero-deuce-lander.vercel.app/"}]...
|
[{"post_id": 4671, "ts": "2026 [{"post_id": 4671, "ts": "2026-06-08T02:15:16Z", "hours": 0.3186, "text": "finished landing page"}, {"post_id": 4650, "ts": "2026-06-08T01:48:45Z", "hours": 2.0606, "text": "adapter, gguf, and mlx (q4) all on huggingface I made a simple landing page hosted custom inference endpoint (might not work very well because im broke) should be able to run through services like Ollama and llama.cpp locally"}, {"post_id": 4501, "ts": "2026-06-07T20:43:42Z", "hours": 3.5564, "text": "I made a custom AI model called Aero-Deuce. it’s based on Google’s Gemma 4 12B, but we fine-tuned/post-trained it using a technique called QLoRA with a custom optimizer called Muon. the idea was to make a small, efficient instruction-following model that runs locally on consumer hardware. we trained it on 30,000 instruction-following examples for 2,000 steps. the training loss dropped from 3.82 to 0.57. it runs at about 14-16 tokens per second on a MacBook Air M5. the model is exported in three formats: a raw LoRA adapter (for merging with the base model), a GGUF file (runs in llama.cpp, LM Studio, Ollama, etc.), and an MLX version (optimized for Apple Silicon). all three will be on HuggingFace soon. the code is on GitHub. still need to benchmark it against the base model and submit it to the HuggingFace leaderboard. code: github.com/Ryz3nPlayZ/aero-deuce adapter: huggingface.co/ZeZZm/aero-deuce gguf: huggingface.co/ZeZZm/aero-deuce-GGUF mlx: huggingface.co/ZeZZm/aero-deuce-MLX"}, {"post_id": 3750, "ts": "2026-06-06T19:59:48Z", "hours": 3.9292, "text": "45% of the way done with test post training run but im already broke"}]...
|
Title: aero-deuce by @zemu | Stardance
Devlogs:
4 Title: aero-deuce by @zemu | Stardance
Devlogs:
45% of the way done with test post training run but im already broke
I made a custom AI model called Aero-Deuce. it’s based on Google’s Gemma 4 12B, but we fine-tuned/post-trained it using a technique called QLoRA with a custom optimizer called Muon. the idea was to make a small, efficient instruction-following model that runs locally on consumer hardware. we trained it on 30,000 instruction-following examples for 2,000 steps. the training loss dropped from 3.82 to 0.57. it runs at about 14-16 tokens per second on a MacBook Air M5. the model is exported in three formats: a raw LoRA adapter (for merging with the base model), a GGUF file (runs in llama.cpp, LM Studio, Ollama, etc.), and an MLX version (optimized for Apple Silicon). all three will be on HuggingFace soon. the code is on GitHub. still need to benchmark it against the base model and submit it to the HuggingFace leaderboard. code: github.com/Ryz3nPlayZ/aero-deuce adapter: huggingface.co/ZeZZm/aero-deuce gguf: huggingface.co/ZeZZm/aero-deuce-GGUF mlx: huggingface.co/ZeZZm/aero-deuce-MLX
adapter, gguf, and mlx (q4) all on huggingface I made a simple landing page hosted custom inference endpoint (might not work very well because im broke) should be able to run through services like Ollama and llama.cpp locally
finished landing page
Ships:
I made Aero-Deuce, a 12-billion parameter AI language model that runs locally on consumer hardware. It’s an instruction-following chatbot fine-tuned and post-trained from Google’s Gemma 4 12B using a technique called QLoRA with the Muon optimizer. It’s a relatively new approach that applies matrix orthogonalization to keep the training efficient. The whole model was trained on 30,000 instruction-following examples across 2,000 steps, going from a loss of 3.82 down to 0.57. The final model is exported in three formats: a GGUF file (~7GB) that works with anything supporting llama.cpp (LM Studio, Ollama, GPT4All), an MLX version optimized for Apple Silicon, and the raw LoRA adapter for anyone who wants to merge it or fine-tune further. I also built a live API endpoint on Modal with streaming support, so anyone can chat with it through a web interface. It's named "Aero-Deuce" because deuce means two, and this is my second attempt at LLMs, my first being a 300m custom model with some weird architecture, and I didn't have the funds to get that one off the ground. The most challenging part was the training pipeline itself. I started on Modal with spot GPUs, which meant my training kept getting preempted. I had to build robust checkpoint resumption just to survive it. Then I switched to Lightning AI for the second half. The base model uses a "unified" architecture (gemma4_unified) that most tooling didn't support — PEFT didn't recognize it, MLX couldn't run it, so I had to manually strip multimodal weights, rename parameter keys, and patch configs to make it work everywhere. Exporting to GGUF required building llama.cpp from source. The HuggingFace uploads stalled repeatedly. There were a lot of nights where nothing worked and I had to dig through error logs at 2am. I'm proud that it actually works end to end. A 12B model that you can download as a single 7GB file and run on a MacBook Air — that's real. The training converged well, the model follows instructions properly, it identifies itself as Aero-Deuce instead of claiming to be Gemma. I built the entire pipeline from scratch: data loading with loss masking, the Muon optimizer implementation, dual-optimizer parameter partitioning, checkpoint resumption, the export pipeline, and the inference API. It's not a notebook tutorial — it's a real system. To test it: go to the live demo at https://aero-deuce-lander.vercel.app, or download the GGUF from huggingface.co/ZeZZm/aero-deuce-GGUF and open it in LM Studio or GPT4All. If you're on a Mac, you can run pip install mlx-lm and use python -m mlx_lm.generate --model ZeZZm/aero-deuce-MLX --prompt "anything". The code is at github.com/Ryz3nPlayZ/aero-deuce. Everything is Apache 2.0. Thanks!...
|
1792990080.156106
|
1793076480.156106
|
|
66405
|
dusklauncher by @zemu | Stardance
|
zemu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: dusklauncher by @zemu | Stardance
|
1792460950.90315
|
1793065750.90315
|
|
3510
|
Test by @zemonarch | Stardance
|
zemonarch
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Test by @zemonarch | Stardance
|
1792507685.7945464
|
1793112485.7945464
|
|
13277
|
my own OS by @zelllytech | Stardance
|
zelllytech
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: my own OS by @zelllytech | Stardance
|
1792522387.4841886
|
1793127187.4841886
|
|
57639
|
My awesome macropad! by @zelasip | Stardance
|
zelasip
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zelasip | Stardanc Title: My awesome macropad! by @zelasip | Stardance...
|
1792716445.1100004
|
1793321245.1100004
|
|
34067
|
My own site! by @zeko | Stardance
|
zeko
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @zeko | Stardance
|
1792795750.2244902
|
1793400550.2244902
|
|
34386
|
Frictionless by @zekikayaodabas | Stardance
|
zekikayaodabas
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @zekikayaodabas | Stardance
|
1792522441.990084
|
1793127241.990084
|
|
10255
|
Potato tank by @zeke | Stardance
|
zeke
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Potato tank by @zeke | Stardance
|
1792810330.1773982
|
1793415130.1773982
|
|
44511
|
Beacon by @zeinN | Stardance
|
zeinN
|
0
|
51.58
|
0
|
[]
|
[{"post_id": 53758, "ts": "202 [{"post_id": 53758, "ts": "2026-08-24T13:13:21Z", "hours": 3.645, "text": "Beacon Devlog #8 Anyone with skill in Fusion, would appreciate help! Quick one today after a break yesterday: got to work learning Fusion to design a shell. After I discovered Control Point Spline and the Mirror tool, the front came together quite quickly. I’ve made a 3D model of my main PCB, and found a 3D model for a display case, which I’ll try to work into the design’s base. If anyone has any resources for creating 3D printable buttons that I could take a look at, it’d be much appreciated. Additionally, as in the screenshot, I can’t seem to bevel this edge (or the opposite edge) with the Fillet tool. Changing the distance does nothing, and neither does changing the corner type or tangency weight. Would love any advice!"}, {"post_id": 52591, "ts": "2026-08-22T19:49:49Z", "hours": 6.7333, "text": "Beacon Devlog #7: PRIMARY PCB COMPLETE! This one took about 20 hours, so I’ll go over the primary setbacks here: initial schematic didn’t really consider high threshold voltage of warm white LEDs - trying to power them off of the primary 3.3v rail would result in manufacturing differences just killing some of them most likely. I instead connected the MOSFETs which power the breakouts directly to the battery regulator voltage, which should hover closer to 4V. A couple of my components (e.g. a 3.3v i2s MEMS microphone) had faulty footprints when downloaded through vendors like DigiKey, which took me embarrassingly long to work out My last post shows a comical amount of errors: these stem from many of my footprints for smaller components (e.g. TVS diode array) having small pads with low distances between each other. I downloaded custom design rules for JLCPCB without really understanding what they did, and had to shuffle with them a bit to get round the 300 warnings (down to about 9 now, I think they’re safe to ignore) Finding suitable headers for the breakout boards (the 2 8-pins at the top) took a while, given how little room I’m working with. Every connector on the board posed a major routing challenge until I realised that I could change my schematic in response to a dead end on the PCB. On a related note, I’m mixing and matching connectors here to fit the few components I already own (e.g. standard 2.54mm headers for my E-Ink) Working out differential pairs was less than fun About 4 hours of work didn’t record while I was working out how to use an old spare monitor with my laptop: not the end of the world, but a shame This is my first project with KiCad: the resolution’s not great, but if you spot any issues please mention them What’s Next Before I apply for funding, I need to make a 3D model of the enclosure, design the LED breakout boards, and make a proper GitHub repo out of these. I hope to have that done in the next 5 days or so, so I can focus more on school when it starts up again. When it’s done, hope you guys give it a try!"}, {"post_id": 51121, "ts": "2026-08-20T16:50:11Z", "hours": 1.0, "text": "might be cooked see you guys in 10 hours"}, {"post_id": 51063, "ts": "2026-08-20T15:25:47Z", "hours": 9.6006, "text": "Beacon Devlog #6 PCB neeeeearly finished: you can see how much space I gave myself that I didn’t end up needing I think if I were to restart now I could tidy it up a bit more: with me not having done this before I underestimated just how much I need to clean up the rats nets first, and have ended up compensating with soooooooo many vias Also need to finalise connector types: mixing and matching for the minute because my AliExpress e-ink uses the nichest connector known to man"}, {"post_id": 49945, "ts": "2026-08-18T22:42:21Z", "hours": 4.0622, "text": "Beacon Devlog #5 just discovered how to get more than one line in here, thanks gang Main board schematic complete! Since the last update, I’ve added an on/off switch to the battery controller, made use of all available IO and finalised the links to the LED breakouts (need to design later, should be simple in comparison) shift register’s doing some heavy liftingg Also spent far too long getting the 3d models and footprints for every part, so working on PCB should be seamless tomorrow."}, {"post_id": 49500, "ts": "2026-08-18T11:25:37Z", "hours": 8.4744, "text": "anyone with PCB design experience, would greatly appreciate if you gave this a quick check, as it’s my first time working on a circuit. beacon devlog #4: aside from some peripheral buttons (maybe a potentiometer) and the shift register/output LEDs, schematic is complete!"}, {"post_id": 47676, "ts": "2026-08-15T19:04:49Z", "hours": 3.9219, "text": "Devlog 3: if anyone knows how to put line breaks in these dev logs pleeeease let me know - started work on the enclosure model, and began working out the logic of the whole circuit: attached is a simulated circuit which should(!) let me control about 40 LEDs with just 3 ESP32 GPIO pins"}, {"post_id": 46466, "ts": "2026-08-13T18:06:45Z", "hours": 6.0831, "text": "ticker devlog 2: got a little distracted from the whole metronome thing when my e-ink display came in the mail - developed an algorithm that draws a random constellation to use as a startup/sleep screen. might implement some different shapes of stars later: only wrote code to handle truncated regular polygons. if I stick to any kind of plan, next up should be learning CAD or KiCAD!"}, {"post_id": 45479, "ts": "2026-08-12T00:01:49Z", "hours": 8.0628, "text": "First dev post on Ticker (name needs work): a metronome which counts along to your beat. About half of my logged time has been spent on a rough design, with the other half being research. The plan is to have the device analyse the signal from an internal microphone to detect beats and determine BPM, and so I’m learning how to implement FFT in C++ (and how to use C++ in general!). Below is today’s design work; my initial idea was to mimic analog/pendulum metronomes with a motor, but I couldn’t think of a clean way to implement it. White strips on front will instead light up in time (having 7 allows us to represent compound times, although may be confusing for harder polyrhythms)"}]...
|
Title: Beacon by @zeinN | Stardance
Devlogs:
Firs Title: Beacon by @zeinN | Stardance
Devlogs:
First dev post on Ticker (name needs work): a metronome which counts along to your beat. About half of my logged time has been spent on a rough design, with the other half being research. The plan is to have the device analyse the signal from an internal microphone to detect beats and determine BPM, and so I’m learning how to implement FFT in C++ (and how to use C++ in general!). Below is today’s design work; my initial idea was to mimic analog/pendulum metronomes with a motor, but I couldn’t think of a clean way to implement it. White strips on front will instead light up in time (having 7 allows us to represent compound times, although may be confusing for harder polyrhythms)
ticker devlog 2: got a little distracted from the whole metronome thing when my e-ink display came in the mail - developed an algorithm that draws a random constellation to use as a startup/sleep screen. might implement some different shapes of stars later: only wrote code to handle truncated regular polygons. if I stick to any kind of plan, next up should be learning CAD or KiCAD!
Devlog 3: if anyone knows how to put line breaks in these dev logs pleeeease let me know - started work on the enclosure model, and began working out the logic of the whole circuit: attached is a simulated circuit which should(!) let me control about 40 LEDs with just 3 ESP32 GPIO pins
anyone with PCB design experience, would greatly appreciate if you gave this a quick check, as it’s my first time working on a circuit. beacon devlog #4: aside from some peripheral buttons (maybe a potentiometer) and the shift register/output LEDs, schematic is complete!
Beacon Devlog #5 just discovered how to get more than one line in here, thanks gang Main board schematic complete! Since the last update, I’ve added an on/off switch to the battery controller, made use of all available IO and finalised the links to the LED breakouts (need to design later, should be simple in comparison) shift register’s doing some heavy liftingg Also spent far too long getting the 3d models and footprints for every part, so working on PCB should be seamless tomorrow.
Beacon Devlog #6 PCB neeeeearly finished: you can see how much space I gave myself that I didn’t end up needing I think if I were to restart now I could tidy it up a bit more: with me not having done this before I underestimated just how much I need to clean up the rats nets first, and have ended up compensating with soooooooo many vias Also need to finalise connector types: mixing and matching for the minute because my AliExpress e-ink uses the nichest connector known to man
might be cooked see you guys in 10 hours
Beacon Devlog #7: PRIMARY PCB COMPLETE! This one took about 20 hours, so I’ll go over the primary setbacks here: initial schematic didn’t really consider high threshold voltage of warm white LEDs - trying to power them off of the primary 3.3v rail would result in manufacturing differences just killing some of them most likely. I instead connected the MOSFETs which power the breakouts directly to the battery regulator voltage, which should hover closer to 4V. A couple of my components (e.g. a 3.3v i2s MEMS microphone) had faulty footprints when downloaded through vendors like DigiKey, which took me embarrassingly long to work out My last post shows a comical amount of errors: these stem from many of my footprints for smaller components (e.g. TVS diode array) having small pads with low distances between each other. I downloaded custom design rules for JLCPCB without really understanding what they did, and had to shuffle with them a bit to get round the 300 warnings (down to about 9 now, I think they’re safe to ignore) Finding suitable headers for the breakout boards (the 2 8-pins at the top) took a while, given how little room I’m working with. Every connector on the board posed a major routing challenge until I realised that I could change my schematic in response to a dead end on the PCB. On a related note, I’m mixing and matching connectors here to fit the few components I already own (e.g. standard 2.54mm headers for my E-Ink) Working out differential pairs was less than fun About 4 hours of work didn’t record while I was working out how to use an old spare monitor with my laptop: not the end of the world, but a shame This is my first project with KiCad: the resolution’s not great, but if you spot any issues please mention them What’s Next Before I apply for funding, I need to make a 3D model of the enclosure, design the LED breakout boards, and make a proper GitHub repo out of these. I hope to have that done in the next 5 days or so, so I can focus more on school when it starts up again. When it’s done, hope you guys give it a try!
Beacon Devlog #8 Anyone with skill in Fusion, would appreciate help! Quick one today after a break yesterday: got to work learning Fusion to design a shell. After I discovered Control Point Spline and the Mirror tool, the front came together quite quickly. I’ve made a 3D model of my main PCB, and found a 3D model for a display case, which I’ll try to work into the design’s base. If anyone has any resources for creating 3D printable buttons that I could take a look at, it’d be much appreciated. Additionally, as in the screenshot, I can’t seem to bevel this edge (or the opposite edge) with the Fillet tool. Changing the distance does nothing, and neither does changing the corner type or tangency weight. Would love any advice!...
|
1792590506.5692775
|
1793195306.5692775
|
|
21466
|
WebOS by @zehra_khan | Stardance
|
zehra_khan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: WebOS by @zehra_khan | Stardance
|
1792644610.5459769
|
1793249410.5459769
|
|
34664
|
My own site! by @zehra_a5z | Stardance
|
zehra_a5z
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @zehra_a5z | Stardance
|
1792691286.3253245
|
1793296086.3253245
|
|
58494
|
My own site! by @zeeshqn | Stardance
|
zeeshqn
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @zeeshqn | Stardance
|
1792752708.6068606
|
1793357508.6068606
|
|
9657
|
Untitled project by @zeeshan111100 | Stardance
|
zeeshan111100
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @zeeshan111100 | Starda Title: Untitled project by @zeeshan111100 | Stardance...
|
1792616034.251278
|
1793220834.251278
|
|
71405
|
My awesome macropad! by @zeept1234 | Stardance
|
zeept1234
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zeept1234 | Starda Title: My awesome macropad! by @zeept1234 | Stardance...
|
1792972038.997316
|
1793576838.997316
|
|
71407
|
Project by @zeept1234 | Stardance
|
zeept1234
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Project by @zeept1234 | Stardance
|
1792972040.7096674
|
1793576840.7096674
|
|
14977
|
My first slack bot! by @zeenialam1 | Stardance
|
zeenialam1
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @zeenialam1 | Starda Title: My first slack bot! by @zeenialam1 | Stardance...
|
1792597879.2327073
|
1793202679.2327073
|
|
32200
|
motorbike monitoring hardware by @zechrits | Stard motorbike monitoring hardware by @zechrits | Stardance...
|
zechrits
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: motorbike monitoring hardware by @zechrits Title: motorbike monitoring hardware by @zechrits | Stardance...
|
1792540325.8123686
|
1793145125.8123686
|
|
47394
|
My awesome macropad! by @zeboxon | Stardance
|
zeboxon
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zeboxon | Stardanc Title: My awesome macropad! by @zeboxon | Stardance...
|
1792511631.600234
|
1793116431.600234
|
|
12272
|
MotifDesigner by @zeankun | Stardance
|
zeankun
|
2
|
25.35
|
314
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-05T02:29:23Z", "hours": 7.0, "multiplier": 18.37, "payout": 134, "blessing": "neutral", "text": "Version 1.0 is now released! Horray! A lot of things have been added! Added snap to grid checkmark on inspector NEW WIDGET : Toggle/checkmark! Add confirming stuffs to your UI! Fixed units on most components New handles and dimension badge Creation, saving and loading in new MotifDesigner Visual Files ( .vfl )! with a visual parser And comes with a brand new visual file format to accompany: MotifDesigner Visual Files! What are those? These are MotifDesigner’s native format. They allow you to define UIs, either programatically or visually. Read more about the file format specification yourself, or have it as a complement for Claude or Claude Code via skills", "repo": "https://github.com/zeankundev/MotifDesigner", "demo": "https://github.com/zeankundev/MotifDesigner/releases/latest/"}, {"ship_num": 2, "ts": "2026-06-12T07:37:46Z", "hours": 17.0, "multiplier": 10.69, "payout": 180, "blessing": "neutral", "text": "This is MotifDesigner, a GUI editor for Motif (basically) in which you can edit your normal GUIs. Think of it as like the WinForms/Qt Creator of Motif! The goal is to actually bring modern UX to ancient looking software, and it’s actually quite fun! Behind all these are hours of debugging efforts, tens of segmentation fault crashes, tons of sacrificed memory for memory leak debugging, and lots of core dumps! I hope this project simplifies what GUI making is, or just making Motif development a bit easier while also looking ancient!", "repo": "https://github.com/zeankundev/MotifDesigner", "demo": "https://github.com/zeankundev/MotifDesigner/releases/latest/"}]...
|
[{"post_id": 24473, "ts": "202 [{"post_id": 24473, "ts": "2026-07-08T01:34:46Z", "hours": 1.3453, "text": "Now added live value editing! Double click (certain elements) to edit its value, and you can use your normal keyboard editing shortcuts. Yes, Home , End , Shift+arrow , Ctrl+A , etc, are supported! Hands off the mouse now! Being honest, this feature is mostly implemented by AI. Text logic and selection is a finicky subject to pick up, given the sheer complexity. But I want to make the value editing UX just like at home, like you would on Figma, and many more! Also, some quality of life updates: re-renders are now automatically scheduled based on your device’s refresh rate. You don’t need to wait for user input now, it happens automatically in the background. ( And yes, free (s) are excluded as usual. Double free() is usually the culprit and yeah, I’m bad at memory management )"}, {"post_id": 22554, "ts": "2026-07-05T02:26:15Z", "hours": 0.3092, "text": "Release 1.0 has been out now! MotifDesigner is usable for the general public now! You know what that means? Shipping time! Oh yeah, don’t forget to report bugs or issues here . Don’t be hesitant. It can be either via your AppImage or your local debug build"}, {"post_id": 22537, "ts": "2026-07-05T01:54:20Z", "hours": 0.5664, "text": "Made file specifications in Markdown, as well as a Claude skill (for you, vibecoders /j) so that Claude can generate proper visual files. No code changes, tho. Attached is an example where I instructed Claude to make a simple supermarket POS interface."}, {"post_id": 21485, "ts": "2026-07-03T13:49:15Z", "hours": 2.8694, "text": "Now the hardest part has been done: importing and parsing visual files! Here’s what I accomplished: Parsing of visual files Syntax errors and redundancy checks to ensure it is indeed the visual file you are opening Auto writing on save whenever you’ve opened something or has saved a new file! How does the MotifDesigner Visual File format work ( .vfl )? (for self programming the visual file) It’s like XML or HTML (whatever that correlates with both) except the tags don’t end in slashes. All visual files must have both [MotifDesignerVisualFile] and [EndMotifDesignerVisualFile] . This will contain two critical pieces of information: the Version parameter, which you must append (e.g. Version=0.5 ). It must be inside the VisualFile tag. the Widgets tag. Same, enclosed with EndWidgets . This will be the place where you will put your elements here. I’ll write more of the file specifications if I have more time Anyway, here’s a video to demonstrate!"}, {"post_id": 20763, "ts": "2026-07-02T13:41:43Z", "hours": 0.4028, "text": "Real thing now! You can now export visual files made by MotifDesigner! It will come in a user-friendly syntax, which is human and machine readable, which is much closer to something like XML! All that’s left is to: implement a parser to parse these visual files something to make the visual file editing complete before moving in to the IDE side of things"}, {"post_id": 20624, "ts": "2026-07-02T08:29:30Z", "hours": 1.0811, "text": "This one, by far the hardest feature to implement: the save dialog . It took me lots of work to do (most was AI assisted) that double frees were actually fired (despite deleting all free methods). Here’s what’s fully implemented: Autotemplating with a default filename Sticky file names, so your typed filename never gets lost (e.g. when changing directories) And lots of UX improvements for the save dialogs The rest are relatively easy to implement, as they require little work, such as the open file dialog, etc. Next steps Next, I hope that There will be basic visual file saving/exporting ( *.vfl ) Parser for those visual files (to open it) Lots of filesystem-related operations as well as a robust project management system"}, {"post_id": 19691, "ts": "2026-07-01T02:35:34Z", "hours": 0.2656, "text": "Oh yeah, I forgot to log this one, but it adds few QoL improvements. Now, it should feel more modern, hence to the Figma-style handle and nets, as well as adding the bottom blue badge to visualize the exact width without looking at the inspector ever again!"}, {"post_id": 14973, "ts": "2026-06-24T09:54:14Z", "hours": 0.6342, "text": "Some features for 0.8 will be on the works by now. This includes: Snap to Grid toggle Added toggle as a new component Overall bug fixes ;) There will be more during the actual 0.8 release so stay tuned"}, {"post_id": 7967, "ts": "2026-06-13T09:11:29Z", "hours": 0.7167, "text": "A lot screwed up, so I decided to fix a lot of them. These are just mostly bug fixes and only a few QoL changes. For those who are afraid of change: Labels should be more legible now (same background as the overall canvas) Forced .hpp file generation (because the header implementation is C++, we don’t want it to mix with C only code A lot of stubborness during code generation ;)"}, {"post_id": 7913, "ts": "2026-06-13T06:10:04Z", "hours": 0.5419, "text": "Hotfix 1 of v0.7 (0.71) is here. Nothing much here, just like the old 0.7 version, except this update are just bug fixes and few QoL improvements. If you are terrified of change, I’ll wrap up what’s changed in this hotfix: The handles and selection frames should no longer offset by now, it is near one-to-one on what you’ll be building at the end (including the header files :D) And yeah, the grid should be more visible now. At TextDialog.cpp , few improvements were made. The text field will focus first rather than the OK button, so you can type your header class right away, and press Enter when you’re all set!"}, {"post_id": 7337, "ts": "2026-06-12T07:29:23Z", "hours": 0.4667, "text": "Quality of life fixes, nothing big, just minor fixes before getting ready to ship at the first phase!"}, {"post_id": 7327, "ts": "2026-06-12T06:32:47Z", "hours": 1.2031, "text": "Finally, added one feature that is extremely important or else render MotifDesigner out of its core goals! Now, header ( *.h ) export is available, which means you can start using it as part of your project! Zero warnings, zero errors, it’s stable now (if there are errors or warnings in .h, it’s either your fault or just file a bug report)"}, {"post_id": 7270, "ts": "2026-06-12T03:52:20Z", "hours": 1.7183, "text": "Added a dialog later on for you to answer the questions it prompted you, as well as regex checking (this will be fixed into a more modular approach later on). Regexes still apply! I’ll probably finish a lot later on (including adding a new visual file, opening a visual file, etc). Right now, this could be the roadmap for future development from now: Current Goals: Implement exporting visual as .h file to be used Creating a new visual file, opening/parsing, and saving Future Goals: Fully implemented C++ editor inside of the designer Project system (a folder containing the visual file, C++ file and the automatically generated header file) Automatic X11/Xm/Xt download if you don’t have one (includes and libraries) In-IDE building with g++ and having the ability to run the result binary Packaging to AppImage with linuxdeploy and appimagetool Add Wakatime/Hackatime support /j (that will/won’t happen)"}, {"post_id": 6823, "ts": "2026-06-11T13:29:17Z", "hours": 2.2417, "text": "Lots of bug fixes (I forgot what I did for the past 2 hours logged T_T) but at least, most bugs were shot down and caught. Especially quick mouse kids, who just mess and drag widgets fast, now it’s “throttled” to a fixed 60fps. And also added status bar to highlight the user on what’s going on and what to do with the tool. Oh yeah, also added where you can use arrow keys to snappingly move between 10 units, just for convenience! (Excuse me, the cursor there is highly offset, I truly apologize for that TwT)"}, {"post_id": 6687, "ts": "2026-06-11T06:17:54Z", "hours": 3.6958, "text": "Finally, the feature we all be waiting for! The canvas! This took me a horrendous amount of time, but it sure was worth the experience It can now drag, scale, and do many transformations like a usual GUI builder would do! And yeah, there were a lot of hiccups (yeah, segfaults and coredump abortions) and managed to fix a lot of them if it weren’t for Claude! Yeah, basically, it looks like a functioning editor by now! Sure it was interesting!"}, {"post_id": 6113, "ts": "2026-06-10T08:44:45Z", "hours": 0.2511, "text": "Now added a check for illegal names using regex! This is done so that you won’t get programmatic errors later on when coding your app in C++ (everyone doesn’t want that!) so it’s better to stay off at the normal naming convention of C"}, {"post_id": 6054, "ts": "2026-06-10T05:17:49Z", "hours": 0.8317, "text": "Added new properties panel! This is to ensure precise modifications were being made so that you still have lots of control with the UI building process"}, {"post_id": 5556, "ts": "2026-06-09T11:47:50Z", "hours": 1.2603, "text": "A lot of things were done. First off, the menubar for your stuffs later on! You’ll do it there! Second, now there’s a toolbar (still WIP)! As well as a lot of segfaults along the way, we managed to get that working for the start of this!"}, {"post_id": 5494, "ts": "2026-06-09T09:26:59Z", "hours": 1.325, "text": "More work yay! Most of the time logged here is just a scrapped feature that will never make it (due to the nature of XmNotebook). Initially, I wanted to add a tab that can switch between the visual editor and the C++ code editor (WIP)! but yeah, I don’t want a flipbook like interface, so I’ll make it as two separate modules. But hey, at least we made progress!"}, {"post_id": 5371, "ts": "2026-06-09T03:39:09Z", "hours": 1.7375, "text": "Actually another long time to comply for shipping (a test one!) which are AppImages! I just don’t want to mess around with dependency hell when distributing an ELF binary (ugh dangerous) so AppImage was our way to go. First, it was a bit flawed, then with some help, we managed to get two variants, generic and IRIX (for those who run MaXX). Hopefully it will be done soon, as this is still a work in progress and should serve the instantaneous basis of my future MotifDesigner roadmap. Attached is the app tested on Ubuntu MATE at Deskterm."}, {"post_id": 4819, "ts": "2026-06-08T10:10:15Z", "hours": 1.0542, "text": "I know this may sound like a gimmick (given that I logged 1h on one specific window) but this was tedious to get into. The About section. It seems easy, if you think, but no! It’s actually really hard to get into without proper techniques and lots of tampering with the XPM pixmaps. Gemini couldn’t help so I reached over to Claude to help and here it is, 1h wasted on just an about section."}, {"post_id": 4762, "ts": "2026-06-08T07:17:56Z", "hours": 0.2944, "text": "Did some variations with the IMC test but this time with the actual X11 Motif window showing up. The same as before except this test is now in an X11 window 🙃"}, {"post_id": 4757, "ts": "2026-06-08T06:34:36Z", "hours": 0.4325, "text": "Doing some tests to actually ensure that inter-module communication is done effortlessly. I don’t want to write more bloat code that results in a bloated main.cpp that just “acts” as a middleman, just let the header files be the ones that’s fully responsible for the IMC calling"}, {"post_id": 4742, "ts": "2026-06-08T05:56:00Z", "hours": 0.3322, "text": "First project bootstrap! Horray!"}]...
|
Title: MotifDesigner by @zeankun | Stardance
Devl Title: MotifDesigner by @zeankun | Stardance
Devlogs:
First project bootstrap! Horray!
Doing some tests to actually ensure that inter-module communication is done effortlessly. I don’t want to write more bloat code that results in a bloated main.cpp that just “acts” as a middleman, just let the header files be the ones that’s fully responsible for the IMC calling
Did some variations with the IMC test but this time with the actual X11 Motif window showing up. The same as before except this test is now in an X11 window 🙃
I know this may sound like a gimmick (given that I logged 1h on one specific window) but this was tedious to get into. The About section. It seems easy, if you think, but no! It’s actually really hard to get into without proper techniques and lots of tampering with the XPM pixmaps. Gemini couldn’t help so I reached over to Claude to help and here it is, 1h wasted on just an about section.
Actually another long time to comply for shipping (a test one!) which are AppImages! I just don’t want to mess around with dependency hell when distributing an ELF binary (ugh dangerous) so AppImage was our way to go. First, it was a bit flawed, then with some help, we managed to get two variants, generic and IRIX (for those who run MaXX). Hopefully it will be done soon, as this is still a work in progress and should serve the instantaneous basis of my future MotifDesigner roadmap. Attached is the app tested on Ubuntu MATE at Deskterm.
More work yay! Most of the time logged here is just a scrapped feature that will never make it (due to the nature of XmNotebook). Initially, I wanted to add a tab that can switch between the visual editor and the C++ code editor (WIP)! but yeah, I don’t want a flipbook like interface, so I’ll make it as two separate modules. But hey, at least we made progress!
A lot of things were done. First off, the menubar for your stuffs later on! You’ll do it there! Second, now there’s a toolbar (still WIP)! As well as a lot of segfaults along the way, we managed to get that working for the start of this!
Added new properties panel! This is to ensure precise modifications were being made so that you still have lots of control with the UI building process
Now added a check for illegal names using regex! This is done so that you won’t get programmatic errors later on when coding your app in C++ (everyone doesn’t want that!) so it’s better to stay off at the normal naming convention of C
Finally, the feature we all be waiting for! The canvas! This took me a horrendous amount of time, but it sure was worth the experience It can now drag, scale, and do many transformations like a usual GUI builder would do! And yeah, there were a lot of hiccups (yeah, segfaults and coredump abortions) and managed to fix a lot of them if it weren’t for Claude! Yeah, basically, it looks like a functioning editor by now! Sure it was interesting!
Lots of bug fixes (I forgot what I did for the past 2 hours logged T_T) but at least, most bugs were shot down and caught. Especially quick mouse kids, who just mess and drag widgets fast, now it’s “throttled” to a fixed 60fps. And also added status bar to highlight the user on what’s going on and what to do with the tool. Oh yeah, also added where you can use arrow keys to snappingly move between 10 units, just for convenience! (Excuse me, the cursor there is highly offset, I truly apologize for that TwT)
Added a dialog later on for you to answer the questions it prompted you, as well as regex checking (this will be fixed into a more modular approach later on). Regexes still apply! I’ll probably finish a lot later on (including adding a new visual file, opening a visual file, etc). Right now, this could be the roadmap for future development from now: Current Goals: Implement exporting visual as .h file to be used Creating a new visual file, opening/parsing, and saving Future Goals: Fully implemented C++ editor inside of the designer Project system (a folder containing the visual file, C++ file and the automatically generated header file) Automatic X11/Xm/Xt download if you don’t have one (includes and libraries) In-IDE building with g++ and having the ability to run the result binary Packaging to AppImage with linuxdeploy and appimagetool Add Wakatime/Hackatime support /j (that will/won’t happen)
Finally, added one feature that is extremely important or else render MotifDesigner out of its core goals! Now, header ( *.h ) export is available, which means you can start using it as part of your project! Zero warnings, zero errors, it’s stable now (if there are errors or warnings in .h, it’s either your fault or just file a bug report)
Quality of life fixes, nothing big, just minor fixes before getting ready to ship at the first phase!
Hotfix 1 of v0.7 (0.71) is here. Nothing much here, just like the old 0.7 version, except this update are just bug fixes and few QoL improvements. If you are terrified of change, I’ll wrap up what’s changed in this hotfix: The handles and selection frames should no longer offset by now, it is near one-to-one on what you’ll be building at the end (including the header files :D) And yeah, the grid should be more visible now. At TextDialog.cpp , few improvements were made. The text field will focus first rather than the OK button, so you can type your header class right away, and press Enter when you’re all set!
A lot screwed up, so I decided to fix a lot of them. These are just mostly bug fixes and only a few QoL changes. For those who are afraid of change: Labels should be more legible now (same background as the overall canvas) Forced .hpp file generation (because the header implementation is C++, we don’t want it to mix with C only code A lot of stubborness during code generation ;)
Some features for 0.8 will be on the works by now. This includes: Snap to Grid toggle Added toggle as a new component Overall bug fixes ;) There will be more during the actual 0.8 release so stay tuned
Oh yeah, I forgot to log this one, but it adds few QoL improvements. Now, it should feel more modern, hence to the Figma-style handle and nets, as well as adding the bottom blue badge to visualize the exact width without looking at the inspector ever again!
This one, by far the hardest feature to implement: the save dialog . It took me lots of work to do (most was AI assisted) that double frees were actually fired (despite deleting all free methods). Here’s what’s fully implemented: Autotemplating with a default filename Sticky file names, so your typed filename never gets lost (e.g. when changing directories) And lots of UX improvements for the save dialogs The rest are relatively easy to implement, as they require little work, such as the open file dialog, etc. Next steps Next, I hope that There will be basic visual file saving/exporting ( *.vfl ) Parser for those visual files (to open it) Lots of filesystem-related operations as well as a robust project management system
Real thing now! You can now export visual files made by MotifDesigner! It will come in a user-friendly syntax, which is human and machine readable, which is much closer to something like XML! All that’s left is to: implement a parser to parse these visual files something to make the visual file editing complete before moving in to the IDE side of things
Now the hardest part has been done: importing and parsing visual files! Here’s what I accomplished: Parsing of visual files Syntax errors and redundancy checks to ensure it is indeed the visual file you are opening Auto writing on save whenever you’ve opened something or has saved a new file! How does the MotifDesigner Visual File format work ( .vfl )? (for self programming the visual file) It’s like XML or HTML (whatever that correlates with both) except the tags don’t end in slashes. All visual files must have both [MotifDesignerVisualFile] and [EndMotifDesignerVisualFile] . This will contain two critical pieces of information: the Version parameter, which you must append (e.g. Version=0.5 ). It must be inside the VisualFile tag. the Widgets tag. Same, enclosed with EndWidgets . This will be the place where you will put your elements here. I’ll write more of the file specifications if I have more time Anyway, here’s a video to demonstrate!
Made file specifications in Markdown, as well as a Claude skill (for you, vibecoders /j) so that Claude can generate proper visual files. No code changes, tho. Attached is an example where I instructed Claude to make a simple supermarket POS interface.
Release 1.0 has been out now! MotifDesigner is usable for the general public now! You know what that means? Shipping time! Oh yeah, don’t forget to report bugs or issues here . Don’t be hesitant. It can be either via your AppImage or your local debug build
Now added live value editing! Double click (certain elements) to edit its value, and you can use your normal keyboard editing shortcuts. Yes, Home , End , Shift+arrow , Ctrl+A , etc, are supported! Hands off the mouse now! Being honest, this feature is mostly implemented by AI. Text logic and selection is a finicky subject to pick up, given the sheer complexity. But I want to make the value editing UX just like at home, like you would on Figma, and many more! Also, some quality of life updates: re-renders are now automatically scheduled based on your device’s refresh rate. You don’t need to wait for user input now, it happens automatically in the background. ( And yes, free (s) are excluded as usual. Double free() is usually the culprit and yeah, I’m bad at memory management )
Ships:
This is MotifDesigner, a GUI editor for Motif (basically) in which you can edit your normal GUIs. Think of it as like the WinForms/Qt Creator of Motif! The goal is to actually bring modern UX to ancient looking software, and it’s actually quite fun! Behind all these are hours of debugging efforts, tens of segmentation fault crashes, tons of sacrificed memory for memory leak debugging, and lots of core dumps! I hope this project simplifies what GUI making is, or just making Motif development a bit easier while also looking ancient!
Version 1.0 is now released! Horray! A lot of things have been added! Added snap to grid checkmark on inspector NEW WIDGET : Toggle/checkmark! Add confirming stuffs to your UI! Fixed units on most components New handles and dimension badge Creation, saving and loading in new MotifDesigner Visual Files ( .vfl )! with a visual parser And comes with a brand new visual file format to accompany: MotifDesigner Visual Files! What are those? These are MotifDesigner’s native format. They allow you to define UIs, either programatically or visually. Read more about the file format specification yourself, or have it as a complement for Claude or Claude Code via skills...
|
1792994214.1753986
|
1793080614.1753986
|
|
45855
|
My very own WebOS by @ze-man | Stardance
|
ze-man
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @ze-man | Stardance
|
1792641111.8758643
|
1793245911.8758643
|
|
45856
|
zeboard by @ze-man | Stardance
|
ze-man
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: zeboard by @ze-man | Stardance
|
1792641112.722062
|
1793245912.722062
|
|
45859
|
Learning V4 by @ze-man | Stardance
|
ze-man
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Learning V4 by @ze-man | Stardance
|
1792641115.2457275
|
1793245915.2457275
|
|
37890
|
My very own WebOS by @zdv | Stardance
|
zdv
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @zdv | Stardance
|
1792709425.6534896
|
1793314225.6534896
|
|
64857
|
Untitled project by @zdery | Stardance
|
zdery
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @zdery | Stardance
|
1792450422.9179173
|
1793055222.9179173
|
|
56733
|
CoolcatOS by @zcsantiago | Stardance
|
zcsantiago
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: CoolcatOS by @zcsantiago | Stardance
|
1792677030.9895527
|
1793281830.9895527
|
|
19179
|
Cyberpunk Mantis arm prop by @zclayton2010 | Stard Cyberpunk Mantis arm prop by @zclayton2010 | Stardance...
|
zclayton2010
|
0
|
0.25
|
0
|
[]
|
[{"post_id": 10915, "ts": "202 [{"post_id": 10915, "ts": "2026-06-17T21:49:32Z", "hours": 0.2544, "text": "The CAD (onshape) and the Arduino code"}]...
|
Title: Cyberpunk Mantis arm prop by @zclayton2010 Title: Cyberpunk Mantis arm prop by @zclayton2010 | Stardance
Devlogs:
The CAD (onshape) and the Arduino code...
|
1792511691.057981
|
1793116491.057981
|
|
1615
|
a website!! by @zazzie | Stardance
|
zazzie
|
0
|
0.62
|
0
|
[]
|
[{"post_id": 311, "ts": "2026- [{"post_id": 311, "ts": "2026-06-01T16:02:27Z", "hours": 0.6158, "text": "I’ve never coded anything before, so this is my very first project :)"}]...
|
Title: a website!! by @zazzie | Stardance
Devlogs Title: a website!! by @zazzie | Stardance
Devlogs:
I’ve never coded anything before, so this is my very first project :)...
|
1792479039.5653863
|
1793083839.5653863
|
|
2216
|
Splatter paint website by @zazzie | Stardance
|
zazzie
|
2
|
10.0
|
112
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-30T21:42:07Z", "hours": 9.0, "multiplier": 12.74, "payout": 111, "blessing": "neutral", "text": "I made a website where you can splatter paint about! That’s it! & I’d say its pretty intuitive so there (hopefully) shouldn’t be much trouble for anyone testing it out! i hope you enjoy, and have fun splatting! :D", "repo": "https://github.com/zazzie-star/Splatter-Paint-Website-P2", "demo": "https://zazzie-star.github.io/Splatter-Paint-Website-P2/"}, {"ship_num": 2, "ts": "2026-06-01T19:31:59Z", "hours": 1.0, "multiplier": 1.03, "payout": 1, "blessing": "neutral", "text": "I made a splatter paint website (that’s it, sorry). I found the whole thing challenging really because I used a tutorial which is meant for Replit rather than Git (and I’m a total beginner). But i am proud that I did it, I’ve never really done this before today. All you need to do is to just swirl your mouse around, and that’s pretty much it!", "repo": "https://github.com/zazzie-star/Splatter-Paint-Website-P2", "demo": "https://zazzie-star.github.io/Splatter-Paint-Website-P2/"}]...
|
[{"post_id": 37887, "ts": "202 [{"post_id": 37887, "ts": "2026-07-30T21:33:31Z", "hours": 1.7878, "text": "this will be the last project update (at least for this ship, so lets get on with it!) project updates: finished readme added the final touches and finished what i wanted to finish thus far aims & issues: i had some issues implementing a button that made it so that when you click then it paints, and unfortunately had to scrap this for now really the biggest issue i found throughout this project is that I struggled using paper.js as it meant i had to code in a (i believe) unconventional way, and I don’t even know yet how to code in a conventional way so it was more of a struggle and I had to look to ai rather than regular tutorials which I’d prefer hopefully in future when i have the skills I can return to this project for a final ship and improve it, but for now I’m happy with what i’ve managed to achieve as a newbie and I’d like to move on to other projects that are more feasible and I can learn from more! p.s. if you’ve made it this far, thank you for following along! (and please let me know if I’ve made too many or too few devlogs)"}, {"post_id": 28597, "ts": "2026-07-14T22:53:48Z", "hours": 1.2258, "text": "short devlog today as I’m visiting my uni town for a uni event! (yippiee!! but very busy…) anyways! onwards with the updates project updates: now the clear canvas button works! it brings up a div saying “are you sure you want to clear canvas?” with yes and no buttons! though i had to ask the in built ai to explain to me how to code the clear canvas part as I am still very much a beginner lol currently working on the settings part! aims & issues: meh honestly nothing because i haven’t had the chance to do much today! OH i might make a back to menu button though, and try and make it so that saved works appear in the gallery…"}, {"post_id": 27950, "ts": "2026-07-13T21:52:32Z", "hours": 1.5056, "text": "project updates: changed ‘previous works’ to gallery (felt fitting) added a ‘save work’ button and a ‘clear canvas’ button the ‘save work’ button now works! i had to ask vs code’s in-built ai how to make it work (as i couldn’t find any tutorials!) and then wrote the code out & asked it to explain what each bit did so I could learn from it, I also made a note of things i learnt for future reference! not sure if i added this in an update but i learned how to make notes on all my code and have been using that as I’ve found it really helpful for learning & keeping track of my work the gallery button also now pulls up a gallery div! issues & aims: no real issues so far - I’m not sure how I’m going to make the gallery display your previous artwork, maybe I could have it so you input your own work and each one has a little frame and you can scroll through? also not sure how i’ll clear the canvas or make a proper settings so I will have to hunt for some tutorials or ask for advice again 😅 thats all so far!"}, {"post_id": 27113, "ts": "2026-07-12T11:47:11Z", "hours": 2.0072, "text": "project updates: the “new work” button now works! (clears the welcome screen so you can start working) the “settings” button now brings up a “settings” div added “Welcome to Splatter Paint!” to the start menu issues & aims: had some issues I had to troubleshoot (like a stray /div causing issues!) but so far we are doing good aiming to create a X button on the settings thinking of adding an Easter egg to the welcome screen… (you’ll have to see ;) ) hoping to create a “save” button also!"}, {"post_id": 26636, "ts": "2026-07-11T15:56:15Z", "hours": 1.2464, "text": "project updates: finally added the buttons, and used css to make them look gooooood they are yet to be functional though! issues & aims: had some issues putting the buttons in the centre of the screen! aiming to make these buttons actually work hopefully I can make a way to save artworks and maybe a settings screen!"}, {"post_id": 26545, "ts": "2026-07-11T12:56:42Z", "hours": 1.0569, "text": "working on the splatter paint website again! project updates: went back to the original jam tutorial and realised how much I messed up on my first ship! (oh well…), now I’m starting work on this again with just a little bit more knowledge so hopefully I can improve what i’ve done! issues & aims: no real issues thus far! aiming to make a start screen, (with a blurry background, like the one you can see here!) hopefully this will have a “welcome to splatter paint!” with start buttons/new work and a ‘previous artworks’ where you can click and it takes you to your previous works I guess I’ll need a save button as well so that people can save their art! and hopefully I can alter it so that it only draws when you click? (or make a settings so that you can select ‘on click’ as when it draws?)"}, {"post_id": 392, "ts": "2026-06-01T19:24:13Z", "hours": 0.6244, "text": "splat paint final"}, {"post_id": 361, "ts": "2026-06-01T18:08:22Z", "hours": 0.6881, "text": "a splatter paint website"}]...
|
Title: Splatter paint website by @zazzie | Stardan Title: Splatter paint website by @zazzie | Stardance
Devlogs:
a splatter paint website
splat paint final
working on the splatter paint website again! project updates: went back to the original jam tutorial and realised how much I messed up on my first ship! (oh well…), now I’m starting work on this again with just a little bit more knowledge so hopefully I can improve what i’ve done! issues & aims: no real issues thus far! aiming to make a start screen, (with a blurry background, like the one you can see here!) hopefully this will have a “welcome to splatter paint!” with start buttons/new work and a ‘previous artworks’ where you can click and it takes you to your previous works I guess I’ll need a save button as well so that people can save their art! and hopefully I can alter it so that it only draws when you click? (or make a settings so that you can select ‘on click’ as when it draws?)
project updates: finally added the buttons, and used css to make them look gooooood they are yet to be functional though! issues & aims: had some issues putting the buttons in the centre of the screen! aiming to make these buttons actually work hopefully I can make a way to save artworks and maybe a settings screen!
project updates: the “new work” button now works! (clears the welcome screen so you can start working) the “settings” button now brings up a “settings” div added “Welcome to Splatter Paint!” to the start menu issues & aims: had some issues I had to troubleshoot (like a stray /div causing issues!) but so far we are doing good aiming to create a X button on the settings thinking of adding an Easter egg to the welcome screen… (you’ll have to see ;) ) hoping to create a “save” button also!
project updates: changed ‘previous works’ to gallery (felt fitting) added a ‘save work’ button and a ‘clear canvas’ button the ‘save work’ button now works! i had to ask vs code’s in-built ai how to make it work (as i couldn’t find any tutorials!) and then wrote the code out & asked it to explain what each bit did so I could learn from it, I also made a note of things i learnt for future reference! not sure if i added this in an update but i learned how to make notes on all my code and have been using that as I’ve found it really helpful for learning & keeping track of my work the gallery button also now pulls up a gallery div! issues & aims: no real issues so far - I’m not sure how I’m going to make the gallery display your previous artwork, maybe I could have it so you input your own work and each one has a little frame and you can scroll through? also not sure how i’ll clear the canvas or make a proper settings so I will have to hunt for some tutorials or ask for advice again 😅 thats all so far!
short devlog today as I’m visiting my uni town for a uni event! (yippiee!! but very busy…) anyways! onwards with the updates project updates: now the clear canvas button works! it brings up a div saying “are you sure you want to clear canvas?” with yes and no buttons! though i had to ask the in built ai to explain to me how to code the clear canvas part as I am still very much a beginner lol currently working on the settings part! aims & issues: meh honestly nothing because i haven’t had the chance to do much today! OH i might make a back to menu button though, and try and make it so that saved works appear in the gallery…
this will be the last project update (at least for this ship, so lets get on with it!) project updates: finished readme added the final touches and finished what i wanted to finish thus far aims & issues: i had some issues implementing a button that made it so that when you click then it paints, and unfortunately had to scrap this for now really the biggest issue i found throughout this project is that I struggled using paper.js as it meant i had to code in a (i believe) unconventional way, and I don’t even know yet how to code in a conventional way so it was more of a struggle and I had to look to ai rather than regular tutorials which I’d prefer hopefully in future when i have the skills I can return to this project for a final ship and improve it, but for now I’m happy with what i’ve managed to achieve as a newbie and I’d like to move on to other projects that are more feasible and I can learn from more! p.s. if you’ve made it this far, thank you for following along! (and please let me know if I’ve made too many or too few devlogs)
Ships:
I made a splatter paint website (that’s it, sorry). I found the whole thing challenging really because I used a tutorial which is meant for Replit rather than Git (and I’m a total beginner). But i am proud that I did it, I’ve never really done this before today. All you need to do is to just swirl your mouse around, and that’s pretty much it!
I made a website where you can splatter paint about! That’s it! & I’d say its pretty intuitive so there (hopefully) shouldn’t be much trouble for anyone testing it out! i hope you enjoy, and have fun splatting! :D...
|
1792990185.3737454
|
1793076585.3737454
|
|
2627
|
Zazzpad! by @zazzie | Stardance
|
zazzie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Zazzpad! by @zazzie | Stardance
|
1792514902.917435
|
1793119702.917435
|
|
2686
|
. by @zazzie | Stardance
|
zazzie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: . by @zazzie | Stardance
|
1792889411.716442
|
1793753411.716442
|
|
4675
|
My first slack bot! by @zazzie | Stardance
|
zazzie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @zazzie | Stardance
|
1792954089.662272
|
1793818089.662272
|
|
18731
|
The ISS-WebOS! by @zazzie | Stardance
|
zazzie
|
0
|
7.28
|
0
|
[]
|
[{"post_id": 26231, "ts": "202 [{"post_id": 26231, "ts": "2026-07-10T21:59:23Z", "hours": 1.9908, "text": "project updates: things are not going well. i went on a tangent trying to figure out how to make it so that my windows don’t go off screen, only to realise that my background image wouldn’t work as a good frame of reference (as part of its off-screen) and that i just simply don’t know what i’m doing enough to figure it out, even with explanations online there was, at one point in time, a sweet, sweet window where my first app icon worked as did the windows. that point in time died immediately. I have no clue what I’m doing wrong because I don’t know what I’m doing and I’m trying to piece it together as best as I can. for now, i’ve managed to get my icon to appear on-screen but it no longer brings up a window so…. these updates are more issues and aims so apologies for that also GOOD NEWS: yayy, the bright side! yay! the window now drags reaaaaal smooth and not every time you move your mouse mistakes are a learning opportunity?"}, {"post_id": 25022, "ts": "2026-07-08T23:03:48Z", "hours": 1.1439, "text": "project updates: added open and close buttons (that work!!) the welcome window now fits totally and appears in the same orientation always (no warping when dragging or appearing in a different layout) issues & aims: the window appears almost off the side of the screen when you load it in… dragging not SUPER smooth hoping to make more and potentially ‘apps’!"}, {"post_id": 24980, "ts": "2026-07-08T21:25:37Z", "hours": 1.3542, "text": "made the iss-os a draggable welcome window! hoping to add a typical bar/x to leave. struggling to wrap my head around js, but I think I have some idea how i’ve managed this! hoping that i can make it drag smoother, plust not go off the sides of the website or distort in shape…"}, {"post_id": 24920, "ts": "2026-07-08T19:52:05Z", "hours": 1.4161, "text": "continuing to slog on with the Web0S, added a custom background I drew & made a bottom bar with an updating time. I’ve also (mostly) fixed the sizing’s so that the background fits. still working on the window & bottom bar, hoping I can add icons soon :D"}, {"post_id": 21043, "ts": "2026-07-02T20:19:32Z", "hours": 1.3758, "text": "Just started work on my Web0S for this mission (and have unfortunately only just realised by looking at other people’s projects that it is not supposed to look like a personal website, so it’ll need a lot of tweaks!) Thus far I’ve added some basic info on the ISS in the hopes that my WebOS will be customised to this (i.e. you can have a window up showing a picture of the ISS/space facts - though I’m really hoping I can put in my own tracker and/or expedition countdowns). I’ve got very little so far, but big plans up ahead- so stay tuned! :D"}]...
|
Title: The ISS-WebOS! by @zazzie | Stardance
Devl Title: The ISS-WebOS! by @zazzie | Stardance
Devlogs:
Just started work on my Web0S for this mission (and have unfortunately only just realised by looking at other people’s projects that it is not supposed to look like a personal website, so it’ll need a lot of tweaks!) Thus far I’ve added some basic info on the ISS in the hopes that my WebOS will be customised to this (i.e. you can have a window up showing a picture of the ISS/space facts - though I’m really hoping I can put in my own tracker and/or expedition countdowns). I’ve got very little so far, but big plans up ahead- so stay tuned! :D
continuing to slog on with the Web0S, added a custom background I drew & made a bottom bar with an updating time. I’ve also (mostly) fixed the sizing’s so that the background fits. still working on the window & bottom bar, hoping I can add icons soon :D
made the iss-os a draggable welcome window! hoping to add a typical bar/x to leave. struggling to wrap my head around js, but I think I have some idea how i’ve managed this! hoping that i can make it drag smoother, plust not go off the sides of the website or distort in shape…
project updates: added open and close buttons (that work!!) the welcome window now fits totally and appears in the same orientation always (no warping when dragging or appearing in a different layout) issues & aims: the window appears almost off the side of the screen when you load it in… dragging not SUPER smooth hoping to make more and potentially ‘apps’!
project updates: things are not going well. i went on a tangent trying to figure out how to make it so that my windows don’t go off screen, only to realise that my background image wouldn’t work as a good frame of reference (as part of its off-screen) and that i just simply don’t know what i’m doing enough to figure it out, even with explanations online there was, at one point in time, a sweet, sweet window where my first app icon worked as did the windows. that point in time died immediately. I have no clue what I’m doing wrong because I don’t know what I’m doing and I’m trying to piece it together as best as I can. for now, i’ve managed to get my icon to appear on-screen but it no longer brings up a window so…. these updates are more issues and aims so apologies for that also GOOD NEWS: yayy, the bright side! yay! the window now drags reaaaaal smooth and not every time you move your mouse mistakes are a learning opportunity?...
|
1792562050.605099
|
1793166850.605099
|
|
47016
|
Opportunities For All by @zazzie | Stardance
|
zazzie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Opportunities For All by @zazzie | Stardanc Title: Opportunities For All by @zazzie | Stardance...
|
1792497228.9836836
|
1793102028.9836836
|
|
53281
|
My awesome macropad! by @zazaansh | Stardance
|
zazaansh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zazaansh | Stardan Title: My awesome macropad! by @zazaansh | Stardance...
|
1792741980.8318121
|
1793346780.8318121
|
|
32548
|
My own site! by @zayzaygamer007 | Stardance
|
zayzaygamer007
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @zayzaygamer007 | Stardance
|
1792547482.9177241
|
1793152282.9177241
|
|
45619
|
My awesome macropad! by @zaynaster | Stardance
|
zaynaster
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zaynaster | Starda Title: My awesome macropad! by @zaynaster | Stardance...
|
1792630277.5350857
|
1793235077.5350857
|
|
9003
|
My first slack bot! by @zayd_ashfer | Stardance
|
zayd_ashfer
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @zayd_ashfer | Stard Title: My first slack bot! by @zayd_ashfer | Stardance...
|
1792626520.0216124
|
1793231320.0216124
|
|
5083
|
My personal portfolio by @zayalan | Stardance
|
zayalan
|
1
|
7.0
|
12
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-09T14:45:59Z", "hours": 7.0, "multiplier": 1.83, "payout": 12, "blessing": "neutral", "text": "I made a personal website for myself. It is my first software project so it was so Challenging. I used html and css for making this.", "repo": "https://github.com/sasukeop108/sasukeop108.github.io", "demo": "https://sasukeop108.github.io/"}]...
|
[{"post_id": 5629, "ts": "2026 [{"post_id": 5629, "ts": "2026-06-09T14:38:11Z", "hours": 5.4781, "text": "Today, I started css part of my website. First, I started from the projects part in my website. Then, I did the about me and contact me part and finally added some more features like hover etc. After that, I pushed the files from vs code to the github repo and i deployed github pages for hosting this. As a beginner idk how i even took 5 hours sob. Anyways i got it working after a lot of struggles."}, {"post_id": 3676, "ts": "2026-06-06T18:44:03Z", "hours": 1.1253, "text": "Today, I worked on most of the html part of my personal portfolio. As im an ultimate beginner with vs code and html it took me longer than which i expected."}]...
|
Title: My personal portfolio by @zayalan | Stardan Title: My personal portfolio by @zayalan | Stardance
Devlogs:
Today, I worked on most of the html part of my personal portfolio. As im an ultimate beginner with vs code and html it took me longer than which i expected.
Today, I started css part of my website. First, I started from the projects part in my website. Then, I did the about me and contact me part and finally added some more features like hover etc. After that, I pushed the files from vs code to the github repo and i deployed github pages for hosting this. As a beginner idk how i even took 5 hours sob. Anyways i got it working after a lot of struggles.
Ships:
I made a personal website for myself. It is my first software project so it was so Challenging. I used html and css for making this....
|
1792979256.9343314
|
1793065656.9343314
|
|
26304
|
My very own WebOS by @zayalan | Stardance
|
zayalan
|
1
|
10.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-28T11:47:08Z", "hours": 10.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "This is the first version of ZayalanOS. It has a calculator and a currency converter It is made using dan da dan theme.", "repo": "https://github.com/sasukeop108/ZayalanOS", "demo": "https://zayalan-os.vercel.app/"}]...
|
[{"post_id": 17548, "ts": "202 [{"post_id": 17548, "ts": "2026-06-28T11:39:49Z", "hours": 2.7153, "text": "Today, I worked on styling the currency converter and i completed the project in whole. I deployed it on vercel."}, {"post_id": 17013, "ts": "2026-06-27T16:48:55Z", "hours": 5.7267, "text": "Today, I worked on making the welcome screen movable, added calculator and aligned the icons at the bottom."}, {"post_id": 16245, "ts": "2026-06-26T11:53:24Z", "hours": 0.7097, "text": "I worked on the top menu bar,background image and i centered the welcome box."}, {"post_id": 16209, "ts": "2026-06-26T10:36:11Z", "hours": 0.6044, "text": "Today, I wanted to start making some more software project so i came upon making a webos. I saw the guides and i completed the welcome screen of my webos."}]...
|
Title: My very own WebOS by @zayalan | Stardance
Title: My very own WebOS by @zayalan | Stardance
Devlogs:
Today, I wanted to start making some more software project so i came upon making a webos. I saw the guides and i completed the welcome screen of my webos.
I worked on the top menu bar,background image and i centered the welcome box.
Today, I worked on making the welcome screen movable, added calculator and aligned the icons at the bottom.
Today, I worked on styling the currency converter and i completed the project in whole. I deployed it on vercel.
Ships:
This is the first version of ZayalanOS. It has a calculator and a currency converter It is made using dan da dan theme....
|
1792990148.773444
|
1793076548.773444
|
|
30365
|
Untitled by @zayalan | Stardance
|
zayalan
|
0
|
6.64
|
0
|
[]
|
[{"post_id": 27742, "ts": "202 [{"post_id": 27742, "ts": "2026-07-13T15:51:25Z", "hours": 0.8886, "text": "Today, i worked on grouping the parts together. I grouped all parts together and i will be doing its layout and routing tommorow."}, {"post_id": 27135, "ts": "2026-07-12T12:43:30Z", "hours": 1.7806, "text": "Today, I started checking the schematics for errors, fixing them and arranging them neatly. Then, I assigned footprints to all components using the help of gemini. Lasty i imported the components to pcb editor."}, {"post_id": 22775, "ts": "2026-07-05T11:14:38Z", "hours": 2.2003, "text": "Today, i worked on completing the schematic by adding the e-ink display,sd card slot and pcm50102a. the schematic is 90 % complete and needs connection of pcm50102a with esp32 s3 and organization of schematics. Thanks!"}, {"post_id": 22295, "ts": "2026-07-04T18:03:58Z", "hours": 1.4333, "text": "I worked on the usb serial programming part and on the battery charger, ldo and usb receptacle."}, {"post_id": 22194, "ts": "2026-07-04T15:18:05Z", "hours": 0.3367, "text": "Today, i did some research about making an mp3 player and i started working on the usb and esp32 s3 part of it."}]...
|
Title: Untitled by @zayalan | Stardance
Devlogs:
Title: Untitled by @zayalan | Stardance
Devlogs:
Today, i did some research about making an mp3 player and i started working on the usb and esp32 s3 part of it.
I worked on the usb serial programming part and on the battery charger, ldo and usb receptacle.
Today, i worked on completing the schematic by adding the e-ink display,sd card slot and pcm50102a. the schematic is 90 % complete and needs connection of pcm50102a with esp32 s3 and organization of schematics. Thanks!
Today, I started checking the schematics for errors, fixing them and arranging them neatly. Then, I assigned footprints to all components using the help of gemini. Lasty i imported the components to pcb editor.
Today, i worked on grouping the parts together. I grouped all parts together and i will be doing its layout and routing tommorow....
|
1792882225.9099836
|
1793746225.9099836
|
|
56256
|
weirdalarmthingy by @zayalan | Stardance
|
zayalan
|
0
|
1.3
|
0
|
[]
|
[{"post_id": 60971, "ts": "202 [{"post_id": 60971, "ts": "2026-09-03T17:31:29Z", "hours": 0.6806, "text": "I worked on the pcb a bit by the help of the guide, currently im stuck with 3d model assigning for switches as it is acting out weird"}, {"post_id": 58991, "ts": "2026-08-31T15:54:07Z", "hours": 0.3333, "text": "Today, I started working on the pcb part of the alarm. I followed the tutorial and routed all the stuff"}, {"post_id": 58082, "ts": "2026-08-30T13:09:33Z", "hours": 0.2833, "text": "Today, I started making my blare mission project. I started placing components at first, Then wiring and finally i assigned footprints to these components"}]...
|
Title: weirdalarmthingy by @zayalan | Stardance
D Title: weirdalarmthingy by @zayalan | Stardance
Devlogs:
Today, I started making my blare mission project. I started placing components at first, Then wiring and finally i assigned footprints to these components
Today, I started working on the pcb part of the alarm. I followed the tutorial and routed all the stuff
I worked on the pcb a bit by the help of the guide, currently im stuck with 3d model assigning for switches as it is acting out weird...
|
1792655503.5287557
|
1793260303.5287557
|
|
56380
|
Zayalan bot thingy by @zayalan | Stardance
|
zayalan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Zayalan bot thingy by @zayalan | Stardance
|
1792659278.3935568
|
1793264078.3935568
|
|
59493
|
personal site by @zayalan | Stardance
|
zayalan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: personal site by @zayalan | Stardance
|
1792799616.9091651
|
1793404416.9091651
|
|
61074
|
Hackpad thingy by @zayalan | Stardance
|
zayalan
|
0
|
1.34
|
0
|
[]
|
[{"post_id": 69244, "ts": "202 [{"post_id": 69244, "ts": "2026-09-16T17:31:00Z", "hours": 0.6667, "text": "after completing the schematic, i assigned footprints to the components. Next did a layout but the switces and diodes were mismatched so i did another layout and routed some of routing."}, {"post_id": 67533, "ts": "2026-09-13T17:35:21Z", "hours": 0.3, "text": "Today, i added neopixel leds in the schematic. I then assigned footprints and imported the components in pcb editor."}, {"post_id": 66727, "ts": "2026-09-12T16:53:01Z", "hours": 0.3778, "text": "I started off by adding the xiao rp2040 and i eventually completed the schematic of my hackpad."}]...
|
Title: Hackpad thingy by @zayalan | Stardance
Dev Title: Hackpad thingy by @zayalan | Stardance
Devlogs:
I started off by adding the xiao rp2040 and i eventually completed the schematic of my hackpad.
Today, i added neopixel leds in the schematic. I then assigned footprints and imported the components in pcb editor.
after completing the schematic, i assigned footprints to the components. Next did a layout but the switces and diodes were mismatched so i did another layout and routed some of routing....
|
1792432038.8626614
|
1793036838.8626614
|
|
32616
|
Spectra-05 by @zayaan | Stardance
|
zayaan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Spectra-05 by @zayaan | Stardance
|
1792572764.217056
|
1793177564.217056
|
|
8036
|
My awesome macropad! by @zaxthu | Stardance
|
zaxthu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @zaxthu | Stardance
|
1792803263.4517071
|
1793408063.4517071
|