Log from 2019-03-07:
[08:57:55] *** Quits: physkets (~physkets@unaffiliated/physkets) (Quit: physkets)
[11:06:42] *** Joins: physkets (~physkets@unaffiliated/physkets)
[14:54:47] *** Quits: physkets (~physkets@unaffiliated/physkets) (Quit: physkets)
[14:56:52] <Lucifer_arma> woo-hoo! Gotta love addict thinking, heh. My brain is trying to convince me I've been sober "long enough" and that "one night isn't going to hurt you"
[14:57:08] <Lucifer_arma> I knew this was coming, I just didn't know when ;)
[15:48:56] <Z-Man> Go wetware!
[17:43:56] <Lucifer_arma> Z-Man: https://wiki.qt.io/Using_3D_engines_with_Qt
[17:44:20] <Lucifer_arma> I'm currently researching (procrastinating) how to make an android port of arma during a prospective from-scratch rewrite
[17:48:11] <Lucifer_arma> https://discourse.panda3d.org/t/panda-in-pyqt/3964/27 <--- gets us to cross-platform desktops with PyQt5 as the widget library
[17:48:55] <Lucifer_arma> the client would have panda3d, PyQt5, and the python standard library as dependencies. The server *could* have PyQt5 as a dependency, but doesn't have to, since everything *it* needs is in the python standard library
[17:49:31] <Lucifer_arma> the android/ios clients would need their own 3d engine, but could still use PyQt5 and the python standard library
[17:49:57] <Lucifer_arma> so, my tentative vote for a rewrite is Panda3d + PyQt5, arma code is pure python
[17:50:38] <Lucifer_arma> (it's only a tentative vote until someone actually tests this combination and clears it for the level of performance we need)
[17:53:00] <Lucifer_arma> of course, if we can find a way to get panda3d on android using the python interpreter that gets built for pyqt5 during deployment, then we're golden in all possible ways
[17:53:14] <Lucifer_arma> panda3d "works" on android as-is, but requires a fair amount of work
[17:53:59] <Lucifer_arma> but if we figure it out, we could contribute those changes upstream and let the panda3d team worry about maintaining them :)
[18:09:08] <Lucifer_arma> aaaand, with this: https://doc.qt.io/qt-5/qt3d-index.html <--- we can stick with C++ and switch to Qt5, which will eliminate pretty much every dependency we have and replace them with one massive dependency that, nevertheless, simplifies building
[18:09:36] <Lucifer_arma> if we do that, we get automatic android and ios support. So, if we stick with C++, Qt5 gets my enthusiastic support.
[19:49:30] <Lucifer_arma> I am uncomfortable with the amount of banging I hear from my upstairs neighbor. It's a bit unusual to hear that much banging being done legitimately, but it's not completely unheard of.
[21:29:17] *** Joins: zmanuel (~Z-Man@p4FE3EA50.dip0.t-ipconnect.de)
[21:29:18] *** Z-Man is now known as Guest71504
[21:29:18] *** Quits: Guest71504 (~Z-Man@p4FE3EBCF.dip0.t-ipconnect.de) (Killed (tepper.freenode.net (Nickname regained by services)))
[21:29:18] *** zmanuel is now known as Z-Man
[21:35:24] *** Quits: Lucifer_arma (~email@example.com) (Read error: Connection reset by peer)
[21:35:54] *** Joins: Lucifer_arma (~firstname.lastname@example.org)
[21:59:36] <Armanelgtron> will armagetron pick up multithreading along the way? IIRC Qt has built in threading
[21:59:44] <Armanelgtron> would
[22:40:59] <Lucifer_arma> Armanelgtron: last I checked, it already had multithreading
[22:55:02] <Armanelgtron> only for authentication, right?
[23:43:40] *** Joins: physkets (~physkets@unaffiliated/physkets)
View entire month
DISCLAIMER: These logs of public chat may contain some content which may not be appropriate for all audiences. Use at your own risk.
Logs from 2006-2009 pulled from wrtlprnft
Format changes at: 2015-08-25, 2017-02-20, and 2020-03-23. Times (2015 and later) should be Eastern.