august

Another hour-ish of work, i decided to write a parser re-vamp, it’s like 2000 lines, but I grabbed some of the code from existing tests and demos of software I never ended up using. I had some issues with the code selecting content unrelated to the assignments (i.e. Posted on dates and stuff). At least with schoology at least, but I don’t actively use a different LMS, so that’s all I can test it on. Since it worked on every real world test I gave it, so I marked it as 1.0.0. I’m still waiting for the re-certification of the extension by the chrome web team, but I expect it’ll be done by the end of spring break. Although it seems there are some unintentional things logged (the “comments” in the notes bit)

Inital setup. Everything mostly works, however I do have some eventual ideas for improvements. I want to add more clear bill viewing, and other features. I do plan on maintaining this, I think the idea is to create more easy setup options if I do add more preset modes for different competition types, e.g. UIL.

Currently the features are:

• Bill Dockets (Bill ID, Caption, Author Name, Status)
• Chambers & Chamber Statuses
• Staff Portal for management (fine grained permissions)
• Clerk Authentication
• Admin Panel

I do plan to add more features at a later date, but for now this is a good start. Below is the stack:

• Next 16+
• React 19
• Drizzle ORM
• CockroachDB (Generous free limits)
• Clerk Authentication (Generous free limits, and high MAU value for larger conferences)

Finished out the extension. Wanted to wait until the approval was granted by the web store team before pushing out a devlog. What we have so far:

1. Capture for certain sites (I plan on adding more)
2. Options for instance use (Main prod site or local development instance)

All in all, a relatively simple project, but a more complicated learning experience when it comes to figuring out how to make a manifest V3 compatible extension.

Minor updates to performance !!

1. Updated next.js config options to decrease build times
2. Implemented a small caching strategy for the fundamentals (tasks, calendar, time tracking, RSS).

I swear. No matter how good my code looks, or how much people tell me too. I will never be good at remembering to commit my changes in small batches rather than like 80 changes at a time. Anyway, moving on. Since I have no idea what came between this devlog, and the last one, I’ll do a round up of the changes made on this commit.

1. Bug fixes. Holy bug fixes. I can’t even count on my fingers and toes how many mistakes I made. Speaking of can I borrow your fingers real fast /silly
2. RSS Video/Audio displays. Because some of us (cough cough nbc cough cough, can’t just link their videos to their articles)
3. Extensions, because it should have been finished already but I guess I forgot
4. Google calendar integration, once I get my google account to process the payment for my chrome extension developer fee.
5. Polychrome task catcher (separate project, that links to polychrome to capture assignment due dates and stuff from schoology, and eventually other stuff.)
6. Task API (to make the chrome extension work)
7. Notifications (The backend bit). Because I HATED that red dot, and needed a backend
   7.1. Notification page. To manage them,,, (Mark them as done and stuff)
8. Build fixes. Kinda part of bug fixes, but just some small stuff about impure functions.
9. Package updates. Because next can’t get enough of yellow stale version dots.
10. Updates to deployment configs for vercel and netlify. (And there goes my sleep. Holy docs)

Misc Notices: The calendar was re-used from an old project, and the chrome extension isn’t in the time tracked for this devlog. (That’s what I’ve been working on for a few days, I will get to making a project listing for it at some point).

P.S. the silly thing is a tone tag, it’s similar to /j which just means joking.
P.P.S. hope you appreciate the new devlog style,,, I’m just far too tired to write all formal,,,

Three hours of plentiful work! I got a lot of things working, and a start on the UI, although that could take some time. I got the main features working, although some bug testing is definitely required. What I got so far:

1. Time tracking
2. A copy paste of a calendar thing I tried, but never used
3. RSS feed stuff
4. Tasks
5. Backend setup stuff
6. An ok looking UI

I don’t think I can ever express how nice it is having icon libraries,,

Gotta get in the before school work right? So as it turns out twenty six minutes is enough time to get the basics set up. So I’ve decided to use Next.js, shadcn/UI for components, and bun for my runtime. I used the bootstrap command for next.

Made some bug fixes, migrated to next 16, and used my script to fetch icons for fluids.

Added some more tests, and made the github repo!

I’ve made a lot of progress over the last few days, and here is what I did today:

• Made a worker to handle factory calculations
• Added a small test suite
• Added byproduct management
• Added icons to items
• Fixed bugs
• And much more

I’ve been using it to make a factory, and it works quite well.

Major work today, I fixed up the factory planning system, added snakey, keybinds, and more features. I am notably still missing byproduct output and management in the factory planner though.

Written on: 1/2/2025

Initialization, and speedy work, although it should have logged more time, I think I stopped the extension on accident, but, it’s fine, an hour is still good work done. Everything works, but I do have some next.js errors for not awaiting params for page ids, but it doesn’t stop the app from working.

Took a while, but finally, I fixed some major bugs to hopefully get a majority of the system working properly. There are definitely some things that need to be improved, but it works!

All of the packages now have documentation!

In my opinion, everything is at a good point to officially “ship” them, or I suppose make them production ready. Although they could use some more features in the future.

Finally!

We now have all the packages published, and a github actions workflow to do the publishing,, this is great.

Welcome to the conference kit devlogs!

Added vue integration & “room” support (multiple people in a call)

I started working on this not too long ago so I didn’t have to subscribe to a SaSS service to use video/audio conferencing. Here is what I have so far:

1. A working webRTC data transmission stream
2. Audio and Video Toggles (Allowing for AV (audio video), Just Audio, Just Video, or Just Data.
3. A flexible set of packages for integration and custom UI design (hooks, components, etc.)
4. Native support for Next.js, and React

Plans for future features:

1. Room support (multiple people at once)
2. Pre-made UI’s
3. More framework integration
4. Better Chat UI
5. Better meeting controls