> I agree with ranking. With the list sorted from the top to
> bottom >>> best to worst, further sorted by date.
How do you rank code? Everyone will be ranking it from a different perspective. I would rank code based on how well it conveys a concept... Others would rank it based on how close to production quality plug-in it is, and yet others would rank it based on the clarity of the code, how well commented it is etc.
It begs the fundamental question, 'What are the archives for?'
Is it to provide learning examples, provide concept code, commercial quality plug-in code etc?
>> Just add a comment after the archive entry if you think
>> something is useless and say why
> Common sense, maybe stretch it a little more with a
> 'report archive' button so one of the mods can look at
> it, then remove it if it is indeed a load of crap! :)
And we have a perfect solution.
> bottom >>> best to worst, further sorted by date.
How do you rank code? Everyone will be ranking it from a different perspective. I would rank code based on how well it conveys a concept... Others would rank it based on how close to production quality plug-in it is, and yet others would rank it based on the clarity of the code, how well commented it is etc.
It begs the fundamental question, 'What are the archives for?'
Is it to provide learning examples, provide concept code, commercial quality plug-in code etc?
>> Just add a comment after the archive entry if you think
>> something is useless and say why
> Common sense, maybe stretch it a little more with a
> 'report archive' button so one of the mods can look at
> it, then remove it if it is indeed a load of crap! :)
And we have a perfect solution.