While this is true, I point out that SOMEBODY will have to add the keywords to the
dictionary. In my case it's me. In an ideal world it would be the programmer that does
the adding. For now, we cannot auto-check keywords that do not exist in the
dictionary.

It seems like a possibility to write a utility that would automatically add keywords
from an include file to a color coded syntax dictionary. Then, when you type the
keywords, the color will tell you if they are spelled correctly.

In fact, this is standard procedure in Mac applications. The scripting keywords are
listed in the aete resource ( along with the required syntax). The scripting
application
looks up the aete resource and lists all the scripting keywords available to it. At
least 1 group of POV developers is working on adding the aete resource to POV-Ray for
Mac. Some similar type of resource could also be added to generic include files if POV
supported such a thing. If the resource is written in C++, which POV 3.5 for Mac will
be, one can simply look up the function prototypes without need for a special
resource.

Once POV is rewritten in C++, adding a dynamic dictionary will be fairly
straightforward. It's already been done in many other Mac applications. In this
manner,
the keyword dictionary would change each time the include files were changed.

Until then, we're stuck with adding our keywords ourselves.

Ken, it addresses the typo problem in exactly the same way the POV editor does - if
you
spell it wrong it shows up the wrong color!

Steve Strickland

Ken wrote:

> Steve wrote:
> >
> > The second part of my message explains the workaround to this specific problem -
> > custom dictionaries and color coded keywords in an external text editor plus
adding
> > the keyword from a custom menu.
>
>   Fortunatly for the windows users of the program the new CodeMax editor
> has program language specific color syntax highlighting included with
> it's available options. When you type a keyword that is on the list it
> is automaticly highlighted in your color of choice. What I don't think
> you can do on the other hand is specify new key words for the highlighting
> function. That is probably addressed in the Pov specific editor .dll
> file.
>    Either way this still does not address the issue of human typo's when
> declaring unspecified words in your current work session.
>
>  Suggestion for Mr. Warp: Take a typing class.
>
> --
> Ken Tyler
>
> mailto://tylereng@pacbell.net

Post a reply to this message