That's a great idea -- there may be a MIME type for HDR files already, so be sure not to step on any toes. Thanks for volunteering, Randolph, as I wouldn't know how to go about it.
Cheers,
-Greg
···
From: "Axel Jacobs" <[email protected]>
Date: October 25, 2008 11:09:21 AM PDT
I agree. There are too many apps which already use "pic", and it's
confusing besides; there's more information in an HDR map than there
is in a conventional image file. Perhaps we could also register a MIME
type for hdr files? Or has that already been done? I'm willing to
undertake the work on that, if people want and if it hasn't been done
yet.
Brilliant!
I've looked into this, but are are not sufficiently confident with HDR
file format.
Let's move this thread over to dev and continue there.
Axel
Dear Greg,
I'm just updating my tutorial, and decided to be be more consistent
with directories and file extensions. I personally still use trad a
lot--it's convenient, fast, and doesn't get in the way.
trad still puts the old .pic extension on image files. The general
consensus nowadays seems to be to use .hdr. Since it's a quick
find-and-replace jobbie, may I propose to use this convention for rad
and trad as well. I'd be happy to send you patch.
Regards
Axel
I rather like (and have become accustomed to, and have built scripts around) the .pic extension referring to a raw Radiance-generated image. I dunno how everyone else feels, but with all the available sources for hdr images, some of which we can call "hdr" images, I'd rather keep our good old .pic extension as a Radiance community standard.
···
On Oct 25, 2008, at 8:20 AM, Axel Jacobs wrote:
trad still puts the old .pic extension on image files. The general
consensus nowadays seems to be to use .hdr. Since it's a quick
find-and-replace jobbie, may I propose to use this convention for rad
and trad as well. I'd be happy to send you patch.
All suffixes in Radiance are just a convention, but since both Windows and Mac OS X look at the suffix as a first indication of file type, it's not a bad idea to standardize them. The "hdr" suffix has definitely been picked up by the mainstream as a Radiance image file, while the "pic" suffix gets confused for other types on the different systems. In this respect, I agree with Axel that it would be beneficial to change this convention, if people are OK with that.
Although I can see Rob's point that it's nice to have a suffix that uniquely identifies a Radiance-generated image from other possible sources, the de facto use of extensions does not support this these days. An extension indicates the file type, not its creator.
If anyone else has a good reason why we should not switch to using ".hdr" in place of ".pic" in rad/trad/etc. in the next release, now is the time to speak up.
-Greg
···
From: Rob Guglielmetti <[email protected]>
Date: October 25, 2008 7:43:24 AM PDT
On Oct 25, 2008, at 8:20 AM, Axel Jacobs wrote:
trad still puts the old .pic extension on image files. The general
consensus nowadays seems to be to use .hdr. Since it's a quick
find-and-replace jobbie, may I propose to use this convention for rad
and trad as well. I'd be happy to send you patch.
I rather like (and have become accustomed to, and have built scripts around) the .pic extension referring to a raw Radiance-generated image. I dunno how everyone else feels, but with all the available sources for hdr images, some of which we can call "hdr" images, I'd rather keep our good old .pic extension as a Radiance community standard.
I agree. There are too many apps which already use "pic", and it's confusing besides; there's more information in an HDR map than there is in a conventional image file. Perhaps we could also register a MIME type for hdr files? Or has that already been done? I'm willing to undertake the work on that, if people want and if it hasn't been done yet.
Randolph
···
On Oct 25, 2008, at 10:10 AM, Greg Ward wrote:
All suffixes in Radiance are just a convention, but since both Windows and Mac OS X look at the suffix as a first indication of file type, it's not a bad idea to standardize them. The "hdr" suffix has definitely been picked up by the mainstream as a Radiance image file, while the "pic" suffix gets confused for other types on the different systems. In this respect, I agree with Axel that it would be beneficial to change this convention, if people are OK with that.
Although I can see Rob's point that it's nice to have a suffix that uniquely identifies a Radiance-generated image from other possible sources, the de facto use of extensions does not support this these days. An extension indicates the file type, not its creator.
If anyone else has a good reason why we should not switch to using ".hdr" in place of ".pic" in rad/trad/etc. in the next release, now is the time to speak up.
-Greg
From: Rob Guglielmetti <[email protected]>
Date: October 25, 2008 7:43:24 AM PDT
On Oct 25, 2008, at 8:20 AM, Axel Jacobs wrote:
trad still puts the old .pic extension on image files. The general
consensus nowadays seems to be to use .hdr. Since it's a quick
find-and-replace jobbie, may I propose to use this convention for rad
and trad as well. I'd be happy to send you patch.
I rather like (and have become accustomed to, and have built scripts around) the .pic extension referring to a raw Radiance-generated image. I dunno how everyone else feels, but with all the available sources for hdr images, some of which we can call "hdr" images, I'd rather keep our good old .pic extension as a Radiance community standard.
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
I agree. There are too many apps which already use "pic", and it's
confusing besides; there's more information in an HDR map than there
is in a conventional image file. Perhaps we could also register a MIME
type for hdr files? Or has that already been done? I'm willing to
undertake the work on that, if people want and if it hasn't been done
yet.
Brilliant!
I've looked into this, but are are not sufficiently confident with HDR
file format.
Let's move this thread over to dev and continue there.
Axel