documentation help requested for new mediawiki - Page 4

Wilbert · 10th March 2006, 17:56

Ah, I didn't realise that Richard needed to install all that stuff

It's not necessary to bother with that, so i will change it.

Wilbert · 28th March 2006, 21:27

@Richard,

The site is being mass spammed (gay sites) by a single person. You can see it when you edit pages. Is it possible to disallow him access?

http://www.avisynth.org/mediawiki/wi...:Recentchanges

Richard Berg · 28th March 2006, 23:38

I banned several IPs but not all -- there are lots of them. I also gave admin rights to Wilbert. I may limit edits to registered users if the problem persists.

Just upgraded to MediaWiki 1.5.8. I'm installing the math library now.

Wilbert · 28th March 2006, 23:45

Quote:

I banned several IPs but not all -- there are lots of them. I also gave admin rights to Wilbert. I may limit edits to registered users if the problem persists.

Just upgraded to MediaWiki 1.5.8. I'm installing the math library now.

So we can use LaTex? Great, thx very much!

Richard Berg · 28th March 2006, 23:47

Well, I've discovered I don't have the rights to compile anything

so it may be awhile.

foxyshadis · 29th March 2006, 00:24

What OS does the server run? gcc can compile to alternate targets (--target), although I don't know how easy or difficult it is; it might require compiling an alternate linker.

Richard Berg · 29th March 2006, 06:51

It's a small hosting company run by folks I know from another message board...it'll get taken care of.

Wilbert · 31st March 2006, 19:00

Quote:

I may limit edits to registered users if the problem persists.

Could you do that for a month or so? This moron doesn't stop spamming. I have more stuff to do than revert 20 edits a day

Richard Berg · 31st March 2006, 19:45

Done.

foxyshadis · 8th April 2006, 23:05

Is there any chance that new page creation can be unrestricted for normal registered users yet? Right now I guess it's admin-only, though I can still edit pages.

Richard Berg · 9th April 2006, 00:40

That was a mistake -- I upgraded to 1.6.x a few days ago. Apparently this version has a separate 'createpage' permission, but since I just copied over my old settings I wasn't granting it to anyone. Should work now.

foxyshadis · 9th April 2006, 02:20

1.6? Sweet, new templates!

*Must resist temptation to tweak madly instead of doing something useful*

foxyshadis · 26th June 2006, 08:18

Richard, I was wondering if you could add something to common.css or the individual style css?

Code:

