On Tue, 28 May 2002 23:49:37 +0200, Fabien wrote:
> I have posted the latest release of Pyvon at p.b.utilities
> Beware it's now 127 Kb large.
> 
> Any comments welcomed.
> 

I like the improvements, but get the following command line error:

Exception in Tkinter callback
Traceback (most recent call last):
  File "/usr/local/lib/python2.2/lib-tk/Tkinter.py", line 1292, in __call__
    return apply(self.func, args)
  File "./pyvon.py", line 1289, in Backspace
    self.fontify()
  File "./pyvon.py", line 774, in fontify
    pos_actu=str(string.join((Ligne, column),'.')) # 1.7
NameError: global name 'Ligne' is not defined

This error only happened on the first run. 

There are problems with the barcket/block highlighting, the braces stay 
highlighted even when I move the cursor to a different block and start 
working there, I don't like having to turn this highlighting off manually.  

Other things I'd want, a block cursor (which they still don't have in the 
Windows version of POV for some reason), I'd also like it to remember 
the scene I was last working on and open it automatically, or at least
remember which directory it was in and open the file selector in that 
directory as default.  

PC editing and selction keys don't seem to work properly, Ctrl-Ins seems 
to mark the way I'd expect, then I move down and do a Shift-Ins and nothing
happens?

The key combinations that you have chosen for editing will be confusing 
for windows users, they're confusing enough to me. 

When text has been marked it changes colour and for some reason remains 
that new (random) colour. 

And why won't the window maximise to the full size of the screen?

I like the insert menu. 

Whatever the problem was with the command dialog box and status line 
seems to have gone away with this release. 

If you get stuck for a web page I could put it on one of my pages, it's 
only a small binary at the moment, it'd fit quite nicely next to PovMenu,
you could have a screen shot too. 

Hope some of this helps. 

-- 
#local i=.1;#local I=(i/i)/i;#local l=(i+i)/i;#local ll=(I/i)/l;box{<-ll,
-((I/I)+l),-ll><ll,-l,ll>pigment{checker scale l}finish{ambient((I/l)/I)+
(l/I)}}sphere{<i-i,l-l,(I/l)>l/l pigment{rgb((I/l)/I)}finish{reflection((
I/l)/I)-(l/I)specular(I/l)/I}}light_source{<I-l,I+I,(I-l)/l>l/l} // Steve

Post a reply to this message

Fabien wrote:
> I have posted the latest release of Pyvon at p.b.utilities
> Beware it's now 127 Kb large.
> 
> Any comments welcomed.
> 
It would be good, if programming is made in _lingua franca_ of internet, 
i.e. in English. By this I mean, that comments, variables, method names 
etc. are in English. Now it is your private project and this might not 
seem important, but I think that this Pyvon has good potential and it 
could become common tool for non-windows (and why not for windows!) 
platform, as it is done in high-level language and quite 
platform-independently. So perhaps in future it will be project, 
inovolving many people? In such case having consistent naming and style 
ensures better readability of code (which is important thing for 
maintenance and further development).
I have also thought about need for such cross-platform interface in some 
high-level scripting language (tcl/tk or Python), but haven't had time 
to do it. Why in scripting language? Because it is easy to port, it 
allows iterative development and easier maintenance. And in case of user 
interface speed of compiled code is not so important (although memory 
consumption could become issue). Anyway, it's good to see, that someone 
has same thoughts and got something working already, this inspired me so 
much, that I took Python book from my work and intend at least get more 
familiar with Python (I can't promise, that I will read this book from 
cover to cover, as it is >800 pages and quite possibly somewhat 
outdated, as it is from year 1996).
Anyway, keep up good work! So far I've used under Linux midnight 
commander for POV-Ray development (can't stand Emacs!), but seems, that 
these days will be gone soon :-)
BTW, if you intend to post your further versions to p.b.u., then perhaps 
it would be better to cancel older versions (to avoid unnecessary server 
space consuming and possible use of older versions by someone?)

Post a reply to this message

> So perhaps in future it will be project, 
> inovolving many people? In such case having consistent naming and style 
> ensures better readability of code (which is important thing for 
> maintenance and further development).
You mean that the code is not clean and messy ?
You are quite right. There is a thing that I definitely have to do, but 
in the end only, is to clean everything up and split the main file into 
several 'include' files.
For the time being, I spend a lot of time adding and debugging new 
features. And it takes a loooong time as I knew nothing of Python in 
November last year. That's why I still do newbie mistakes.



> Anyway, keep up good work! So far I've used under Linux midnight 
> commander for POV-Ray development (can't stand Emacs!), but seems, that 
> these days will be gone soon :-)
It's good to know that I have converted someone and that Emacs does not 
suit everybody's needs.



