[rkward-devel] a new approach to external plugins
Thomas Friedrichsmeier
thomas.friedrichsmeier at ruhr-uni-bochum.de
Fri Sep 2 07:03:06 UTC 2011
Hi,
On Thursday 01 September 2011, meik michalke wrote:
> for instance, you can assume that every varaible in the dialog
> will be used in the JS file at some point, so they could all be added
> there automatically as well. the same way you could have an automatic help
> file outlined -- then it really starts to save time, typing and looking up
> in docs ;-)
ok, yes, this sounds like an interesting direction, indeed.
> > Why don't you place them next to the "rkward" and "rkwardtest" packages
> > in SVN (perhaps as "rkwarddev")? We can still wait for them to mature
> > some more (if necessary), before we add them to the installation
> > (rpackage_install.cmake.in).
>
> fine, i'll do that. the dependency should be taken care of somehow, though.
> or does RKWard draw in other packages at installation time anyway?
Good point. This will be a problem. We cannot even assume an internet
connection during RKWard installation. It might be possible to work around
this by putting
require (XiMpLe)
in .onLoad() / .First.lib(). This would delay the installation of the
dependency until the package is first loaded.
Or of course the XML functions would have to be included, for the time
being...
Regards
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/rkward-devel/attachments/20110902/f0f20bb6/attachment.sig>
More information about the Rkward-devel
mailing list