be my guest! fyi i have some queued up that i’m gonna make, those being
Neural Networks
Animation
SciSnap! V3
Metaprogramming
List Utilities
Iteration, composition
Bignums, rationals, complex #s
Catch Errors
Database
so i can handle these ones.
also, if you need help polishing yours afterwards to better fit the Scratch style if you think something is off, i’d be happy to fix it for you!
ohh wait, are you essentially making concept art for me to use as reference when making some of the banners? if so, then that’s perfectly fine!
if you’re just showing off a basic version of what you are planning to make, then that’s also perfect! i just need to know so I don’t accidentally skip over any banners if the first case is true
I suggest that the banner has more than that. {OOP} is not really a proper object in most cases. Maybe an object with more utility like {"number": 42, "website": "Split!"} as a banner represents the library better. The point of the banner is to capture the idea visually. Leave the simple for the icon.
also, @d016, i’m thinking about making the banner developments a separate topic, as to not clutter the main topic with purely banner-related posts. though that’d make more clutter on the forum itself and could be seen as redundant… i’ll just get feedback from you guys on if i should do it or not!
Showing blocks can help with users knowing what the library looks like before even importing it.
Looks almost good. I agree with @bh that the example font just needs to be changed to preferably serif to demonstrate the font support of the library better.
The arrows sorta look like a repost icon. I think it’d be better to have the loop arrow ⬏ by itself, and then maybe a two-arrows-with-same-tail symbol like the one that means “share” on phones. (I can’t find it in Unicode.) Oh sort of like this: ≺ only with arrowheads.