[ruby-talk:7572] Re: flatten_by(n)

"Conrad Schneiker" <[e-mail]> writes:

> But more generally speaking, do we need something of a "sub-module RAA" of 
> sorts to collect and catalog for all the useful methods that people 
> continually come up with to deal with various tasks and problems that they 
> encounter? IMHO, yes. (We could still use modules for packaging these 
> mostly individual methods, I suppose, with some sort of mnemonic 
> class+method naming convention.)

An excellent idea, but I'm not sure it fits comfortably with the
archive. I think the online Ruby chips need to sit in a different kind 
of setting, one which is more open to people editing within each
article.

I briefly had a look at Faq-o-matic as a way for hosting this, but
felt it was too restrictive. I suspect we may end up writing out own.

Some requirements might include:

1. Ability to execute the code, so that we know it works, and attach
   the output to the example (sort of like the library reference does)

2. Ability to hide scaffolding code, so that only the relevant snippet 
   is displayed.

3. Ability to download code: by example, by topic, or globally.

4. Simple submission scheme

5. Workflow management of peer review queue

6. Consistent indexing, with keywords

7. Ability to have the same snippet appear under different headings
   (for example arr1 - arr2 might appear under 'Set Operations' and
   'Stop Word Removal')

8. Internally stored in a presentation-neutral format, so that we can
   publish it different forms (including a real book if the quality if 
   high enough).


I'm sure there are others.


Dave



(There's a new thread on the wiki for this now)