Hi,
Thomas:
Can you take a look at rk.sync.Rd and rk.call.plugin.Rd, esp the TODO places.
I've added a rk.list.plugins (...) to public.R, I hope it is not
adding a "new feature." While documenting rk.call.plugin, I felt that
the user generally will have no idea of what goes as the first
argument ("plugin"). Is there any way to improve this? Right now, I am
just scanning the pluginmap files... Can the C++ side list all the
available plugins? If not, is there any automatic way to know the
"path" argument there?
Regards,
--
Prasenjit
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
RKWard-devel mailing list
RKWard-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rkward-devel
