Am Montag, 6. Oktober 2014, 20:28:45 schrieb Thomas Friedrichsmeier:
> - Providing better control over which plugins are active. I'm still not 
> convinced, the level of individual plugins is (typically) the right 
> granularity of control, but in fact, control should be more fine-grained
> than  the current "official" pluginmaps, and esp. more fine-grained than
> simply using all.pluginmap, by default.

are there R functions yet to enable/disable plugins? you know, if there were, 
in combination with rk.list.plugins() i could simply write my own plugin for 
that control.

a function which lists all meta (like <about>, <dependencies> and info on the 
menu structure) information on plugins would also be great, because the name 
alone doesn't explain so much.

viele grüße :: m.eik

  dipl. psych. meik michalke
  institut f"ur experimentelle psychologie
  abt. f"ur diagnostik und differentielle psychologie
  heinrich-heine-universit"at d-40204 d"usseldorf

Attachment: signature.asc
Description: This is a digitally signed message part.

Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
RKWard-devel mailing list

Reply via email to