[IC] GMK CYL CPL | Major Kitting Update

[balance]

_____________________________________________________________________________________________________________________________________________________________________
/*
 * GMK CPL (C Programming Language) - Interest Check
 * Hello Geekhack! Today, I present you a set inspired by my beginning in the coding world. Every programmer starts with a certain language, mine was the C Language.
 * This set is a nod to syntax-highlighted code on a white background.
 * For lovers of clean syntax, logic, and elegance.
 * Discord Server
 * Interest Check Form
 */

#include <stdio.h>
#include <stdbool.h>

#define SET "GMK CPL"
#define MATERIAL "Double-shot ABS"
#define PROFILE "Cherry"
#define MAKER "GMK"

// Color Scheme
const char *colors[] = {
    "PANTONE 656 C (alphas)",
    "RAL 270 20 20 (legends)",
    "GMK TU2 / GMK AE / RAL 360 40 50 / PANTONE 927 C (mods/accents)"
};

// Kit Structure
struct Kit { const char *name; bool available; };
struct Kit kits[] = {
    { "Base Kit", true },
    { "Alt Mod Kit 1", true },
    { "Numpad", true },
    { "Spacebars", true }
};

// Kits
void print_kits() {
    puts("Kits:");
    for (int i = 0; i < 4; i++)
        printf(" - %s: %s\n", kits.name, kits.available ? "Yes" : "No");
}









//Board Renders
void print_renders(const char *a, const char *b, const char *c) {
    printf("Renders:\n  1. %s\n  2. %s\n  3. %s\n", a, b, c);
}



















// Interest Check Form
void interest_check() {
    puts("\n Interest Check Form");
    puts("Let me know if this set caught your eye! Vote in the IC form and spread the word.");
    puts("Your feedback helps shape the final product.");
}

// Discord Link
void join_discord() {
    puts("\n Join the Community");
    puts("Stay updated, ask questions, and share your thoughts on Discord:");
    puts("Discord Server");
}

// Main Output
int main() {
    printf("\n--- Interest Check: %s ---\n\n", SET);
    print_kits();
    puts("\nIf you're interested, leave a comment below!");
    puts("Feedback and suggestions are appreciated.\n");
    print_renders("TGR Alice", "TGR Jane", "Sunsetter");
    interest_check();
    join_discord();
    return 0;
}

[balance]

reserved

[Giorgey]

Been keeping an eye on your work and this set looks fantastic.

[LavenderB]

eh

[MartinThePolarBear]

I like the accent mod kit

[Randomlosername]

Very cool set.

[cartersrush]

I'd put the basics kit mods in the base kit.That would make the set more unique.
Replace the basics kit with an icon mods kit instead.
Add icon shifts in the accents kit.
Maybe consider WS32?
Though historically more ppl would be interested in a dark version.
Eg monokai , oblivion

[JQ27]

ISO Enters in Syntax Highlight Kit would be nice. Otherwise, a dead kit for ISO users.

[IOVERCALLHISTIOCYTES]

Balance I’m sure you’ve thought of this already: If the IC numbers are good but not 2021 GB level, putting the basics kit mods into the base kit defrays the new mold cost out over 250/500 MOQ vs a child kit where at 100 MOQ that’s gonna be a pricey child kit.

“Do you want the base kit to have the basics kit mods?” Might be a decent way to get data on your Ic form.

Can the numpad get an accent enter too? If that took making numlock the base colors instead id be alright w it. Shouldn’t go in syntax highlight and you’ve already got the reddish color in the kit anyways.

Carter had suggested WS32 and I kinda wanted CR black legends to take the highlight kit elsewhere, but your custom colors look nice and I suppose you should stick with em

[NihonCK]

I agree with the adjustment to kiting is required. Didn't you learn from Astraeus?

Would love to see this set come to being made, but you need to reconsider the state of the hobby right now, unless you have someone that's going to guarantee the buyout of all the kits to make production. This theme relies on the accents a lot from my perspective, base kit alone, I doubt it.

Also agree, adjust your choice for white, I don't want yellow'd keycaps after a few years of UV exposure I was thinking of something else

[IOVERCALLHISTIOCYTES]

Is Pantone 656c gonna yellow like ws2 did?

[rayy]

