| 00:24.32 | *** join/#brlcad KimK (~Kim__@ip68-102-66-31.ks.ok.cox.net) |
| 00:34.20 | *** join/#brlcad asad__ (~asad00@host59-2.natpool.mwn.de) |
| 00:46.50 | *** join/#brlcad asad_ (~asad00@host10-2.natpool.mwn.de) |
| 00:52.58 | *** join/#brlcad fxfkidyfwkoqvzdn (~armin@dslb-088-066-145-016.088.066.pools.vodafone-ip.de) |
| 03:35.08 | *** join/#brlcad ickby_ (~stefan@x5d8476b6.dyn.telefonica.de) |
| 03:53.59 | *** join/#brlcad tandoorichick (~Thunderbi@117.222.155.140) |
| 04:46.25 | *** join/#brlcad Shalom (~Shalom@122.175.14.179) |
| 05:07.08 | *** join/#brlcad amarjeet (~amarjeet@202.164.53.117) |
| 06:40.22 | *** join/#brlcad teepee_ (~teepee@unaffiliated/teepee) |
| 07:02.27 | *** join/#brlcad merzo (~merzo@11-143-53-37.pool.ukrtel.net) |
| 08:28.04 | *** join/#brlcad sniok (~sniok@89.252.29.238) |
| 08:29.16 | *** join/#brlcad d_rossberg (~rossberg@104.225.5.10) |
| 08:38.42 | *** join/#brlcad asad_ (~asad00@host10-2.natpool.mwn.de) |
| 08:53.17 | *** join/#brlcad merzo (~merzo@user-94-45-58-141.skif.com.ua) |
| 09:00.54 | *** join/#brlcad teepee` (bc5c2134@gateway/web/freenode/ip.188.92.33.52) |
| 09:58.33 | *** join/#brlcad skat00sh (uid103741@gateway/web/irccloud.com/x-yoahcokdfsdlgpud) |
| 10:08.57 | *** join/#brlcad d_rossbe1g (~rossberg@104.225.5.10) |
| 10:26.16 | *** join/#brlcad Shalom (~Shalom@122.175.14.179) |
| 10:27.02 | *** join/#brlcad merzo (~merzo@user-94-45-58-141.skif.com.ua) |
| 10:49.44 | *** join/#brlcad starseeker (~starseeke@104.225.5.10) |
| 11:17.49 | *** join/#brlcad d_rossberg (~rossberg@104.225.5.10) |
| 12:14.07 | *** join/#brlcad asad_ (~asad00@host10-2.natpool.mwn.de) |
| 12:55.41 | *** join/#brlcad yorik (~yorik@189-18-174-137.dsl.telesp.net.br) |
| 13:38.02 | *** join/#brlcad tandoorichick1 (~Thunderbi@117.209.186.234) |
| 14:00.26 | *** join/#brlcad amarjeet (~amarjeet@49.138.64.175) |
| 14:00.28 | *** join/#brlcad shubham (71c1885d@gateway/web/freenode/ip.113.193.136.93) |
| 14:01.06 | *** part/#brlcad asad_ (~asad00@host10-2.natpool.mwn.de) |
| 14:54.26 | *** join/#brlcad kintel (~kintel@unaffiliated/kintel) |
| 15:33.56 | *** join/#brlcad amarjeet (~amarjeet@101.213.150.193) |
| 15:56.32 | *** join/#brlcad tandoorichick (~Thunderbi@45.118.110.233) |
| 15:56.35 | *** join/#brlcad teepee_ (~teepee@unaffiliated/teepee) |
| 16:01.01 | *** join/#brlcad amarjeet (~amarjeet@101.213.150.193) |
| 16:09.24 | *** join/#brlcad sniok (~sniok@89.252.29.238) |
| 16:24.40 | *** join/#brlcad kintel (~kintel@unaffiliated/kintel) |
| 16:27.34 | *** join/#brlcad amarjeet (~amarjeet@101.214.89.173) |
| 16:31.14 | *** join/#brlcad tandoorichick (~Thunderbi@45.118.110.233) |
| 16:37.20 | *** join/#brlcad tandoorichick (~Thunderbi@45.118.110.233) |
| 16:42.08 | *** join/#brlcad Mathnerd314 (~quassel@supertux/Mathnerd314) |
| 17:00.23 | *** join/#brlcad tandoorichick (~Thunderbi@45.118.110.233) |
| 17:03.12 | *** join/#brlcad Mandeep_Singh (~mandeep@45.127.64.21) |
| 17:08.29 | *** join/#brlcad amarjeet (~amarjeet@49.138.191.193) |
| 17:14.56 | *** join/#brlcad amarjeet (~amarjeet@49.138.191.193) |
| 17:25.53 | *** join/#brlcad brlcad (~sean@104.225.5.10) |
| 17:33.44 | *** join/#brlcad amarjeet (~amarjeet@101.215.19.181) |
| 17:40.39 | *** join/#brlcad asad_ (~asad00@host10-2.natpool.mwn.de) |
| 17:48.38 | *** join/#brlcad shubham (71c1885d@gateway/web/freenode/ip.113.193.136.93) |
| 17:54.53 | *** join/#brlcad tandoorichick (~Thunderbi@117.249.248.248) |
| 18:01.15 | *** join/#brlcad kintel (~kintel@unaffiliated/kintel) |
| 18:39.32 | *** join/#brlcad tandoorichick (~Thunderbi@117.249.248.248) |
| 18:43.10 | *** join/#brlcad merzo (~merzo@183-98-133-95.pool.ukrtel.net) |
| 19:27.37 | *** join/#brlcad asad_ (~asad00@host10-2.natpool.mwn.de) |
| 20:20.57 | brlcad | asad_: so if you looked through the ideas page, did anything jump out? |
| 20:21.32 | asad_ | For me given that it would be my first time contributing to brlcad. |
| 20:21.47 | asad_ | the GUI feature requests were most interesting |
| 20:23.07 | brlcad | they're also some of the more complicated :) |
| 20:24.04 | asad_ | hmm so it would be great if you can help me define a task that would suite a beginner contributor |
| 20:24.07 | brlcad | so a topic came up just recently that would be really great to see come to fruition, something not on the list I believe |
| 20:25.12 | brlcad | basically, a stand-alone double-clickable geometry viewer application that automatically displays a given model |
| 20:25.49 | brlcad | kind of like 3D-PDF, but using our infrastructure instead of Adobe's |
| 20:27.22 | brlcad | ideally, want a single "file" that can be e-mailed around |
| 20:28.42 | asad_ | so from what i gather, it's kind of a portable brlcad (mged) |
| 20:29.19 | brlcad | not quite -- don't want or need editing or creation |
| 20:29.38 | asad_ | you can view models if you have the entire brlcad suite installed but with this the aim is to just display a model file. |
| 20:29.39 | brlcad | just a simple read-only viewer for a given model (so no file->open loading, just show me the model) |
| 20:29.58 | asad_ | ah seems interesting |
| 20:30.03 | brlcad | so the .g model is somehow integrated into this "file" |
| 20:30.06 | Stragus | Model and everything bundled in the executable? Interesting |
| 20:30.11 | brlcad | yes |
| 20:30.44 | asad_ | yeah making a separate tool sounds fun but let's see the complexity |
| 20:31.23 | brlcad | my thought is that the .g file can be simply concatenated to the end of a given viewer executable, then the app can just seek to find it (.g have identifiable header bytes) |
| 20:32.00 | brlcad | our libdm library will draw the geometry for you into an application context |
| 20:32.16 | brlcad | so it will work for CSG models, triangle models, NURBS geometry, etc |
| 20:33.29 | brlcad | for the front-end application, you could use Qt or OSG or just about anything really so long as we can static link it all down to a single thing |
| 20:34.47 | Stragus | I would put some struct describing the file's content at the end, seek at the end and get the data |
| 20:35.56 | brlcad | little more complicated compilation setup, but could also work |
| 20:36.26 | brlcad | especially cross-platform building |
| 20:37.46 | brlcad | asad_: what do you think? sound interesting? |
| 20:38.54 | asad_ | yeah it is, the task is very precise and clear but i;m a bit lost on the g file format. maybe i need to look into it more because the heavy lifting is going to be done by libdm |
| 20:39.15 | brlcad | librt will read the .g file and it's geometry for you |
| 20:39.46 | brlcad | or might even be able to use libged, a higher-level library |
| 20:40.13 | brlcad | either way, you'll end up calling db_open or ged_open after you find the header bytes |
| 20:40.54 | brlcad | could use any tech or libs or language, so long as the end result is a single file that can be e-mailed and double-clicked to see the geometry for at least mac, windows, linux, bsd |
| 20:42.10 | asad_ | single file? is it a standalone executeable that can used to open any .g file e.e.,g <exe> xyz.g OR something else |
| 20:42.49 | brlcad | single file .. exe that has the .g embedded IN it |
| 20:43.07 | brlcad | not any .g |
| 20:43.12 | asad_ | oh |
| 20:43.47 | asad_ | now i get your 3D-PDF example |
| 20:45.16 | brlcad | so I assume you've run mged, if you've opened moss.g for example (a typical dev test model), it would be like creating a moss.exe binary (on windows) or a moss.app bundle (on Mac) etc |
| 20:46.38 | brlcad | the visual for starters could simply be the same display that mged shows when you run the "attach" command (e.g., try "attach X" on linux or "attach wgl" on windows after opening moss.g and running "draw all.g") |
| 20:54.06 | brlcad | asad_: what is the coding socis timeline? |
| 20:54.29 | asad_ | 1st June till 30th August |
| 20:55.36 | brlcad | cool, that should be plenty of time and there are many ways the interface can be extended once you get basic viewing working |
| 20:55.59 | asad_ | 1-14 September evaluation |
| 20:56.22 | brlcad | first step, if this sounds viable to you, will be to itemize the basic milestones and tasks, just a dozen or so |
| 20:56.47 | brlcad | something like the PROJECT listings you can see in the doc/STRATEGY file would be perfect |
| 20:57.48 | asad_ | got it |
| 20:58.23 | asad_ | I will also update the design document, so that you can review it and then we can put the initial version on the wiki. |
| 20:58.36 | brlcad | be sure to check out the 'isst' utility in addition to basic familiarization with 'mged' and/or 'archer' |
| 20:58.39 | brlcad | great |
| 20:59.16 | asad_ | yeah that's my first priority to play around with mged as much as possible and trace the function calls. |
| 20:59.22 | brlcad | isst is an existing viewer interface that doesn't use libdm, instead using ray tracing |
| 20:59.26 | brlcad | mged and archer both use libdm |
| 21:00.08 | brlcad | there is a LOT of compilated code to navigate there, so don't be shy to share questions or progress here |
| 21:00.42 | brlcad | especially questions about the code, there's a half dozen guys here that can point you to the right file or function in seconds for questions that might take you hours exploring on your own |
| 21:01.25 | asad_ | sure, btw do we have a documentation for source code function call type diagram for basic mged operations? |
| 21:01.35 | asad_ | yeah that sounds good to |
| 21:01.37 | brlcad | treat the codebase like a big city .. some parts clean, some parts slum, some parts very densely occupied, etc ;) |
| 21:02.18 | asad_ | great, also can we do a ESOCIS weekly status meeting here? |
| 21:02.25 | brlcad | most mged functions end up in libged which in turn ends up down in librt |
| 21:02.53 | brlcad | yeah, we can see how the progress goes throughout the week |
| 21:03.04 | asad_ | what days/times work for you? |
| 21:03.17 | brlcad | I read the logs, so if you share progress while you work, we won't need a specific day/time |
| 21:03.26 | asad_ | and what's your time zone :) |
| 21:03.56 | brlcad | UTC-4 |
| 21:05.25 | asad_ | Ok that works for me too. But usually in status meetings the plan was to try to summarize weekly work and advertise next week's tasks. |
| 21:07.39 | asad_ | plus it's easy to sync up. |
| 21:09.34 | asad_ | I would suggest every Friday 16:00 (UTC-4) |
| 21:12.55 | Notify | 03BRL-CAD:ejno * 68038 (brlcad/trunk/include/rt/func.h brlcad/trunk/include/rt/misc.h and 2 others): work on rt_reduce_db(); collapses hierarchy but does not attempt to preserve attributes |
| 21:19.46 | brlcad | weekly summaries can also go to your dev log and/or the dev mailing list (you should introduce yourself in the new few days) |
| 21:20.12 | asad_ | sure, I will. |
| 21:20.35 | asad_ | Thanks for clarifying. |
| 21:22.43 | brlcad | I'll send a brief welcoming introduction now and you can follow-up :) |
| 21:49.35 | *** join/#brlcad LordOfBikes (~armin@dslb-088-066-145-016.088.066.pools.vodafone-ip.de) |