I cancelled “Watchlist” and started over with “Watched”.
I hate how I’ve set the documentation system to look like. I use headers, they’re great, but function/struct documentation… it’s awful. So I’m thinking of some different style for these. I’d like to use “$” so that my documentation software would pick it up. We’ll see!
I’m working on an app that would keep track of what episodes I watched of YouTube/TV series.
It’s going oki. I’m just not really focused on it that much (or on the code part of things, at least).
I also figured out a good way to do headers & documentation comments. (finally)
/* ================================================================================** $Project: Watchlist** $Module: Logic* $File: application.h** $Purpose: Defines the application structure and its associated functions. The* application is responsible for managing the main loop and handling* application-wide resources.** $License: MIT* $Author: The Kumor** ================================================================================ */
/* ------------------------------------------------------------------------* $Name: wht_Text_Init** $Purpose: Initializes a text control with the specified parameters and* creates the control's window as a child of the specified parent control.* * $Parameters:* self: Pointer to the control to be initialized.* x: The x-coordinate of the control's position.* y: The y-coordinate of the control's position.* w: The width of the control.* h: The height of the control.* text: The text to be displayed in the control.* ------------------------------------------------------------------------ */voidwht_Text_Init(wht_Control* self, i32 x, i32 y, i32 w, i32 h, str text, wht_Control* parent);
/* ------------------------------------------------------------------------* $Name: wht_Window* * $Purpose: Window structure for encapsulating properties specific to a* window control, inheriting from the base control structure.* * $Members:* Control: The base control structure for the window,* containing common control properties.* ------------------------------------------------------------------------ */typedefstruct{ wht_Control Control;} wht_Window;
/* ------------------------------------------------------------------------* $Name: wht_Control* * $Purpose: Control structure for encapsulating common control properties.* ------------------------------------------------------------------------ */typedefstruct{ HWND m_Handle; i32 m_X, m_Y; str m_Text;} wht_Control;
Before I make some structs opaque, I’ll leave these variables with m_ prefixes available. But they’re not considered in headers.
I’ll create a documentation software that would parse these comments and C/C++/Lua/etc code and produce a searchable database of things. It’ll also include “sections” ($Section) blocks. But that’s a different project, and isn’t my immediate focus (perhaps late April?)
I figured out IntelliSense at least doesn’t break with these. And as for Visual Studio Code, it even picks up $Parameters section and makes this particular line bigger.
Visual Studio 2022’s autofill / AI is writing 50% of these comments. I also do readmes based on project reports which are partially generated by AI (I mean, 28 pages is a lot of manual labor!). But projects themselves are written fully by me, with help of the autofill for mundane tasks. I’m kind of scared people will look at these projects and be like “lol, that readme’s made by chatgpt” and assume project wasn’t done by a human. But I try not to care. People will say what they want, and in the end, I write code by myself.
Application consists of field and side menu. In the side menu, user chooses a vegetable/fruit to plant. Each plant has an image and name associated with them. Polish and English being the supported languages. Once planted, field recalculates an area trying to find if plants around like it.
I managed to render it inside a WinAPI app. It’s a quick one, just to test for the actual application, which is Garden. You can check out the test app here.
I’ve decided this will be Garden’s application icon
This is the best I can do lol.
So, next thing I have to do is make actual button rendering, embed Lua and I guess that’s it for now? I also have to find some good resources on vegetable neighborhood. That’s crucial.
I’ve been coding this for a while, but as I said, I didn’t have much free time for these things. Now it’s changed.
This project is primarily for my mom. She wanted an easy way to manage creation of her garden. Mainly with regards to “what vegetables can be next to XYZ”. I’m thinking of using Lua for scripting in the vegetable types and their neighborhoods.
So far I created event system and basic field concept. They’ll have images on them and will flare up with particular color (red for bad neighborhood, orange for so-so, green for ok).
I’m not so much in a rush, but I want to finish this thing. Check it out on it’s repo.
I was thinking of making some video upload utility. Reasoning: I am an admin on a Garry’s Mod server. Once I run out of nitro, I’ll have to rely on third-party video sites to show evidence, in case it’s needed.
The name is a bit funny. I thought of UploadTool. That would run a subdomain or some subdirectory/service called KumorTube on my website. I thought of shortening the name to KumTube. I know what you’re thinking, but it’s really not THAT. I just happen to have a funny second name.
But I’d have to go through all these procedures I have when starting a new project and it’s tiring. I’ll think about this idea later.
Apparently, when a .html file’s extension is changed to .php (and it’s just plain HTML ) GitHub thinks it’s Hack (Hacklang?). Looks quite funny not gonna lie.