> BTW, if you intend to post your further versions to p.b.u., then perhaps 
> it would be better to cancel older versions (to avoid unnecessary server 
> space consuming and possible use of older versions by someone?)
The best is a web page from which to download. I've already got a few 
proposals

Post a reply to this message

> 
> I like the improvements, but get the following command line error:
> 
> Exception in Tkinter callback
> Traceback (most recent call last):
>   File "/usr/local/lib/python2.2/lib-tk/Tkinter.py", line 1292, in __call__
>     return apply(self.func, args)
>   File "./pyvon.py", line 1289, in Backspace
>     self.fontify()
>   File "./pyvon.py", line 774, in fontify
>     pos_actu=str(string.join((Ligne, column),'.')) # 1.7
> NameError: global name 'Ligne' is not defined
> 
> This error only happened on the first run. 
> 
> There are problems with the barcket/block highlighting, the braces stay 
> highlighted even when I move the cursor to a different block and start 
> working there, I don't like having to turn this highlighting off manually.  
It's a bug I have with Linux (and not windows). I just wanted to 
highlight the brace for half a second or so, and then go back to its 
original state. As Linux is my main priority, I'll leave as it is for 
the time being.



> I'd also like it to remember 
> the scene I was last working on and open it automatically, or at least
> remember which directory it was in and open the file selector in that 
> directory as default.  
> 
I have fixed that today. It now remembers which directory was open the 
last time.



> The key combinations that you have chosen for editing will be confusing 
> for windows users, they're confusing enough to me. 
Which one do you find confusing?
I tried to create the same key combinations as in Windows.


> When text has been marked it changes colour and for some reason remains 
> that new (random) colour. 
That's why I've added the force syntax coloring option (until the 
highlighting works fine).

> 
> And why won't the window maximise to the full size of the screen?
I don't know the Tkinter command for that (yet).


> If you get stuck for a web page I could put it on one of my pages, it's 
> only a small binary at the moment, it'd fit quite nicely next to PovMenu,
> you could have a screen shot too. 
Thanks for the offer. How often are you ready to update your web page ?



> Hope some of this helps. 
Yes it does. Thanks for your comments.


Fabien

Post a reply to this message

On Wed, 29 May 2002 22:44:03 +0200, Fabien HENON wrote:
 
> 
>> I'd also like it to remember 
>> the scene I was last working on and open it automatically, or at least
>> remember which directory it was in and open the file selector in that 
>> directory as default.  
>> 
> I have fixed that today. It now remembers which directory was open the 
> last time.

That's good. 

  
>> The key combinations that you have chosen for editing will be confusing 
>> for windows users, they're confusing enough to me. 
> Which one do you find confusing?
> I tried to create the same key combinations as in Windows.
> 

I mean Shift-Arrow marks text, Ctrl-Ins remembers selection, Shift-Ins 
paste remembered selection, Shift-Del delete and remember selection, 
Shift-End mark to end of line, Shift-Home mark to beginning of line etc,
just the way you'd do it in Notepad, Word, Edit.ext and so on. 
 
 
>> If you get stuck for a web page I could put it on one of my pages, it's 
>> only a small binary at the moment, it'd fit quite nicely next to PovMenu,
>> you could have a screen shot too. 
> Thanks for the offer. How often are you ready to update your web page ? 

I'd just add a paragraph to http://www.zeropps.uklinux.net/linstuff.html, 
and add a link to that section at the top of that page.  It is something
that doesn't take long to do.  I'd put it either above or below PovMenu.

-- 
#local i=.1;#local I=(i/i)/i;#local l=(i+i)/i;#local ll=(I/i)/l;box{<-ll,
-((I/I)+l),-ll><ll,-l,ll>pigment{checker scale l}finish{ambient((I/l)/I)+
(l/I)}}sphere{<i-i,l-l,(I/l)>l/l pigment{rgb((I/l)/I)}finish{reflection((
I/l)/I)-(l/I)specular(I/l)/I}}light_source{<I-l,I+I,(I-l)/l>l/l} // Steve

Post a reply to this message

I would like a fixed width font in the status box...

Post a reply to this message

Artis wrote:
> I would like a fixed width font in the status box...
> 

Good idea. I'll fix that right away.

Fabien

Post a reply to this message

> You are quite right. There is a thing that I definitely have to do, but
> in the end only, is to clean everything up and split the main file into
> several 'include' files.

I should start learning python...

> It's good to know that I have converted someone and that Emacs does not
> suit everybody's needs.

The pov-mode of Emacs is very buggy, for me anyways. I got it to run at 
all, but rendering didn't seem to work. Now I can edit AND render in one, 
and I like that (-;

Post a reply to this message