My version of a plugin repository

worktycho · 05-11-2015, 10:57 PM

Did you develop this in Internet Explorer?

NiLSPACE · (This post was last modified: 05-11-2015, 11:02 PM by NiLSPACE.)

(05-11-2015, 10:46 PM)tigerw Wrote: That's very strange. Could you screenshot?

Right here ^^: http://puu.sh/hJlwB/9a1887eed2.png

worktycho · (This post was last modified: 05-11-2015, 11:10 PM by worktycho.)

Tiger, just grab a standards compliant browser and look at you're site. The slideshow is broken on first render.

Also why is the separating line by the logo animated? Its just distracting

tigerw · 05-11-2015, 11:21 PM

(05-11-2015, 11:09 PM)worktycho Wrote: Tiger, just grab a standards compliant browser and look at you're site. The slideshow is broken on first render.

Also why is the separating line by the logo animated? Its just distracting

Okay okay, it's still a work in progress.

STR: it should be fixed.

jan64 · (This post was last modified: 05-12-2015, 12:34 AM by jan64.)

What if our plugin repo was tightly integrated with github?
We wouldn't have to worry about storage, account management and the repo would be integrated.
So, basically a catalog of github repos with rating, reporting, comments and a nice api for autoupdate plugin to fetch updates from.

bearbin · 05-12-2015, 02:29 AM

You could integrate with GitHub, but it would be much more complicated to develop and use for new users not used to working with GitHub.

jan64 · 05-12-2015, 02:49 AM

Using github isn't THAT hard, and we want to promote good habits.

bearbin · 05-12-2015, 04:53 AM

It's not difficult to use, in fact it's easier than the alternatives.

But most plugin devs don't start out using git, and it can be a substantial barrier to entry, and would discourage a lot of plugins to be made.

tonibm19 · 05-12-2015, 05:03 AM

They could use web interface, I started with it, and then moved to Github windows app, which is easy too.

xoft · (This post was last modified: 05-12-2015, 07:07 AM by xoft.)

I think, if using GitHub is too difficult for you, then writing a good plugin is basically impossibly difficult for you Tongue

Is the repository hosting the plugin downloads, or just storing links? If we forced GitHub, we could just store links, even for historical versions.

Any chance of an API that a plugin may use to perform a version check? Such as "Give me the latest version numbers for plugins X, Y and Z". Preferably in some simple-to-parse format (not JSON - we don't have a parser API in MCS yet)