 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi!
In order to assist the users of POV-Ray on Unix and related platforms,
it's useful for me to know what it is people want. This will help me to
prioritize platform-specific development. I can guess, but I find that
asking works better. I know of no better place to go to get user
feedback from the users of POV-Ray on Unix than this newsgroup. You
could do me a favor by answering the following questions. Feel free to
either respond on this news server or to email me. I'm not interested
in marketing data, selling email addresses, or any of that underhanded
stuff, but I suspect you already figured that out. I've asked some of
these questions here before, but I'm looking to correlate them with
other data.
OK, here are the questions:
1) Under what operating systems do you use POV-Ray? Please be specific
as to e.g. Linux distributions, versions, and so forth. Multiple
answers are fine.
2) Do you want POV-Ray for Unix to have an official GUI front-end for
your platform? Please indicate which one(s) if you list several
platforms.
3) Would you want such a front-end to have a built-in editor?
4) Any preference on languages/GUI libraries on such a front end, pro or
con? (Tcl/Tk, Perl/Tk, Python Tkinter, Java AWT, gtk+, Gnome, KDE,
Motif/Lesstif)
5) What editor do you use for editing .pov files?
6) What format(s) do you prefer for documentation? (HTML, ASCII, PDF,
ps, man, info, Word document, etc.)
7) What sort of package management do you prefer for precompiled
binaries?
8) What unofficial version(s) of POV-Ray (e.g. MegaPov, PVMPOV) do you
use on a regular basis?
What I plan to get from this:
1) Insight into the platforms for which official binaries perhaps ought
to exist, used with 2, 3, and 4 to determine the operating systems(s)
for which there is the strongest demand for a GUI, which in turn will
help determine the language/toolkit used.
2) Related to the second part of 1. Given the eventuality of an
official GUI for Unix, this lets me know what platforms it needs to run
on, which again affects the choice of language/toolkit. In any event,
the core renderer will remain available from the command line.
3) While the last thing Unix needs is another text editor, I may be
included to include one given
sufficient interest. Or I might do it on a lark, for which I'd hope
you'd forgive me. ;-)
4) Related to 2. This is one of the big questions from a practical
standpoint. The fact that it's still a question gives you some idea of
where development is on an official front-end at this point (put on the
back burner until 3.5 is further along). This also lets me know whether
anyone hates any of the options (Tk is ugly, Motif is ugly, Gnome/KDE is
the subject of a religious war, Gnome and KDE aren't necessarily that
portable to some of the commercial Unices)
5) Related to 3. This gives me some idea of what users might want from
an editor, if one gets included. I'm also just curious.
6) Lets me know what documentation format Unix users want shipped with
POV-Ray. There are tradeoffs involved (ascii: universally supported,
trivially searched, available on a console; HTML: widely supported,
supports images, reasonably searchable, available over a network; PDF:
fairly widely supported, supports images, most visually attractive).
Word documents aren't a serious suggestion, but they're one of the
formats we have for 3.1, so I'm laying it on the table for folks to hiss
at. ;-)
7) Lets me know what package formats I might want to add. Tarballs will
always remain available, but I'm looking into adding other options, and
I'm wondering how much interest there is.
8) Lets me know what folks are using. Mostly to satisfy my curiosity.
Some of the things that were asked about in my last survey have happily
been rendered (no pun intended) moot. Specifically, the demand for a
configure/make/make install has been addressed, and there's now just one
binary that uses whatever form of display makes the most sense in the
context. I have a version of MegaPov with these changes that I'd like
to see tested widely before I decide to put them into 3.5. It's a
little rough at this point, and I'm sure I've made lots of beginner's
mistakes, but it seems to beat the living daylights out of the current
system, and it's going to make my life a whole lot easier from here on
out. Once I'm done with documentation, it will be made available. Look
for it
in a few days.
-Mark Gordon
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> 1) Under what operating systems do you use POV-Ray? Please be specific
> as to e.g. Linux distributions, versions, and so forth. Multiple
> answers are fine.
LINUX (SuSE 6.3)
IRIX 6.5
>
> 2) Do you want POV-Ray for Unix to have an official GUI front-end for
> your platform? Please indicate which one(s) if you list several
> platforms.
Not neccessarily. Wouldn't hurt either.
> 3) Would you want such a front-end to have a built-in editor?
No.
> 4) Any preference on languages/GUI libraries on such a front end, pro or
> con? (Tcl/Tk, Perl/Tk, Python Tkinter, Java AWT, gtk+, Gnome, KDE,
> Motif/Lesstif)
No
> 5) What editor do you use for editing .pov files?
emacs
> 6) What format(s) do you prefer for documentation? (HTML, ASCII, PDF,
> ps, man, info, Word document, etc.)
PDF, ps, html
> 7) What sort of package management do you prefer for precompiled
> binaries?
rpm
> 8) What unofficial version(s) of POV-Ray (e.g. MegaPov, PVMPOV) do you
> use on a regular basis?
none
Marc
--
Marc Schimmler
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mark Gordon <mtg### [at] mailbag com> wrote:
: 1) Under what operating systems do you use POV-Ray? Please be specific
: as to e.g. Linux distributions, versions, and so forth. Multiple
: answers are fine.
- Solaris 7 (in a Sun Ultra 5)
- Windows98 (in a P-II)
I have access to other platforms, but I don't use povray actively in those.
As for the Solaris 7 povray, I probably would not use any official compile
but I will probably always compile it by my own.
: 2) Do you want POV-Ray for Unix to have an official GUI front-end for
: your platform? Please indicate which one(s) if you list several
: platforms.
I always make my povray files with emacs and would probably not change
to any other editor (unless it had the same features). A GUI would be, then,
fancy but mostly useless.
Of course a GUI could have other things that could be useful, like all
the other features of Winpov besides the editor. For example the ability of
marking a rendering area in the render window with the mouse could be very
useful.
I would not mind a GUI, but could live perfectly without one.
: 3) Would you want such a front-end to have a built-in editor?
As I said, I would probably not use any other editor unless it had the
same features as emacs (with pov-mode).
The GUI would definitely have to have support for an external editor.
: 4) Any preference on languages/GUI libraries on such a front end, pro or
: con? (Tcl/Tk, Perl/Tk, Python Tkinter, Java AWT, gtk+, Gnome, KDE,
: Motif/Lesstif)
Not really, as long as it works well and fast here.
I have coded a bit with gtk. It's a pain to code but seems to work fine
and efficiently.
: 5) What editor do you use for editing .pov files?
Emacs (with pov-mode.el).
: 6) What format(s) do you prefer for documentation? (HTML, ASCII, PDF,
: ps, man, info, Word document, etc.)
HTML and PDF are fine. Plain ascii is horrible. Man pages could be good.
No PS nor Word, thanks (well, I can view PS, but browsing it is a pain).
: 7) What sort of package management do you prefer for precompiled
: binaries?
Sorry, don't know about this.
: 8) What unofficial version(s) of POV-Ray (e.g. MegaPov, PVMPOV) do you
: use on a regular basis?
MegaPov.
: What I plan to get from this:
: 1) Insight into the platforms for which official binaries perhaps ought
: to exist, used with 2, 3, and 4 to determine the operating systems(s)
: for which there is the strongest demand for a GUI, which in turn will
: help determine the language/toolkit used.
I'm sure that Linux users will like a GUI that is similar to the one
in Winpov.
Some GUI packages are quite platform independant, so code made for those
can be compiled in almost any platform that has that GUI library ported.
: Some of the things that were asked about in my last survey have happily
: been rendered (no pun intended) moot. Specifically, the demand for a
: configure/make/make install has been addressed, and there's now just one
: binary that uses whatever form of display makes the most sense in the
: context.
I have made an almost-universal makefile which can compile almost anything
(it calculates all the dependencies by itself) and use a modified version
when compiling megapov. The makefile itself is really short because almost
everything is calculated automatically. It needs gmake, though.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mark Gordon wrote:
> OK, here are the questions:
>
> 1) Under what operating systems do you use POV-Ray? Please be specific
> as to e.g. Linux distributions, versions, and so forth. Multiple
> answers are fine.
>
I'm now using Redhat 6.1 with an 2.2.12 kernel. I'm going to switch to
my own build 'distribution' (LFS: www.linuxfromscratch.org).
> 2) Do you want POV-Ray for Unix to have an official GUI front-end for
> your platform? Please indicate which one(s) if you list several
> platforms.
>
Do you mean a window where a can click at the options? Would be nice, as
long as I can disable it. (I don't like the way it works in povray for
windows).
And can it automatically check for a newer saved version of the current
scene and render it?
> 3) Would you want such a front-end to have a built-in editor?
>
No
> 4) Any preference on languages/GUI libraries on such a front end, pro or
> con? (Tcl/Tk, Perl/Tk, Python Tkinter, Java AWT, gtk+, Gnome, KDE,
> Motif/Lesstif)
>
gtk+ or Gnome. I persionally dislike the windows look like GUIs. Like
QT. i don't wheter the other possibillities look like windows
> 5) What editor do you use for editing .pov files?
>
Mcedit. The build in editor of the Midnight Commander, which can be
externally invoked.
I'm thinking about switching to emacs, because of the LISP
possibillities.
> 6) What format(s) do you prefer for documentation? (HTML, ASCII, PDF,
> ps, man, info, Word document, etc.)
>
HTML for the full documentation (some more clarifying images would be
nice.
A man page for a describtion of the commandline parameters.
> 7) What sort of package management do you prefer for precompiled
> binaries?
.tar.gz
.rpm or .deb gives you so less freedom about how you want to install the
software
>
> 8) What unofficial version(s) of POV-Ray (e.g. MegaPov, PVMPOV) do you
> use on a regular basis?
None
Remco Poelstra
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> 1) Under what operating systems do you use POV-Ray? Please be specific
> as to e.g. Linux distributions, versions, and so forth. Multiple
> answers are fine.
Started as Redhat Linux 6.0, lots of stuff upgraded from source.
>
> 2) Do you want POV-Ray for Unix to have an official GUI front-end for
> your platform? Please indicate which one(s) if you list several
> platforms.
Not particularly, I wouldn't use it. It would just make the package take
longer to build.
> 3) Would you want such a front-end to have a built-in editor?
No.
> 4) Any preference on languages/GUI libraries on such a front end, pro or
> con? (Tcl/Tk, Perl/Tk, Python Tkinter, Java AWT, gtk+, Gnome, KDE,
> Motif/Lesstif)
No.
> 5) What editor do you use for editing .pov files?
Nedit, MC internal editor.
> 6) What format(s) do you prefer for documentation? (HTML, ASCII, PDF,
> ps, man, info, Word document, etc.)
TeX, HTML
> 7) What sort of package management do you prefer for precompiled
> binaries?
Don't use 'em any more.
> 8) What unofficial version(s) of POV-Ray (e.g. MegaPov, PVMPOV) do you
> use on a regular basis?
MegaPov
Cheers, PoD.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 22 Jun 2000 22:50:56 -0500, Mark Gordon <mtg### [at] mailbagcom>
wrote:
>OK, here are the questions:
>
>1) Under what operating systems do you use POV-Ray? Please be specific
>as to e.g. Linux distributions, versions, and so forth. Multiple
>answers are fine.
Slackware 7 kernel 2.2.14
Windows 98 SE
>2) Do you want POV-Ray for Unix to have an official GUI front-end for
>your platform? Please indicate which one(s) if you list several
>platforms.
Yes.
>3) Would you want such a front-end to have a built-in editor?
No, but official modes for emacs and nedit would help, especially if
keyboard shourcuts are made to match those in the POV-Ray for Windows
GUI.
>4) Any preference on languages/GUI libraries on such a front end, pro or
>con? (Tcl/Tk, Perl/Tk, Python Tkinter, Java AWT, gtk+, Gnome, KDE,
>Motif/Lesstif)
No, as long as it's not Gnome/KDE specific.
>5) What editor do you use for editing .pov files?
CodeMax.
>6) What format(s) do you prefer for documentation? (HTML, ASCII, PDF,
>ps, man, info, Word document, etc.)
HTML, PDF, .hlp . Man is fine but maybe not for a project as large as
POV-Ray.
>7) What sort of package management do you prefer for precompiled
>binaries?
Dunno. I always get the source and compile it :)
>8) What unofficial version(s) of POV-Ray (e.g. MegaPov, PVMPOV) do you
>use on a regular basis?
MegaPOV.
Peter Popov ICQ : 15002700
Personal e-mail : pet### [at] usanet
TAG e-mail : pet### [at] tagpovrayorg
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Here are my answers:
> 1) Under what operating systems do you use POV-Ray? Please be specific
> as to e.g. Linux distributions, versions, and so forth. Multiple
> answers are fine.
Linux Redhat 6.1 (Probably changing soon to slackware...)
> 2) Do you want POV-Ray for Unix to have an official GUI front-end for
> your platform? Please indicate which one(s) if you list several
> platforms.
No, since I made my own GUI, that calls POV-Ray for each frame of an animation,
it can trace graphics, give time estimate, etc... Building an official GUI
wouldn't be very effective IMO. Improving the source code to implement it our
way would be better!
> 3) Would you want such a front-end to have a built-in editor?
If there ever were a front-end to POV-Ray (I hope the GUIless will still exist),
I wouldn't want any other editor than Emacs... maybe the front-end could call
your prefered editor or is you choice is none give the default one (made by your
team, a povray oriented editor)...
> 4) Any preference on languages/GUI libraries on such a front end, pro or
> con? (Tcl/Tk, Perl/Tk, Python Tkinter, Java AWT, gtk+, Gnome, KDE,
> Motif/Lesstif)
Definitely C++, and I would suggest using OpenGL... there is a GUI toolkit for
labels, buttons, slidebars and such that can control your OpenGL animation...
but the animation stuff is of almost no use for you, you can just put the render
there, a toolbar over here, a menu up there, etc... and it would be graphically
accelerated (the front-end that is, menus and such) by any 3dAccel Card!
> 5) What editor do you use for editing .pov files?
Emacs, is use it for any kind of edition (.c, .cc, .pov, .html, etc!..)
> 6) What format(s) do you prefer for documentation? (HTML, ASCII, PDF,
> ps, man, info, Word document, etc.)
I would be cool to have a HTML documention for quick reference and a PDF or ps
version for printed manuals (BTW, could you add color graphics of examples in
the doc? that would be very attractive and more fun to read!)
> 7) What sort of package management do you prefer for precompiled
> binaries?
I don't like the ideas of package management, but since I'm in Redhat and never
saw anything else, I'd say rmps?
> 8) What unofficial version(s) of POV-Ray (e.g. MegaPov, PVMPOV) do you
> use on a regular basis?
None, I use the Only, the Real POV-Ray! ;)
> What I plan to get from this:
> 1) Insight into the platforms for which official binaries perhaps ought
> to exist, used with 2, 3, and 4 to determine the operating systems(s)
> for which there is the strongest demand for a GUI, which in turn will
> help determine the language/toolkit used.
If you need help developping the GUI, I could help much for the OpenGL
version... And keep in mind that the render is still POV-RAYTRACING!: slow but
so marvellous! This is not a modeller, the OpenGL could easily manage animation
effects such as motionblur, fades-in/out, there could be an animation mixer
implemented!... The future is ours to take! ;)
> 2) Related to the second part of 1. Given the eventuality of an
> official GUI for Unix, this lets me know what platforms it needs to run
> on, which again affects the choice of language/toolkit. In any event,
> the core renderer will remain available from the command line.
Talking about platforms... by building this thing with OpenGL libs, you can
easily port it to the Mac or Windows, let say it would take like 5 mins to
compile a working version for both of them! It's the same code! Maybe except
for file management (/home/name/..., c:/documents/..., MacOS:Documents:...)
> 3) While the last thing Unix needs is another text editor, I may be
> included to include one given
> sufficient interest. Or I might do it on a lark, for which I'd hope
> you'd forgive me. ;-)
That sounds good to me!
> 4) Related to 2. This is one of the big questions from a practical
> standpoint. The fact that it's still a question gives you some idea of
> where development is on an official front-end at this point (put on the
> back burner until 3.5 is further along). This also lets me know whether
> anyone hates any of the options (Tk is ugly, Motif is ugly, Gnome/KDE is
> the subject of a religious war, Gnome and KDE aren't necessarily that
> portable to some of the commercial Unices)
Think about OpenGL!... by linking the app static, the users would not need the
GLlibs... only for those that have accelCards, but they already have it!
> 5) Related to 3. This gives me some idea of what users might want from
> an editor, if one gets included. I'm also just curious.
Think about Emacs... it's simply the best editor... we could provide a POV-ray
oriented configuration for tabs and everything...
> 6) Lets me know what documentation format Unix users want shipped with
> POV-Ray. There are tradeoffs involved (ascii: universally supported,
> trivially searched, available on a console; HTML: widely supported,
> supports images, reasonably searchable, available over a network; PDF:
> fairly widely supported, supports images, most visually attractive).
> Word documents aren't a serious suggestion, but they're one of the
> formats we have for 3.1, so I'm laying it on the table for folks to hiss
> at. ;-)
You should provide a README saying to download the documentation.tgz with the
povray_GUI.tgz, and you should simply include all the docs in it!
> 7) Lets me know what package formats I might want to add. Tarballs will
> always remain available, but I'm looking into adding other options, and
> I'm wondering how much interest there is.
There I can't help much... maybe rpms, but don't count me...
> 8) Lets me know what folks are using. Mostly to satisfy my curiosity.
What I'm using? If you were more specific? I use POV-Ray 3.1 with emacs, some
C++ with g++, I render to ppm... What else?
-----------
BTW, I would really enjoy working with that GUI... That would be not too fancy,
very effective, would never slow a render, very informative, what can I say!
Hope this can be useful,
Simon Lemieux
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Here are my answers:
> 1) Under what operating systems do you use POV-Ray? Please be specific
> as to e.g. Linux distributions, versions, and so forth. Multiple
> answers are fine.
Linux Redhat 6.1 (Probably changing soon to slackware...)
> 2) Do you want POV-Ray for Unix to have an official GUI front-end for
> your platform? Please indicate which one(s) if you list several
> platforms.
No, since I made my own GUI, that calls POV-Ray for each frame of an animation,
it can trace graphics, give time estimate, etc... Building an official GUI
wouldn't be very effective IMO. Improving the source code to implement it our
way would be better!
> 3) Would you want such a front-end to have a built-in editor?
If there ever were a front-end to POV-Ray (I hope the GUIless will still exist),
I wouldn't want any other editor than Emacs... maybe the front-end could call
your prefered editor or is you choice is none give the default one (made by your
team, a povray oriented editor)...
> 4) Any preference on languages/GUI libraries on such a front end, pro or
> con? (Tcl/Tk, Perl/Tk, Python Tkinter, Java AWT, gtk+, Gnome, KDE,
> Motif/Lesstif)
Definitely C++, and I would suggest using OpenGL... there is a GUI toolkit for
labels, buttons, slidebars and such that can control your OpenGL animation...
but the animation stuff is of almost no use for you, you can just put the render
there, a toolbar over here, a menu up there, etc... and it would be graphically
accelerated (the front-end that is, menus and such) by any 3dAccel Card!
> 5) What editor do you use for editing .pov files?
Emacs, is use it for any kind of edition (.c, .cc, .pov, .html, etc!..)
> 6) What format(s) do you prefer for documentation? (HTML, ASCII, PDF,
> ps, man, info, Word document, etc.)
I would be cool to have a HTML documention for quick reference and a PDF or ps
version for printed manuals (BTW, could you add color graphics of examples in
the doc? that would be very attractive and more fun to read!)
> 7) What sort of package management do you prefer for precompiled
> binaries?
I don't like the ideas of package management, but since I'm in Redhat and never
saw anything else, I'd say rmps?
> 8) What unofficial version(s) of POV-Ray (e.g. MegaPov, PVMPOV) do you
> use on a regular basis?
None, I use the Only, the Real POV-Ray! ;)
> What I plan to get from this:
> 1) Insight into the platforms for which official binaries perhaps ought
> to exist, used with 2, 3, and 4 to determine the operating systems(s)
> for which there is the strongest demand for a GUI, which in turn will
> help determine the language/toolkit used.
If you need help developping the GUI, I could help much for the OpenGL
version... And keep in mind that the render is still POV-RAYTRACING!: slow but
so marvellous! This is not a modeller, the OpenGL could easily manage animation
effects such as motionblur, fades-in/out, there could be an animation mixer
implemented!... The future is ours to take! ;)
> 2) Related to the second part of 1. Given the eventuality of an
> official GUI for Unix, this lets me know what platforms it needs to run
> on, which again affects the choice of language/toolkit. In any event,
> the core renderer will remain available from the command line.
Talking about platforms... by building this thing with OpenGL libs, you can
easily port it to the Mac or Windows, let say it would take like 5 mins to
compile a working version for both of them! It's the same code! Maybe except
for file management (/home/name/..., c:/documents/..., MacOS:Documents:...)
> 3) While the last thing Unix needs is another text editor, I may be
> included to include one given
> sufficient interest. Or I might do it on a lark, for which I'd hope
> you'd forgive me. ;-)
That sounds good to me!
> 4) Related to 2. This is one of the big questions from a practical
> standpoint. The fact that it's still a question gives you some idea of
> where development is on an official front-end at this point (put on the
> back burner until 3.5 is further along). This also lets me know whether
> anyone hates any of the options (Tk is ugly, Motif is ugly, Gnome/KDE is
> the subject of a religious war, Gnome and KDE aren't necessarily that
> portable to some of the commercial Unices)
Think about OpenGL!... by linking the app static, the users would not need the
GLlibs... only for those that have accelCards, but they already have it!
> 5) Related to 3. This gives me some idea of what users might want from
> an editor, if one gets included. I'm also just curious.
Think about Emacs... it's simply the best editor... we could provide a POV-ray
oriented configuration for tabs and everything...
> 6) Lets me know what documentation format Unix users want shipped with
> POV-Ray. There are tradeoffs involved (ascii: universally supported,
> trivially searched, available on a console; HTML: widely supported,
> supports images, reasonably searchable, available over a network; PDF:
> fairly widely supported, supports images, most visually attractive).
> Word documents aren't a serious suggestion, but they're one of the
> formats we have for 3.1, so I'm laying it on the table for folks to hiss
> at. ;-)
You should provide a README saying to download the documentation.tgz with the
povray_GUI.tgz, and you should simply include all the docs in it!
> 7) Lets me know what package formats I might want to add. Tarballs will
> always remain available, but I'm looking into adding other options, and
> I'm wondering how much interest there is.
There I can't help much... maybe rpms, but don't count me...
> 8) Lets me know what folks are using. Mostly to satisfy my curiosity.
What I'm using? If you were more specific? I use POV-Ray 3.1 with emacs, some
C++ with g++, I render to ppm... What else?
-----------
BTW, I would really enjoy working with that GUI... That would be not too fancy,
very effective, would never slow a render, very informative, what can I say!
Hope this can be useful,
Simon Lemieux
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 22 Jun 2000 22:50:56 -0500, Mark Gordon wrote:
>
>1) Under what operating systems do you use POV-Ray? Please be specific
>as to e.g. Linux distributions, versions, and so forth. Multiple
>answers are fine.
Linux RH 6.2
>
>2) Do you want POV-Ray for Unix to have an official GUI front-end for
>your platform? Please indicate which one(s) if you list several
>platforms.
No not a gui but a straightforward editor a la EDIT.EXE in dos (where
SHIFT+ARROWKEY marks text and SHIFT+INSERT copies it etc). Something
that can be run in more than one xterm at once.
>3) Would you want such a front-end to have a built-in editor?
>
>4) Any preference on languages/GUI libraries on such a front end, pro or
>con? (Tcl/Tk, Perl/Tk, Python Tkinter, Java AWT, gtk+, Gnome, KDE,
>Motif/Lesstif)
I use Gnome.
>5) What editor do you use for editing .pov files?
Pico. (with manus and line wraps turned off).
>6) What format(s) do you prefer for documentation? (HTML, ASCII, PDF,
>ps, man, info, Word document, etc.)
ASCII and if images are included then HTML or PDF.
>
>7) What sort of package management do you prefer for precompiled
>binaries?
Just tar.gz is fine.
>8) What unofficial version(s) of POV-Ray (e.g. MegaPov, PVMPOV) do you
>use on a regular basis?
MegaPov.
>What I plan to get from this:
>1) Insight into the platforms for which official binaries perhaps ought
>to exist, used with 2, 3, and 4 to determine the operating systems(s)
>for which there is the strongest demand for a GUI, which in turn will
>help determine the language/toolkit used.
>2) Related to the second part of 1. Given the eventuality of an
>official GUI for Unix, this lets me know what platforms it needs to run
>on, which again affects the choice of language/toolkit. In any event,
>the core renderer will remain available from the command line.
>3) While the last thing Unix needs is another text editor, I may be
>included to include one given
>sufficient interest. Or I might do it on a lark, for which I'd hope
>you'd forgive me. ;-)
Yes Yes Yes, see my answer above.
>4) Related to 2. This is one of the big questions from a practical
>standpoint. The fact that it's still a question gives you some idea of
>where development is on an official front-end at this point (put on the
>back burner until 3.5 is further along). This also lets me know whether
>anyone hates any of the options (Tk is ugly, Motif is ugly, Gnome/KDE is
>the subject of a religious war, Gnome and KDE aren't necessarily that
>portable to some of the commercial Unices)
>5) Related to 3. This gives me some idea of what users might want from
>an editor, if one gets included. I'm also just curious.
>6) Lets me know what documentation format Unix users want shipped with
>POV-Ray. There are tradeoffs involved (ascii: universally supported,
>trivially searched, available on a console; HTML: widely supported,
>supports images, reasonably searchable, available over a network; PDF:
>fairly widely supported, supports images, most visually attractive).
>Word documents aren't a serious suggestion, but they're one of the
>formats we have for 3.1, so I'm laying it on the table for folks to hiss
>at. ;-)
>7) Lets me know what package formats I might want to add. Tarballs will
>always remain available, but I'm looking into adding other options, and
>I'm wondering how much interest there is.
>8) Lets me know what folks are using. Mostly to satisfy my curiosity.
>
>Some of the things that were asked about in my last survey have happily
>been rendered (no pun intended) moot. Specifically, the demand for a
>configure/make/make install has been addressed, and there's now just one
>binary that uses whatever form of display makes the most sense in the
>context. I have a version of MegaPov with these changes that I'd like
>to see tested widely before I decide to put them into 3.5. It's a
>little rough at this point, and I'm sure I've made lots of beginner's
>mistakes, but it seems to beat the living daylights out of the current
>system, and it's going to make my life a whole lot easier from here on
>out. Once I'm done with documentation, it will be made available. Look
>for it
>in a few days.
>
>-Mark Gordon
--
Cheers
Steve email mailto:sjl### [at] ndirectcouk
%HAV-A-NICEDAY Error not enough coffee 0 pps.
web http://www.ndirect.co.uk/~sjlen/
or http://start.at/zero-pps
11:54pm up 6 days, 45 min, 1 user, load average: 1.39, 1.41, 1.28
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mark Gordon wrote:
> 1) Under what operating systems do you use POV-Ray? Please be specific
> as to e.g. Linux distributions, versions, and so forth. Multiple
> answers are fine.
Linux Mandrake 6.1 and Red Hat 6.1
> 2) Do you want POV-Ray for Unix to have an official GUI front-end for
> your platform? Please indicate which one(s) if you list several
> platforms.
No.
> 3) Would you want such a front-end to have a built-in editor?
No.
> 4) Any preference on languages/GUI libraries on such a front end, pro or
> con? (Tcl/Tk, Perl/Tk, Python Tkinter, Java AWT, gtk+, Gnome, KDE,
> Motif/Lesstif)
No.
> 5) What editor do you use for editing .pov files?
XEmacs
> 6) What format(s) do you prefer for documentation? (HTML, ASCII, PDF,
> ps, man, info, Word document, etc.)
HTML
> 7) What sort of package management do you prefer for precompiled
> binaries?
RPM
> 8) What unofficial version(s) of POV-Ray (e.g. MegaPov, PVMPOV) do you
> use on a regular basis?
MegaPov and PvmPov
--
__ __ __ __ _
| | / \ / / |_ / |/
\/\/ \__/ /_ /_ |__ \_ |\
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
