Page 1 of 1

[idea] for developers of plugins

Posted: Sat Apr 01, 2006 11:26 pm
by SHRIKEE
I just saw this idea on another cms system and it kinda got me thinking.

they offer a simple plugin as base for others. One to show some simple functionality and make it easy to develop plugins.

Is this an idea to use for serendipity?

This base plugin would add no features or nothing. Just a simple working thingy to see how stuff works.

Re: [idea] for developers of plugins

Posted: Sat Apr 01, 2006 11:30 pm
by garvinhicking
What should that plugin show then? I'm all for it, if you'd have an example?

I think s9y even does it a tad better, because we already have many, many plugins easily accessable to see examples for nearly everything you want to achieve? Many of those plugins are pretty small...

In our technical documentation on s9y.org we also have a very small example code for a very basic plugin...

Best regards,
Garvin

Posted: Sat Apr 01, 2006 11:47 pm
by SHRIKEE
i dunno what to show,

on the cms they have it show a page with one line telling the people it works.

i was just sharing thoughts. :)
in my experience a documented page or to-do-it-yourself is a whole difference.
i always prefer to just start making things and then see if it works and continue it :)

Posted: Sun Apr 02, 2006 12:34 am
by garvinhicking
Hi!

Yes, exactly, I agree. Learning by doing is the best experience, which is why I think we have a great base of plugins to look at?

With a CMS it's a bit easier, because there you just need to show a page that emits output. But for s9y the plugins can touch any functionality, so there is not a simple plugin to show anything unspecific...

If there is anything we can do to make it better, I'm all for it, so many thanks for sharing your thoughts! I am just thinking what exactly to show as a small plugin :)

Regards,
Garvin

Posted: Sun Apr 02, 2006 1:04 am
by SHRIKEE
yea, i cant think of anything really. except a new page. but we have a excellent plugin for that already.
no need to trigger a serie of new ones.

I guess sticking with the documentation will be the best option then.

And as you said with a cms its somewhat easier.