I'd put the basics kit mods in the base kit.That would make the set more unique.
Replace the basics kit with an icon mods kit instead.
Add icon shifts in the accents kit.
Maybe consider WS32?
Though historically more ppl would be interested in a dark version.
Eg monokai , oblivion

LET. HIM. COOK!

[konstantin]

Is it just me or does Const Long, Sscanf, Eof etc. in camel case feel super wrong?
Also, it's a bit odd to see Breakpoint, Type, Arr, String included as novelty mod legends, yet no Struct, Return, Void, Unsigned or other actual C keywords. A K&R reference somewhere would be nice to see too.

I agree with what others have said about moving the C novelty mods to the base kit and making them the main feature of the set. With the current market, I don't think this set is likely to hit MOQ if it's this split up.

I think the pink accented Enter doesn't look very good next to the accented Shifts. I suggest dropping that key, or swapping it with a green Enter.
I also think you can drop the green-legend `~, \| keys from base, as the difference in legend color between them and the default keys is barely noticeable. Further, Tab and Backspace legends are already green, so again you have the same accent color on two adjacent rows, which isn't great.

Show Image

FYI, some keys in the Basics kit are currently labeled with the wrong rows:

• 1.5u Type, 2u (mislabeled as 1.75u) Breakpoint should be R2;
• 1.5u Break, 1.75u Breakpoint should be R2;
• 1.75u Const Long, 1.75u Continue, 1.25u Type, 1.5u Print should be R3;
• ISO Printf should span rows R2–R3.

Show Image

If you don't end up merging the numpad kit into base, you could add a R1 1u = key to it.

[Livid]

Is it just me or does Const Long, Sscanf, Eof etc. in camel case feel super wrong?

You mean Pascal case? Either way, it's not like there's a convention, it's usually up to a team or company's style guide if anything at all. I do agree though that capitalizing functions especially is NOT something you would see in C code.

[balance]

Update 1 ();

{
    printf("Merged the basics kit with the Main Function kit/ Added Struct and Void in the base kit as mods / Added a C keycap instead of a B for Alice-like boards/ Removed the green ~, \| keys from base");
    printf("Added accented ISO in the Syntax Highlight Kit / Removed Pink Esc and Enter keycap");
    printf("Added accented Enter and 1u =  in the Constants Kit/ ");
}

[SxM Designs]

I dont get the capitalized/camel case mods.. It just looks wrong to anyone who has programmed a single line in c
If you are doing new molds, please consider small lettered mods.

[Livid]

Added a C keycap instead of a B for Alice-like boards

This is a really odd choice

I dont get the capitalized/camel case mods..

Why are you the second person that thinks it's camel case if anything it's Pascal case, but on second thought both of them only even apply to multi-word names, so it's actually neither. Just a strange design choice that I also disagree with for the record

[konstantin]

You mean Pascal case? Either way, it's not like there's a convention, it's usually up to a team or company's style guide if anything at all. I do agree though that capitalizing functions especially is NOT something you would see in C code.

Why are you the second person that thinks it's camel case if anything it's Pascal case, but on second thought both of them only even apply to multi-word names, so it's actually neither. Just a strange design choice that I also disagree with for the record

It is camel case, specifically UpperCamelCase (as opposed to lowerCamelCase). I consciously use and prefer those terms over Pascal case (which I haven't used professionally in years, and probably not since uni).

That aside, the casing for (most of) these words isn't really up to convention because they're reserved C keywords or identifiers, so they wouldn't compile unless spelled exactly. However, I guess it's an alright concession to make in order to fit the typical GMK aesthetic. GMK does have lowercase text mods available, though (e.g. GMK Hennessey), so that may be something worth considering for this set:

More

[tactilesbad]

at least this is a bit less froyo

[Livid]

It is camel case, specifically UpperCamelCase (as opposed to lowerCamelCase).

That's a nickname at best besides if UpperCamelCase is an entirely distinct naming convention then my point stands that what is used here is veritably not "camel case"

That aside, the casing for (most of) these words isn't really up to convention because they're reserved C keywords or identifiers

I'm aware & agree, was just speaking generally. Honestly didn't look close enough to realize every "novelty" included is a reserved name, guess that makes sense though to keep to the theme