 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 10 Sep 2002 08:50:34 +0200, Fabien HENON wrote:
>> I don't want to discourage you from working on this but feel that these
>> basic issues need sorting out. A real configure and install script would
>> be good.
>
>
> An install script just to untar an archive ! I don't see what's the point.
> A script is good when you have to configure, compile and move your
> libraries into the proper directory.
>
Why shoudn't the components of Pyvon go into the proper directories?
Why isn't the executable put into a bin directory that's in the search
path? Why are all the other files in the same directory instead of in
their own lib directory?
>
> In the present case, everything you need is in a single directory. Just
> type the name of the only file that has executable chmod and that's it.
Yes but to use it you have to go to that directory first becasue you don't
install it into anywhere useful, ie there is no install scirpt and no
reasonable install instructions.
The documentation is every bit as important as the software.
>
> When you exit from Pyvon, the software does it all for you ( write your
> parameters and preferences in your home directory).
>
Ok I see the RC file now, but you don't keep to a naming convention,
firstly you call the executable Pyvon and you put it in a directory (that
could be anywhere), called Pyvon but call the rc file .pyvonrc with a
lowercase "P".
--
%HAV-A-NICEDAY email mailto:ste### [at] zeropps uklinuxnet
Steve web http://www.zeropps.uklinux.net/
or http://start.at/zero-pps
9:44am up 74 days, 20:09, 2 users, load average: 1.10, 1.09, 1.02
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Why shoudn't the components of Pyvon go into the proper directories?
> Why isn't the executable put into a bin directory that's in the search
> path? Why are all the other files in the same directory instead of in
> their own lib directory?
> Ok I see the RC file now, but you don't keep to a naming convention,
> firstly you call the executable Pyvon and you put it in a directory (that
> could be anywhere), called Pyvon but call the rc file .pyvonrc with a
> lowercase "P".
While in principle I agree with these two points, I would suggest
that you help Fabien creating this install script for him. Sounds that it
would be more useful than flamming :-)
By the way, any executable should not start with uppercase letter,
which is otherwise very annoying. I would adopt the same rule for the
package name as well.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Steve wrote:
> On Tue, 10 Sep 2002 08:50:34 +0200, Fabien HENON wrote:
>
>
>>>I don't want to discourage you from working on this but feel that these
>>>basic issues need sorting out. A real configure and install script would
>>>be good.
>>
>>
>>An install script just to untar an archive ! I don't see what's the point.
>>A script is good when you have to configure, compile and move your
>>libraries into the proper directory.
>>
>
>
> Why shoudn't the components of Pyvon go into the proper directories?
What do you propose ? /usr/local/bin ?
Besides, users can install Pyvon in the directory they want.
> Why isn't the executable put into a bin directory that's in the search
> path?
I am not a Linux Guru. To know which directories are in the search path,
there is the variable $PATH (or something like that), but afterwards,
how do you deal with.
I much prefer to go for simplicity and play safe : I put all the files
into the same directory.
That may not be neat, but it 100 % safe and it works.
I do not count the times I compiled sources of a software and ended up
with an error because some mysterious library from some unknown package
is missing. I have used Linux for 2 years, and there are still many dark
corners to me.
Why are all the other files in the same directory instead of in
> their own lib directory?
First, there are no lib files, just the equivalent of include files for Pov.
Second, I did try to put the menu_*** files into a sub-directory. But to
no avail. I have to ask a Python newsgroup how to do that.
The other solution is to move those menu_*** into the Python directory.
But I can not be 100 % certain that it is always located in the same
directory on every system. Besides, I don't want to tamper with people's
system by moving files where they are not meant to be.
If an user wants to install a newer version or to get rid of Pyvon, they
just have to delete its directory. There won't be anything left of it.
>
>
>>In the present case, everything you need is in a single directory. Just
>>type the name of the only file that has executable chmod and that's it.
>
>
> Yes but to use it you have to go to that directory first becasue you don't
> install it into anywhere useful,
I'll try to copy the starting script into /usr/bin and make a link to
/usr/local/pyvon, and see how it works
>ie there is no install scirpt and no
> reasonable install instructions.
I have already replied that I forgot to add the 'cd Pyvon' command in
the installation.txt file. I'll try to fix that tonight.
>
> The documentation is every bit as important as the software.
I should have waited a few more days before releasing this version and
spending more time checking the files. I would not have got this kind of
flaming.
I have the impression to work on a on-line help-desk and that you are
calling for a software that you paid for and that is not working.
As far as I know, it is working on your system.
Ok, I have forgotten a few things through an oversight, but I am doing
this on my free time, and it is freeware.
I you want to make an installation script, go ahead, I would be glad to
see one working. I do not know enough shell instructions for that.
>
>
>>When you exit from Pyvon, the software does it all for you ( write your
>>parameters and preferences in your home directory).
>>
>
>
> Ok I see the RC file now, but you don't keep to a naming convention,
> firstly you call the executable Pyvon and you put it in a directory (that
> could be anywhere), called Pyvon but call the rc file .pyvonrc with a
> lowercase "P".
>
Ok, I agree with that. I'll remove the uppercase P of both the directory
and the starting script.
Fabien H
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nicolas Calimet wrote:
>> Why shoudn't the components of Pyvon go into the proper directories?
>> Why isn't the executable put into a bin directory that's in the search
>> path? Why are all the other files in the same directory instead of in
>> their own lib directory?
>
>
>> Ok I see the RC file now, but you don't keep to a naming convention,
>> firstly you call the executable Pyvon and you put it in a directory (that
>> could be anywhere), called Pyvon but call the rc file .pyvonrc with a
>> lowercase "P".
>
>
>
> While in principle I agree with these two points, I would suggest
> that you help Fabien creating this install script for him. Sounds that it
> would be more useful than flamming :-)
I agree, it would be a bit more constructive.
> By the way, any executable should not start with uppercase letter,
> which is otherwise very annoying. I would adopt the same rule for the
> package name as well.
Ok, I'll remove the uppercase letter P in both the starting script and
directory.
Fabien H
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 10 Sep 2002 21:26:10 +0200, Fabien HENON wrote:
> I should have waited a few more days before releasing this version and
> spending more time checking the files. I would not have got this kind of
> flaming.
>
> I have the impression to work on a on-line help-desk and that you are
> calling for a software that you paid for and that is not working.
> As far as I know, it is working on your system.
> Ok, I have forgotten a few things through an oversight, but I am doing
> this on my free time, and it is freeware.
>
I had no intention of flaming anyone. I just won't comment on it any
more.
--
sphere{z*5,1pigment{rgb.5}finish{reflection.3specular.5}}box{<-50,-3,-50>
<50,-2,50>pigment{checker/*\__\\__/ * \_\\__*/scale 2}finish{ambient.7}}
light_source/*__\\__\\__\\__\\__\( ~ )\__\\__\\__\\__\\*/{<2,5,1>*4,1}
/*\\__\\__\\__\\__\\__\\__\\__\\__\~ -/__\\__\\__\\__\\__\\*//* Steve */
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Fabien HENON wrote:
> at :
>
> http://pyvon.sourceforge.net
>
Wow, you've put a lot of work into this Fabien. I had no problems
downloading it and installing it following the directions on the
installation page on your web site. I noticed you already changed
the filenames to be all lowercase. I think that's easier for
people to deal with. You'll probably want to update the installation
page with all lowercase command examples too if you haven't already.
The screen split nicely between the editing window and the streams
window. I opened a filename with a space in it and it rendered
fine. I tested some of the stuff from the insert menu and that all
worked wonderfully as well :)
The only problem I had isn't a big thing, just a little odd. If I
ctrl-c a line of text near the top of a file, then ctrl-v a line
or several lines below, the whole file in the editor window scrolls
down about a screenful. Another odd thing with copy-pasting is
if I copy a line, then paste it, then cut (ctrl-x) a different
line and paste it, I end up pasting the earlier line I had copied,
not the cut line. I hope that makes sense ;) It's as if the
ctrl-x operation is not replacing the copy buffer.
All in all I'd say the program is working really well :)
Btw, I'm running it under Redhat 7.1 if you're interested.
-Roz
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I changed my mind about an installation script.
I compiled an rpm on my Mandrake system. I'd like to know how it works
on your system.
Fabien H
Roz wrote:
> Fabien HENON wrote:
>
>> at :
>>
>> http://pyvon.sourceforge.net
>>
>
> Wow, you've put a lot of work into this Fabien. I had no problems
> downloading it and installing it following the directions on the
> installation page on your web site. I noticed you already changed
> the filenames to be all lowercase. I think that's easier for
> people to deal with. You'll probably want to update the installation
> page with all lowercase command examples too if you haven't already.
>
> The screen split nicely between the editing window and the streams
> window. I opened a filename with a space in it and it rendered
> fine. I tested some of the stuff from the insert menu and that all
> worked wonderfully as well :)
>
> The only problem I had isn't a big thing, just a little odd. If I
> ctrl-c a line of text near the top of a file, then ctrl-v a line
> or several lines below, the whole file in the editor window scrolls
> down about a screenful. Another odd thing with copy-pasting is
> if I copy a line, then paste it, then cut (ctrl-x) a different
> line and paste it, I end up pasting the earlier line I had copied,
> not the cut line. I hope that makes sense ;) It's as if the
> ctrl-x operation is not replacing the copy buffer.
>
> All in all I'd say the program is working really well :)
>
> Btw, I'm running it under Redhat 7.1 if you're interested.
>
> -Roz
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Fabien HENON wrote:
> I changed my mind about an installation script.
>
> I compiled an rpm on my Mandrake system. I'd like to know how it works
> on your system.
>
The rpm installed just fine and the program runs from any directory with
the "pyvon" command.
It was unusual to see all the compiler settings you used in the
Description section of the package just under your provided description.
I'm not sure if you intended to include all the compiler settings there
or if it's something weird with my RedHat reading an rpm generated on a
Mandrake system. Other than that, everything looks good :)
-Roz
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I have just noticed that the insert do not work properly.
I have uploaded the fixed version.
If there is enough users I'll make an install for non-rpm systems in a
couple of days.
Fabien H.
Roz wrote:
> Fabien HENON wrote:
>
>> I changed my mind about an installation script.
>>
>> I compiled an rpm on my Mandrake system. I'd like to know how it works
>> on your system.
>>
>
> The rpm installed just fine and the program runs from any directory with
> the "pyvon" command.
>
> It was unusual to see all the compiler settings you used in the
> Description section of the package just under your provided description.
> I'm not sure if you intended to include all the compiler settings there
> or if it's something weird with my RedHat reading an rpm generated on a
> Mandrake system. Other than that, everything looks good :)
>
> -Roz
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 13 Sep 2002 13:25:12 +0200, Fabien HENON wrote:
> If there is enough users I'll make an install for non-rpm systems in a
> couple of days.
I think that is advisable, some people don't like using RPMs.
--
#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
|
|
| |
| |
|
|
|
|
| |
|
|
