This isn't really crucial to the operation of the POV-Editor, but I
noticed that when using the "File Open" dialog, there was no provision
to display file types other than typical POV-Ray file types. For
example, the editor supports the editing of Basic, C/C++, HTML,
Pascal, XML, and other languages. However, none of the associated file
types for these languages are listed in the "Files of type:" drop-down
menu. 

Of course, it is always possible to choose "All Files", but it would
be much nicer to have specific options for the other languages that
the editor is capable of working with.

Was this just a minor oversight, and if so, is it easy to fix?

(I *do* plan to use the POV editor for more than just POV files.)


Thanks for reading,
Glen

Post a reply to this message

"Glen Berry" <7no### [at] ezwvcom> wrote:

> This isn't really crucial to the operation of the POV-Editor, but I
> noticed that when using the "File Open" dialog, there was no provision
> to display file types other than typical POV-Ray file types. For
> example, the editor supports the editing of Basic, C/C++, HTML,
> Pascal, XML, and other languages. However, none of the associated file

Furthermore, since many people seem to be using .mcr for files that contain
just a macro or two, maybe that should be added to both file-types
associated with povray in W$ndows and to the dialog?

If not, than maybe the team could make an official statement to rebuke
those
non-standard vandals who persist in such evil file-naming practices...? ;P

 - Nikodemus

Post a reply to this message

"Nikodemus Siivola" <tsi### [at] cchutfi> wrote in message
news:3ba3c030@news.povray.org...
>
> "Glen Berry" <7no### [at] ezwvcom> wrote:
>
> > This isn't really crucial to the operation of the POV-Editor, but I
> > noticed that when using the "File Open" dialog, there was no provision
> > to display file types other than typical POV-Ray file types. For
> > example, the editor supports the editing of Basic, C/C++, HTML,
> > Pascal, XML, and other languages. However, none of the associated file

Well, you know, it is the POV-Ray Editor in this case  :-)  not a web page
publisher or program compiler.

> Furthermore, since many people seem to be using .mcr for files that
contain
> just a macro or two, maybe that should be added to both file-types
> associated with povray in W$ndows and to the dialog?
>
> If not, than maybe the team could make an official statement to rebuke
> those
> non-standard vandals who persist in such evil file-naming practices...? ;P
>
>  - Nikodemus


Guess it was never decided what if any new extensions might be used.
There's always the wild card *.* for choosing any others.  Not convenient, I
know.

Bob H.

Post a reply to this message

You don't need an extension listed in the extensions list to be able
to view only those files. Just type in '*.xml' (for example) as a
filename and it will list XML files. This is standard Windows beh-
aviour.

-- Chris

Post a reply to this message

"Chris Cason" wrote:
> You don't need an extension listed in the extensions list
> to be able to view only those files. Just type in '*.xml'

IIRC before there was a single option to show all .pov, .inc and .ini files.
Now I can only show one at a time. Of course I can do it manually as you
suggests, but it's rather annoying to write *.pov;*.inc;*.ini compared to
how easy it was before.

Rune
--
3D images and anims, include files, tutorials and more:
Rune's World:    http://rsj.mobilixnet.dk (updated June 26)
POV-Ray Users:   http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk

Post a reply to this message

> IIRC before there was a single option to show all .pov, .inc and .ini files.
> Now I can only show one at a time. Of course I can do it manually as you
> suggests, but it's rather annoying to write *.pov;*.inc;*.ini compared to
> how easy it was before.

I did not suggest you do this manually, I was suggesting to the person who wanted
to load XML files that typing it was more appropriate than us adding it as a type.

In your case the problem is unintentional, and will be fixed.

-- CHris

Post a reply to this message

On Mon, 17 Sep 2001 02:29:25 +1000, "Chris Cason"
<newsadmin@-despam-povray.org> wrote:

>> IIRC before there was a single option to show all .pov, .inc and .ini files.
>> Now I can only show one at a time. Of course I can do it manually as you
>> suggests, but it's rather annoying to write *.pov;*.inc;*.ini compared to
>> how easy it was before.
>
>I did not suggest you do this manually, I was suggesting to the person who wanted
>to load XML files that typing it was more appropriate than us adding it as a type.

Well, it's certainly not more "appropriate" from a users viewpoint,
but from the viewpoint of a developer, there could certainly be good
reasons why one might not want to invest the time needed to add this
feature. I can live with that.

>In your case the problem is unintentional, and will be fixed.
>
>-- CHris

If you do this, will you also add support for some of the other
POV-related file extensions that were left out originally? For
example, I'm thinking of things like *.cat, *.mcr, *.sph, *.tri


Later,
Glen

Post a reply to this message

In article <xOGkO6cycku13Et0ri0kghPLk0kD@4ax.com> , Glen Berry 
<7no### [at] ezwvcom>  wrote:

> If you do this, will you also add support for some of the other
> POV-related file extensions that were left out originally? For
> example, I'm thinking of things like *.cat, *.mcr, *.sph, *.tri

None of these are in any way supported by POV-Ray (it just reads text files
with whatever extension if you tell it to).  If a user decides to use
different extensions it is simply a problem because some of these are used
by other programs and POV-Ray cannot detect if they are for POV-Ray or not!
In general it is a bad idea to create "your own" file extensions because it
creates all kinds of these problems.

    Thorsten

Post a reply to this message

On Sun, 16 Sep 2001 14:08:01 -0400, "Thorsten Froehlich"
<tho### [at] trfde> wrote:

>In article <xOGkO6cycku13Et0ri0kghPLk0kD@4ax.com> , Glen Berry 
><7no### [at] ezwvcom>  wrote:
>
>> If you do this, will you also add support for some of the other
>> POV-related file extensions that were left out originally? For
>> example, I'm thinking of things like *.cat, *.mcr, *.sph, *.tri
>
>None of these are in any way supported by POV-Ray (it just reads text files
>with whatever extension if you tell it to).  If a user decides to use
>different extensions it is simply a problem because some of these are used
>by other programs and POV-Ray cannot detect if they are for POV-Ray or not!
>In general it is a bad idea to create "your own" file extensions because it
>creates all kinds of these problems.
>
>    Thorsten

That sounds fair enough. 

However, I want to point out that 3 of the 4 extensions I gave above
come from the official 3.5 distribution of POV-Ray. Here are the names
of the files:

quartic.cat
teapot.cat
teapot.sph
teapot.tri

I could have also included the following files and their extensions:

teapot.c1
teapot.c2
teapot.c3

All these files are written in plain text, and are meant to be used
with POV-Ray. According to your own philosophy on this subject, should
these files be converted to the ".inc" extension, to set a good
example for the rest of us? Of course, the files themselves might need
a bit of re-formatting. The ".cat" files for example, would probably
need to be converted to commented text, if placed in an "include" or
"POV" file.

Just curious,
Glen

Post a reply to this message

> Well, it's certainly not more "appropriate" from a users viewpoint,

I disagree. The more file types I add to the drop-down box, the longer
it takes the 99% of users who do not use these additional extensions
(*.xml, *.html, *.java, and all the other types the editor understands)
to scroll through the list of types in the drop-down box to find the one
they want.

From a UI design standpoint, the purpose of this list box is to provide
shortcuts to the most commonly-used extensions; not a complete list of
all possible extensions that the editor may be asked to load.

> If you do this, will you also add support for some of the other
> POV-related file extensions that were left out originally? For
> example, I'm thinking of things like *.cat, *.mcr, *.sph, *.tri

I've already added .mcr since I believe it is becoming fairly common. I
would have te be convinced that a large number of users are editing files
using the other extensions before I added them.

-- Chris

Post a reply to this message