<div dir="ltr">On Tue, Apr 9, 2013 at 3:51 PM, Michael Lawrence <span dir="ltr"><<a href="mailto:lawrence.michael@gene.com" target="_blank">lawrence.michael@gene.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Jason,<br><div class="gmail_extra"><br><br><div class="gmail_quote"><div class="im">On Tue, Apr 9, 2013 at 12:51 AM, Jason S. Iacovoni <span dir="ltr"><<a href="mailto:jason.iacovoni@inserm.fr" target="_blank">jason.iacovoni@inserm.fr</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Dear List</div><div><br></div><div>I have previously developed a lot of GUIs for my bioinformatics programs using Qt (in C++). But nowadays, I find I spend most of my time in R. Thus I was initially quite excited when I found out about visnab, ggobi, exploRase and qtbase. Before I start porting my library into R, I want to know what exactly is the planned future for qtbase. While I understand that SMOKE does a lot of the work bringing Qt into R, is it possible that this package will become abandoned in the future?</div>
</div></blockquote><div><br><br></div></div><div>The qtbase package is not abandoned. It's just fairly mature. I was working last week on Qt 5 support, but it turns out that Smoke just isn't ready. The cranvas project is actively developing on top of qtbase and qtpaint. <br>
<br></div></div></div></div></blockquote><div> </div><div style>Sounds great, will definitely want to use qtpaint and cranvas as well once the underlying nuts and bolts are in place.</div><div style> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><div class="im"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">
<div><br></div><div>From my googling and list reading, it seems that visnab is not active</div></div></blockquote></div><div><br>visnab has been on the back burner as Tengfei worked on ggbio and other
things for his thesis. The good news is that his new job is likely to
support continued development of the software. Actually, he fixed a bunch of bugs in visnab last week.<br> <br></div><div class="im"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><div> and that ggobi is mentioned as the current project.</div></div></blockquote><div><br></div></div><div>I think you mean the anagram "ggbio"..<br></div></div></div></div></blockquote><div><br>
</div><div style>Ok, my bad. I now see that there are 2 different projects. I think my brain never processed the 2 different spellings. Thanks.</div><div style> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><div> But in looking at exploRase, which imports rggobi, it appears to use Gtk2 and not Qt. </div></div></blockquote><div><br></div></div><div>exploRase is my PhD project which some day might be reimplemented using cranvas or something web-based. The GGobi/rggobi project is mostly in "end of life mode" though. RGtk2 is still very much maintained and supported. <br>
<br></div><div class="im"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>At the same time, I see that getting a Windows package for qtbase is moving forward. But this particular list seems very quiet, almost too quiet, so I am hesitant.</div>
<div><br></div></div></blockquote><div><br></div></div><div>Once there is a Windows version, things may be more active. So much is being done on the web these days when it comes to GUIs, but there is still a niche for the desktop.<br>
<br></div></div></div></div></blockquote><div><br></div><div style>Definitely important. The whole goal of Qt has been to be cross platform. Also a very strong advantage to R, so I praise the people working on this and wish them success. And congrats to those that made it possible on Mac, I have never found it easy to build my Qt libs and apps on Mac.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><div></div><div>In any event, I am very confused about the present and the future of qtbase as the library looks perfectly suitable for me to port my C++/Qt code into R. But I would hate to get started on this only to find that developers are moving off to other GUI toolkits and find that my library depends on an abandoned project.</div>
<div><br></div></div></blockquote><div><br></div></div><div>At least for Linux and Mac, you should expect qtbase and qtpaint to be maintained and further developed into the foreseeable future.<br></div><div class="im"><div>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><div></div><div>Finally, I seem to be finding myself learning loads of packages that list Michael Lawrence as an author. Is this really one single person? Are there clones available for hire?</div><div>
<br></div></div></blockquote><div><br></div></div><div>The closest thing to my clone is still 8 years old. Have not yet found a way to accelerate aging.<br> <br></div></div></div></div></blockquote><div><br></div><div style>
Accelerated aging only applies to the parents, not the kids. While you are getting older faster, your kids only appear to you to be aging faster. I do not think I will let this coding project go that long. Thanks for your replies and I will get started on porting my stuff using qtbase.</div>
<div style><br></div><div style>And I might as well add that I feel like I owe you an enormous thanks for all your work on all the packages I use, from IRanges to rtracklayer, as well as the Qt-based packages. It has been a steep learning curve, but we are well underway now processing our Chip-seq data in R. When I started these projects about 10 years ago, none of this infrastructure was in place.</div>
<div style><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><div>Michael<br><br></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><div></div><div>Thanks</div><div>jiaco</div>
</div>
<br>_______________________________________________<br>
Qtinterfaces-devel mailing list<br>
<a href="mailto:Qtinterfaces-devel@lists.r-forge.r-project.org" target="_blank">Qtinterfaces-devel@lists.r-forge.r-project.org</a><br>
<a href="https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/qtinterfaces-devel" target="_blank">https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/qtinterfaces-devel</a><br></blockquote></div><br></div>
</div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Jason S. Iacovoni<br>Bioinformatic Plateau<br>05.61.32.56.18<div><span style="border-collapse:collapse;font-family:arial,sans-serif;font-size:13px">INSERM / UNIVERSITE PAUL SABATIER UMR 1048<br>
Institut des Maladies Métaboliques et Cardiovasculaires (I2MC)</span></div><div><span style="border-collapse:collapse;font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial;font-size:small;border-collapse:separate">Building L4, Room 106<br>
</span>1 avenue Jean Poulhès - BP 84225<br>31432 Toulouse Cedex 4</span><br></div>
</div></div>