| 00:00.02 | brlcad | thinking to ask others for pointers without hesitation |
| 00:00.19 | brlcad | doesn't mean you'll get an answer, but it usually helps (a lot) and you often will |
| 00:00.35 | brlcad | i'll tell you the answer if you want, but you'll remember it better if you figure it out |
| 00:01.32 | zero_level | brlcad: I would want to ask a personel question. |
| 00:01.55 | zero_level | Is it very poor of me that i have never used getopt. |
| 00:02.02 | zero_level | or it is fine ? |
| 00:02.06 | brlcad | poor in what sense? |
| 00:02.28 | zero_level | poor as in poor. :-) |
| 00:05.13 | brlcad | ~dict poor |
| 00:05.42 | brlcad | certainly not unsatisfactory (and notice there are 10 other definitions) |
| 00:07.36 | zero_level | alright so the question mark was an issue. |
| 00:07.44 | brlcad | nope |
| 00:07.48 | brlcad | I believe there are about 3000 functions in libc |
| 00:08.01 | brlcad | the fact that you don't know one of them does not imply anything poor about you |
| 00:08.31 | brlcad | the ? is the -? help option |
| 00:10.08 | brlcad | zero_level: this is an excellent intro: http://www.ibm.com/developerworks/aix/library/au-unix-getopt.html |
| 00:10.31 | brlcad | even includes a -o file example ;) |
| 00:11.40 | zero_level | I think i have fixed that. |
| 00:16.15 | brlcad | what was the fix? |
| 00:16.40 | zero_level | "sw:n:S:W:N:x:y:o:h?" (not sure) |
| 00:16.49 | zero_level | reading the ibm page now. |
| 00:17.03 | brlcad | heh |
| 00:17.23 | brlcad | well you added something, what did you add? |
| 00:17.42 | zero_level | although worked fine in basic case. |
| 00:19.01 | brlcad | the difference between "sw:n:S:W:N:x:y:o?" and "sw:n:S:W:N:x:y:o:h?" |
| 00:21.04 | zero_level | it will accept argument for -o option (not sure_ |
| 01:05.19 | Notify | 03BRL-CAD:mohitdaga * 56731 (brlcad/trunk/src/libicv/bw.c brlcad/trunk/src/libicv/pix.c): Add wrtting flags to open function in pix_save and bw_save. Also remove redundant comments. |
| 01:06.17 | *** join/#brlcad mpictor_ (~mpictor_@2601:d:b280:b5:a4c9:9437:afb6:e0fc) |
| 01:22.28 | Notify | 03BRL-CAD:mohitdaga * 56732 (brlcad/trunk/src/util/CMakeLists.txt brlcad/trunk/src/util/bwrect.c): Use libicv in bwrect utility. Also modify the usage criterio of bwrect. This utility now accepts command line arguments instead of prompt based user inputs. Also it can read from stdin and save in stdout. |
| 01:23.08 | zero_level | brlcad : There is one issue in opening bw, pix images for saving. |
| 01:23.55 | zero_level | although I use O_TRUNC flag. Still if the image exists in the folder the 'open' function fails. |
| 01:26.21 | zero_level | ``Erik, brlcad pls have a look at 56732 and tell me if we would like to proceed in this way. (for making other utils use libicv functions). |
| 01:27.06 | zero_level | is running regress. |
| 01:34.24 | zero_level | brlcad : I just saw bwcrop.c |
| 01:35.25 | zero_level | Although it uses the same mechanism for buffer fill as in pixscale. But incidently i didnt see "ioctl" error. |
| 01:35.38 | zero_level | Will look more deeply tommorow. |
| 01:36.05 | zero_level | goes for some sleep |
| 02:47.22 | *** join/#brlcad mpictor_ (~mpictor_@2601:d:b280:b5:a4c9:9437:afb6:e0fc) |
| 03:24.53 | brlcad | zero_level: you should have read in the docs that the ':' in the optstring denotes when an option expects an argument to follow (e.g., cmd -c vs cmd -c foo) |
| 03:27.21 | brlcad | you added ':' to the optstring after the 'o', so "-o filename" works, otherwise it was just expecting "-o" (no filename |
| 04:32.37 | *** join/#brlcad caen23 (~caen23@92.81.199.113) |
| 04:50.59 | *** join/#brlcad mpictor_ (~mpictor_@2601:d:b280:b5:a4c9:9437:afb6:e0fc) |
| 05:36.36 | Notify | 03BRL-CAD:brlcad * 56733 brlcad/trunk/include/vmath.h: add macros for testing whether an object is invalid (not within our defined range of INFINITY to -INFINITY |
| 05:36.49 | Notify | 03BRL-CAD:brlcad * 56734 brlcad/trunk/CHANGES: no longer should be using RT_BADNUM/RT_BADVAL |
| 05:37.42 | Notify | 03BRL-CAD:brlcad * 56735 brlcad/trunk/src/libdm/dm-rtgl.c: if all we're going to do is print it, skip the bad vector check |
| 05:43.14 | Notify | 03BRL-CAD:brlcad * 56736 (brlcad/trunk/src/librt/bundle.c brlcad/trunk/src/librt/shoot.c): cannot afford to be doing this bombing validity test during ray tracing. let the calling application test. |
| 05:46.08 | Notify | 03BRL-CAD:brlcad * 56737 (brlcad/trunk/CMakeLists.txt brlcad/trunk/src/rt/main.c): no longer need NO_BADRAY_CHECKING |
| 06:55.54 | *** join/#brlcad mpictor_ (~mpictor_@2601:d:b280:b5:a4c9:9437:afb6:e0fc) |
| 09:01.04 | *** join/#brlcad mpictor_ (~mpictor_@2601:d:b280:b5:a4c9:9437:afb6:e0fc) |
| 09:16.08 | zero_level | brlcad : yeah. I think the issue regarding getopt was resolved. Thanks to your pointers. |
| 13:27.34 | *** join/#brlcad infobot (~infobot@rikers.org) |
| 13:27.34 | *** topic/#brlcad is BRL-CAD || http://brlcad.org || logs: http://ibot.rikers.org/%23brlcad/ || GSoC 2013! http://brlcad.org/wiki/Google_Summer_of_Code |
| 13:39.57 | brlcad | zero_level: you seemed unsure that you understood it is all, it's clear that the format string is right now |
| 13:42.10 | brlcad | ``Erik: I don't see a need for more api .. why not just always returned aligned memory? either via posix_memalign() under bu_alloc() or doing it manually ... easy enough to test for libtie, but then I've yet to see the TIE bug to confirm |
| 13:42.30 | brlcad | ponders setting up a 32-bit mac compile |
| 13:56.25 | ``Erik | bz exhibits the issue |
| 14:07.11 | brlcad | and of course 32-bit compile doesn't cmake right |
| 14:07.16 | brlcad | k |
| 14:12.00 | ``Erik | eh? it cmake's fine on a 32b machine... I had to go through some hoops to get it to work on a 64b linux, it kept trying to link 64b system libs |
| 14:14.32 | brlcad | this is a 64/32 machine, so the flags have to be right |
| 14:14.34 | brlcad | and they're not |
| 14:17.20 | brlcad | looks like cmake logic is confused about "C flags", or at least what's needed when one runs BRLCAD_CHECK_FLAG |
| 14:17.31 | brlcad | that it must set the flag for compilation AND linking |
| 14:18.02 | brlcad | not passing the flag to CMAKE_*_LINKER_FLAGS |
| 14:18.59 | brlcad | ld: warning: in CMakeFiles/cmTryCompileExec3145753208.dir/src.c.o, file was built for i386 which is not the architecture being linked (x86_64) |
| 15:25.50 | *** join/#brlcad caen23 (~caen23@92.83.182.68) |
| 15:43.02 | zero_level | brlcad : I hope the issue with bwrect was fine. Thus I think I move forward with the same style for other utils. |
| 15:48.37 | brlcad | zero_level: why is unistd.h included? |
| 15:48.43 | brlcad | you cannot include it without wrappers |
| 15:53.01 | brlcad | and bwrect does not look like it's set up right for processing the input/output files |
| 15:53.49 | brlcad | try: cat bwrect | bwrect ... |
| 15:55.12 | brlcad | the icv calls themselves look great |
| 15:55.17 | brlcad | nice and simple |
| 15:57.39 | brlcad | API critique: load+free do not pair well as a naming convention, I'd suggest icv_open() and icv_close() |
| 15:59.22 | *** join/#brlcad ClientAlive (~shine@216.16.61.156) |
| 15:59.42 | brlcad | zero_level: you mentioned last week that you were done with merging all of your external changes so icv.h should be in a near-stable state, please give it another review to make sure the file is organized (declarations are in some reaonsable order, grouped accordingly) |
| 15:59.59 | ClientAlive | Holy shit! There is a #brlcad!! |
| 16:00.09 | brlcad | of course there is |
| 16:00.17 | ClientAlive | lol |
| 16:00.34 | ClientAlive | Aye... |
| 16:00.38 | ClientAlive | Are there any up to date tutorials for BRL-CAD? Video tutorials even? All I can find are these .pdf's (like a decade old) from Army Research Laboratory |
| 16:00.47 | brlcad | this channel has been live since before we became open source in 2004 |
| 16:01.06 | ClientAlive | That's so awesome! :) |
| 16:01.17 | ClientAlive | I just found out about it yesterday |
| 16:01.19 | brlcad | ClientAlive: the pdf's are still a pretty good starting place |
| 16:01.30 | ClientAlive | really? |
| 16:01.32 | brlcad | there's so much to cover and they only scratch the introductory surface |
| 16:01.35 | ClientAlive | sigh |
| 16:01.54 | ClientAlive | well... Ok, I guess :) |
| 16:01.55 | brlcad | we're working on a new set, but that all takes tons of time |
| 16:02.13 | brlcad | yeah, once you get through that mged tutorial, you'll know maybe 5% |
| 16:02.19 | brlcad | and it's like 300 pages |
| 16:02.40 | brlcad | (though most can get through it all in less than a day) |
| 16:03.03 | brlcad | http://brlcad.org/wiki/Documentation |
| 16:03.52 | ClientAlive | Ok, so, what I found on my computer to launch is actually called "Archer" <- Is that the correct program to be running? (I know some programs have multiple components you can run - like some ripping/burning software does). |
| 16:04.35 | brlcad | archer is our alpha release of a new GUI replacement to MGED |
| 16:05.17 | brlcad | archer can work, but you'll notice that it won't exactly match the MGED tutorial instrutions .. though it's pretty damn close |
| 16:05.35 | ClientAlive | so that makes it different enought to not line up with the old Army Research tutorials? Or no |
| 16:05.38 | brlcad | the mged intro is #2 in the docs list |
| 16:05.47 | ClientAlive | right |
| 16:05.49 | ClientAlive | ok |
| 16:06.09 | ClientAlive | You think vol 1 is even worth reading? |
| 16:06.15 | ClientAlive | I have it installed already |
| 16:06.47 | brlcad | one of our devs went through all the tutorials with archer and there were very few hiccups (some commands are named a little different) |
| 16:07.04 | ClientAlive | right on |
| 16:07.04 | brlcad | but then he knew the mapping, so I don't have a notion for how hard it will be starting from scratch |
| 16:07.26 | brlcad | you might want to start with MGED, go through the tutorials, and then switch to the archer interface |
| 16:07.43 | ClientAlive | well how have others learned? Word or mouth? Apprenticeship? |
| 16:07.58 | ClientAlive | I'm not trying to be a smartass, I'm serious |
| 16:08.08 | ClientAlive | *of* |
| 16:08.13 | brlcad | time and effort |
| 16:08.15 | brlcad | it's an expert system |
| 16:08.35 | brlcad | and like most, it really does take some training to learn the commands and infrastructure |
| 16:08.55 | ClientAlive | the thing looks friggin awesome! I have zero exper with something like this though |
| 16:09.06 | brlcad | most hop in here and ask questions, which is perfectly fine |
| 16:09.31 | brlcad | we're here 24/7 (though we may take a couple hours to respond sometimes, gotta eat and crap and write code and what not) |
| 16:09.42 | ClientAlive | I'm sure I'll come hang out sometimes, now that I know ya'all are here :) |
| 16:10.08 | ClientAlive | brlcad: peace :) |
| 16:10.56 | brlcad | sure, welcome and thanks for checking it out ;) |
| 16:11.21 | brlcad | we've got a lot of exciting stuff coming down the pipeline, but it does take a ton of time to implement new features |
| 16:11.24 | brlcad | and we're a relatively small team |
| 16:11.37 | brlcad | but we've been around a really long time and our rate is only increasing |
| 16:11.50 | brlcad | http://ibot.rikers.org/%23brlcad/ ... yeah, 200407 started logging, heh |
| 16:13.12 | ClientAlive | I started out trying to force blender into the role but that didn't turn out so well :0 |
| 16:13.14 | ClientAlive | lol |
| 16:13.23 | brlcad | so are you working on linux? windows? mac? |
| 16:13.40 | ClientAlive | ubuntu 12.04 atm :) |
| 16:13.56 | brlcad | yeah, blender sucks for CAD work, but I love those guys and what they're doing in the content creation domain |
| 16:14.47 | brlcad | so one thing to realize is that brl-cad includes hundreds of small commands that all are designed to work together (kind of like cat, ls, sed, awk, cut, find, etc on the command line) |
| 16:15.00 | ClientAlive | I can't knock blender for what it is. I messed around with it for a week or so - and still couldn't get caliper.py to install |
| 16:15.01 | brlcad | as well as gui applications like mged and mged/archer |
| 16:15.20 | ClientAlive | oh, ok |
| 16:15.26 | zero_level | brlcad : for isatty(..) |
| 16:15.59 | brlcad | sushi:.cmake morrison$ grep isatty ../src/util/* | wc |
| 16:16.00 | brlcad | <PROTECTED> |
| 16:16.00 | brlcad | sushi:.cmake morrison$ grep unistd ../src/util/* | wc |
| 16:16.00 | brlcad | <PROTECTED> |
| 16:16.04 | ClientAlive | well that sounds pretty interesting. I love working on the command line |
| 16:17.09 | brlcad | ClientAlive: so if creating geometry that way sounds interesting, you might want to check out http://brlcad.org/wiki/Main_Page#Tutorials |
| 16:17.31 | brlcad | shows how to do various things via shell scripts, python, perl |
| 16:17.32 | ClientAlive | cool |
| 16:24.21 | brlcad | a crash course for you to try, run: mged -c test.g make sph sph |
| 16:24.25 | brlcad | rt test.g sph |
| 16:27.12 | brlcad | zero_level: those grep lines were for you .. notice that many tools call isatty() but most don't include unistd.h |
| 16:27.58 | brlcad | unistd.h is not available on windows, so you need to figure out what the rest are doing (probably bio.h) |
| 16:36.09 | zero_level | brlcad : I avoided open because its no longer files we are handling. |
| 16:36.17 | zero_level | load is paired with save. |
| 16:38.53 | zero_level | And avoided freeing the memory in save. in order to support other processing. |
| 16:40.56 | Notify | 03BRL-CAD:mohitdaga * 56739 brlcad/trunk/src/util/bwrect.c: Remove unistd.h. Since unistd.h is not available in windows. |
| 16:48.03 | zero_level | brlcad : About variable declaration I want a sample from you. |
| 16:49.48 | zero_level | like some rviews about this. http://paste.kde.org/p3c7109ee/ |
| 17:05.31 | zero_level | ``Erik. Do u think its strict convention about asignment operator. To follow spaces. |
| 17:05.44 | zero_level | a = b; |
| 17:05.59 | zero_level | a=b; /* IS IT WRONG ?* / |
| 17:18.33 | ``Erik | use spaces |
| 17:20.32 | zero_level | ``Erik : Also, As I mentioned yesterday. |
| 17:20.49 | zero_level | There is an issue about icv_save. |
| 17:21.49 | zero_level | Although I use O_TRUNC flag. still it doesnt open a file if it is already created. |
| 18:00.45 | ``Erik | check the file mode, the default for pix files is 444, which prohibits writing |
| 18:54.26 | *** join/#brlcad caen23 (~caen23@92.83.182.68) |
| 19:52.12 | Notify | 03BRL-CAD Wiki:Vladbogolin * 5967 /wiki/User:Vladbogolin/GSoC2013/Logs: /* Week 8 */ |
| 19:55.46 | *** join/#brlcad mpictor (~mark@2601:d:b280:b5:d63d:7eff:fe2d:2505) |
| 20:54.00 | *** join/#brlcad ClientAlive (~shine@216.16.61.156) |
| 20:56.17 | ClientAlive | I think there's a problem with my hotkeys for constraint translation. I would assume that with that view the object would only move in one straight line, right? But when I hit shit + alt + < some mouse button > I can drag the oject all about in circles or wherever. |
| 20:57.50 | ClientAlive | Anyways... |
| 21:00.15 | ClientAlive | Sorry, what it actually does is move the entire application window when use shift+alt+<mouse button> |
| 21:00.19 | ClientAlive | What can I do? I've already tried going in throught settings and change the hotkeys for what it was actually doing when I hit shift+alt (moving the entire application window). |
| 22:37.13 | *** join/#brlcad merzo (~merzo@14-58-132-95.pool.ukrtel.net) |
| 23:07.37 | ``Erik | starseeker: https://github.com/Inaimathi/forthlike |