00:06.45 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
00:10.10 |
Notify |
03BRL-CAD:brlcad * 62742 brlcad/trunk/CHANGES:
the histogram interface isn't going away, and don't need to
deprecate to rename (minimally impacting if done
carefully). |
00:16.36 |
Notify |
03BRL-CAD:brlcad * 62743 brlcad/trunk/CHANGES:
schedule removal of all the public API routines that expose a
Tcl_Interp (except for libtclcad) |
00:39.53 |
*** join/#brlcad clock
(~clock@77-58-143-135.dclient.hispeed.ch) |
01:18.25 |
*** join/#brlcad ries
(~ries@D979EA84.cm-3-2d.dynamic.ziggo.nl) |
01:25.22 |
Notify |
03BRL-CAD:brlcad * 62744 brlcad/trunk/CHANGES:
missed two tcl funcs |
01:27.56 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
01:36.44 |
starseeker |
yow - didn't even have SBCL on my
machine |
01:37.01 |
Notify |
03BRL-CAD:brlcad * 62745
brlcad/trunk/include/db.h: remove the v4 boolean preprocessor
symbols, new DB_OP symbols replace them |
01:40.23 |
Notify |
03BRL-CAD:brlcad * 62746 brlcad/trunk/CHANGES:
db4 symbols removed |
01:47.08 |
*** join/#brlcad ries
(~ries@D979EA84.cm-3-2d.dynamic.ziggo.nl) |
02:10.28 |
Notify |
03BRL-CAD:brlcad * 62747
brlcad/trunk/include/raytrace.h: ws column-70 comment
formatting |
02:53.23 |
Notify |
03BRL-CAD:brlcad * 62748
brlcad/trunk/src/conv/nmg/g-nmg.c: use the wdb symbols since we're
calling mk_addmember |
03:01.46 |
Notify |
03BRL-CAD:starseeker * 62749
brlcad/trunk/src/librt/op.c: Make the 'treat this as C++' test
happy and explicitly cast to the enum |
03:06.50 |
starseeker |
brlcad: don't we want the regex for
fbio.h->fb.h? |
03:07.15 |
*** join/#brlcad sofat
(~sofat@202.164.53.117) |
03:09.19 |
Notify |
03BRL-CAD:starseeker * 62750
brlcad/trunk/CHANGES: Put fbio.h regex back into CHANGES |
03:11.45 |
sofat |
brlcad there is link of about us page please
check. |
03:11.47 |
sofat |
http://202.164.53.122/~hitesh/wordpress/ |
03:12.11 |
sofat |
one work is left |
03:12.25 |
sofat |
is plugin for xml parsing |
03:30.20 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
03:50.24 |
brlcad |
<PROTECTED> |
03:58.15 |
Notify |
03BRL-CAD:brlcad * 62751
brlcad/trunk/include/rt/op.h: need a null to indicate an unset
op |
03:59.08 |
Notify |
03BRL-CAD:brlcad * 62752
brlcad/trunk/include/wdb.h: begin eliminating the magic op chars,
use the new DB_OP_* values |
04:16.08 |
Notify |
03BRL-CAD:brlcad * 62753
(brlcad/trunk/src/conv/g-dot.c brlcad/trunk/src/conv/g-xxx.c and 17
others): propagate the DB_OP_* enumeration type in leu of having
magic chars all throughout the code |
04:28.41 |
*** join/#brlcad teepee
(~teepee@gateway/tor-sasl/teepee) |
07:35.13 |
*** join/#brlcad luca79
(~luca@net-2-34-220-156.cust.vodafonedsl.it) |
07:37.51 |
*** join/#brlcad d_rossberg
(~rossberg@66-118-151-70.static.sagonet.net) |
07:38.46 |
*** join/#brlcad ries
(~ries@D979EA84.cm-3-2d.dynamic.ziggo.nl) |
08:03.15 |
*** join/#brlcad teepee-
(bc5c2133@gateway/web/freenode/ip.188.92.33.51) |
09:15.38 |
*** join/#brlcad luca79
(~luca@net-2-34-220-156.cust.vodafonedsl.it) |
09:36.45 |
*** join/#brlcad teepee-
(bc5c2133@gateway/web/freenode/ip.188.92.33.51) |
10:18.53 |
*** join/#brlcad teepee-
(bc5c2133@gateway/web/freenode/ip.188.92.33.51) |
11:29.23 |
*** join/#brlcad teepee-
(bc5c2133@gateway/web/freenode/ip.188.92.33.51) |
11:40.07 |
*** join/#brlcad teepee-
(bc5c2133@gateway/web/freenode/ip.188.92.33.51) |
11:40.24 |
*** part/#brlcad teepee-
(bc5c2133@gateway/web/freenode/ip.188.92.33.51) |
12:05.13 |
``Erik |
installs xcode6
o.O |
12:06.15 |
``Erik |
I wonder if it'll be able to cope with a cmake
-G Xcode BRL-CAD |
12:06.28 |
starseeker |
winces |
12:07.00 |
starseeker |
historically, that's a pretty slow way to
build BRL-CAD |
12:08.49 |
*** join/#brlcad Stragus
(~alexis@50-193-129-193-static.hfc.comcastbusiness.net) |
12:15.49 |
*** join/#brlcad clock
(~clock@77-58-143-135.dclient.hispeed.ch) |
12:19.32 |
*** join/#brlcad archivist
(~archivist@host81-149-189-98.in-addr.btopenworld.com) |
12:33.44 |
``Erik |
thus the experiment :D |
12:37.56 |
*** join/#brlcad FreezingCold
(~FreezingC@CPE602ad06bea2a-CM602ad06bea27.cpe.net.cable.rogers.com) |
12:40.18 |
*** join/#brlcad ries
(~ries@D979EA84.cm-3-2d.dynamic.ziggo.nl) |
13:33.10 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
13:55.18 |
Notify |
03BRL-CAD:starseeker * 62754
brlcad/trunk/src/libfb/if_osgl.cpp: Add some logging to get a feel
for the logic flow of the framebuffer. Remove the hardware option
for color maps - there was a note that the code was never tested
even in the original ogl fb, and it's X specific as well. |
14:10.03 |
*** join/#brlcad teepee-
(bc5c2133@gateway/web/freenode/ip.188.92.33.51) |
14:12.17 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
14:22.07 |
Notify |
03BRL-CAD:starseeker * 62755
brlcad/trunk/src/libfb/if_osgl.cpp: Unless we hit a major blocker,
just go with double buffer. OSG should provide us with the
necessary tools to make that 'just work' and single buffer + OSG
looks like it involves some complications that probably aren't
worth dealing with. |
15:03.35 |
Notify |
03BRL-CAD:starseeker * 62756
(brlcad/trunk/src/fbserv/fbserv.c
brlcad/trunk/src/libfb/if_osgl.cpp): Somewhere in here (probably
should be in do_event rather than the poll function itself) we seem
to need to update the OSG viewer frame to recover from drawing
damage when the window is hidden. fbserv has an odd setup where it
has hardcoded WIN32 and non-WIN32 timing values for calling fb_poll
- need to make that a |
15:03.37 |
Notify |
recommendation from the fb implementation via
a callback. The non-WIN32 default (60 seconds??) is far too slow
for any sort of interactive updating - it only works with ogl
because the X window used there handles repainting without needing
to call fb_poll. |
15:13.04 |
*** join/#brlcad Stragus
(~alexis@50-193-129-193-static.hfc.comcastbusiness.net) |
15:42.19 |
*** join/#brlcad Stragus
(~alexis@50-193-129-193-static.hfc.comcastbusiness.net) |
15:45.04 |
Notify |
03BRL-CAD Wiki:Rpetcher61 * 0
/wiki/User:Rpetcher61: |
15:47.59 |
Notify |
03BRL-CAD:starseeker * 62757
(brlcad/trunk/include/fb.h brlcad/trunk/src/fbserv/fbserv.c and 14
others): Encode the refresh rates in the fb definitions, so we can
let ogl and osgl do different things. As a happy bonus, another
WIN32 ifdef bites the dust. |
15:54.30 |
``Erik |
yup, new xcode still sucks tryign to load
BRLCAD.xcodeproject |
15:55.57 |
Notify |
03BRL-CAD:carlmoore * 62758
brlcad/trunk/doc/docbook/system/man1/en/rt.xml: touch-up of rt
manpage; includes 2 usages of 'opposite of' |
15:56.25 |
starseeker |
``Erik: almost wonder if it would be worth
pointing them to our build as a possible optimization test
case |
15:56.57 |
brlcad |
starseeker: what version of glibc was that
pthread error for? |
15:57.24 |
starseeker |
erm. Not sure offhand - whatever the latest
is in Ubuntu |
15:59.38 |
brlcad |
we might have a problem, but there's a glibc
thread indicating that was a bug in glibc 2.7-16 and another saying
it still persists in 2.9-21, fixed in 2.10 |
16:01.03 |
starseeker |
my guess is it's eglibc 2.19, but I'll have to
check tonight |
16:01.44 |
brlcad |
k |
16:01.56 |
brlcad |
chances are, it's a bug in our code, so I'll
keep looking |
16:05.24 |
starseeker |
could this be related?
http://stackoverflow.com/questions/1105745/pthread-mutex-assertion-error |
16:08.24 |
starseeker |
come to think of it probably not, since I only
seem to be running into it with the optimized builds |
16:14.14 |
Notify |
03BRL-CAD:starseeker * 62759
brlcad/trunk/src/libfb/if_osgl.cpp: We need to allocate both of
these once shared memory re-enters the picture for stand-alone
windows. |
16:16.34 |
brlcad |
starseeker: very much related |
16:17.24 |
brlcad |
the question is whether it's our logic or the
compiler performing a mutex lock on a mutex that thread doesn't
own |
16:18.09 |
brlcad |
like I said, almost certain it's our logic and
perhaps related to the new thread IDs, but sanity check against the
system glibc version is something easy to eliminate |
16:41.09 |
Notify |
03BRL-CAD:carlmoore * 62760
brlcad/trunk/src/libfb/if_osgl.cpp: fix spelling |
16:43.11 |
Notify |
03BRL-CAD:carlmoore * 62761
brlcad/trunk/src/rt/view.c: Fix the Usage for rt; this file is
view.c (where is viewedge.c used?) |
17:26.49 |
*** join/#brlcad DarkCalf
(~DarkCalf@173.231.40.98) |
17:27.26 |
Notify |
03BRL-CAD:carlmoore * 62762
brlcad/trunk/doc/docbook/system/man1/en/rtedge.xml: touchup of
rtedge.xml |
17:30.23 |
*** join/#brlcad FreezingCold
(~FreezingC@CPE602ad06bea2a-CM602ad06bea27.cpe.net.cable.rogers.com) |
17:35.42 |
Notify |
03BRL-CAD:starseeker * 62763
brlcad/trunk/src/other/CMakeLists.txt: add a make clean file for
distcheck |
17:47.33 |
*** join/#brlcad sofat
(~sofat@202.164.45.204) |
18:23.46 |
Notify |
03BRL-CAD:starseeker * 62764
(brlcad/trunk/include/bu/malloc.h brlcad/trunk/src/libbu/malloc.c
and 4 others): Start some refactoring/reshuffling of the shmget
logic. |
18:25.20 |
*** join/#brlcad mihaineacsu
(~mihaineac@92.81.139.223) |
18:31.06 |
Notify |
03BRL-CAD:starseeker * 62765
(brlcad/trunk/src/libfb/CMakeLists.txt
brlcad/trunk/src/libfb/if_osgl.cpp): Separate out the OSG derived
handler into its own file, so it's clear what is and isn't based
off of the OSG license code. (Helps readability too.) |
18:40.17 |
*** join/#brlcad sofat
(~sofat@202.164.45.204) |
18:40.25 |
sofat |
hi brlcad |
18:41.32 |
sofat |
sir i want to discuss some points regarding
the language conversion |
18:41.34 |
sofat |
on about as page |
18:41.34 |
sofat |
us |
18:57.36 |
sofat |
brlcad, sir are you there ? |
19:02.27 |
Stragus |
He will see the message, he may be busy at the
moment |
19:02.49 |
Notify |
03BRL-CAD:starseeker * 62766
brlcad/trunk/src/libfb/if_osgl.cpp: Use setImage for the osg::Image
in order to use memory provided by osgl_getmem |
19:11.33 |
*** join/#brlcad clock
(~clock@77-58-143-135.dclient.hispeed.ch) |
19:16.32 |
brlcad |
~ask |
19:16.32 |
infobot |
Questions in the channel should be specific,
informative, complete, concise, and on-topic. Don't ask if you can
ask a question first. Don't ask if a person is there; just ask
what you intended to ask them. Better questions more frequently
yield better answers. We are all here voluntarily or against our
will. |
19:17.16 |
brlcad |
sofat, on irc, you should just speak instead
of asking if someone is here ... they'll/I'll respond as soon as
possible if you're still on IRC nearly always |
19:17.45 |
brlcad |
and this is not formal, you don't have to call
anyone sir |
19:17.55 |
sofat |
sorry |
19:18.24 |
brlcad |
don't be sorry, lots of people start out that
way ;) |
19:18.37 |
sofat |
okay so brlcad |
19:18.46 |
sofat |
i want to ask some questions |
19:18.50 |
brlcad |
lots of people live on irc, 24 hours a day, 7
days a week ;) |
19:19.10 |
sofat |
okay |
19:21.07 |
sofat |
my question regarding language conversation ,
In this case first i use google language converter |
19:22.26 |
brlcad |
eh? why? :) we have translations hand-written
by people that speak those languages... |
19:23.25 |
brlcad |
it'd be awesome to offer automatic
translations for languages we don't yet have, but that's not a
priority for the first step here |
19:24.02 |
sofat |
ok so i have one idea |
19:24.06 |
brlcad |
do you have a source checkout, did you compile
and look at the about page sources? |
19:24.43 |
sofat |
yes |
19:26.30 |
Notify |
03BRL-CAD:starseeker * 62767
brlcad/trunk/src/libfb/if_osgl.cpp: Not clear these comments have
much to do with the implementation as it exists today. |
19:27.18 |
sofat |
if i add new tag regarding the language into
xml file structure |
19:28.40 |
sofat |
so this is very easy way to pick the language
of content and then i store the content according the language in
database |
19:30.23 |
``Erik |
automatic translation tends butcher idioms...
could be a start for a human translator to fix, but I wouldn't put
too much trust in anything automatic :) take a phrase, pop it in
google translate and carry that phrase through a few languages and
back to the original, it's a fun variant of the 'telephone' game
:D |
19:30.26 |
sofat |
so user want to read the data the pick a
language form drop down and get the data |
19:33.21 |
brlcad |
sofat: but the language is already
indicated |
19:33.41 |
sofat |
english |
19:33.45 |
brlcad |
no |
19:33.48 |
brlcad |
the directory is the 2-char language
code |
19:34.08 |
brlcad |
that's specifically why I suggested the about
page |
19:34.15 |
brlcad |
because we have it in 4-5 different
languages |
19:34.46 |
sofat |
yes i know |
19:35.07 |
brlcad |
then I'm not understanding |
19:35.28 |
brlcad |
or you're not understanding, someone is
confused :) |
19:35.35 |
brlcad |
probably me |
19:35.47 |
sofat |
yes :) |
19:36.01 |
sofat |
i think me |
19:36.20 |
brlcad |
where are the about page sources? |
19:37.26 |
brlcad |
(in our repository) |
19:37.33 |
sofat |
no |
19:38.32 |
sofat |
sir about us page is not single page its part
of wordpress |
19:38.33 |
brlcad |
that was not a yes/no question ... I'm asking
where you think the files are for the "about" page. where are
they? |
19:41.58 |
sofat |
about us is not specific file its page in
wordpress |
19:42.28 |
sofat |
http://pastie.org/9559799 |
19:43.03 |
brlcad |
okay, so that's part of the
misunderstanding |
19:43.16 |
brlcad |
the about page IS a specific file (actually,
it's several files) |
19:43.18 |
sofat |
yes i am secure |
19:43.22 |
brlcad |
it's a file in our repository |
19:43.37 |
brlcad |
do you have a checkout of our source files
from subversion? |
19:44.08 |
brlcad |
if you have mac or linux, this step should
work: |
19:44.11 |
brlcad |
~cadsvn |
19:44.11 |
infobot |
To obtain BRL-CAD from Subversion: svn
checkout https://svn.code.sourceforge.net/p/brlcad/code/brlcad/trunk
brlcad |
19:44.17 |
sofat |
linux |
19:44.44 |
sofat |
please give me subversion link. |
19:44.44 |
brlcad |
run that command and it'll pull all our files
to your computer |
19:47.00 |
sofat |
wait |
19:49.17 |
mihaineacsu |
<PROTECTED> |
19:51.46 |
*** join/#brlcad Stragus
(~alexis@50-193-129-193-static.hfc.comcastbusiness.net) |
19:53.31 |
sofat |
my Internet speed is slow |
19:53.42 |
brlcad |
it's a lot of files ;) |
19:53.53 |
sofat |
yes |
19:53.58 |
sofat |
i see |
19:54.19 |
Stragus |
is trying to find the french
and spanish versions of BRL-CAD's page to check for
errors |
19:54.23 |
brlcad |
so when that finishes, go look in
brlcad/doc/docbook ... there is all our documentation
files |
19:54.25 |
Stragus |
pages* |
19:54.49 |
sofat |
okay |
19:55.42 |
brlcad |
Stragus: hay la mayoridad de los tutoriales en
espan~ol pero no el about pagina |
19:56.27 |
Stragus |
Okay :) |
19:56.33 |
brlcad |
about is humorously available as en, hy, it,
and ru :) |
19:57.04 |
brlcad |
i could do one in es, but I'm wanting to
rewrite it first |
19:57.08 |
brlcad |
it's a terribly dated about page |
19:57.12 |
*** join/#brlcad Notify
(~notify@66-118-151-70.static.sagonet.net) |
19:57.27 |
brlcad |
notes that would possibly
make a great set of gci tasks |
19:57.43 |
Stragus |
Really? The links for alternate languages
aren't clearly visible, I must say |
19:58.11 |
brlcad |
what links? |
19:58.31 |
Stragus |
You say the about page has alternate versions,
are these versions online somewhere? |
19:58.44 |
brlcad |
there are no links .. we just have the
translations in our repo (docbook/xml source files) |
19:58.53 |
Stragus |
Ah, got it |
19:58.58 |
brlcad |
they are compiled and installed |
19:59.01 |
brlcad |
but not online |
19:59.07 |
brlcad |
that's sort of what sofat is working
on |
19:59.07 |
Stragus |
nods |
19:59.13 |
Stragus |
Cool then |
19:59.50 |
brlcad |
we compile them to html by default and
optionally to pdf if the tools are available |
20:02.32 |
brlcad |
sofat: this may likely be helpful: http://el-tramo.be/blog/integrating-docbook-with-wordpress/ |
20:03.18 |
brlcad |
basically, that person just created a
different stylesheet .. we could use something like that stylesheet
to automatically output files that can live in the web root and be
known to wordpress |
20:06.05 |
*** join/#brlcad mihaineacsu
(~mihaineac@92.81.139.223) |
20:07.36 |
*** join/#brlcad gagan_
(~gagan@124.253.225.188) |
20:09.26 |
gagan_ |
Hi guys, I read about the rt^3 and seems
interesting |
20:09.33 |
gagan_ |
anyone could tell me more about it ? |
20:10.44 |
brlcad |
gagan_: sure, what would you like to
know? |
20:11.01 |
gagan_ |
brlcad, just some more idea |
20:11.09 |
gagan_ |
how it works |
20:11.25 |
gagan_ |
If I want to start how can I go into its
development |
20:11.27 |
brlcad |
it's overarching goal is to implement a solid
modeling CAD kernel that can be used to build CAD
applications |
20:11.39 |
brlcad |
CAx applications actually |
20:11.56 |
*** join/#brlcad sofat
(~sofat@202.164.45.204) |
20:12.09 |
sofat |
thanks |
20:12.10 |
brlcad |
encapsulating and reusing the massive
libraries in brl-cad, but keeping things simple so the API is easy
to use and clean |
20:12.15 |
gagan_ |
brlcad, I am noob in 3D modelling so please
pardon my vague questions |
20:12.22 |
brlcad |
gagan_: don't be shy |
20:12.23 |
gagan_ |
but does that depend on raytracing
engine |
20:12.52 |
gagan_ |
should not the kernel store data like radius,
center and material of a sphere ? |
20:13.01 |
gagan_ |
how raytracing comes into action here
? |
20:13.10 |
brlcad |
so good questions |
20:13.28 |
brlcad |
in BRL-CAD (not in rt^3), we have a bunch of
libraries that do different things |
20:13.47 |
brlcad |
e.g., there's libbu which is a basic utility
library for things like handling strings and allocating
memory |
20:13.56 |
brlcad |
there's libbn for math, basic
numerics |
20:14.34 |
brlcad |
the biggest and most complex is "librt" which
is a bit of a misnomer in the sense that it's both the geometry
representation and ray tracing capabilities |
20:14.44 |
gagan_ |
Yes |
20:14.49 |
gagan_ |
I see there |
20:14.59 |
brlcad |
it is the library where geometry is stored,
data like radius, center, material, etc ;) |
20:15.08 |
gagan_ |
even I was thinking you have kept primitives
under shapes in librt |
20:15.15 |
brlcad |
it's also the library where we can shoot a ray
to sample that geometry (i.e., analyze it) |
20:15.21 |
brlcad |
yep |
20:15.44 |
brlcad |
the two are very tightly coupled from the
binary file representation on disk to what is actually accessed in
memory |
20:16.08 |
brlcad |
this is predominantly done for high
performance, there are very minimal I/O operations to read very
large/complex geometry |
20:16.28 |
gagan_ |
I see |
20:16.41 |
brlcad |
and database objects are only evaluated as
much as they need to be exposed (again, for performance) |
20:17.29 |
brlcad |
so I can give you a table of contents REALLY
fast or with just a little more processing, I can tell you how many
entities there are of a given type, or with a little more unfolding
I can say how big they are, and with a little more I can evaluate
them |
20:17.40 |
brlcad |
layers, like an onion ;) |
20:18.50 |
brlcad |
so if you never use the ray tracing portion,
you don't pay any costs, but if you need to shoot a ray -- this can
also be done efficiently with very little memory |
20:19.48 |
brlcad |
rt^3 (aka Geometry Engine, aka MOOSE) is
similar in objectives to the ACIS CAD kernel |
20:20.05 |
brlcad |
it aims to encapsulate a LOT of complexity and
simplify |
20:20.56 |
gagan_ |
thinking over this |
20:21.05 |
gagan_ |
So raytracing comes into role |
20:21.27 |
gagan_ |
when I need to view a realistic view or
analyse the object |
20:21.38 |
gagan_ |
calculate its weight/mass |
20:21.41 |
gagan_ |
correct ? |
20:22.12 |
brlcad |
yes! |
20:22.19 |
brlcad |
and other purposes |
20:22.23 |
brlcad |
raytracing is just one of several common
analysis queries (basically an extension of "is this point inside
or outside the object?") |
20:22.26 |
gagan_ |
other purposes like ? |
20:22.32 |
gagan_ |
I see |
20:22.51 |
brlcad |
which is used for determining whether two
objects overlap, for example |
20:22.57 |
gagan_ |
hmm |
20:23.03 |
brlcad |
this is called an "Interference" in most CAD
systems |
20:23.19 |
gagan_ |
does it play any role in operations like
union |
20:23.24 |
brlcad |
and is a modeling error that usually must be
corrected to have accurate mass/weight properties |
20:23.59 |
gagan_ |
do I need that for union substraction
? |
20:24.03 |
brlcad |
it only plays a role in so much as we might
not evaluate a boolean expression until we shoot a ray |
20:24.29 |
brlcad |
faster to evaluate at raytracing time and
preserve the feature edit (subtract this hole) |
20:24.52 |
brlcad |
it's the basis for some parametric editing
capabilities |
20:25.01 |
gagan_ |
I see |
20:26.46 |
gagan_ |
CGAL supports bolleen operations |
20:27.04 |
gagan_ |
so does CGAL also uses raytracing
method |
20:27.14 |
gagan_ |
or there are some other available methods
? |
20:28.23 |
brlcad |
iirc, cgal only does booleans on polyhedra,
no? |
20:28.40 |
gagan_ |
Yes |
20:29.02 |
brlcad |
we also have booleans on polyhedra .. that's
an entirely different set of code (our "nmg" library) |
20:29.28 |
brlcad |
and we're in the middle of implementing
booleans on brep/nurbs |
20:29.34 |
brlcad |
that's the holy grail |
20:29.44 |
gagan_ |
~_~ |
20:29.45 |
infobot |
STOP THAT! |
20:29.51 |
brlcad |
heh |
20:29.56 |
brlcad |
infobot: shut up |
20:29.57 |
infobot |
from memory, shut up is I'll think about
it |
20:30.10 |
sofat |
lol |
20:30.12 |
brlcad |
infobot: no, shut up is <reply>I'll
think about it |
20:30.12 |
infobot |
brlcad: okay |
20:30.16 |
brlcad |
infobot: shut up |
20:30.17 |
infobot |
I'll think about it |
20:30.27 |
brlcad |
fun fun |
20:30.31 |
gagan_ |
LD |
20:30.33 |
gagan_ |
:D |
20:30.43 |
sofat |
yah |
20:30.49 |
brlcad |
the "~" marker is that bot's attention
character |
20:30.52 |
brlcad |
~hello |
20:30.53 |
infobot |
Howdy Bub |
20:30.55 |
gagan_ |
Oh I see |
20:31.13 |
sofat |
yo yo hello thats new version |
20:31.19 |
sofat |
develop by me |
20:31.52 |
brlcad |
wow, confluence wiki might be the way to
go... |
20:31.58 |
gagan_ |
If we add ogre to brlcad, ratracing will still
remain |
20:32.09 |
gagan_ |
and is necessary part |
20:32.10 |
gagan_ |
I see |
20:32.19 |
brlcad |
sofat: so I think this ship needs a change of
direction, after you get brl-cad compiled :) |
20:32.45 |
brlcad |
gagan_: the raytracing lib is also the ".g"
library for the file format and all objects |
20:33.26 |
brlcad |
gagan_: I'd like to separate the two concepts
(creating a libg), but it's a bit complicated at the moment and
unclear whether it can happen without affecting performance or
encapsulation |
20:33.57 |
gagan_ |
hmm |
20:34.03 |
brlcad |
by the way, we have about 9 other libraries
too ;) |
20:34.19 |
gagan_ |
-_- |
20:34.54 |
brlcad |
oops, my bad -- 18 others |
20:35.05 |
gagan_ |
again -_- |
20:35.06 |
teepee |
whispers 3 hours 25
minutes... ;) |
20:35.18 |
brlcad |
haha, thx teepee |
20:35.38 |
brlcad |
7 hours 25 minutes.. |
20:35.49 |
teepee |
nope, the widget is broken |
20:35.56 |
brlcad |
huh |
20:35.58 |
teepee |
in my browser it says 1 hour |
20:36.58 |
teepee |
it's calculating local time to midnight, but
the text above says different :) |
20:39.45 |
brlcad |
yeah, i see that |
20:39.48 |
brlcad |
no worries |
20:39.53 |
brlcad |
panics |
20:44.41 |
Notify |
03BRL-CAD:starseeker * 62769
brlcad/trunk/src/libfb/if_osgl.cpp: Getting closer - need to
consolidate the write routines... |
20:52.05 |
starseeker |
brlcad: are you looking at this? https://www.atlassian.com/opensource/overview
(confluence) |
21:03.38 |
*** join/#brlcad gagan_
(~gagan@124.253.225.188) |
21:04.41 |
Notify |
03BRL-CAD:n_reed * 62770
brlcad/branches/brep-debug/src/libbrep/intersect.cpp:
MinimumDistanceTo() returns a bad result if input segments are on
the same line, so we need another check |
21:06.33 |
Notify |
03BRL-CAD Wiki:Sean * 7737 /wiki/Compiling:
tighten up the steps a bit, remove installation, clarify which are
optional for the vm |
21:21.15 |
Notify |
03BRL-CAD:n_reed * 62771
brlcad/branches/brep-debug/src/libbrep/intersect.cpp: remove
redundant conditional |
21:54.54 |
*** part/#brlcad gagan_
(~gagan@124.253.225.188) |
22:32.42 |
*** join/#brlcad Stragus
(~alexis@173-166-149-129-washingtondc.hfc.comcastbusiness.net) |
22:47.58 |
Notify |
03BRL-CAD Wiki:Sean * 7738
/wiki/OpenCL_GPGPU_Raytracing: Created page with "Contact "brlcad"
on irc.freenode.net" |
22:54.16 |
Notify |
03BRL-CAD Wiki:Sean * 7739
/wiki/OpenCL_GPGPU_Raytracing: |
22:57.45 |
Notify |
03BRL-CAD Wiki:Sean * 7740
/wiki/Coherent_Raytracing: Created page with "Contact "brlcad" on
irc.freenode.net BRL-CAD has one of the oldest and fastest parallel
ray tracing implementations around but we don't currently leverage
modern techniques t..." |
23:03.43 |
Notify |
03BRL-CAD Wiki:Sean * 7741
/wiki/RoundtripDocumentation: Created page with "BRL-CAD uses the
Docbook XML format for most of our documentation. However, most
everyone appreciates the simplicity of editing documentation online
(e.g., on a wiki). We wa..." |
23:09.16 |
Notify |
03BRL-CAD:starseeker * 62772
brlcad/trunk/src/libfb/if_osgl.cpp: Get fbclear working when we're
using the viewer |
23:09.33 |
Notify |
03BRL-CAD Wiki:Sean * 7742 /wiki/X3D_Importer:
Created page with "BRL-CAD has support for dozens of different 3D
geometry file formats. We do not, however, have an importer for the
X3D geometry format. Your project involves implementing
im..." |
23:12.00 |
*** join/#brlcad starseek1r
(~starseeke@66-118-151-70.static.sagonet.net) |
23:12.50 |
*** join/#brlcad brlcad
(~sean@66-118-151-70.static.sagonet.net) |
23:16.15 |
*** join/#brlcad teepee
(~teepee@gateway/tor-sasl/teepee) |
23:34.50 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
23:57.52 |
Notify |
03BRL-CAD:starseeker * 62773
brlcad/trunk/src/libfb/if_osgl.cpp: Looking much better
now. |