 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi,
the current editor for the Windows version of POV-Ray is quite good, but
the only major lack it has is, that it comes only with 16 predefined
colors for usage within the editor. And most of these colors I don't
like, as they simply don't work well with the color scheme my Windows 7
is using.
Can't the developers add support for True Color to the editor? That
would be nice.
Or are there any other scene editors that can be integrated into the
Windows version of POV-Ray and allow a syntax with True Colors?
Thank you.
---
Diese E-Mail wurde von AVG auf Viren geprüft.
http://www.avg.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 14.07.2017 um 09:53 schrieb Sven Littkowski:
> the current editor for the Windows version of POV-Ray is quite good, but
> the only major lack it has is, that it comes only with 16 predefined
> colors for usage within the editor. And most of these colors I don't
> like, as they simply don't work well with the color scheme my Windows 7
> is using.
POV-Ray for Windows has multiple major lacks, but I wouldn't consider
this one of them. There are more serious problems.
> Can't the developers add support for True Color to the editor? That
> would be nice.
>
> Or are there any other scene editors that can be integrated into the
> Windows version of POV-Ray and allow a syntax with True Colors?
To the best of my knowledge, the editor colour picker is an integral
part of CodeMax, which is a poor fit for the POV-Ray project, if only
due to the licensing issues, so presumably we won't invest any
noteworthy amount of work into it.
CodeMax is the only editor component the Windows GUI is designed to work
with, and the Windows GUI itself is horribly outdated in itself, so
presumably we won't invest a lot of work into that one either.
If we find the time to do any serious GUI development work, the plan is
to build a new one from scratch, using a portable GUI framework as the
basis (Qt comes to mind).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Is there any chance that something like an in-browser text editor could be used?
There seem to be quite a few of them.
Not sure how that would all work out with backwards-compatibility and whatnot.
https://www.google.com/search?q=browser+text+editor
I've always desired something like RTF, but I know how desirable it is to have a
simple text-only input for creating a render...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 14.07.2017 um 20:06 schrieb Bald Eagle:
> Is there any chance that something like an in-browser text editor could be used?
> There seem to be quite a few of them.
> Not sure how that would all work out with backwards-compatibility and whatnot.
>
> https://www.google.com/search?q=browser+text+editor
>
> I've always desired something like RTF, but I know how desirable it is to have a
> simple text-only input for creating a render...
You can use /any/ text editor capable of saving plain vanilla ASCII
text. You could even use MS Word for that purpose.
A text editor capable of syntax highlighting would be of advantage of
course. But you may need to roll your own highlighting rules.
The difference of course is that it won't be an inbuilt editor, so
starting a render will be a bit more complex than just a button press.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 14.07.2017 11:25, clipka wrote:
> Am 14.07.2017 um 09:53 schrieb Sven Littkowski:
>
>> the current editor for the Windows version of POV-Ray is quite good, but
>> the only major lack it has is, that it comes only with 16 predefined
>> colors for usage within the editor. And most of these colors I don't
>> like, as they simply don't work well with the color scheme my Windows 7
>> is using.
>
> POV-Ray for Windows has multiple major lacks, but I wouldn't consider
> this one of them. There are more serious problems.
>
>> Can't the developers add support for True Color to the editor? That
>> would be nice.
>>
>> Or are there any other scene editors that can be integrated into the
>> Windows version of POV-Ray and allow a syntax with True Colors?
>
> To the best of my knowledge, the editor colour picker is an integral
> part of CodeMax, which is a poor fit for the POV-Ray project, if only
> due to the licensing issues, so presumably we won't invest any
> noteworthy amount of work into it.
>
> CodeMax is the only editor component the Windows GUI is designed to work
> with, and the Windows GUI itself is horribly outdated in itself, so
> presumably we won't invest a lot of work into that one either.
>
> If we find the time to do any serious GUI development work, the plan is
> to build a new one from scratch, using a portable GUI framework as the
> basis (Qt comes to mind).
>
I don't complain about any other faults of the editor, I rather like it.
A few ideas, however, i have suggested many months or over a year ago.
But the improvement about customization (colors), I would really be
happy to see that. As i said before: based on my Windows 7 color scheme,
those few colors of the editor just don't look good or have too low
contrast towards the Windows environment. I really beg for a color picker.
---
Diese E-Mail wurde von AVG auf Viren geprüft.
http://www.avg.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 7/25/2017 9:39 AM, Sven Littkowski wrote:
> I don't complain about any other faults of the editor, I rather like it.
> A few ideas, however, i have suggested many months or over a year ago.
>
It surprised me yesterday. It did a "Find & Replace" on an almost 800
Meg text file.
None of my other text editors could handle the file.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 25-7-2017 10:39, Sven Littkowski wrote:
> I don't complain about any other faults of the editor, I rather like it.
> A few ideas, however, i have suggested many months or over a year ago.
>
> But the improvement about customization (colors), I would really be
> happy to see that. As i said before: based on my Windows 7 color scheme,
> those few colors of the editor just don't look good or have too low
> contrast towards the Windows environment. I really beg for a color picker.
>
> ---
> Diese E-Mail wurde von AVG auf Viren geprüft.
> http://www.avg.com
>
I don't know. Using a Win7 environment myself, I am quite happy with the
(standard) colour scheme proposed. What is the problem?
--
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 7/25/2017 12:16 PM, Thomas de Groot wrote:
> On 25-7-2017 10:39, Sven Littkowski wrote:
>> I don't complain about any other faults of the editor, I rather like it.
>> A few ideas, however, i have suggested many months or over a year ago.
>>
>> But the improvement about customization (colors), I would really be
>> happy to see that. As i said before: based on my Windows 7 color scheme,
>> those few colors of the editor just don't look good or have too low
>> contrast towards the Windows environment. I really beg for a color
>> picker.
>>
>> ---
>> Diese E-Mail wurde von AVG auf Viren geprüft.
>> http://www.avg.com
>>
>
> I don't know. Using a Win7 environment myself, I am quite happy with the
> (standard) colour scheme proposed. What is the problem?
>
Win7 here too. I always use a plain interface, myself. But I can see the
requirement to have a fancy border. If that's what Sven means?
I am guess he is aware of how to customise the font, colour, shortcuts
etc. There was some discussion about being able to use Truetype or
Cleartype fonts a while back but we got a definitive answer with
reasons. So it can't be that.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 7/25/2017 1:54 PM, Stephen wrote:
> I am guess he is aware of how to
Should read I guess he is...
It's not just my fingers playing up today. I'm beginning to hate
Thunderbird with its fancy skins.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 25.07.2017 09:02, Stephen wrote:
> On 7/25/2017 1:54 PM, Stephen wrote:
>> I am guess he is aware of how to
>
> Should read I guess he is...
>
>
> It's not just my fingers playing up today. I'm beginning to hate
> Thunderbird with its fancy skins.
>
At the moment, I work with gray background, but this one and any other
background just looks not right. Since I do software programming, I work
since over 20 years with my own standard colors for the one or other
thing inside a syntax. But I cannot use "my" custom colors with the
editor at the moment. Thus I am not able to recognize things inside a
POV-Ray syntax based on the color code. Why such a big discussion about
such a small additional feature? It is not really difficult to add that
feature.
---
Diese E-Mail wurde von AVG auf Viren geprüft.
http://www.avg.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 7/27/2017 4:19 AM, Sven Littkowski wrote:
> On 25.07.2017 09:02, Stephen wrote:
>> On 7/25/2017 1:54 PM, Stephen wrote:
>>> I am guess he is aware of how to
>>
>> Should read I guess he is...
>>
>>
>> It's not just my fingers playing up today. I'm beginning to hate
>> Thunderbird with its fancy skins.
>>
>
> At the moment, I work with gray background, but this one and any other
> background just looks not right. Since I do software programming, I work
> since over 20 years with my own standard colors for the one or other
> thing inside a syntax. But I cannot use "my" custom colors with the
> editor at the moment. Thus I am not able to recognize things inside a
> POV-Ray syntax based on the color code. Why such a big discussion about
> such a small additional feature? It is not really difficult to add that
> feature.
>
I must admit I was wrong. I thought the editor was configurable. I
suppose it is, in a way. But reminiscent of the way DOS programs looked.
It is so long since I looked at the settings I was remembering how I
felt about them, then.
So I support your feature request.
But, if memory serves me well. There is no one to do it. The Pov team
are all working on other things and your request is cosmetic.
So unless you can hack the editor code. The only other thing to do is
keep nagging until one of them gets sick enough of it to add a custom
colour into the list. That's how it was done in days of yore. ;)
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 27.07.2017 um 05:19 schrieb Sven Littkowski:
> At the moment, I work with gray background, but this one and any other
> background just looks not right. Since I do software programming, I work
> since over 20 years with my own standard colors for the one or other
> thing inside a syntax. But I cannot use "my" custom colors with the
> editor at the moment. Thus I am not able to recognize things inside a
> POV-Ray syntax based on the color code. Why such a big discussion about
> such a small additional feature? It is not really difficult to add that
> feature.
Well then... if you find the feature not really difficult to add, I
recommend you implement those changes yourself, and license them to us
under the old POV-Ray v3.6 license.
Our version of the proprietary 3rd party CodeMax library has remained
virtually unchanged from POV-Ray v3.6 (except for bug fixes), so you can
use the CodeMax source code from the POV-Ray v3.6 package as a starting
point for your development.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 27.07.2017 06:56, clipka wrote:
> Am 27.07.2017 um 05:19 schrieb Sven Littkowski:
>
>> At the moment, I work with gray background, but this one and any other
>> background just looks not right. Since I do software programming, I work
>> since over 20 years with my own standard colors for the one or other
>> thing inside a syntax. But I cannot use "my" custom colors with the
>> editor at the moment. Thus I am not able to recognize things inside a
>> POV-Ray syntax based on the color code. Why such a big discussion about
>> such a small additional feature? It is not really difficult to add that
>> feature.
>
> Well then... if you find the feature not really difficult to add, I
> recommend you implement those changes yourself, and license them to us
> under the old POV-Ray v3.6 license.
>
> Our version of the proprietary 3rd party CodeMax library has remained
> virtually unchanged from POV-Ray v3.6 (except for bug fixes), so you can
> use the CodeMax source code from the POV-Ray v3.6 package as a starting
> point for your development.
>
Just make it Delphi source code, and I will do this. It would be my
pleasure. And I have no problem to license it to the great POV-Ray team.
But I cannot program in other languages than Delphi (Pascal).
---
Diese E-Mail wurde von AVG auf Viren geprüft.
http://www.avg.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymous org> wrote:
> You can use /any/ text editor capable of saving plain vanilla ASCII
> text. You could even use MS Word for that purpose.
>
> A text editor capable of syntax highlighting would be of advantage of
> course. But you may need to roll your own highlighting rules.
Yes, indeed.
Te one thing I would find VERY useful is some sort of editor that has
differential coloring of nested parentheses for mathematical formulae.
Debugging those can drive me a little nuts sometimes.
Does anyone have a [preferably small, lightweight, free] 3rd party editor that
would work well for this?
I suppose if I need to, I could use Excel...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 04.08.2017 14:10, Bald Eagle wrote:
> clipka <ano### [at] anonymousorg> wrote:
>
>> You can use /any/ text editor capable of saving plain vanilla ASCII
>> text. You could even use MS Word for that purpose.
>>
>> A text editor capable of syntax highlighting would be of advantage of
>> course. But you may need to roll your own highlighting rules.
>
>
> Yes, indeed.
> Te one thing I would find VERY useful is some sort of editor that has
> differential coloring of nested parentheses for mathematical formulae.
>
> Debugging those can drive me a little nuts sometimes.
>
> Does anyone have a [preferably small, lightweight, free] 3rd party editor
that
> would work well for this?
> I suppose if I need to, I could use Excel...
>
>
Weaverslave?
---
Diese E-Mail wurde von AVG auf Viren geprüft.
http://www.avg.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bald Eagle" <cre### [at] netscapenet> wrote:
> clipka <ano### [at] anonymousorg> wrote:
>
> > You can use /any/ text editor capable of saving plain vanilla ASCII
> > text. You could even use MS Word for that purpose.
> >
> > A text editor capable of syntax highlighting would be of advantage of
> > course. But you may need to roll your own highlighting rules.
>
>
> Yes, indeed.
> Te one thing I would find VERY useful is some sort of editor that has
> differential coloring of nested parentheses for mathematical formulae.
>
> Debugging those can drive me a little nuts sometimes.
>
> Does anyone have a [preferably small, lightweight, free] 3rd party editor that
> would work well for this?
> I suppose if I need to, I could use Excel...
The release candidate 2 of Blender 2.79 has our latest patch for POV syntax
highlighting in:
https://download.blender.org/release/Blender2.79/
When you put your cursor next to a {} brace sign, it highlights in red the
corresponding pair of braces. Lanuhum and I added one more color than POVwin, so
"transforming" keywords are distinguished from objects, and in the same color
group as mathematical functions.
All this looks perfect for your need. And possibly of some others users.
I added a "run" operator to render a preview of edited text only regardless of
Blender 3D scene. Also note that another add-on exists that can enable
auto-completion and I successfully tried it with POV files.
See the wiki for screen captures cluing how to use pov colored syntax in blender
(file suffixes are recognized automatically):
https://wiki.blender.org/index.php/Extensions:2.6/Py/Scripts/Render/POV-Ray#Adding_POV_code_directly
Please note that, as of today, Lanuhum and I are Python scripters (and I a lame
one!)yet we tried to mimic existing C code and successfully dared to submit this
C patch which is not our language, but was still accepted by the main Blender
developers, I mean to say that if you really preferred such changes to happen in
Povwin and the likes, don't be scared to try !
Otherwise of course, just tell us what's wrong with it in our Blender's
implementation, and we'll try to improve it based on your feedback. Thanks!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Mr" <nomail@nomail> wrote:
> The release candidate 2 of Blender 2.79 has our latest patch for POV syntax
> highlighting in:
>
> https://download.blender.org/release/Blender2.79/
>
> When you put your cursor next to a {} brace sign, it highlights in red the
> corresponding pair of braces. Lanuhum and I added one more color than POVwin, so
> "transforming" keywords are distinguished from objects, and in the same color
> group as mathematical functions.
> All this looks perfect for your need. And possibly of some others users.
> I added a "run" operator to render a preview of edited text only regardless of
> Blender 3D scene. Also note that another add-on exists that can enable
> auto-completion and I successfully tried it with POV files.
Thanks!
This looks like something which is useful, and I'll have to see about installing
it and trying it out.
By the way:
"Pov items can be anything but for now only the equivalent of Blender materials
can be replaced with this method. In Povray, it is called texture {} don't get
confused, it really includes all the material properties."
Don't forget that POV-Ray also has an actual material{} directive...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bald Eagle" <cre### [at] netscapenet> wrote:
> "Mr" <nomail@nomail> wrote:
>
> > The release candidate 2 of Blender 2.79 has our latest patch for POV syntax
> > highlighting in:
> >
> > https://download.blender.org/release/Blender2.79/
> >
> > When you put your cursor next to a {} brace sign, it highlights in red the
> > corresponding pair of braces. Lanuhum and I added one more color than POVwin, so
> > "transforming" keywords are distinguished from objects, and in the same color
> > group as mathematical functions.
> > All this looks perfect for your need. And possibly of some others users.
> > I added a "run" operator to render a preview of edited text only regardless of
> > Blender 3D scene. Also note that another add-on exists that can enable
> > auto-completion and I successfully tried it with POV files.
>
>
> Thanks!
> This looks like something which is useful, and I'll have to see about installing
> it and trying it out.
>
> By the way:
> "Pov items can be anything but for now only the equivalent of Blender materials
> can be replaced with this method. In Povray, it is called texture {} don't get
> confused, it really includes all the material properties."
>
> Don't forget that POV-Ray also has an actual material{} directive...
I did not forget, but since the exporter doesn't make use of it, I decided to
keep things more simple in this explanation so as to not confuse Blender users
further (the developer page linked at the top of the wiki mentions it however)
The problem goes much deeper than just differing terminologies.
In pov, the texture syntax is non standard as Blender's user interface used to
be before the rewrite ;-)
mostly, texture influences are not channelled in parallel user workflows
except for normal_map and image_map, ior are object related while they can be
texture related in Blender. etc.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
If I get a chance to do so, I might try to install this at home tonight and see
how it goes:
https://atom.io/
"Atom is a text editor that's modern, approachable, yet hackable to the core—a
tool you can customize to do anything but also use productively without ever
touching a config file."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
More info:
https://github.com/h-a-n-n-e-s/atom-language-povray/issues/1
https://atom.io/packages/tools-povray
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 05.09.2017 11:01, Bald Eagle wrote:
> More info:
> https://github.com/h-a-n-n-e-s/atom-language-povray/issues/1
>
> https://atom.io/packages/tools-povray
>
>
>
Thanks!
---
Diese E-Mail wurde von AVG auf Viren geprüft.
http://www.avg.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
