<div dir="ltr"><div>I know it might not be the right time to say this. </div><div>As complex as the R ecosystem is, I've noticed that the RKWard interface crashes when It loads objects that don't satisfy the assumptions of a data frame. As a concrete example the starwars tibble which comes with the dplyr package, contains three lists. It can be loaded to the workspace area, but when the user tries to visualize it on the data viewer the GUI will crash. Could it be possible to stop this from happening? For example, checking if "data.frames" have at least one list (as with the case of that object class: tbl_df;tbl;data.frame) to not load those objects on the data view and returning a warning.</div><div><br></div><div><img src="cid:ii_lycbeipi19" alt="image.png" width="563" height="305"><br></div><div><br></div><div>If loaded, it apparently works with no problem...</div><div><br></div><div><img src="cid:ii_lycbhnh320" alt="image.png" width="563" height="305"><br></div><div><br></div><div>but when scrolling to the right it surely will crash, at least this time, it did.</div><div>On the last linux appimage </div><div><br></div><div> rkward-master-1191-linux-gcc-x86_64.AppImage 2024-07-07 17:11 370M </div><div><br></div><div> this is as far as I could get:</div><div><br></div><div><img src="cid:ii_lycc2rct23" alt="image.png" width="563" height="305"><br></div><div>As soon as I double clicked on the object it crashed the first time I tried... the second time until scrolling to the right.</div><div><img src="cid:ii_lycc5n3w24" alt="image.png" width="563" height="305"></div><div>Hopefully it could aid in building a more robust interface which won't crash when an unaware user tries to use a data.frame/tibble object.</div>Regards<div>Alfonso</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">El jue, 13 jun 2024 a la(s) 8:12 a.m., Thomas Friedrichsmeier (<a href="mailto:thomas.friedrichsmeier@kdemail.net">thomas.friedrichsmeier@kdemail.net</a>) escribió:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi!<br>
<br>
Here's a short update on current progress towards a KF6 (aka KDE 6)<br>
based release of RKWard, and a call to start testing.<br>
<br>
As a bit of background, the transition from KF5 to KF6 is complicated<br>
by the fact, that some Linux distributions do not ship KF6 libraries,<br>
yet, and may not have them in their stable releases for a long time,<br>
while other distributions are already shipping some of our dependencies<br>
(importantly, kate) in a KF6-only version. To address this, I worked on<br>
getting out AppImage builds to a state that is (as far a I know) ready<br>
for productive use. Importantly, the AppImages can now be used with a<br>
full featured R installation on the host system.<br>
<br>
Of course, we plan on having Ubuntu daily builds, again, too, once<br>
backported KF6-libraries are available.<br>
<br>
AppImage packages - as well as Windows and Mac builds - are available<br>
from <a href="https://cdn.kde.org/ci-builds/education/rkward/master/" rel="noreferrer" target="_blank">https://cdn.kde.org/ci-builds/education/rkward/master/</a> . Note that<br>
these packages are generated, automatically, straight from the<br>
development sources, and individual builds have not undergone human<br>
testing. That said, no major problems are currently expected on Linux<br>
and Windows, and we'll need your help to detect an address remaining<br>
issues!<br>
<br>
Unfortunately, on MacOS, the situation is currently more dire. While<br>
packages exist, these have not been tested at all. Since a number of<br>
large changes have been done to platform-dependent code regarding the<br>
startup procedure, there is a fairly high probability that these build<br>
will quite simply fail to start at all (but no major issues are<br>
expected once that difficulty is overcome). The problem is quite simply<br>
that we do not have the hardware for testing and fixing these builds.<br>
<br>
*If you own a Mac, we want your help!* The first step will be to<br>
download and (try to) run the .dmg, and report, what you see. Based on<br>
that, and depending on how much time you're will to invest, I'll be<br>
going to ask you for more info for diagnostics. Thanks!<br>
<br>
Regards<br>
Thomas<br>
</blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div style="text-align:center"><div style="text-align:left">Dr. Alfonso Cano Robles</div><div><br></div><div><br></div><div><span style="background-color:rgb(166,206,57);color:rgb(255,255,255);font-size:16px;font-weight:800;text-transform:uppercase;font-family:"noto sans",sans-serif"> ORCID ID: </span></div><div><span style="font-size:12px;color:rgb(73,74,76);font-family:"noto sans",sans-serif;text-align:start"><a href="https://orcid.org/0000-0002-9496-2301" target="_blank">https://orcid.org/0000-0002-9496-2301</a></span></div><div><img width="96" height="96" src="https://ci3.googleusercontent.com/mail-sig/AIorK4zzvBeSrfsCWgqO8ZlBW-lOqQW4FpVCzUQmszsP0lG1_3_Vliwpuod478N1Nx2fEg9TOgUkpPdYOwf6"></div></div></div></div></div></div></div></div></div>