gt; Subject: Re: [Radiance-dev] Winrview and Winimage sources
> Date: March 16, 2016 1:10:33 PM PDT
>
> I see three topics there:
>
> Image viewer
> Do we actually have another option for that on Windows?
> What does OpenStudio use?
> On a side note: The next Gimp version (3.1
Because it's so fuc*ing big.
On 3/16/16, 1:51 PM, "Randolph M. Fritz"
mailto:rmfri...@gmail.com>> wrote:
Why is Qt an especially onerous dependency? It's LGPL and pretty common.
___
Radiance-dev mailing list
Radiance-dev@radiance-online.org
http://www
ses. Likewise for rvu, which I would prefer to be a driver connected
>> using the existing call mechanism.
>>
>> Cheers,
>> -Greg
>>
>> > From: Georg Mischler
>> > Subject: Re: [Radiance-dev] Winrview and Winimage sources
>> > Date: M
connected using the
existing call mechanism.
Cheers,
-Greg
> From: Georg Mischler
> Subject: Re: [Radiance-dev] Winrview and Winimage sources
> Date: March 16, 2016 4:59:48 AM PDT
>
> Just shows that I've been away from Radiance for too long, and didn't
> follow clos
I see what you mean. Even as binaries those are a hefty dependency.
___
Radiance-dev mailing list
Radiance-dev@radiance-online.org
http://www.radiance-online.org/mailman/listinfo/radiance-dev
I think the pipe approach is a good one. A separation of UI and
computational functions is probably a good way to organize the code, when
it is possible.
___
Radiance-dev mailing list
Radiance-dev@radiance-online.org
http://www.radiance-online.org/mailma
Am 2016-03-16 21:00, schrieb Randolph M. Fritz:
On 3/16/16, 1:51 PM, "Randolph M. Fritz"
mailto:rmfri...@gmail.com>> wrote:
Why is Qt an especially onerous dependency? It's LGPL and pretty
common.
On Wed, Mar 16, 2016 at 12:54 PM, Guglielmetti, Robert
wrote:
Because it's so fuc*ing big.
contained in 4 modules.
-Greg
> From: Georg Mischler
> Subject: Re: [Radiance-dev] Winrview and Winimage sources
> Date: March 16, 2016 4:24:01 PM PDT
>
> I don't think I'm gonna touch (or even try to understand) that driver
> business. On Windows, preview renderers have t
to call rvu as the parent process -- is that what
qtrvu is doing, or does it copy all the sources for rendering or call
the raycalls.c? I guess I should familiarize myself with that source
tree, but I've just been ignoring it up until now...
-Greg
From: Georg Mischler
Subject: Re: [Radia
But the Radiance source is 3 MB, and Qt 5.6 for Windows is 836 MB. Radiance's
dependency list is short and small excepting the Qt requirement for qtrvu. It's
kinda nice. Maybe I'm making too much of this. I dunno.
On 3/16/16, 2:00 PM, "Randolph M. Fritz"
mailto:rmfri...@gmail.com>> wrote:
On 3
On 3/16/16, 1:51 PM, "Randolph M. Fritz" > wrote:
Why is Qt an especially onerous dependency? It's LGPL and pretty common.
On Wed, Mar 16, 2016 at 12:54 PM, Guglielmetti, Robert <
robert.guglielme...@nrel.gov> wrote:
> Because it's so fuc*ing big.
>
When 2 GB RAM is standard for a low-end syst
er connected
> using the existing call mechanism.
>
> Cheers,
> -Greg
>
> > From: Georg Mischler
> > Subject: Re: [Radiance-dev] Winrview and Winimage sources
> > Date: March 16, 2016 4:59:48 AM PDT
> >
> > Just shows that I've been away from
Radiance picture viewer for Windows.
Then, we could re-introduce it to the source tree and keep it up to
date in future releases. Likewise for rvu, which I would prefer to
be a driver connected using the existing call mechanism.
Cheers,
-Greg
From: Georg Mischler
Subject: Re: [Radiance-dev] Winrvi
Just shows that I've been away from Radiance for too long, and didn't
follow closely enough what other people are doing.
RadDisplay looks very nice and useful! That's the direction I wouldd
have
liked to take the old viever in Rayfront (given the time I didn't have).
But my ignorance was only a
Hi,
There is our tool RadDisplay, which shows values when mousing over image.
On site there is rather old version of tool, but still does basic image
exploration http://deluminaelab.com/en/raddisplay_details.html
We are preparing new version of web site, and have in some plan to release
newer ver
"I miss being able to get luminance/radiance values by mousing over the
image, though."
Sigh. "If we had..."
___
Radiance-dev mailing list
Radiance-dev@radiance-online.org
http://www.radiance-online.org/mailman/listinfo/radiance-dev
On Windows, I used to use Picturenaut, which I liked a lot, but lately it's
been giving me library issues. No one else is complaining about that on
their forum, though, so it could just be a problem with my system.
Now I'm using Mitsuba, which is also a full-blown open source renderer but
has the
> As far as I am aware, there is no other standalone image viewer
> available on Windows.
I use HDRView.exe under Windows. It used to be available on Paul
Debevec's site, but is no longer. I send him an email a couple of
years ago, asking him whether he'd allow me to pass it on, but I did
not re
worth, now that I've been told *we* developed it
Cheers,
-Greg
From: Georg Mischler
Subject: [Radiance-dev] Winrview and Winimage sources
Date: March 15, 2016 3:55:10 AM PDT
Am 2016-03-15 03:40, schrieb Gregory J. Ward:
The sources to both winrview and winimage are sitting here on
hat's going to be more trouble than
it's worth, now that I've been told *we* developed it
Cheers,
-Greg
> From: Georg Mischler
> Subject: [Radiance-dev] Winrview and Winimage sources
> Date: March 15, 2016 3:55:10 AM PDT
>
> Am 2016-03-15 03:40, schrieb Grego
Am 2016-03-15 03:40, schrieb Gregory J. Ward:
The sources to both winrview and winimage are sitting here on my
disk. I don't think the DR team changed anything relevant after
my fixes.
Unfortunately, my old contract with LBNL does not cover
redistribution in source form. To make this possible, w
21 matches
Mail list logo
