08-30-2025, 12:27 AM
I'm bringing this topic back up as again, it's something that I really think we all as a community need to work on/add too and agree on...that way we can all show our ideas, explain our reasonings and together make a standardised, uniform and collaborative set of extended libs for QB64 PE - All well documented, governed and agreed on...this will help in collaboration, teaching, enticing new users, expansion and allow us ALL to have our work accessible to everyone with ease..
i'd love to have a foundational lib that i'd built gdk on so it would just harmoniously fit with fzxngn (it's a new headache for me!), heck a vertex is vertex a triangle a triangle, a color a color etc...from input to databases, from sounds to visual effects and guis, game tools, and SO MUCH MORE (you've all made some really cool stuff!) so as they'll all work on very similar principles, lets just start FFS!
Sorry Steve, i agree with the rest of your comments but this is not possible...in creating a library you ENFORCE reserved names, functions etc....it's the concession i guess, to use it, you cant abuse it! As long as functions and type use a (group certified) prefix like i do with GDK and any other library i make, it's easily managed and any local variables in subs/functions can be __ or something...though whilst in dev everyone should be free to code as they want...with the idea that once an agreed level of function, naming and the code for a function is "agreed on", it''ll then be converted to fit the again agreed on rules for submision to the library.
Please jump in guys! There's something here for everyone to do! Testing, documenting, suggesting, creating, etc...
Unseen
i'd love to have a foundational lib that i'd built gdk on so it would just harmoniously fit with fzxngn (it's a new headache for me!), heck a vertex is vertex a triangle a triangle, a color a color etc...from input to databases, from sounds to visual effects and guis, game tools, and SO MUCH MORE (you've all made some really cool stuff!) so as they'll all work on very similar principles, lets just start FFS!
Quote:2) Code everything assuming that the other people will have different defaults than you.
Sorry Steve, i agree with the rest of your comments but this is not possible...in creating a library you ENFORCE reserved names, functions etc....it's the concession i guess, to use it, you cant abuse it! As long as functions and type use a (group certified) prefix like i do with GDK and any other library i make, it's easily managed and any local variables in subs/functions can be __ or something...though whilst in dev everyone should be free to code as they want...with the idea that once an agreed level of function, naming and the code for a function is "agreed on", it''ll then be converted to fit the again agreed on rules for submision to the library.
Please jump in guys! There's something here for everyone to do! Testing, documenting, suggesting, creating, etc...
Unseen