01:40.08 |
*** join/#brlcad tancred
(~tancred@d233-64-63-249.clv.wideopenwest.com) |
02:01.29 |
CIA-10 |
BRL-CAD: 03brlcad *
10brlcad/src/liboptical/material.c: quell warning about type
conversion |
02:14.06 |
tancred |
I am curious. How difficult would it be to
have a "undo" feature in brlcad? So that if I don't like something
I did X number of undo changes could be done. |
02:16.44 |
brlcad |
tancred: that's been the topic of discussion
for several years now |
02:17.08 |
brlcad |
difficult is relative, of course -- but it
wouldn't be incredibly too hard |
02:17.15 |
brlcad |
there are many ways it could be done,
though |
02:25.40 |
tancred |
Have you heard about the Command design
pattern? |
02:35.03 |
tancred |
I have go now. I would like to talk about the
design later. Is there a time when the main developers are
online? |
02:35.42 |
brlcad |
yes, i'm familiar with it |
02:36.26 |
tancred |
Well I would like to talk later about the
design. When are you typically online? |
02:36.29 |
brlcad |
most of the devs are EST, though only a few
have made it in to here to date |
02:36.35 |
brlcad |
i'm here most all the time, though
;) |
02:36.46 |
brlcad |
and if I'm not, I read the log |
02:37.01 |
tancred |
How do I obtain the log via IRC? |
02:37.02 |
brlcad |
feel free to post and idle, and I'll
respond |
02:37.20 |
brlcad |
~logs |
02:37.21 |
ibot |
apt/ibot/jbot/purl all log to http://ibot.rikers.org/<channelname>/
where channelname is html encoded ie: %23debian | lines that start
with a space are not shown | some channels have stats at http://ibot.rikers.org/stats/<channelname>.html.gz |
02:37.33 |
tancred |
Thanks. |
02:37.40 |
*** part/#brlcad tancred
(~tancred@d233-64-63-249.clv.wideopenwest.com) |
03:00.04 |
narnia |
which means that only a few developers are in
the correct timezone. ;-) |
03:03.32 |
brlcad |
or just that more devs are needed :) |
03:11.03 |
narnia |
well this is true. |
03:13.47 |
narnia |
here is an interesting fact: while looking to
the disk space hogs i found this: 344M /usr/local/brlcad vs
2.3G /usr/local/OpenCASCADES.2 |
03:14.50 |
narnia |
orders of magnitude difference. |
03:21.22 |
brlcad |
not quite an order of magnitude :) only about
7x |
03:25.43 |
*** join/#brlcad guu
(guu@myth.gibbscam.com) |
07:06.48 |
*** join/#brlcad learner
(~brlcad@brlcad.bronze.supporter.pdpc) |
07:06.48 |
*** join/#brlcad dan_falck
(~danfalck@wbar1.sea1-4-5-017-067.sea1.dsl-verizon.net) [NETSPLIT
VICTIM] |
07:06.48 |
*** join/#brlcad CIA-10
(~CIA@flapjack.navi.cx) |
07:06.48 |
*** join/#brlcad brlcad
(~brlcad@brlcad.bronze.supporter.pdpc) [NETSPLIT
VICTIM] |
07:06.48 |
*** mode/#brlcad [+oo learner
brlcad] by irc.freenode.net |
07:06.55 |
*** join/#brlcad narnia
(~terrylr@johann.blauedonau.com) [NETSPLIT VICTIM] |
07:06.57 |
*** join/#brlcad guu
(guu@myth.gibbscam.com) [NETSPLIT VICTIM] |
07:09.05 |
CIA-10 |
BRL-CAD: 03brlcad *
10brlcad/src/liboptical/Makefile.am: ACK! shade has a multispectral
mode too and must be included into libmultispectral otherwise nasty
crashes occur. |
07:10.08 |
*** join/#brlcad ChanServ
(ChanServ@services.) |
07:10.08 |
*** mode/#brlcad [+o ChanServ]
by irc.freenode.net |
07:11.05 |
CIA-10 |
BRL-CAD: 03brlcad *
10brlcad/src/rttherm/Makefile.am: get rid of the stale files and
make lib dependant upon liboptical (for AmbientIntensity, rdebug,
background and maybe a couple other globals). |
07:14.41 |
CIA-10 |
BRL-CAD: 03brlcad * 10brlcad/src/liboptical/
(7 files): consistency on the #ifdef inclusions of
RT_MULTISPECTRAL, clean up the spectrum extern declarations now
that spectrum is now a liboptical global. |
07:17.45 |
narnia |
after re-read part11 for the nth time i have
come to an understanding of 'use' and 'reference'. the best analogy
for 'use' is include files. 'use' many be chained. the 'used'
object becomes local to the schema's scope. the best analogy for
'reference' is extern. the 'referenced' item is visible to the
schema's scope but not local to the schema's scope. if any object
is both 'used' and 'referenced' in the same schema 'use' wins
out. |
07:22.53 |
CIA-10 |
BRL-CAD: 03brlcad *
10brlcad/src/libmultispectral/init.c: remove rdebug,
AbientIntensity, spectrum, and background from libmultispectral as
those defines are (at least now) coming from liboptical's init.c.
this avoids duplicate symbol and initialization scope
errors |
07:23.48 |
CIA-10 |
BRL-CAD: 03brlcad *
10brlcad/src/rttherm/pixtest.c: spectrum is in liboptical library
now |
07:24.50 |
CIA-10 |
BRL-CAD: 03brlcad *
10brlcad/src/rttherm/ssamp-bw.c: quell a basename duplicate symbol
warning |
07:26.00 |
CIA-10 |
BRL-CAD: 03brlcad *
10brlcad/src/rttherm/ssampview.c: quell basename duplicate symbol
warning (system lib on os x), quell Tcl_CreateCommand argument type
warnings) |
07:27.12 |
CIA-10 |
BRL-CAD: 03brlcad *
10brlcad/src/rttherm/viewtherm.c: env_region is provided through
liboptical so not needed in the front end |
07:30.34 |
CIA-10 |
BRL-CAD: 03brlcad * 10brlcad/NEWS: fixed
rttherm previous results interference bug |
07:38.44 |
CIA-10 |
BRL-CAD: 03brlcad *
10brlcad/include/spectrum.h: add the headers this header depends
on |
07:41.44 |
CIA-10 |
BRL-CAD: 03brlcad *
10brlcad/src/rt/do.c: |
07:41.44 |
CIA-10 |
BRL-CAD: fix rttherm (and pretty much any of
the rt progs) from crashing when the output |
07:41.44 |
CIA-10 |
BRL-CAD: file already exists and is larger
than the size currently being rendered. also |
07:41.44 |
CIA-10 |
BRL-CAD: change the pixmap malloc to a
bu_malloc to avoid returning null |
08:11.30 |
narnia |
someone has been a busy little beaver.
;-) |
08:53.20 |
*** join/#brlcad PrezKennedy
(~Matthew@130.85.253.237) |
16:03.15 |
*** join/#brlcad ibot
(ibot@c-24-1-105-52.client.comcast.net) |
16:03.15 |
*** topic/#brlcad is http://brlcad.org/ || BRL-CAD is now Open
Source! || Screenshots: http://sourceforge.net/project/screenshots.php?group_id=105292
|| http://brlcad.org/images/mged.jpg
|| Release 7.2.0 is posted (20050305) |
17:34.37 |
*** join/#brlcad cad281
(~519b6e9e@bz.bzflag.bz) |
17:36.02 |
cad281 |
hi all |
17:36.35 |
*** join/#brlcad cad281
(~519b6e9e@bz.bzflag.bz) |
17:56.16 |
*** join/#brlcad Li
(lieven@host81-155-110-158.range81-155.btcentralplus.com) |
18:03.20 |
*** join/#brlcad Li
(lieven@host81-155-110-158.range81-155.btcentralplus.com) |
18:22.54 |
*** join/#brlcad Li
(lieven@host81-155-110-158.range81-155.btcentralplus.com) |
18:22.59 |
Li |
hi all |
18:24.06 |
narnia |
Li, hello, how goes it? |
18:24.17 |
Li |
well thank, you? |
18:24.46 |
narnia |
enjoying a spring day. |
18:25.16 |
Li |
here: rain and dreary, awaiting spring with
eagerness... |
18:25.33 |
Li |
May I ask you a question? |
18:25.38 |
narnia |
here: breezy, sun shine, warm. |
18:25.42 |
narnia |
sure |
18:25.58 |
Li |
I just started brlcad and am well impressed
... |
18:26.06 |
narnia |
good to hear |
18:26.26 |
Li |
using br-pix I can get 'sceenshots' but
... |
18:26.42 |
brlcad |
hello Li |
18:26.52 |
narnia |
yes |
18:27.04 |
Li |
I want to use them in a postscript file with
the background transparant. Know of any way to do this? |
18:27.11 |
Li |
hello brlcad |
18:27.14 |
narnia |
gimp |
18:27.37 |
Li |
of course ... |
18:27.43 |
brlcad |
Li: depends what you are
screenshotting |
18:28.04 |
Li |
what do you mean brlcad? |
18:28.07 |
brlcad |
Li: you can export postscript or plotter rules
to a file of the wireframe |
18:28.57 |
brlcad |
if you want the rendered, you'll have to use
an image-editing package to remove the background color for
transparencty |
18:29.19 |
Li |
Up to now I have been br-pix ing raytraced
pictures |
18:30.03 |
Li |
what would I start reading to export to
postscript? |
18:31.36 |
Li |
of course i meant fb-pix in all of the
above |
18:32.41 |
brlcad |
br-pix? |
18:32.46 |
brlcad |
ahh |
18:33.13 |
brlcad |
Li: in mged on the File menu Render
View |
18:33.43 |
brlcad |
again, that is only the wireframe, not any
raytraced image |
18:34.18 |
brlcad |
fb-png is probably more useful for insertion
into other documents |
18:34.30 |
Li |
I understand but it may be an alternative way
to represent my model. Many thanks. |
18:35.15 |
Li |
fb-png or the likes are indeed better to look
at and once I get the transparancy sorted it will look
great. |
18:35.20 |
brlcad |
if you export a plot file, there are a handful
of pl-* commands that might be of interest |
18:36.41 |
Li |
I have not really come accross plot files
before so there's an other thing I will read up on. |
18:37.00 |
brlcad |
it wouldn't be too difficult to add a
transparency option to the *-png commands for the background
color |
18:37.37 |
brlcad |
that would be single-value transparency,
though -- full alpha channel support would be more
difficult |
18:38.01 |
brlcad |
Li: it's the old format that used to control
the line plotter devices you may have seen in old movies
:) |
18:38.06 |
Li |
yes, I see what you mean. |
18:38.43 |
Li |
brlcad, are you (co-)developer of
this? |
18:41.01 |
brlcad |
yes |
18:41.41 |
Li |
thanks for making this available for public
use. |
18:41.55 |
brlcad |
it only took me five years :) |
18:43.15 |
brlcad |
getting BRL-CAD open sourced was rather
difficult and took a relatively "long time" (tm) .. in the end we
were just ultimately lucky (right place, people, time) |
18:44.29 |
Li |
I can imagine that being the difficult
part. |
18:44.51 |
brlcad |
It's been great since, though |
18:45.06 |
Li |
I have just compiled on a linux ppc (ibook2)
and simply ran a make on it and all worked (until now) |
18:45.29 |
brlcad |
until now? |
18:45.46 |
brlcad |
something hasn't worked? or you mean the
transparency feature? |
18:45.53 |
Li |
I have only done basic things with it.
:-) |
18:46.08 |
Li |
I do not foresee problems. |
18:46.42 |
Li |
I got it to crash (but that was my own
fault) |
18:46.48 |
brlcad |
feel free to hang out here and get more
involved :) |
18:47.08 |
brlcad |
oh? a crash is bad even if your "fault"
:) |
18:47.16 |
Li |
I will and look forward to it. |
18:48.08 |
Li |
I created a circular refernce in 2 regions.
then tried drawing them. bang. |
18:49.58 |
brlcad |
eek, that's not good |
18:50.06 |
brlcad |
funny, but not good :) |
18:50.35 |
Li |
:-)) |
18:50.46 |
brlcad |
do you have an sf.net account to post a bug
report for that? |
18:51.59 |
Li |
No I have not but I am not sure this warrants
a bug since I created the reference with ted so it would be very
difficult to check and flag. Do you agree? |
18:52.16 |
brlcad |
anything that causes a crash is a
bug |
18:53.04 |
brlcad |
now if it pops up a dialog and quits, that's
different .. but it shouldn't ever crash |
18:53.32 |
Li |
true. I will get that organised. Can i file
feature requests there too (transparancy)? |
18:54.33 |
brlcad |
of course! |
18:54.35 |
brlcad |
please so |
18:54.38 |
brlcad |
s/so/do/ |
18:55.02 |
Li |
Many thanks all. Now I must get back to
work. |
18:55.14 |
brlcad |
same here, thank you |
21:38.50 |
*** join/#brlcad narnia
(~terrylr@johann.blauedonau.com) |