<br><br><div class="gmail_quote">On Sun, Mar 21, 2010 at 8:31 PM, hadley wickham <span dir="ltr"><<a href="mailto:h.wickham@gmail.com">h.wickham@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">> I guess it's a question of where to draw the line between the low-level Qt<br>
> bindings and the R API. The Painter object is not bound by smoke, so it<br>
> still has an explicit R API, like qdrawGlyph(), qstrokeColor<-(), etc. Layer<br>
> and PlotView are bound by smoke, but qtpaint still provides R-level<br>
> constructors, mostly for the named argument matching. The R calling<br>
> convention is particularly convenient for constructors, since there often<br>
> several arguments, which usually have reasonable default values.<br>
<br>
</div>It seems like for a given package we should pick one style and stick<br>
with it. Since all the Qt objects are mutable, maybe using $<br>
accessors throughout the API makes the most sense.</blockquote><div><br>I think this is the policy I have followed more or less. Only the
constructors have special wrappers.. and there are some special things
like S3 methods on dim(). <br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> But then we need<br>
to figure out how to document it in a way that works with the usual R<br>
documentation style.<br>
<div><div></div><div></div></div></blockquote><div><br>Since the bindings are dynamic, the documentation should probably also be dynamic. I was thinking of using the R help server to do this. The hard part is the source of the docs. I'm sure this would transformed from the Qt docs. The issue is that installation of the Qt docs is optional (as it takes up a lot of space). But it's possible to access it programmatically, which is nice. One problem is that this would only work through a web-browser, not from within R. It might be possible to use the dynamic Rd features. Have to look into it. <br>
<br>A variant on this would be transforming the docs (from C++ to R) at run-time and then displaying in QtAssistant, which is a much nicer help interface compared to R's.<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div> <br></div></div></blockquote><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div class="h5">
Hadley<br>
<br>
--<br>
Assistant Professor / Dobelman Family Junior Chair<br>
Department of Statistics / Rice University<br>
<a href="http://had.co.nz/" target="_blank">http://had.co.nz/</a><br>
</div></div></blockquote></div><br>