Plugins?

[Shorty]

What exactly are they? Are they just code? Or what?

Also with the plugin system in v5 will this possibly eliminate code clashes or whatever?

[RedBassett]

ProBoards has not released much info on plugins yet, however plugins are just extension code. There may be some backend hooks included in the system, but it will probably be a better way of handling any sort of codes, instead of large text boxes for all the codes in a section.

- RedBassett

[Chris]

May 7, 2012 10:23:11 GMT -8 Shorty said:

What exactly are they? Are they just code? Or what?

Also with the plugin system in v5 will this possibly eliminate code clashes or whatever?

Code conflicts are not automatically handled. I discussed it with Patrick and we decided it'd be unnecessarily complex and too much overhead.

[Shorty]

May 7, 2012 11:23:05 GMT -8 Chris said:

May 7, 2012 10:23:11 GMT -8 Shorty said:

What exactly are they? Are they just code? Or what?

Also with the plugin system in v5 will this possibly eliminate code clashes or whatever?

Code conflicts are not automatically handled. I discussed it with Patrick and we decided it'd be unnecessarily complex and too much overhead.

Will it help with the conflicts though?

[Ryan Roos]

Plugins are a way for developers to create forum codes in a more user friendly matter.

Old Way - Code
Developers make a code that does something.
User of the code searches around trying to find right code.
User literally copies and pastes code into their headers and footers, sometimes multiple pieces of code to multiple places.
User has to manually search the code changing variables and different settings.
Code usually works but sometimes repeating earlier steps is necessary.

Risk: Codes are easier to take from developers.
Risk: User could accidentally break the code and not understand how.


New Way - Plugins
Developers (Authors) make a plugin that does something.
User goes to the Plugin Library in v5 (or elsewhere).
User installs plugin and is prompted for installation settings.
User goes into the settings area of the plugin and uses friendly UI to change options.
Plugin works.

Bonus: Author code is more secure and controlled by the authors. Easier to release updates. Users can be notified of updates automatically (if Plugin is from the Plugin Library)
Bonus: Less chance of users making a mistake since they use a UI to adjust settings.
Bonus: Eventual opportunities for Authors to make a profit on Plugins in the Plugin Library.

Conflicts can still arise, though we've added a new key system along with other things that should help reduce conflicts. Additionally dealing with conflicts is as easy as turning plugins on and off, instead of cutting and pasting huge swaths of code trying to find the fix.

Note: Headers and Footers still exists. Plugins are new, not replacing the old. They will work side by side with the old.

[Shorty]

What is a UI?

[Ryan Roos]

User Interface - think of a control panel with different options

[Shorty]

oh okay. so pretty all variables of previous codes will be edited thru this UI?

[Ryan Roos]

May 7, 2012 13:18:59 GMT -8 Shorty said:

oh okay. so pretty all variables of previous codes will be edited thru this UI?

Yes for example.

The old way might have had a string of code.


<!--Note from author, replace the caps letters below with the proper information. Then copy paste this into your header.-->
<blah>
<style type="text/css">
.shop {
/* replace this hex code with the color you want for your shop border.*/
border-color: #FF0000;
border: solid 2px;
}
</style>

<random>

<div class="shop">
<b>NAME OF SHOP</b>
ENTER THE DESCRIPTION OF YOUR SHOP HERE
</div>

</random>

</blah>


Obviously that's complex, did you even find the 3 things you need to edit?

The new way will have a settings page for the plugin. The UI for those same 3 options would be presented like the attachment here. It even has a color picker to help you with the hex code.


Do you see how much easier that would be to fill out or edit?

EDIT: This attachment is an actual screenshot from a plugin. I only reduced its size in Photoshop for viewing ease.

[Shorty]

That is freaking beautiful man, just beautiful....

[Chris]

Ryan: How are plugins' order chosen? I don't remember discussing this while out there.

[Ryan Roos]

May 7, 2012 19:09:45 GMT -8 Chris said:

Ryan: How are plugins' order chosen? I don't remember discussing this while out there.

Do you mean the order they take priority? They can be reordered by the user.

[snap2000]

May 7, 2012 20:40:41 GMT -8 Ryan Roos said:

May 7, 2012 19:09:45 GMT -8 Chris said:

Ryan: How are plugins' order chosen? I don't remember discussing this while out there.

Do you mean the order they take priority? They can be reordered by the user.

Is it possible / planned for the plugin management page also have some additional, readily accessible information? Perhaps a short description and a link to update notes / known issues?

[Chris]

May 7, 2012 21:23:06 GMT -8 snap2000 said:

May 7, 2012 20:40:41 GMT -8 Ryan Roos said:

Do you mean the order they take priority? They can be reordered by the user.

Is it possible / planned for the plugin management page also have some additional, readily accessible information? Perhaps a short description and a link to update notes / known issues?

I believe we planned in update notes. Known issues is a separate thing.



Ryan: So, what about individual header/footer order? while it is probably bad practice to believe so, I can foresee them needing reversed orders (i.e. matching <div></div> in proper order.)

[Robyn]

May 7, 2012 13:40:56 GMT -8 Ryan Roos said:

May 7, 2012 13:18:59 GMT -8 Shorty said:

oh okay. so pretty all variables of previous codes will be edited thru this UI?

Yes for example.

The old way might have had a string of code.


<!--Note from author, replace the caps letters below with the proper information. Then copy paste this into your header.-->
<blah>
<style type="text/css">
.shop {
/* replace this hex code with the color you want for your shop border.*/
border-color: #FF0000;
border: solid 2px;
}
</style>

<random>

<div class="shop">
<b>NAME OF SHOP</b>
ENTER THE DESCRIPTION OF YOUR SHOP HERE
</div>

</random>

</blah>


Obviously that's complex, did you even find the 3 things you need to edit?

The new way will have a settings page for the plugin. The UI for those same 3 options would be presented like the attachment here. It even has a color picker to help you with the hex code.


Do you see how much easier that would be to fill out or edit?

EDIT: This attachment is an actual screenshot from a plugin. I only reduced its size in Photoshop for viewing ease.

1) With the plugin system, what flexiblities do the coding authors have as far as the presentation of the UI? Can/Do they allow:

a) the code author to create tip boxes with arrrows that appear and point the user in the right order to fill things out and could also provide examples?

b) An instant preview (depending on the plugin) that shows the results of the chosen settings the user puts in via screenshot?


2) Can one edit the plugin directly in HTML and/or CSS if the user is comfortable, confidence, or aware of those codes?

example: You have a code that changes member's display name color and font and style based on what you decide. The plugin lets you type things out and use color pallets to select colors, etc. But if the user is aware of CSS, they can go to "edit mode" (instead of UI mode or whatever you could call it) and directly edit the plugin code.

Of course if 2 is allowed, then you'd need warnings to inform users that they are responsible for any mistakes they make and shouldn't come crying to the support forum for trying to edit the CSS if they don't know CSS.


3) Assuming 2 is possible or accepted, you could be more flexible and let the plugin author even let the user chose between direct code edits or UI editing.

4) I am unfamiliar with the plugin directory and assume not much news or confirming ideas have been public. However, as far as presentation, will you be including "Most popular" plugins, "Top rated" plugins (Assuming you will be given the ability to rate them either 5 stars or however) "Newest plugins", "Plugin of the week/month", etc.?