IRC log for #brlcad on 20130610

00:43.11*** join/#brlcad zero_level (~zero_leve@117.205.18.35)
02:20.08*** join/#brlcad crdueck (~cdk@24.212.219.10)
02:44.00*** join/#brlcad zero_level (~zero_leve@117.205.31.205)
02:58.13*** join/#brlcad zero_level (~zero_leve@117.205.31.205)
03:59.23Notify03BRL-CAD Wiki:JoelDBenson * 5374 /wiki/Creating_and_editing_arbn_primitives: created using content formerly in the BRL-CAD Primitives article, in order to reduce the length of that article
04:02.07Notify03BRL-CAD Wiki:JoelDBenson * 5375 /wiki/Creating_and_editing_arbn_primitives: /* Creating and editing arbn primitives */ removed redundant heading
04:06.27Notify03BRL-CAD Wiki:JoelDBenson * 5376 /wiki/Talk:Creating_and_editing_arbn_primitives: Created page with "==Creation Note== I am working on completing the [[BRL-CAD Primitives]] article as an overview of all such shapes. To keep it to a managable length, I plan on creating a seri..."
04:18.12Notify03BRL-CAD Wiki:JoelDBenson * 5377 /wiki/BRL-CAD_Primitives: /* Arbitrary convex polyhedra */ moved creation discussions to a separate article, and finished this section as an overview of arb primitives
04:40.50Notify03BRL-CAD Wiki:JoelDBenson * 5378 /wiki/Talk:BRL-CAD_Primitives: Responded to Sean's comments and adding an explanation of my most recent changes
04:50.35Notify03BRL-CAD Wiki:JoelDBenson * 5379 /wiki/BRL-CAD_Primitives: /* ARB8 Records */ minor edit of arb4, arb5 and raw bullet points
08:31.14*** join/#brlcad zero_level (~zero_leve@117.212.25.123)
08:51.35*** join/#brlcad zero_level (~zero_leve@117.205.25.147)
09:15.41*** join/#brlcad zero_level (~zero_leve@117.205.24.242)
10:46.49*** join/#brlcad zero_level (75cd11e0@gateway/web/freenode/ip.117.205.17.224)
13:10.35Notify03BRL-CAD:erikgreenwald * 55698 (svn:executable ## -1 +0,0 ## and 2 others): remove executable prop for .c filesProperty Changed:----------------brlcad/trunk/src/libdm/adc.cbrlcad/trunk/src/libdm/grid.cbrlcad/trunk/src/libdm/labels.cbrlcad/trunk/src/libdm/rect.cbrlcad/trunk/src/libdm/scale.c
13:55.10brlcad``Erik: interesting: https://github.com/cosmos72/stmx/
14:02.24brlcad``Erik: heh, that VW is the same weight as my car ... 0-60 in <2s yikes
14:22.13``Erikheh, yeh, kw/kg of .828 vs your .155 or my .160 (or starseekers .089)
14:23.53*** join/#brlcad d_rossberg (~rossberg@66-118-151-70.static.sagonet.net)
14:26.44``Erikprobably needs a new set of tires every time it fuels
14:26.48brlcad``Erik: your paste expired, what was the failure?
14:27.09``Erikum, something about inline being an extension if it's the ubuntu/i386 one
14:27.39brlcadsomething that would have succeeded if strict was turned off?
14:28.28brlcadprobably related to the -std=gnu90 flag I re-enabled on debug compilation
14:28.38``Erikhttp://paste.lisp.org/display/137541
14:28.59``Erikyeah, it doesn't happen with CMAKE_BUILD_TYPE=Release
14:30.21brlcadwhat grep INLINE .cmake/CMakeCache.txt | grep -v //
14:30.57brlcadpresume the inline test succeeded, probably just needs to test for that flag after the standards flags
14:31.32``Erik6 lines, says inline is found and called "inline"
14:32.44brlcadyeah
15:03.32Notify03BRL-CAD Wiki:JoelDBenson * 5380 /wiki/Talk:BRL-CAD_Primitives: /* Completion of ARBs section */
15:07.37*** join/#brlcad zero_level (75d41d46@gateway/web/freenode/ip.117.212.29.70)
15:07.51*** join/#brlcad cstirk (~quassel@c-71-56-216-45.hsd1.co.comcast.net)
15:40.47Notify03BRL-CAD Wiki:JoelDBenson * 5381 /wiki/BRL-CAD_Primitives: /* ARB8 Records */ minor changes to geometric terminology
16:08.04brlcad``Erik: what does this output?  touch foo.h; clang -std=gnu89 -pedantic -dM foo.h
16:12.45brlcadnever mind, got it
16:39.34brlcad``Erik: can you give that a try?
16:39.40Notify03BRL-CAD:brlcad * 55699 brlcad/trunk/include/common.h: __STRICT_ANSI__ is not the right define to key off of as it catches c89 and c99 (for gcc and clang). if we're compililing gnu89 pedantic, we need to check for GNU inline behavior, which is indicated for gcc 4.1+ and clang via the __GNUC_GNU_INLINE__ define. leaving __STRICT_ANSI__ in place to not rock the windows boat prior to release.
16:51.05*** join/#brlcad Yoshi47 (~jan@64.235.102.210)
17:12.47``Erikseems to work for libbu doing gcc debug and clang debug
17:13.42``Erikbuilds the rest
17:28.21*** join/#brlcad zero_level (75cd18fc@gateway/web/freenode/ip.117.205.24.252)
17:29.44brlcad``Erik: awesome, thanks
17:30.32brlcadif richard is earshot and willing to try a windows libbu compile with __STRICT_ANSI__ removed (in common.h), that would wrap that issue up
17:42.37Notify03BRL-CAD Wiki:Level zero * 5382 /wiki/User:Level_zero/GSOC13/api: /* API DESIGN */
17:43.54*** join/#brlcad crdueck (~cdk@24-212-219-10.cable.teksavvy.com)
17:47.28Notify03BRL-CAD:n_reed * 55700 brlcad/trunk/include/common.h: don't want to remove inline uses from cpp files
18:03.30Notify03BRL-CAD:carlmoore * 55701 (brlcad/trunk/src/util/pixscale.c brlcad/trunk/src/util/pixshrink.c): remove old -h (high-res); use h,?,run-with-no-arguments for help
18:11.28*** join/#brlcad zero_level (75cd154e@gateway/web/freenode/ip.117.205.21.78)
18:13.24Notify03BRL-CAD Wiki:Level zero * 5383 /wiki/User:Level_zero/GSOC13/api: /* STructures and API */
18:14.52Notify03BRL-CAD:n_reed * 55702 brlcad/trunk/src/libdm/dm-ogl.c: remove duplicate prototypes
18:21.50Notify03BRL-CAD Wiki:Level zero * 5384 /wiki/User:Level_zero/GSOC13/api: /* Structure */
18:26.10Notify03BRL-CAD Wiki:Level zero * 5385 /wiki/User:Level_zero/: /* GSOC 13 */
18:26.28zero_levelhi Erik:
18:26.57zero_levelpls review my structure definitions and api designs
18:27.01zero_levelthese are available here
18:27.02zero_levelhttp://brlcad.org/wiki/User:Level_zero/GSOC13/api
18:27.19zero_levelAlso i have created an Index Page for all my work with BRLCAD
18:27.34zero_levelThis is available here http://brlcad.org/wiki/User:Level_zero/#GSOC_13
18:28.30zero_levelAlso Do u suggest of putting my rough notes for the utilities on wiki..
18:31.15zero_level``Erik and brlcad I would also like to get my patches reviewed.
18:31.47zero_levelInformation Regarding them are here http://brlcad.org/wiki/User:Level_zero/patches
18:32.47Notify03BRL-CAD:carlmoore * 55703 brlcad/trunk/src/fb/pix-fb.c: remove h for high-res; implement h,? for help
18:33.12zero_level<PROTECTED>
18:38.21*** join/#brlcad vladbogo (~vlad@188.25.101.47)
18:40.28*** join/#brlcad zero_level (75cd154e@gateway/web/freenode/ip.117.205.21.78)
18:47.21brlcadstarseeker: you should add BRL-CAD to http://en.wikipedia.org/wiki/CMake#Notable_applications
19:09.04brlcadzero_level: it's a good start!
19:09.50zero_levelbrlcad : thanks had to do a lot of code reading
19:10.05brlcadzero_level: few suggestions...
19:10.38brlcadI'd like to see some comments for starters, to say what the intent is of each function, what the params are if it's not obvious from the names, and some consistency with the I/O
19:11.10zero_levelok i will put them in the patch file
19:11.44brlcadnot fond of "oper1" and "oper2" ... vague
19:12.01brlcadalso should denote which parameters can be const
19:12.23zero_levelactually those two represents operations with one image and operations with two images
19:12.26brlcadmight also want to consider "standardizing" your parameters
19:13.04brlcadexcept so are all the other functions, no? ... represent operations with one or two images.. :)
19:13.05zero_levelcan u suggest some instances, that will be easy for future
19:13.22brlcadwhat I mean about standardizing is like a usage pattern
19:13.47zero_levelthose two functions are for airthmetic and logical operations like addition multiplication, or, and etc..
19:14.14brlcadfor example, option #1:  void function(output, const input, ...input params...)
19:14.51brlcadoption #2: void function(const input, output, ... input/output params ...)  <-- this is kind of what you mostly have now sans const
19:15.11brlcadoption #3: output function(const intput, ...input/output params ...)
19:15.11brlcadetc
19:15.29brlcadthe idea is to consciously pick a form and then stick to it religiously
19:16.04brlcadwhich is "best" really depends on many factors, like whether there are any functions that need to return more than one value?
19:16.13zero_levelyes, this will be a good style :-) will try to adher to one of them after seeing what we require here
19:17.11brlcadyou should already have a pretty good sense of what is required now
19:17.22brlcadas that is a pretty extensive list
19:17.56brlcadwhat is icv_operation.oper?
19:18.51zero_levelthat will carry information regarding operation type
19:19.03zero_leveli will post enumerate list for them
19:19.36brlcadif it's an enum, it should be typedef'd instead of a char
19:21.04zero_leveli would rather make it an integer type
19:21.20zero_leveland a list of enum for operations
19:21.38zero_levellike it is done for format in icv.h
19:22.52brlcadthat's the point, you make it a typedef so you can change it later as needed
19:23.08brlcadicv.h is merely a starting point, it has LOTS of room for improvement
19:23.20brlcadso use it as a reference for ideas only, not as religion ;)
19:23.47brlcadfor example, I look at format in icv.h and think it should also be a typedef'd type
19:24.03zero_levelok
19:24.22zero_levelthen the same applies for method in icv_scale and shrink
19:24.29brlcadtypedef enum {...} icv_format_t; ...  struct icv_image_file { ... int fd; icv_format_t format; ...};
19:25.00zero_levelyeah got ur poing regarding typedef
19:26.30zero_levelbrlcad: there are three groups left as per my proposal
19:26.35brlcaddo any of the functions not return void?
19:27.33zero_levelactually i intend to implement them as such that all the functions are called using call by reference
19:27.54zero_leveland the addresses for desired output is sent during function call
19:28.14brlcadwhat do you mean called using call by reference?
19:28.30brlcadsome sort of icv_exec() function?
19:29.06brlcadzero_level: how'd you come up with your groupings?
19:29.32zero_levelone by one :-)
19:29.40zero_levelcall by reference means
19:29.52zero_levelfor example
19:30.30zero_level<PROTECTED>
19:31.14zero_levelhere instead of making a return type of icv_image_file_t
19:31.52zero_leveli have used icv_image_file_t  *img_out, one of the argument
19:31.55brlcadokay, I guess you're reading "into" my question then ... :)
19:32.34brlcadmaking a return type of icv_image_file_t wouldn't necessarily make sense for all function types -- the "output" might not be the image
19:32.39zero_levelabout groupings --
19:33.06zero_leveli have picked the utilities which perform comman functions
19:33.15brlcadicv_image_FILE_t is bothersome... implies there is or will be an icv_image_NOTFILE_t
19:33.17zero_levellike crop and rect
19:33.37brlcadI got that, but how'd you come up with them?
19:33.58brlcadreading their man pages or the source files and grouping them based on what it sounds like they do?
19:34.26zero_leveland also reading there source codes
19:34.36brlcadif you can give a name to each group, that would be very helpful
19:34.37zero_levelbecause there is commanilities in the codes as well
19:34.43zero_levelok
19:34.54brlcadgroup1 for example seems to be "Cropping"
19:35.15zero_leveli also plan to create a seperate file for each group
19:35.23zero_levelwhich will ensure completeness
19:35.44brlcadall the better reason to make sure they can all be described in one or two words
19:36.14brlcaddon't be shy to break things up into multiple files or use subdirectories even
19:36.16zero_levelShould i remove file from icv_image_file_t and make it icv_image_file
19:36.32zero_levelopps
19:36.38brlcadyou tell me
19:37.23brlcadwhat happens when icv_crop() (or any of them, really) fails ?
19:46.00*** join/#brlcad mpictor (~mark@2601:d:b280:9:d63d:7eff:fe2d:2505)
19:51.51``Erikheh, osX.9 SeaLion
19:52.09brlcad:)
19:52.11``Erik(ya been watching the streaming wwdc? I'm just catching the twitter chatter about it)
19:52.41``Erikogl4? :o
19:54.56``Erik(ran into an issue with c++ name conflicts at link time, but Nick seemed to have gotten that taken care of... this old celery is a slow compiler and I've been busy futzing with a tk/dm-ogl bridge to replace togl for isst)
19:55.15brlcadonly part way through
19:58.17``Erikbummer, mbp retina isn't getting anything this cycle
19:59.15brlcadMPro update first .. needing that one
20:00.04``Erik<-- still on a 2008 13" mb (the alum uni one)
20:00.21*** join/#brlcad Ch3ck (~Ch3ck@41.202.197.36)
20:02.40``Erikseeing a bit of "ios7 looks pretty sweet", I should probably log into my dev account once in a while to figure out what's going on O.o
20:03.29``Erik"multitasking for all apps", heh
20:03.55brlcadmy mbp is a little older than that
20:04.30Ch3ckjust finished preparing my design document  for the first progress report and
20:04.48``Erikwhu? they're ditching rounded corners and gloss overlays, making it look like win8?
20:04.56Ch3ckjust about to post on my wiki will need some reviews..
20:05.18starseeker``Erik: you sure you're not watching a hoax?
20:05.46``ErikI might be, I read something about the icon transition being jarring and googled for images...
20:07.25``Erikstarseeker: coulda used your brain to pick, spent the day learning how to make a tcl module that cranks up a dm-ogl window... :) the biggest issue seems to be replacing the togl event loop, I'm thinking a pure tcl approach might be good
20:08.26``Erik@codejake: TL;DR: iOS 7 is Windows Phone OS with rounded corners.
20:08.58``Erik[@wilw:42] Watched a little #WWDC on a break. Excited for iOS users to have some of the things we've had on Android for years.
20:09.52``Erikwil wheaton trolls like a true intarwebz geek
20:13.42starseeker``Erik: doubt there's much to pick about tcl/ogl issues - the isst code represents the sum total of my knowledge (such as it is)
20:14.36``Erikit took a while to unwind the cmake macros to figure out the C module compile line (and I think I'm doing mine different than yours, surely less robust)
20:15.07``Erik(apparently, the stubs thing is important)
20:15.10starseekeryeah, I'm not happy with how far we are from vanilla CMake
20:15.26starseekerproblem is you save a lot of lines when you wrap boiler plate into macros
20:15.59starseekerif you see ways to make it simpler, sing out - I was almost certainly not seeing the forest very well while hacking down trees for that part of the build system...
20:17.39starseekerbrlcad and I were discussing some of that stuff and how to improve it a little while back, actually - one of the things to do after the release
20:18.07starseekerstares at a pile of stink bugs and concludes he should probably haul out the vacuum...
20:32.34Notify03BRL-CAD Wiki:IIIzzzaaakkk * 5386 /wiki/User:Izak/Design_documen: /* Short description and Development plan */
20:44.24Notify03BRL-CAD:carlmoore * 55704 (brlcad/trunk/src/sig/f-d.c brlcad/trunk/src/sig/f-i.c): remove unneeded braces
20:50.02Notify03BRL-CAD:carlmoore * 55705 brlcad/trunk/src/sig/i-f.c: cosmetic stuff, to look as much as possible like d-f.c
22:42.24Notify03BRL-CAD:brlcad * 55706 brlcad/trunk/src/libged/gqa.c: key off any negative tolerance value for weight/volume, not just the specific value we initialized with
22:49.30Notify03BRL-CAD:brlcad * 55707 brlcad/trunk/src/libged/gqa.c: introducing new magic numbers (literal values) without explanation is taboo, go with something (an order of magnitude) that should be defensible. value is still significantly smaller than the previous quarter-mm value...

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