| Viewing Single Post From: Plug-in System | |
|---|---|
| Jory | Jun 28 2009, 11:32 AM |
 
|
I have one major issue with any type of "centralised" plugin list: People will assume we (Zathyus staff) will be able to support them1. Sure, we can create a system that sends an email to the code creator. Maybe we can even create something central where somebody needs to register in order to submit a code, where they can then see and awnser tickets about their codes. But we won't be able to make sure they will. And then what? Then, we end up having to explain things, try to fix things ourselfs, etc. And just removing a code won't work either. Because then you have two options for boards that already use the code: Remove it and break things on that board, or leave it and be responsible for supporting the code. Don't get me wrong, I like this idea. (Or at least, I like the way I'm interpeting it.) It could make things much easier for our users. But from a support point of view, I for one do not want this. (Unless we can find a way to force code creators to provide support. But Brandon says our strike team is busy elsewhere. Bah.  )1: Not that they don't assume things like that about custom codes not. But it would be far worse. Oh, I do know how to solve the compatebillity issue: Upon registration, you get a username. Each code also has a "codename". Both these names are valid Javascript class/variable names. Then if I where to want to make a code called "Banner Rotator", it would be something like this: That way, if somebody else wants to make a banner rotator, it would be in otherpersonsusername.BannerRotator.execute(). (FYI, execute() gets automatically called by our hypothetical system.  )Do note I'm not sure this exact syntax is valid in Javascript. But I'm sure there is something close enough. |
 |
|
| Plug-in System · ZetaBoards Discussion | |
- ZB Home ·
- ZB Docs ·
- ZB FAQ ·
- ZB Directory
- IF Home ·
- IF Docs ·
- IF FAQ ·
- IF Directory
4:13 AM Nov 24
