| 01:58.48 | *** join/#brlcad smurfette (i=Pandora@c-69-247-220-102.hsd1.mo.comcast.net) | |
| 05:35.32 | *** join/#brlcad pacman87 (n=Timothy@resnet-45-219.dorm.utexas.edu) | |
| 07:21.02 | *** join/#brlcad clock_ (n=clock@84-72-91-240.dclient.hispeed.ch) | |
| 08:04.00 | *** join/#brlcad d_rossberg (n=rossberg@bz.bzflag.bz) | |
| 10:29.00 | CIA-4 | BRL-CAD: 03d_rossberg * r32560 10/rt^3/trunk/ (4 files in 2 dirs): the core of ray trace |
| 11:14.47 | *** join/#brlcad mafm (n=mafm@elnet-111.lip.pt) | |
| 11:30.24 | *** join/#brlcad elite01 (n=elite01@unaffiliated/elite01) | |
| 12:57.30 | CIA-4 | BRL-CAD: 03bob1961 * r32561 10/brlcad/trunk/src/libged/ged.c: |
| 12:57.30 | CIA-4 | BRL-CAD: Making sure ged_log and ged_result_string will initially contain an empty string |
| 12:57.30 | CIA-4 | BRL-CAD: instead of a null pointer (I wrongly assumed that bu_vls_init did this :-( ). |
| 12:57.30 | CIA-4 | BRL-CAD: This way, any callers of libged functions can harvest ged_log or ged_result_str |
| 12:57.30 | CIA-4 | BRL-CAD: without the need to check whether or not it contains a null pointer (i.e. it |
| 12:57.33 | CIA-4 | BRL-CAD: should always contain atleast an empty string assuming the application doesn't |
| 12:57.35 | CIA-4 | BRL-CAD: free the vls). |
| 12:58.40 | CIA-4 | BRL-CAD: 03bob1961 * r32562 10/brlcad/trunk/src/libged/ (ged_private.h qray.h): Include missing header |
| 13:41.49 | *** join/#brlcad cad44 (n=cec3133a@bz.bzflag.bz) | |
| 14:08.46 | CIA-4 | BRL-CAD: 03bob1961 * r32563 10/brlcad/trunk/src/libtclcad/ged_obj.c: Add code to draw view axes (temporarily hardwired to always be on and drawn in center of view) |
| 14:59.33 | CIA-4 | BRL-CAD: 03d_rossberg * r32564 10/rt^3/trunk/ (3 files in 2 dirs): a little bit more output from the ray trace |
| 15:30.45 | *** join/#brlcad cad89 (n=444ba1fb@bz.bzflag.bz) | |
| 16:00.49 | ``Erik | heh, remember how I was bitching about them screwing up my machine and having stuff crash? even vim is crashing, so I have a hard time just blaming ms... :D |
| 16:01.56 | *** join/#brlcad cad74 (n=a991030d@bz.bzflag.bz) | |
| 16:17.54 | prasad_ | too many metaballs |
| 16:21.21 | ``Erik | heh |
| 16:21.33 | ``Erik | my balls are awesome, WORSHIP MY BALLS! *duck* |
| 16:37.08 | *** join/#brlcad andrecastelo (n=chatzill@189.71.33.203) | |
| 16:49.46 | *** join/#brlcad geocalc (n=geocalc@91-171-207-250.rev.libertysurf.net) | |
| 17:43.26 | CIA-4 | BRL-CAD: 03bob1961 * r32565 10/brlcad/trunk/ (186 files in 4 dirs): (log message trimmed) |
| 17:43.26 | CIA-4 | BRL-CAD: Removed ged_result_flags from struct ged and added another return type (i.e. |
| 17:43.26 | CIA-4 | BRL-CAD: BRLCAD_HELP). This should make libged easier to use. Before, you would have |
| 17:43.26 | CIA-4 | BRL-CAD: checked the return value and the result_flags to determine if the function was |
| 17:43.26 | CIA-4 | BRL-CAD: returning a help message or results of the function call. Now you check only the |
| 17:43.29 | CIA-4 | BRL-CAD: return value. BTW, the reason an application may need to distinguish the |
| 17:43.31 | CIA-4 | BRL-CAD: difference between BRLCAD_OK and BRLCAD_HELP may be to refresh a display if the |
| 17:48.22 | *** join/#brlcad andrecastelo_ (n=chatzill@189.71.35.149) | |
| 19:11.00 | starseeker | brlcad: Hmm, I wasn't aware of it, but there does seem to be some sort of find command already in libged. Would the new find command replace it? |
| 19:23.22 | *** join/#brlcad d_rossberg (n=rossberg@bz.bzflag.bz) | |
| 20:42.02 | brlcad | starseeker: that's the 'dbfind' command .. some commands were renamed in archer, that being one of them |
| 20:42.52 | brlcad | what you're doing would replace that |
| 20:44.12 | brlcad | there is also a tcl 'find' command unfortunately, so there is still a name conflict that will have to get sorted out later |
| 20:44.53 | brlcad | what I had in mind was to encapsulate all of our commands in a ged:: namespace that is auto-loaded in mged, so it can still be just 'find' |
| 20:45.16 | brlcad | and you'd just call ::find or ged::find to get tcl's or ged one respectively |
| 20:45.21 | brlcad | or at least something like that |
| 20:51.13 | brlcad | actually even better in this case, find is already namspace scoped for itcl so you can just use 'find' |
| 21:16.24 | ``Erik | hehehe, that guy just lost 26k of fleet on my base, I lost 220 and got a nice fat 11k derb pile :D awesome |
| 21:16.42 | ``Erik | 2200, rather |
| 21:17.20 | starseeker | So do you go attack him now? |
| 21:18.27 | brlcad | ``Erik: random luck of the draw or something else? |
| 21:18.29 | ``Erik | theoretically... but I probably wouldn't profit from it, so I won't |
| 21:18.43 | ``Erik | idiot at the wheel, he got upset at my potshots and decided to "teach me a leson" |
| 21:18.45 | ``Erik | lesson |
| 21:19.12 | brlcad | upgraded his beta account for a month so it can continue through the weekend unattended whilest packing |
| 21:19.19 | ``Erik | I'll message you the transcript when I get home so you can get a chuckle and learn how not to do it :) |
| 21:22.23 | starseeker | looks at stack of libged and find code for "light" weekend reading and hopes he has enough time to get through it. |
| 21:23.39 | starseeker | :q |
| 21:23.42 | starseeker | whoops |
| 21:23.43 | brlcad | the find.c in libged is probably code you'll end up needing |
| 21:23.48 | brlcad | it's basic traversal |
| 21:23.54 | starseeker | nods |
| 21:24.03 | brlcad | or at least some variation on it in a more general form |
| 21:24.22 | brlcad | it's one of the dozen or so 'findish' commands for walking the hierarchy looking for things |
| 21:24.31 | starseeker | Yes, I printed it to get the "how to read a tree from libged" perspective |
| 21:26.32 | starseeker | It doesn't seem to actually use db_functree though - db_tree_funcleaf maybe |
| 21:27.00 | starseeker | I take it the dp = gedp->ged_wdbp->dbip->dbi_Head[i]; dp != DIR_NULL; dp = dp->d_forw logic gets all top level objects? |
| 21:28.10 | brlcad | I don't remember for sure, but I don't believe so |
| 21:28.23 | brlcad | I believe that is the hash entry for all db objects |
| 21:28.33 | starseeker | checks other code... |
| 21:28.36 | brlcad | it's just the "Head" of the db linked list |
| 21:28.41 | starseeker | Oh, right |
| 21:28.44 | brlcad | so you can iterate over all objects in a db using that |
| 21:28.55 | brlcad | if the directory has been loaded, that is |
| 21:29.20 | starseeker | so that's not what you want to do if you're searching within a particular subtree then |
| 21:29.40 | starseeker | hmm. |
| 21:29.48 | brlcad | that's very low level .. kinda like putting all objects in one dir on the filesystem and running ls |
| 21:30.01 | brlcad | no hierarchy, but you can get at everything |
| 21:30.42 | brlcad | so iff you knew you were doing a top-level search with path / then you could use that, but I don't see why you'd want to |
| 21:31.00 | starseeker | nods |
| 21:31.04 | starseeker | any performance gains? |
| 21:31.47 | starseeker | looks for a db_functree use in libged |
| 21:32.06 | brlcad | not really |
| 21:32.20 | starseeker | ah, of course - killtree and xpush |
| 21:32.29 | starseeker | plus a few in wdb_obj |
| 21:33.45 | starseeker | wants a kill command that kills only the object in a tree not referenced by any other tree |
| 21:40.06 | brlcad | chuckles at "the website is down" |
| 22:03.29 | starseeker | notes McCain's VP pick and listens to hear the pop of wacko far right voter brains unable to cope with the two major presidential tickets :-) |
| 22:04.04 | starseeker | whatever else it may be, this has gotta be one of the more interesting run-ups to an election in recent history |
| 22:52.17 | ``Erik | http://www.kontraband.com/pics/13365/Proof-Evolution-Is-Phoney/ |
| 23:07.28 | ``Erik | wow O.o http://www.kontraband.com/pics/13277/Trailer-Parking-Catastrophy/ |
| 23:17.12 | *** join/#brlcad tulth (n=user@ip70-181-106-46.oc.oc.cox.net) | |
| 23:18.01 | tulth | hey guys. Anyone know how to get brl-cad operating with gnu emacs instead of jove? |
| 23:29.49 | tulth | or at least, run mged from a shell prompt |
| 23:30.58 | brlcad | tulth: if you set your editor, it'll use it |
| 23:31.27 | brlcad | and what do you mean by run mged from a shell prompt? |
| 23:31.47 | brlcad | if you mean non-gui, you can run mged -c |
| 23:31.54 | brlcad | that's classic console mode |
| 23:32.01 | tulth | ahh that may be exactly what i want |
| 23:32.13 | tulth | sorry, i'm just starting with it |
| 23:33.17 | brlcad | np |
| 23:33.28 | tulth | with the console mode, how can i bring up the graphics window |
| 23:33.37 | brlcad | if you want the gui from there, you can run "gui" or the attach command |
| 23:33.52 | brlcad | it'll prompt you on startup to attach something |
| 23:34.04 | tulth | ah cool |
| 23:34.04 | brlcad | nu is nothing, X will give you the classic X console |
| 23:34.14 | brlcad | ogl might crash ;) |
| 23:34.51 | tulth | interesting, it brought up the command window too, which echoes my console i/o |
| 23:35.01 | brlcad | yep, 'gui' does that |
| 23:35.09 | brlcad | kicks off the tcl gui -- which is both windows |
| 23:35.26 | brlcad | attach is just the graphics window, but without a menu |
| 23:35.57 | tulth | that might work for me as well |
| 23:36.29 | brlcad | fyi, if you're not using the tcl/gui interface -- much of the mged tutorial will be rather different |
| 23:36.53 | tulth | you are a mindreader; i'm working through it now |
| 23:37.11 | tulth | i'll leave the gui up for now, still typing in my emacs eshell though for my commaand |
| 23:37.13 | brlcad | everything in the tutorials you can do via the gui can be done via the console or via classic mode regardless, though - you'll just have a little trouble figuring out just exactly what |
| 23:37.31 | brlcad | the mged quick reference sheet should help some |
| 23:37.56 | brlcad | wow, running mged via eshell.. |
| 23:38.02 | brlcad | lemme know how that works out ;) |
| 23:38.08 | tulth | yea, its great so far |
| 23:38.36 | brlcad | does mged's tab-completion work there? |
| 23:38.47 | tulth | hrm probably not |
| 23:38.58 | tulth | no, just tabs haha |
| 23:38.59 | brlcad | (try: make sph sph ; e s[tab] |
| 23:41.11 | tulth | yea, it just tabs |
| 23:41.16 | brlcad | k |
| 23:41.58 | brlcad | wants a brl-cad major mode |
| 23:42.05 | brlcad | that behaves like tar mode |
| 23:42.23 | tulth | yea, that would be fantastic |
| 23:42.39 | tulth | though, i haven't used tar mode |
| 23:42.55 | tulth | lots of others are nice, like gdb mode |
| 23:42.55 | brlcad | traverse the hierarchy, see the object details, edit values directly, have a few cmds to create new objects |
| 23:43.00 | tulth | org mode is cool too |
| 23:43.20 | tulth | yea, like maybe browse it with dired? |
| 23:43.21 | brlcad | an "mged mode" would be more like gdb mode |
| 23:43.29 | brlcad | right, dired is similar |
| 23:43.39 | brlcad | tar mode emulates dired on a tar file |
| 23:44.12 | brlcad | g mode would emulate direct on a g file |
| 23:44.17 | brlcad | s/direct/dired/ |
| 23:44.21 | tulth | hrm maybe even something like norton commander |