| Viewing Single Post From: Plug-in System | |
|---|---|
| Paper | Jun 28 2009, 06:48 AM |
Member
  ![]](http://209.85.62.24/static/1/pip_r.png)
|
A plug-in database is a very good idea, and would help to put Zetaboards in front of competitors such as Proboards. Currently Proboards have a kind of quality screening process, that ensure a certain standard of instruction, support and workability before it is added to the hack list. I would say though, that competition between different coders who make similar codes is important, as it drives up quality and features, so a plug in system should offer different coding solutions for the same thing, and allow users to choose and rate which one they wish to use. Proboards have stifled this in that similar codes to ones already in the hack list are rejected. Ultimately better codes sometimes end up being rejected. And I make no apology being critical on a Zetaboard forum! Compatibility is not really a huge issue. Naming variables correctly would avoid much incompatibility. Thorough testing, for example by installing all codes available in a plug-in database would determine if there are conflicts caused by the code. If such conflicts exist, each code in the database can be tested against a code until the two conflicting codes are found. The problem then can be corrected, or the codes can be marked as incompatible. Support is another easily solvable issue. If you have your code in the plug in database, you accept that you must provide periodic support for it. The plug in system could allow support tickets to be sent to the coder. |
 |
|
| Plug-in System · ZetaBoards Discussion | |
- ZB Home ·
- ZB Docs ·
- ZB FAQ ·
- ZB Directory
- IF Home ·
- IF Docs ·
- IF FAQ ·
- IF Directory
7:18 PM Nov 22
