IRC log for #brlcad on 20160919

00:36.03*** join/#brlcad LordOfBikes_ (~armin@dslb-092-075-146-120.092.075.pools.vodafone-ip.de)
01:09.08starseekerryoshu: um.  our misc/CMake/FindTINYCTHREAD.cmake file may need tweaking
01:09.29starseekerryoshu: we have a third party lib management system that relies on find_package working
01:09.35starseekerNotify: ping
01:09.57starseeker``Erik: did notify get backed up again?
01:10.41ryoshustarseeker: do you know how to tweak it?
01:10.46ryoshuI have no clue
01:10.55ryoshuwhy it cannot find libs
02:18.01*** join/#brlcad kintel (~kintel@unaffiliated/kintel)
02:31.57*** join/#brlcad kintel (~kintel@unaffiliated/kintel)
03:49.59*** join/#brlcad teepee_ (~teepee@unaffiliated/teepee)
04:05.48*** join/#brlcad amarjeet (~Amarjeet@169.149.151.37)
04:41.48*** join/#brlcad amarjeet_ (~Amarjeet@169.149.138.79)
08:04.35*** join/#brlcad gaganjyot_ (~gaganjyot@138.91.194.195)
08:46.52*** join/#brlcad d_rossberg (~rossberg@104.225.5.10)
09:50.15Notify03BRL-CAD:starseeker * 68844 (brlcad/trunk/src/libpkg/example/client.c brlcad/trunk/src/libpkg/example/server.c): start simplifying my old attempt at understanding libpkg. Can send basic data from server to client now and assemble data in the client as exmplified by all_msgs collecting vls. Still need to demonstrate sending more interesting stuff from client back to server...
09:52.01Notify03BRL-CAD:starseeker * 68845 (brlcad/trunk/src/libpkg/example/client.c brlcad/trunk/src/libpkg/example/ntp.h brlcad/trunk/src/libpkg/example/server.c): More simplification of the example, demonstrate data going back from client to server.
09:52.04Notify03BRL-CAD:starseeker * 68846 (brlcad/trunk/src/libpkg/example/CMakeLists.txt brlcad/trunk/src/libpkg/example/client.c brlcad/trunk/src/libpkg/example/server.c): Rename example header defining protocol.
09:52.44Notify03BRL-CAD:starseeker * 68847 brlcad/trunk/src/conv/CMakeLists.txt: Still crude and limited to the point of being essentially nonfunctional, but since it can at least import something it's time to checkpoint. Working in importer for DYNA finite element models - examples can be found at http://www.ncac.gwu.edu/vml/models.html
10:35.54*** join/#brlcad amarjeet (~Amarjeet@169.149.167.172)
12:46.43*** join/#brlcad teepee_ (~teepee@unaffiliated/teepee)
13:31.16*** join/#brlcad yorik (~yorik@179.99.47.84)
14:55.37*** join/#brlcad kintel (~kintel@unaffiliated/kintel)
15:06.34Notify03BRL-CAD:starseeker * 68848 brlcad/trunk/misc/CMake/BRLCAD_CPackOptions.cmake.in: We need CPACK_PACKAGING_INSTALL_PREFIX if we're doing an RPM...
15:18.39*** join/#brlcad Caterpillar (~caterpill@unaffiliated/caterpillar)
15:28.57*** join/#brlcad kintel (~kintel@unaffiliated/kintel)
15:33.25Notify03BRL-CAD:d_rossberg * 68849 (rt^3/trunk/include/brlcad/BagOfTriangles.h rt^3/trunk/src/coreInterface/BagOfTriangles.cpp and 2 others): activated the bag-of-triangles primitivea first test was successful but it's still experimental
16:08.53*** join/#brlcad amarjeet (~Amarjeet@169.149.168.192)
17:08.08*** join/#brlcad amarjeet_ (~Amarjeet@169.149.169.25)
17:23.49*** join/#brlcad amarjeet (~Amarjeet@169.149.187.174)
17:29.19*** join/#brlcad amarjeet_ (~Amarjeet@169.149.187.174)
17:49.08brlcadstarseeker: cool to see the pkg work -- note that gtransfer in src/gtools is essentially such an example sending "more interesting stuff" mentioned in 68844
17:49.47brlcadif it didn't introduce a library dependency, it would have made a good stand-alone example
18:22.50starseekerbrlcad: I was looking for a sort of "hello world" for libpkg - gtransfer might have helped, but a lot of what I ran into in 68844-68846 was surprising to me.  I think it's starting to make sense, but having to set pks_user_data in the callback threw me for a while
18:24.11starseekerthe "interesting stuff" I was talking about in 68844 actually ment "any kind of data payload moving from client back to server." ;-)
19:40.30brlcadstarseeker: yep, got that
19:42.09brlcadtpkg tries to be a hello world of sorts, coming in around 224 lines for both client and server
19:43.29brlcadgtransfer comes in at 330 lines as an example transferring a real payload, specific data
19:44.27brlcadalso, you shouldn't have set pks_user_data in the callback .. and I don't see where you're doing that
19:45.23Notify03BRL-CAD:starseeker * 68850 brlcad/trunk/src/conv/dyn-g.cpp: Import the individual element shell lines with part groupings, one bot per part id.
19:46.04brlcadit's a user data pointer, set on the connection via the switch table (allowing different data per message type)
19:51.32Notify03BRL-CAD:starseeker * 68851 brlcad/trunk/src/conv/dyn-g.cpp: flip triangles around - this needs more careful study to determine the right way to create these...
19:52.20starseekerbrlcad: sorry, that's what I ment
19:52.25starseeker(setting it in the table)
19:52.45starseekerinitially I tried to set it in the pkg_conn, and was surprised when the table overwrote it
19:53.38starseekerat some point I'll try to properly doxygenify up pkg.h and add some examples in there, but the main goal right now was for me to understand enough to be able to get it going if it turns out we need it
20:21.43Notify03BRL-CAD:starseeker * 68852 brlcad/trunk/src/conv/dyn-g.cpp: Make some regions to and hierarchy to organize things a bit.
20:52.17*** join/#brlcad LordOfBikes (~armin@dslb-092-075-146-120.092.075.pools.vodafone-ip.de)
21:02.01*** join/#brlcad LordOfBikes (~armin@dslb-092-075-146-120.092.075.pools.vodafone-ip.de)
21:08.26Notify03BRL-CAD:starseeker * 68853 brlcad/trunk/src/conv/dyn-g.cpp: Part objects appear to have meaningful names - grab them for the regions.
21:14.32brlcadstarseeker: yeah, that probably shouldn't happen or be better documented
21:14.46brlcador not exist with the same name in two places
21:16.15brlcadit's not clear to me why there's a pointer in pkg_conn given the switch is in there already
21:16.44brlcadnote that pks_user_data is relatively brand new
21:26.56starseekerbrlcad: is libpkg one server - one client, or can there be multiple clients?
21:29.04brlcadthere can be multiple clients
21:29.32brlcadthe single server, single client example you started with was just for simplicity
21:30.12brlcada simple chat room would probably be a good example of that
21:35.14*** join/#brlcad LordOfBikes (~armin@dslb-092-075-146-120.092.075.pools.vodafone-ip.de)
22:11.35*** join/#brlcad LordOfBikes (~armin@dslb-092-075-146-120.092.075.pools.vodafone-ip.de)
22:15.17*** join/#brlcad LordOfBikes (~armin@dslb-092-075-146-120.092.075.pools.vodafone-ip.de)
22:31.07*** join/#brlcad kintel (~kintel@unaffiliated/kintel)
22:35.50*** join/#brlcad kintel (~kintel@unaffiliated/kintel)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.