pre { border: 1pt solid #999; padding: .8em 1.2em; margin: .5em 0; color: #039;white-space: pre; font-size: .9em; font-family: monospace; overflow: auto; }

Several attempts to replicate this through a template failed because wiki adds random <p> tags into the included text. The main reason I'd rather not stick with the default <pre> behavior is that it's impossible to differentiate examples from the descriptions. The border's a frill that doesn't need to be there, if you prefer.

Wilbert · 26th June 2006, 10:05

@foxyshadis,

You can move all your plugin/script stuff to:

http://www.avisynth.org/mediawiki/wiki/External_plugins

Feel free to change the layout if you think it's not good. I think it's important that a user knows whether its a plugin or script (usually plugins will have a higher processing speed), so that's why i added that.

foxyshadis · 26th June 2006, 10:42

Oh neat, I didn't know you moved it. That looks like a good idea, adding description. I'd probably just make the script/plugin designation the beginning of the description, then perhaps definition list would be a better medium for them:
; filter : description

With a little javascript magic you could allow descriptions to be turns on/off that way, but I'll not get too far ahead of myself.

Gerard V · 30th June 2006, 08:40

I'm able to help out with a few hours of work on this. Is there anything a relative noob can do to help you? I have mucked about with AviSynth for about 6 months now, mainly with DV and HDV material. I'm not much of an expert but I am a reasonably good writer and willing to find out what I dont know. If you start me on something at the shallow end I'll do a good job.

foxyshadis · 30th June 2006, 09:22

A couple of things that could help are:

rewriting some of the outdated parts (I think wilbert already largely updated the FAQ)
writing documentation for external filters/scripts that have none
rewriting or clarifying confusing docs or extending them with useful tips
condensing some of the useful threads into entries (eg, denoising comparisons, film-look, etc)
giving it a more coherent organization to find stuff more easily
designing a better logo... the list goes on!

yes, this was a gratuitous excuse to use a vbb list...

Hey, a wiki page on "How you can contribute to wiki" sounds like a great idea to keep everyone updated.

Gerard V · 30th June 2006, 11:22

So, just be be sure I'm tackling something that is of use, if I document any of the filters listed on here, that would be useful? If so I'll start with something easy like WavSource and go from there.

Wilbert · 30th June 2006, 19:32

It would be nice if you can work on the following:

Quote:

writing documentation for external filters/scripts that have none

old script page:
* http://www.avisynth.org/ShareFunctions

old external plugin pages:
* http://www.avisynth.org/Section+3%3A...lorspaces#q3.5
* http://forum.doom9.org/showthread.php?t=84481
* off-line docs

new script / external plugin page:
http://www.avisynth.org/mediawiki/wiki/External_plugins

So, if you could add short descriptions of external plugins (as done for DGDecode for example) that would be great (including links where to find the plugins). Adding complete descriptions is fine too (as done for Masktools for example) but has a low priority.

foxyshadis · 30th June 2006, 20:47

Quote:

Originally Posted by Gerard V

So, just be be sure I'm tackling something that is of use, if I document any of the filters listed on here, that would be useful? If so I'll start with something easy like WavSource and go from there.

Watch out, capitalization errors will probably show up on there, because the link to WAVSource should be WavSource. Currently there's no quick & simple way to discern the canon capitalization, but running a search helps narrow it down. Everything internal to 2.5x is documented.

26th June 2006, 08:18	#73 \| Link
foxyshadis Angel of Night Join Date: Nov 2004 Location: Tangled in the silks Posts: 9,559	Richard, I was wondering if you could add something to common.css or the individual style css? Code: pre { border: 1pt solid #999; padding: .8em 1.2em; margin: .5em 0; color: #039;white-space: pre; font-size: .9em; font-family: monospace; overflow: auto; } Several attempts to replicate this through a template failed because wiki adds random <p> tags into the included text. The main reason I'd rather not stick with the default <pre> behavior is that it's impossible to differentiate examples from the descriptions. The border's a frill that doesn't need to be there, if you prefer. Last edited by foxyshadis; 26th June 2006 at 08:21.

30th June 2006, 08:40	#76 \| Link
Gerard V Registered User Join Date: May 2006 Location: Wellington, New Zealand Posts: 112	I'm able to help out with a few hours of work on this. Is there anything a relative noob can do to help you? I have mucked about with AviSynth for about 6 months now, mainly with DV and HDV material. I'm not much of an expert but I am a reasonably good writer and willing to find out what I dont know. If you start me on something at the shallow end I'll do a good job. __________________ Gerard V - Comedy Hypnotist The World's 16th fastest Hypnotist http://www.thathypnoshow.com and http://www.gerardv.com Inventor of the Pink Panther hypno gag

30th June 2006, 09:22	#77 \| Link
foxyshadis Angel of Night Join Date: Nov 2004 Location: Tangled in the silks Posts: 9,559	A couple of things that could help are: rewriting some of the outdated parts (I think wilbert already largely updated the FAQ) writing documentation for external filters/scripts that have none rewriting or clarifying confusing docs or extending them with useful tips condensing some of the useful threads into entries (eg, denoising comparisons, film-look, etc) giving it a more coherent organization to find stuff more easily designing a better logo... the list goes on! yes, this was a gratuitous excuse to use a vbb list... Hey, a wiki page on "How you can contribute to wiki" sounds like a great idea to keep everyone updated.

30th June 2006, 11:22	#78 \| Link
Gerard V Registered User Join Date: May 2006 Location: Wellington, New Zealand Posts: 112	So, just be be sure I'm tackling something that is of use, if I document any of the filters listed on here, that would be useful? If so I'll start with something easy like WavSource and go from there. __________________ Gerard V - Comedy Hypnotist The World's 16th fastest Hypnotist http://www.thathypnoshow.com and http://www.gerardv.com Inventor of the Pink Panther hypno gag

10th March 2006, 17:56	#61 \| Link
Wilbert Moderator Join Date: Nov 2001 Location: Netherlands Posts: 6,364	Ah, I didn't realise that Richard needed to install all that stuff It's not necessary to bother with that, so i will change it.

28th March 2006, 21:27	#62 \| Link
Wilbert Moderator Join Date: Nov 2001 Location: Netherlands Posts: 6,364	@Richard, The site is being mass spammed (gay sites) by a single person. You can see it when you edit pages. Is it possible to disallow him access? http://www.avisynth.org/mediawiki/wi...:Recentchanges

28th March 2006, 23:38	#63 \| Link
Richard Berg developer wannabe Join Date: Nov 2001 Location: Brooklyn, NY Posts: 1,211	I banned several IPs but not all -- there are lots of them. I also gave admin rights to Wilbert. I may limit edits to registered users if the problem persists. Just upgraded to MediaWiki 1.5.8. I'm installing the math library now.

28th March 2006, 23:47	#65 \| Link
Richard Berg developer wannabe Join Date: Nov 2001 Location: Brooklyn, NY Posts: 1,211	Well, I've discovered I don't have the rights to compile anything so it may be awhile.

29th March 2006, 00:24	#66 \| Link
foxyshadis Angel of Night Join Date: Nov 2004 Location: Tangled in the silks Posts: 9,559	What OS does the server run? gcc can compile to alternate targets (--target), although I don't know how easy or difficult it is; it might require compiling an alternate linker.

29th March 2006, 06:51	#67 \| Link
Richard Berg developer wannabe Join Date: Nov 2001 Location: Brooklyn, NY Posts: 1,211	It's a small hosting company run by folks I know from another message board...it'll get taken care of.

31st March 2006, 19:45	#69 \| Link
Richard Berg developer wannabe Join Date: Nov 2001 Location: Brooklyn, NY Posts: 1,211	Done.

8th April 2006, 23:05	#70 \| Link
foxyshadis Angel of Night Join Date: Nov 2004 Location: Tangled in the silks Posts: 9,559	Is there any chance that new page creation can be unrestricted for normal registered users yet? Right now I guess it's admin-only, though I can still edit pages.

9th April 2006, 00:40	#71 \| Link
Richard Berg developer wannabe Join Date: Nov 2001 Location: Brooklyn, NY Posts: 1,211	That was a mistake -- I upgraded to 1.6.x a few days ago. Apparently this version has a separate 'createpage' permission, but since I just copied over my old settings I wasn't granting it to anyone. Should work now.

9th April 2006, 02:20	#72 \| Link
foxyshadis Angel of Night Join Date: Nov 2004 Location: Tangled in the silks Posts: 9,559	1.6? Sweet, new templates! Must resist temptation to tweak madly instead of doing something useful

26th June 2006, 10:05	#74 \| Link
Wilbert Moderator Join Date: Nov 2001 Location: Netherlands Posts: 6,364	@foxyshadis, You can move all your plugin/script stuff to: http://www.avisynth.org/mediawiki/wiki/External_plugins Feel free to change the layout if you think it's not good. I think it's important that a user knows whether its a plugin or script (usually plugins will have a higher processing speed), so that's why i added that.

26th June 2006, 10:42	#75 \| Link
foxyshadis Angel of Night Join Date: Nov 2004 Location: Tangled in the silks Posts: 9,559	Oh neat, I didn't know you moved it. That looks like a good idea, adding description. I'd probably just make the script/plugin designation the beginning of the description, then perhaps definition list would be a better medium for them: ; filter : description With a little javascript magic you could allow descriptions to be turns on/off that way, but I'll not get too far ahead of myself.