|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi all,
Waited till the 3.5 release to go inside pov again... since DKB...(or so?)
a long time has passed as i can see :))
mmm...enough joking
Not imposing just suggesting ... :)
well for lazy but practical people, the optional ability when
editing/opening a file to create sub-sections containing the different
parts of the scene/file:
the same way it is done for the different opened files :
ex:
[messages][Scene1.pov] [Scene2.pov] [exemple.pov]...
----------| |-------------------------------------------------
[Includes][Constants][Macro][Camera]|[Lights]|[Object1]...etc |
| |
| |
|
|Include stuff of Scene1.pov
|
|
|
Beginning of sections could be identified by some keywords
or intelligent parsing of the file could do it (need some AI here..)
and this could make building a scene much more practical and clear (I
think?)
+ Allowing a sub-menu for each sections
- could make optional the rendering of some objects
- or just render this part of the file (crop) (Including some
Mandatory/Choosable sections..)
on a single clic...
I just wanted to know if it was just another bad idea xor if some of you
could find it useful ?
- answers allowed -
(BTW Is It the right place to post this kind of messages ? yeah I think It
Is but...)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Me Again,
....have to report a BiG-BuG on the posting
Seem that two lines are missing from the preview:(maybe because of
brackets?)
(thus making no sense at all for the whole message >8(
here are they again:
after line 11
>ex:
-|messages||Scene1.pov||Scene2.pov||ShpereOnChecker.pov|
>----------| |-------------------------------------------------
>||includes|constants||macros||camera||lights||
>|
...
>|(include stuff of Scene1.pov)
>|
I hope this will make it more understandable
CherryMoon wrote:
>Hi all,
>Waited till the 3.5 release to go inside pov again... since DKB...(or so?)
>a long time has passed as i can see :))
>mmm...enough joking
>
>Not imposing just suggesting ... :)
>well for lazy but practical people, the optional ability when
>editing/opening a file to create sub-sections containing the different
>parts of the scene/file:
>the same way it is done for the different opened files :
>ex:
>> 2 lines missing see on top...
>>
>----------| |-------------------------------------------------
>| |
>| |
>|
>|Include stuff of Scene1.pov
>|
>|
>|
>
>
>Beginning of sections could be identified by some keywords
>or intelligent parsing of the file could do it (need some AI here..)
>and this could make building a scene much more practical and clear (I
>think?)
>
>+ Allowing a sub-menu for each sections
>- could make optional the rendering of some objects
>- or just render this part of the file (crop) (Including some
>Mandatory/Choosable sections..)
>on a single clic...
>
>I just wanted to know if it was just another bad idea xor if some of you
>could find it useful ?
>
>- answers allowed -
>
>(BTW Is It the right place to post this kind of messages ? yeah I think It
>Is but...)
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
web.3d650aeb25298f3fddfe293c0@news.povray.org...
> well for lazy but practical people, the optional ability when
> editing/opening a file to create sub-sections containing the different
> parts of the scene/file:
Not a bad idea at all. I don't think that having strict sub-section names
would be useful (there are a zillion ways to optimise a scene script and
sometimes the camera may well be found at the bottom), but the possibility
of having sections tags that the editor would recognise as such would be
quite interesting. It could allow the user to skip easily from one section
to another instead of scrolling.
G.
--
**********************
http://www.oyonale.com
**********************
- Graphic experiments
- POV-Ray and Poser computer images
- Posters
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 23 Aug 2002 01:37:39 +0200, "Gilles Tran" <git### [at] wanadoofr>
wrote:
>the possibility
>of having sections tags that the editor would recognise as such would be
>quite interesting. It could allow the user to skip easily from one section
>to another instead of scrolling.
We have bookmarks already which provide this functionality but don't
impose any specific coding style on the end user. I think it's better
the way it is now.
Peter Popov ICQ : 15002700
Personal e-mail : pet### [at] vipbg
TAG e-mail : pet### [at] tagpovrayorg
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Peter Popov" <pet### [at] vipbg> wrote in message
news:0igbmug66hj857uocjg36abk2d1s5gqdsv@4ax.com...
>
> We have bookmarks already which provide this functionality but don't
> impose any specific coding style on the end user. I think it's better
> the way it is now.
>
You learn something new every day....
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>We have bookmarks already which provide this functionality but don't
Yep thanks for the information, and sorry to ask for something that already
exist.I'm trying this right now....
(5 minutes later)
Yeah, I found the idea very useful...but it would be better if their
location can be saved on the file(ex:#declare
bookmarks-lines=5,22,30...generated on the first
bookmark-implementation-saving of a file)
The main drawback I found is the fact that still this is a non-direct access
and could not make optional the rendering of a single part of the scene
>impose any specific coding style on the end user. I think it's better
I think implementing section-tabs+right-click menu((de)select,crop,...)may
be done OPTIONNALY in addition of creating bookmarks the way they are
without imposing any coding style
thus allowing two new features: 1-Partial rendering and 2-Direct access..
I don't know that much in programming but I'm sure it's a matter of minutes
for you -C-ASM-LEXX&YACK-cracks ;)
I know, I know so much to do, so little time.... <)
Peter Popov wrote:
>On Fri, 23 Aug 2002 01:37:39 +0200, "Gilles Tran" <git### [at] wanadoofr>
>wrote:
>
>>the possibility
>>of having sections tags that the editor would recognise as such would be
>>quite interesting. It could allow the user to skip easily from one section
>>to another instead of scrolling.
>
>We have bookmarks already which provide this functionality but don't
>impose any specific coding style on the end user. I think it's better
>the way it is now.
>
>
>Peter Popov ICQ : 15002700
>Personal e-mail : pet### [at] vipbg
>TAG e-mail : pet### [at] tagpovrayorg
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>Not a bad idea at all. I don't think that having strict sub-section names...
Thanks but -Of course-,-Of course-, NO strict naming here...(I took some
optional-though-not-randomly-chosen-names-I-must-admit as exemples ;)
>sometimes the camera may well be found at the bottom), but the possibility...
this doesn't change anything because "scanning" file sequentially and then
placing them into appropriate sections doesn't mean they MUST follow a
strict order
>of having sections tags that the editor would recognise as such would be
and again Thanks because -sections tags- (or tabs?) was the word I was
chasing after ...seem that your english is better than mine!
Gilles Tran wrote:
>web.3d650aeb25298f3fddfe293c0[at]news.povray.org...
>
>> well for lazy but practical people, the optional ability when
>> editing/opening a file to create sub-sections containing the different
>> parts of the scene/file:
>
>Not a bad idea at all. I don't think that having strict sub-section names
>would be useful (there are a zillion ways to optimise a scene script and
>sometimes the camera may well be found at the bottom), but the possibility
>of having sections tags that the editor would recognise as such would be
>quite interesting. It could allow the user to skip easily from one section
>to another instead of scrolling.
>
>G.
>
>
>--
>**********************
>http://www.oyonale.com
>**********************
>- Graphic experiments
>- POV-Ray and Poser computer images
>- Posters
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
CherryMoon wrote:
> thus allowing two new features: 1-Partial rendering and 2-Direct access..
These are not new features. You can do it with almost any text editor.
Put each object on a separate file, with a conditional test setup (camera
and lighting), and a switch for test pupouses. Then you can render only
that file for testing the object. Also, you have direct access by loading
this file on the editor and clicking his tab anytime you want to access it.
It's a simple and useful technique.
--
Jaime Vives Piqueres
La Persistencia de la Ignorancia
http://www.ignorancia.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
0igbmug66hj857uocjg36abk2d1s5gqdsv@4ax.com...
> We have bookmarks already which provide this functionality but don't
> impose any specific coding style on the end user. I think it's better
> the way it is now.
Well bookmarks are not named and are not persistent so the functionality is
limited here. I was thinking more in the lines of what's already available
in the ini file, where the [] are used for the section headers. I'm not
saying it's a priority anyway, but when working with long scripts a little
combo box like the one for ini could come handy.
G.
--
**********************
http://www.oyonale.com
**********************
- Graphic experiments
- POV-Ray and Poser computer images
- Posters
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |