Code block presets?
-
Creaticode should have a presets area on the tabs section with presets for both 2d and 3d
My idea is that CreatiCode will have block presets like: 2D movement, 3D movement, AI Chat block presets, and so on
@jd131111 this would be like a public backpack with verification to submit to it
<div component="post/signature" data-uid="255" class="post-signature">Check out my chat room project so you ppl can not use forums as chat rooms! https://play.creaticode.com/projects/66f2e1dcd1be43d82b886fbd?version=1 <p dir="auto">
</div> -
We do have some forum moderators (volunteers), who are doing a great job spotting issues in new posts. Of course, if you see any issues, please feel free to report them as well.
@info-creaticode said in Code block presets?:
We do have some forum moderators (volunteers), who are doing a great job spotting issues in new posts. Of course, if you see any issues, please feel free to report them as well.
Thank you
-
Yes, it is similar to a backpack thatâs shared with everyone, and you will also be able to search for the snippet you need.
@info-creaticode It could be like community built custom blocks is what im getting. I like the idea, so people can share code and stuff easier to use across projects. I do have one request for it though: it needs to be implemented in a library-like fashion. This would prepare students for the real world & getting into serious programming, like with NodeJS or python, etc., where to get extended functionality you would need to download packages/libraries from NPM to your project (or code it yourself). For how it would get added, there would be a âadd package/library (package chooser)â block that needs to be put in the stage in a âwhen green flag clickedâ block. The package chooser shows all community made libraries.
These community made libraries could/would consist of variables, tables, lists, and most importantly, custom blocks. To access stuff from libraries, they would appear as an extension to your project like how âWidgetsâ is or â3Dâ.
In fact, an easier/alternative method that you guys could also add would be allowing users to submit their own scratch extensions (they would need to be reviewed by someone before appearing publicly).
then
For this idea, when the add extension menu is up, there would be community extensions as well for more advanced users (such as myself) that would like to give extensions to the community and add more functionality to CreatiCode projects using code. For a normal user, they could be able to put trusted (moderator reviewed) extensions in their projects.I know the idea needs more fleshing out but this is just what Iâm putting out there for now as I think more of how a system like this could work.
#LLJW
<span style="color:white;background-image:linear-gradient(to right, lightblue, navy)">My name is Jeff</span> -
@info-creaticode It could be like community built custom blocks is what im getting. I like the idea, so people can share code and stuff easier to use across projects. I do have one request for it though: it needs to be implemented in a library-like fashion. This would prepare students for the real world & getting into serious programming, like with NodeJS or python, etc., where to get extended functionality you would need to download packages/libraries from NPM to your project (or code it yourself). For how it would get added, there would be a âadd package/library (package chooser)â block that needs to be put in the stage in a âwhen green flag clickedâ block. The package chooser shows all community made libraries.
These community made libraries could/would consist of variables, tables, lists, and most importantly, custom blocks. To access stuff from libraries, they would appear as an extension to your project like how âWidgetsâ is or â3Dâ.
In fact, an easier/alternative method that you guys could also add would be allowing users to submit their own scratch extensions (they would need to be reviewed by someone before appearing publicly).
then
For this idea, when the add extension menu is up, there would be community extensions as well for more advanced users (such as myself) that would like to give extensions to the community and add more functionality to CreatiCode projects using code. For a normal user, they could be able to put trusted (moderator reviewed) extensions in their projects.I know the idea needs more fleshing out but this is just what Iâm putting out there for now as I think more of how a system like this could work.
You are right. We should allow users to submit new extensions.
However, the code snippet library should be more like backpack than extension, since it will allow users to modify the code blocks after a snippet is imported. If it is an extension, then users wonât see its implementation and also wonât be able to customize it.
-
You are right. We should allow users to submit new extensions.
However, the code snippet library should be more like backpack than extension, since it will allow users to modify the code blocks after a snippet is imported. If it is an extension, then users wonât see its implementation and also wonât be able to customize it.
@info-creaticode Ohh, that makes sense and I understand. Since itâs more adding things to your backpack than an extension, then it needs to be bigger and work more because the struggles I have with the backpack are that itâs a bit small and oftentimes says something like âBackpack failed to loadâ after opening and closing the menu a couple times.
Perhaps libraries would be a seperate thing then, since thatâs the point of libraries, to be shared for others to use and not be modified. I was thinking that perhaps a seperate page would be made to customize extensions after they have been published and that it would work like extensions more. For libraries added to a project, their information could be accessed using this perhaps?
And things like tables, lists, and functions (custom blocks) would be accessed from other things and maybe even just a section/extension for it itself rather than using the â[property] of [sprite]â block as that is more limited. I just think the idea of like modules/libraries is a great oppourtunity to show how they work in other programming languages in an easier way as well as making CreatiCode easier to code projects with.Community extensions/libraries (in the way i suggested) would be implemented a database rather than being hardcoded into the site code, which would be great for advanced users like myself to write code for new blocks that can do more and donât need to be added into CreatiCode itself, like the suggestions Iâve made in the past that have been rejected (for things like string encryption and making HTTP requests).
My solution is for there to not only be a code snippets library but also a community extensions library. Their differences should be explained so people can know what the right choice(s) are to make, and they could even use both in their projects. When these are used, the creators of these snippets/extensions would also need to be credited, so on the project page, there needs to be a message in the same fashion of âCredit to the original author, (author)â when itâs remixed, but like âCode snippet (title) by (author) was usedâ.
For both of these, they would need to be moderator reviewed, like in a posting queue system.
#LLJW
<span style="color:white;background-image:linear-gradient(to right, lightblue, navy)">My name is Jeff</span> -
@info-creaticode Ohh, that makes sense and I understand. Since itâs more adding things to your backpack than an extension, then it needs to be bigger and work more because the struggles I have with the backpack are that itâs a bit small and oftentimes says something like âBackpack failed to loadâ after opening and closing the menu a couple times.
Perhaps libraries would be a seperate thing then, since thatâs the point of libraries, to be shared for others to use and not be modified. I was thinking that perhaps a seperate page would be made to customize extensions after they have been published and that it would work like extensions more. For libraries added to a project, their information could be accessed using this perhaps?
And things like tables, lists, and functions (custom blocks) would be accessed from other things and maybe even just a section/extension for it itself rather than using the â[property] of [sprite]â block as that is more limited. I just think the idea of like modules/libraries is a great oppourtunity to show how they work in other programming languages in an easier way as well as making CreatiCode easier to code projects with.Community extensions/libraries (in the way i suggested) would be implemented a database rather than being hardcoded into the site code, which would be great for advanced users like myself to write code for new blocks that can do more and donât need to be added into CreatiCode itself, like the suggestions Iâve made in the past that have been rejected (for things like string encryption and making HTTP requests).
My solution is for there to not only be a code snippets library but also a community extensions library. Their differences should be explained so people can know what the right choice(s) are to make, and they could even use both in their projects. When these are used, the creators of these snippets/extensions would also need to be credited, so on the project page, there needs to be a message in the same fashion of âCredit to the original author, (author)â when itâs remixed, but like âCode snippet (title) by (author) was usedâ.
For both of these, they would need to be moderator reviewed, like in a posting queue system.
@jeffreyrb03-gmail said in Code block presets?:
For libraries added to a project, their information could be accessed using this perhaps?
Can you please explain this part more? An extension is usually just a list of new blocks. It is not clear why you would need this sensing block to access it.
-
@info-creaticode Ohh, that makes sense and I understand. Since itâs more adding things to your backpack than an extension, then it needs to be bigger and work more because the struggles I have with the backpack are that itâs a bit small and oftentimes says something like âBackpack failed to loadâ after opening and closing the menu a couple times.
Perhaps libraries would be a seperate thing then, since thatâs the point of libraries, to be shared for others to use and not be modified. I was thinking that perhaps a seperate page would be made to customize extensions after they have been published and that it would work like extensions more. For libraries added to a project, their information could be accessed using this perhaps?
And things like tables, lists, and functions (custom blocks) would be accessed from other things and maybe even just a section/extension for it itself rather than using the â[property] of [sprite]â block as that is more limited. I just think the idea of like modules/libraries is a great oppourtunity to show how they work in other programming languages in an easier way as well as making CreatiCode easier to code projects with.Community extensions/libraries (in the way i suggested) would be implemented a database rather than being hardcoded into the site code, which would be great for advanced users like myself to write code for new blocks that can do more and donât need to be added into CreatiCode itself, like the suggestions Iâve made in the past that have been rejected (for things like string encryption and making HTTP requests).
My solution is for there to not only be a code snippets library but also a community extensions library. Their differences should be explained so people can know what the right choice(s) are to make, and they could even use both in their projects. When these are used, the creators of these snippets/extensions would also need to be credited, so on the project page, there needs to be a message in the same fashion of âCredit to the original author, (author)â when itâs remixed, but like âCode snippet (title) by (author) was usedâ.
For both of these, they would need to be moderator reviewed, like in a posting queue system.
@jeffreyrb03-gmail said in Code block presets?:
For both of these, they would need to be moderator reviewed, like in a posting queue system.
We will probably allow the users to submit a new snippet after automatically running it through a moderation AI checker. Then, later, anyone can review them and report issues.
-
@jeffreyrb03-gmail said in Code block presets?:
For libraries added to a project, their information could be accessed using this perhaps?
Can you please explain this part more? An extension is usually just a list of new blocks. It is not clear why you would need this sensing block to access it.
@info-creaticode That was just an idea I didnât think much about before putting it there. To access things from an extension it would be done the normal way.
-
@jeffreyrb03-gmail said in Code block presets?:
For both of these, they would need to be moderator reviewed, like in a posting queue system.
We will probably allow the users to submit a new snippet after automatically running it through a moderation AI checker. Then, later, anyone can review them and report issues.
@info-creaticode I originally was going to say either AI or moderator review, but then I realized, for a snippet trying to get a user to run dangerous code or say a snippet that places inappropriate images, the AI can easily be fooled due to its lack of spatial awareness/capabiltiies. You could obfuscate a string, with various methods like say jumbling the letters and dejumbling them, to put strings the AI canât interpret, and it would be even more effective to put comments that distract the AI like â3D raycasting algorithmâ or something or misleading function names. I think human review would be good alongside AI since bad things could happen.
#LLJW
<span style="color:white;background-image:linear-gradient(to right, lightblue, navy)">My name is Jeff</span> -
@info-creaticode I originally was going to say either AI or moderator review, but then I realized, for a snippet trying to get a user to run dangerous code or say a snippet that places inappropriate images, the AI can easily be fooled due to its lack of spatial awareness/capabiltiies. You could obfuscate a string, with various methods like say jumbling the letters and dejumbling them, to put strings the AI canât interpret, and it would be even more effective to put comments that distract the AI like â3D raycasting algorithmâ or something or misleading function names. I think human review would be good alongside AI since bad things could happen.
Yes those things can happen, but they can also occur with new comments or projects, and we canât really review all of them manually. So we will just have to assume most users are well-intended and delete any user that tries to do harmful things immediately when we find out.
-
Not a bad idea, not gonna lie. However I feel like it going to Extentions is a bad idea. Maybe we could make a separate category called Community Code so that official Extentions donât get mixed up.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better đ
Register Login