[RQt-devel] next steps

[Michael Lawrence]

On Fri, Nov 13, 2009 at 5:56 AM, Deepayan Sarkar
<deepayan.sarkar at gmail.com>wrote:

> Hi (Michael, mostly),
>
> I'm at the stage where I'm happy with updates to qtutils, which is
> basically all R code, using signals etc.
>
> My next target is qtdevices, i.e., a traditional R graphics device
> using QGraphicsScene. Is this feasible at this point? I've checked in
> a few relevant questions in qtbase/questions.txt, the first couple of
> which would help me plan my next steps:
>
>
>  o Can we use user-written classes (defined in C++) from R yet? e.g.,
>   RSyntaxHighlighter
>
>
Yes, this is possible. Check out, for example, the class wizard demo.


>  o Related question: Let's say I want to manipulate a QWidget in
>   native code; e.g.
>
>   In R:
>
>      edit <- Qt$QTextEdit()
>
>   The in C++:
>
>      QTextEdit *editor = getPointer(edit);
>      RSyntaxHighlighter *highlighter =
>          new RSyntaxHighlighter(editor->document());
>
>   unwrapQWidget() doesn't work obviously, as it uses the old model.
>   What would be the equivalent in the new world?  If this is
>   available, then we probably get some flexibility in using both the
>   old and new models together, even if we can't easily make new C++
>   classes available in R.
>
>
>
This would be unwrapSmoke().


> Any thoughts?
>
> -Deepayan
> _______________________________________________
> Qtinterfaces-devel mailing list
> Qtinterfaces-devel at lists.r-forge.r-project.org
>
> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/qtinterfaces-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.r-forge.r-project.org/pipermail/qtinterfaces-devel/attachments/20091113/9d6dfc1e/attachment.htm