Snippet Codes sections

[Jonforum]

I would like to address a small idea.
What would you think of an additional section called Snippets and codes?
I think it would be a good way to make available a small library of snippets that will have nothing to do in the plugin section. !

A good way to share information that would also have a playful side.

 

[Nightblade50]

That sounds good, I would like to see that!

 

[Kvothe]

I agree with it! On the best forum of Brasil, MRM (R.I.P 'cause don't exist any more), we had a section for this.

 

[Andar]

You are not the first to have that idea, something similiar has been in discussion internally for the last few months. I don't know when the last questions on how to handle it will be solved however.

 

[Shaz]

What is the difference between a snippet and a plugin? They both have to be implemented the same way - as a .js file in the plugins folder, and added via the plugin manager. It just seems to me an extra place to search if you're looking for something.

 

[Nightblade50]

What is the difference between a snippet and a plugin? They both have to be implemented the same way - as a .js file in the plugins folder, and added via the plugin manager. It just seems to me an extra place to search if you're looking for something.

Well, a snippet is a small plugin.

 

[Shaz]

So why not just put it in the plugin section?

As it is, there are already 2 places to look for plugins on this forum - one in the Plugin Releases folder, and the other in the Plugin Requests folder, which is where people usually put small snippets in response to requests.

I can see some pros and cons of a section just for small plugins, but as a plugin writer, I don't want to have to decide which section my plugin needs to go into, especially if the only thing to base it on is "is it small?" What is small?

It obviously has merit, if the mods/admins have already been discussing it. I personally don't see the need though.

 

[Nightblade50]

So why not just put it in the plugin section?

As it is, there are already 2 places to look for plugins on this forum - one in the Plugin Releases folder, and the other in the Plugin Requests folder, which is where people usually put small snippets in response to requests.

I can see some pros and cons of a section just for small plugins, but as a plugin writer, I don't want to have to decide which section my plugin needs to go into, especially if the only thing to base it on is "is it small?" What is small?

It obviously has merit, if the mods/admins have already been discussing it. I personally don't see the need though.

That's a good point. I have a VX Ace script thread (in my signature, under "my awesome resources") and those scripts are what I would call "snippets." they are very short.

 

[Jonforum]

@Thomas Smith @Shaz
https://en.wikipedia.org/wiki/Snippet_(programming)

 

[Nightblade50]

@Thomas Smith @Shaz
https://en.wikipedia.org/wiki/Snippet_(programming)

I will read that.

 

[mlogan]

We've actually been in discussion on a solution to this for a while, it's just taken a back seat to other things (including real life issues for us mods). Hopefully, it will be up soon.

 

[Roninator2]

As I understand snippet's to be the small parts of code (or perhaps an add on or modification) written for members that ask for patches or features etc. Similar to the plugins or scripts threads, I think having a snippet thread or pinned post that had links to the posts where the code that was made could be useful. Sometimes solutions for problems are lost due to be buried in the mountain of threads that get made. Unless google has a running list of all the threads and posts in this forum, then I may not find the patch that was made and make a new thread for the same or similar request.
Something like that, it's sort of a rough idea anyways and would require a lot of work, I'm sure.

 

[Jonforum]

in a general way

a plugin: it a code that allow to manage some code in a libs and add features.
a snippets: it a simple hack that modifies the behavior of a other code.

I saw some plugins edit only a variable and be called plugin, it makes me rather laugh.

 

[mlogan]

Hey all, finally opened the snippet topic. https://forums.rpgmakerweb.com/index.php?threads/js-snippets-thread.92501/

Thanks for the recent bump in this topic - it reminded me that that needed doing. Sorry it took so long.

 

[Jonforum]

Hey all, finally opened the snippet topic. https://forums.rpgmakerweb.com/index.php?threads/js-snippets-thread.92501/

Thanks for the recent bump in this topic - it reminded me that that needed doing. Sorry it took so long.

You probably made a mistake, you created a topics instead a tread.

 

[Shaz]

I saw some plugins edit only a variable and be called plugin, it makes me rather laugh.

No matter how many lines, it's still a plugin, because that's how it has to be implemented.

I strongly recommend against changing the core files, even for a one-line mod. Because you forget you've done it, you take an update and update your project, then you have to figure out why things are different, which could be a massive waste of time if you did it a long time ago.

you created a topics instead a tread

topic = thread. They are the same thing.

 

[Jonforum]

No matter how many lines, it's still a plugin, because that's how it has to be implemented.
I strongly recommend against changing the core files, even for a one-line mod. Because you forget you've done it, you take an update and update your project, then you have to figure out why things are different, which could be a massive waste of time if you did it a long time ago.
topic = thread. They are the same thing.

In a general way to stay clean, you must have a special file to replace all all method from rmmv.
as you said, when you update the original source, it becomes impossible to manage.

topic = thread. They are the same thing.

ho ok, sorry, maybe my bad English !
for me, it not same thing in my language.