Hi Moritz,
as Chip has pointed out it is not a problem w.r.t. hashbang lines or the
like, but an attempt to get at unique filetypes that one can then use to
associate icons with filetypes.
I would not use file extensions that are longer than 3 characters - it's
just not handy when working
...@wu-wien.ac.at]
Sent: Tuesday, October 13, 2009 3:01 AM
To: Open Object Rexx Developer Mailing List
Subject: Re: [Oorexx-devel] Requesting ideas for filename extension ...
Hi Moritz,
as Chip has pointed out it is not a problem w.r.t. hashbang lines or the
like, but an attempt to get at unique
Mailing List
Subject: Re: [Oorexx-devel] Requesting ideas for filename
extension ...
Hi Moritz,
as Chip has pointed out it is not a problem w.r.t. hashbang lines or
the
like, but an attempt to get at unique filetypes that one can then
use to
associate icons with filetypes.
I would
Rony G. Flatscher wrote:
Hi there,
in preparation of packaging BSF4Rexx 4.0 for the beta-test I would like
to take advantage of those new icons that Gray Wilson has kindly created
for BSF4Rexx and OOo (OpenOffice support via BSF4Rexx). In order to be
able to utilize these icons, there need
Hi Moritz,
Yes, I agree that the concept of encoding file metadata in the filename is an
unreliable anachronism; it goes 'way back to some of the earliest filesystems.
However, that is the mechanism by which Windows associates icons, which is the
problem that Rony is trying to solve in as
I'm with Klass on this one, Rony. And you really should avoid case-sensitivity
as well.
There are only three pieces of information that the extension must convey:
'Rexx', 'BSF4Rexx(Java)', and 'OpenOffice'. It's not necessary to specify that
it is Open Object Rexx, since that's the only Rexx
