> The real answer was Task Views on CRAN (most of the OQs topics *are* already > Task Views), so crantastic is very partial. If you have a little time and want
I think crantastic and task views solve somewhat different problems (although I agree that crantastic should mirror the task views too). Task views are of considerable effort to set up, and often written by one person. Tags on crantastic are dead simple to set up and can be contributed to by multiple people (although I'm not yet sure what to do about potential conflicts) > to really draw in the masses, try doing clickable image maps from the > Bioconductor pkgDepTools: > > http://bioconductor.org/packages/2.1/bioc/html/pkgDepTools.html > > because some of the unobtrusive short-name packages are key nodes in package > dependency graphs. The dependency trees are very illuminating. Automating the > updates would be positive. If you could also run against the Task View > listings, That's a good idea. I do mean to add dependency links in both direction, and to automate the updates I just need to get a cron job set up. Hadley > Roger > > > The intent isn't to provide large in-depth reviews, but to make it > > easy to add comments like yours above. I agree it would be also nice > > to have some central place that lists all articles which cite a given > > R package, but that would be a lot of work. > > > > Hadley > > > > > ______________________________________________ > R-help@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-help > PLEASE do read the posting guide http://www.R-project.org/posting-guide.html > and provide commented, minimal, self-contained, reproducible code. > -- http://had.co.nz/ ______________________________________________ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
