Hi Walt
Shame your idea couldn't work
Incidentally if you had got something working how would you have portrayed it in the spreadsheet?
(I had imagined for example that we'd could have a colour coding system(or number rating allowing filtering or both) to indicate status. e.g
Blue -anything by Erel, or any code handed over to Erel or any class still clearly in use with out any recognised forum indicated faults.
Green - libs with no known faults and are clearly supported and or well used/core libs, (scroll2d, reflections etc), most classes (as you can then modify and fix yourself)
Yellow, beta releases, current items with possible issues unanswered forum queries
may be depreciated but still usable
yellow current libs with potential issues or unresvoled issues, or beta mature beta Bob valentines table class
pink - has unresolved issues , author support unlikely
red - major issues, author no longer a member or been off line for ? years, should be binned or moved to old libs
white/blank those that have not been "scored" by us or forum yet
And I suppose if started, could leave all white except for Erel stuff, and we do as and when with help from others, but your call entirely.
Incidentally from a grand total 2474, I unscientifically tried ordering on reverse date to more easily see potentially archivable stuff and then filtered out Erel leaving only 1973 items. Filtering out several names such as Don Manfred (who does archive old stuff) and then several others including Johan, Klaus, and a list of about 40 authors who appear current or core contributors, whittling it down to 837 !, and then after removing snippets, tutorials and others got it down to 459

. I could then have removed all those created in last year, and removed others names but ran out of time...
However this showed why only looking at things individually will do ..
The top (bottom?) of the list was MTWs Clipboard library of Jan 2011. Doesn't appear to be any significant issues and might still be an entirely usable product but MTW, although a a licensed member has not been seen online since May 2014. So would I risk using this code if not in Erels possession ( or he could support). Probably not
Obviously throughout all the development world, we continually have to make judgement calls on risk of using various products and libs and hopefully at some point in B4x we'll improve the way we can avoid redundant libs and code without negatively affecting B4A and it's community in anyway
