Codes versus Plug-ins?

[bluebayou]

Okay, so I've been slowly trying to get up-to-speed on the awesomeness that will be V5.

I've been reading about how a lot of the current codes we may be using on our boards might not be needed because of plug-ins on the new version.

Forgive this totally non-tecky question, but what the heck's a plug-in?

[RedBassett]

A plugin is a code wrapped in a package that allows it to be easily added/removed/modified without touching the coding itself.

Think of it as a way of installing codes like you would software on your computer: all with your mouse, no copy and paste and editing lines of code.

[bluebayou]

Thanks, Red! Even *I* can understand that.

To install a plug-in, I won't have to mess with my headers/footers, then?

[®i©hie]

No, all plugins are "uploaded/installed" on the forum. Plus you can easily turn them on/off and even set permissions for each one.

[Ryan Roos]

Aug 21, 2012 3:42:09 GMT -8 bluebayou said:

Thanks, Red! Even *I* can understand that.

To install a plug-in, I won't have to mess with my headers/footers, then?

Correct. No messing with headers and footers when you're using a plugin.

Depending on the author and the quality of the plugin you will likely just have a nice interface to change settings.

So lets say you wanted a sidebar right now. You'd have to go search for a code. Copy half of it to your headers, copy the other half to your footers. Then you would need to go line by line through the code editing it. Replacing placeholder text with your own text. Editing direct code to change the settings. Maybe you want it on the right side instead of the left and you have to edit a bunch of code. Maybe it doesn't work properly the first time.

In v5 you can use a plugin.

So you go to the plugin library (a central hub for plugins) and find a sidebar mod that sounds good to you. You install it. You go to the settings page of the plugin and change the settings you want. Enter your content in nice text boxes. You decide you want the bar on the right side, you change that option in a drop down menu and it works.

A lot easier. It will also be easy to install multiple plugins and compare them side by side to see which you like the most. Install 3 sidebar plugins by different authors and turn them on and off one at a time and compare which you like. Doing that with 3 codes in headers and footers would be rough, with no on and off switches and a lot of code to move around.

And just to clarify there still will be headers and footers for people that want to use them. Plugins is just the next logical step in codes. On and off switches, member permissions, theme permissions, user interfaces, installation; lots of features that make them superior.

[Celeste]

Patrick Clinger made a video about installing plugins on v5. If you haven't seen it, you might want to take a look: www.youtube.com/watch?v=mYElzRo0jDQ

[bluebayou]

Aug 21, 2012 7:27:24 GMT -8 Celeste said:

Patrick Clinger made a video about installing plugins on v5. If you haven't seen it, you might want to take a look: www.youtube.com/watch?v=mYElzRo0jDQ

Great Video - thanks for the link, Celeste.

Derpy Zombie ROCKS!!!

[bluebayou]

Thank-you, Ryan.

Now I'm excited for V5, because it sounds like even *I* would have a hard time screwing it up.

Are the current codes in use in this version going to be re-written as plug-ins for V5? Or just any new codes after the launch?

[Ajay]

Aug 21, 2012 8:39:20 GMT -8 bluebayou said:

Thank-you, Ryan.

Now I'm excited for V5, because it sounds like even *I* would have a hard time screwing it up.

Are the current codes in use in this version going to be re-written as plug-ins for V5? Or just any new codes after the launch?

Some of the current v4.5 codes that exist, will be implemented into v5 already, so there's no need for you to have a seperate code added into your headers & footers. However some that aren't added into v5 already, will need to be recoded.

[Chris]

Ryan, I forgot to ask Pat this during the demo, but we can reorder plugins easily, right?

[Ryan Roos]

Aug 21, 2012 15:42:05 GMT -8 Chris said:

Ryan, I forgot to ask Pat this during the demo, but we can reorder plugins easily, right?

[Ajay]

. That's awesome!

[bluebayou]

Aug 21, 2012 15:17:07 GMT -8 Ajay said:

Some of the current v4.5 codes that exist, will be implemented into v5 already, so there's no need for you to have a seperate code added into your headers & footers. However some that aren't added into v5 already, will need to be recoded.

I have a few codes on my board. Not excessive, but the ones I do have I'm really attached to. Unless the codes I use are implemented right into the new V5 platform, are the original authors of these codes changing them into plug-ins? Or modifying the code to make it work in the new headers and footers of V5? Am I right in assuming that all codes currently being used need to be modified for V5? If so, how will I know which have been re-done, which ones haven't, and which ones are now redundant because they're a part of V5?

I apologize in advance for these numerous and pretty clueless questions.

[Ajay]

Well you will know if you don't see a specific feature that needs a code that haven't been added to v5. Yes, the original coders will have to modify the code.

[Ryan Roos]

Aug 22, 2012 4:50:31 GMT -8 bluebayou said:

Aug 21, 2012 15:17:07 GMT -8 Ajay said:

Some of the current v4.5 codes that exist, will be implemented into v5 already, so there's no need for you to have a seperate code added into your headers & footers. However some that aren't added into v5 already, will need to be recoded.

I have a few codes on my board. Not excessive, but the ones I do have I'm really attached to. Unless the codes I use are implemented right into the new V5 platform, are the original authors of these codes changing them into plug-ins? Or modifying the code to make it work in the new headers and footers of V5? Am I right in assuming that all codes currently being used need to be modified for V5? If so, how will I know which have been re-done, which ones haven't, and which ones are now redundant because they're a part of V5?

I apologize in advance for these numerous and pretty clueless questions.

We hope to set up a dev environment where coders can take requests and we can catalog and organize all of the new plugins. It would hopefully be as simple as going there and making a request for the codes you have. Then hopefully someone friendly would come along and tell you whats a new feature, link you to plugins for most of your codes, and if you had something new the community could take it as a new project to make a plugin for. That's the goal at least.

We have already implemented many of the most popular codes. We (ProBoards) will be providing a certain amount of plugins as well to cover other popular codes that didn't make the feature cut. After that hopefully coders that are active will help. I wouldn't worry about it.