Print methods for widgets and rendering in R Markdown about htmlwidgets HOT 5 CLOSED

Can you elaborate more on why you want to postpone calling createWidget? I would like to understand the use case better before heading down this path.

from htmlwidgets.

One of the reasons for this is that a different S3 method is used for the
knitr case. In that case it's actually the knit_print method rather than
the print method so you probably just need to explicitly implement
knit_print. See:

https://github.com/ramnathv/htmlwidgets/blob/master/R/knitr-methods.R#L36-L38

On Mon, Dec 29, 2014 at 6:55 PM, Ramnath Vaidyanathan <
[email protected]> wrote:

Can you elaborate more on why you want to postpone calling createWidget?
I would like to understand the use case better before heading down this
path.

—
Reply to this email directly or view it on GitHub
#59 (comment).

from htmlwidgets.

@ramnathv, the idea for postponing is that in this case the object to be passed to createWidget will be built incrementally and the most natural way to view the widget is through printing the final object (think of building a plot object through a series of commands and then simply typing the name of the plot object to show it). Regardless of that, I suppose the real issue is reliably displaying widgets through a print method.

@jjallaire, your suggestion worked - thanks - I had gone down that route but missed the registerMethods stuff that was required to make it work. I'll close.

from htmlwidgets.

Okay, glad that worked!

Curious about the widget you are working on -- can you share any details about it at this point?

from htmlwidgets.

@hafen, I think I understand your use case. Note that it is possible to construct the plot using createWidget and then manipulate it downstream as you would manipulate any R object. My implementation of rCharts for htmlwidgets uses this design pattern and is consistent with how ggvis does it.

from htmlwidgets.