1 jaromy Feb 18, 2009 04:47
3 yabba Feb 18, 2009 07:05
jaromy wrote:
b) create a new topic in the Plug-in forum to announce it
You can now create your support thread ;)
¥
4 jaromy Feb 18, 2009 09:05
Thanks, guys! I appreciate the help.
For creating the webpage that explains the plug-in (i.e. step by step instructions, what it does, code examples, etc), how do I go about creating that documentation on the b2evo website? Seems more logical to post it there, than to have it hosted on my own website...
For example, the starrating plugin appears as a page at:
http://manual.b2evolution.net/Plugins/starrating_plugin
How can I get a similar page at (for instance)?:
http://manual.b2evolution.net/Plugins/sharethiswidget_plugin
Cheers,
Jaromy
5 jaromy Feb 19, 2009 04:21
OK, nevermind my last question... I figured it out:
http://manual.b2evolution.net/Help:Editing
Reading up on MediaWiki now... never used it before :) I was a bit confused by the lack of a "Create a Page" link or something to that effect.
For all other newbies out there, here's what you do: search for a page with the same title as what you're proposing. When/if nothing shows up, *then* you get the link to create a new page.
Genius.
6 edb Feb 19, 2009 04:47
MY humble opinion:
Your Own Blog = lousy for sharing but great for letting you communicate with users.
Plugins Page = great for sharing it with everyone but lousy for communicating with users.
A Forum Post = pretty good for sharing and pretty good for communicating with users but lousy at letting me "truly express myself" due to no pornographic smilies.
BOPIT = great for letting users who've already found a plugin and don't need to communicate with me about it know that they might want to update, lousy for ... uh ... it's not good because ... er ... because the author has a weird name? Oh and also great for telling users that I've got a plugin they might want to know about. In short, there is nothing wrong with BOPIT other than the really hot little devil that wants the author to upgrade it :)
The Wiki Manual Thing = great if you're into doing stupid stuff just because someone else is doing it, lousy at everything else. In fact, wikis are proof that the internet is totally stupid.[/list:u]
Therefore after I write it and zip it and upload it I do the following: blog about it, submit it to the plugins page, post it on the forums, add it to bopit. I then recall that there is a place in the wiki for plugins and chuckle cuz I know I'm done :D
7 jaromy Feb 19, 2009 22:22
EdB, thanks for the reply.
It would be nice if things were more consolidated. As a developer, it's a pain to have to update in 5 different places! I guess that's why I've been leaning toward the Wiki Manual. Plus, I don't really want to be hosting b2evo dev stuff on my website. I'd rather do it here (and sourceforge) where it seemingly belongs.
8 jaromy Feb 19, 2009 22:22
New question: how do you guys generate the "README.html" file for plug-ins? Is there a way to automatically export it from the MediaWiki page?
9 edb Feb 19, 2009 22:31
I pretty much just copy an existing one into my plugin folder and edit it using my favorite editor.
10 jaromy Feb 19, 2009 23:31
Cool, thanks. That's pretty much what I'm doing for now... just saving the html page that's rendered in my browser from MediaWiki, then editing it in Dreamweaver - cutting out extraneous HTML, scripts, etc.
11 afwas Feb 20, 2009 03:49
hi jaromy,
Two more steps:
0) Contact Personman (see plugins page) and provide him details as (0) download URL (1) support thread (2) the URL to the man page you just created etc and he'll add it to the plugins page
1) If you're serious about coding plugins contact blueyed and he'll grant you dev access to [url=https://sourceforge.net/projects/evocms-plugins/]svn://evocms-plugins[/url].
Good luck
12 edb Feb 20, 2009 04:23
Afwas wrote:
... 1) If you're serious about coding plugins contact blueyed and he'll grant you dev access to [url=https://sourceforge.net/projects/evocms-plugins/]svn://evocms-plugins[/url] ...
I guess we can respectfully disagree on this eh? Cuz see even though I'm pretty much an entry-level hack I am quite serious about my plugins, which happens to be the reason mine aren't going to where I don't own them. Yet I see the value for both the "serious" and casual plugin author. Life is good that way yah?
@jaromy: thanks for contributing. It's really cool to see someone come along and pop out a couple of plugins like this.
This is for all you've done :cookie:
13 jaromy Feb 20, 2009 07:51
Hi guys,
Afwas, thanks for helping out - I'll contact Personman to make sure the plugins get added and everything links up.
EdB, I'd consider myself more of the casual plugin author - that is, I'll make them as I need to if I can't find something already :) Previously was making 'hacks', but figured I should learn how to make a legit plugin - if nothing else, it would be easier to migrate to that feature to the next upgrade version of b2evo.
Anyway, I'm happy to share the love. Hopefully a few folks will find them useful.
Cheers,
J
14 waltercruz Feb 23, 2009 17:52
And now we have 3 share this plugins ;)
Just 2, I dropped the mine some time ago :)
[url=http://plugins.b2evolution.net/index.php/2005/08/04/submit_a_plugin_or_hack]Submit a plugin[/url]