I'm working with Visviva (on WikiProject Deletion sorting) to find a way to sort all this out.
It's based on an idea developed at another encyclopedia wiki - one which actually PAYS ME to flounder around and flummox things up!
It uses templates for transclusion. Details forthcoming, as it will take at least the rest of this week to document and test this.
Note that I put "document it" first! I write software in the following stages:
1. Document what the software is intended to do. 2. Write the system tests and unit tests for the source code. 3. Oh, yes, when we have time ... Write the source code!
I think this is discussed at greater length at Wikipedia, either at [[refactoring]] or [[test-first development]]. It's amazing how many bugs you can KEEP FROM coming to life, merely by writing the tests first. It also reduces total development time. Oh, why did I ever quit the Wikipedia Development Team? (Because you didn't want to learn PHP, remember? Shut up, I'm not going to have a MPD on the mailing list! Why not? JRM had one on your user talk page. Oh, please!)
Somewhat distractedly,
Uncle Ed Developer Emeritus Admin Provisional
-----Original Message----- From: Alphax [mailto:alphasigmax@gmail.com] Sent: Thursday, August 04, 2005 9:54 AM To: Phroziac; English Wikipedia Subject: [WikiEN-l] Shrinking VFD (was I better shut up)
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
Phroziac wrote:
If VFD were kept, how about un-inlining the closed vfds, and giving links to them instead? Would make the CSDs clutter it somewhat less.
Several people use combinations of Javascript and CSS which allow this to be done. With one click they can hide all closed VFDs.
Ed, are you sure you are sane? By the way, what do you think of the pure wiki deletion system? I like it alot, personally.
On 8/4/05, Poor, Edmund W Edmund.W.Poor@abc.com wrote:
I'm working with Visviva (on WikiProject Deletion sorting) to find a way to sort all this out.
It's based on an idea developed at another encyclopedia wiki - one which actually PAYS ME to flounder around and flummox things up!
It uses templates for transclusion. Details forthcoming, as it will take at least the rest of this week to document and test this.
Note that I put "document it" first! I write software in the following stages:
- Document what the software is intended to do.
- Write the system tests and unit tests for the source code.
- Oh, yes, when we have time ... Write the source code!
I think this is discussed at greater length at Wikipedia, either at [[refactoring]] or [[test-first development]]. It's amazing how many bugs you can KEEP FROM coming to life, merely by writing the tests first. It also reduces total development time. Oh, why did I ever quit the Wikipedia Development Team? (Because you didn't want to learn PHP, remember? Shut up, I'm not going to have a MPD on the mailing list! Why not? JRM had one on your user talk page. Oh, please!)
Somewhat distractedly,
Uncle Ed Developer Emeritus Admin Provisional
-----Original Message----- From: Alphax [mailto:alphasigmax@gmail.com] Sent: Thursday, August 04, 2005 9:54 AM To: Phroziac; English Wikipedia Subject: [WikiEN-l] Shrinking VFD (was I better shut up)
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
Phroziac wrote:
If VFD were kept, how about un-inlining the closed vfds, and giving links to them instead? Would make the CSDs clutter it somewhat less.
Several people use combinations of Javascript and CSS which allow this to be done. With one click they can hide all closed VFDs.
WikiEN-l mailing list WikiEN-l@Wikipedia.org http://mail.wikipedia.org/mailman/listinfo/wikien-l