Back from holidays

Hi!

I'm back from holidays. 

Went to the beach once. Went to Lisbon (our capital) for a week with my
family. You never went there? You should. Very pretty. Then again, I'm
biased. ;)

Played around with kpovmodeler some. Found out no tool, no matter how
excelent, solves a complete lack of artistic hability.
Darn. Back to coding. At least I'm good at that. (yes I am!! My mother said
so. She did! Okay, she didn't, but I must be good at something. Right?!
Right!?!? Stop snickering.)

First things first, a wee bug, more of an annoyance really: If povray's
default .ini file has a line setting Display=on, we get two windows every
time we call povray for some rendering. This is very distracting. We just
need to add -D to the calling of povray. I did it at home, but don't recall
the object now.

For kpovmodeler 1.1:
I think we have a problem with the automatic use of .ini files by povray.
IMHO, either we stop povray of using the default .ini file, or if that's not
possible, we provide an .ini file of our own. Otherwise we're susceptible to
any new setting the users place on povray. Since kpovmodeler works as a
front-end to povray, all options must be set through kpovmodeler.

Now on to the library objects (If you would like to see it, I can send some
screenshots to the list):

How does it work: 
  Importing: It's in "Insert | Library object", with the pmdeclare icon.
Opens an Open File dialog, with a preview of the objects. It starts in the
users local data directory (~/.kde/share/apps/kpovmodeler/library). You can
browse all the files, searching for the one you want. When you select the
file it places it on the scene, at the location where you have the cursor.

  Exporting: Only declares are allowed. Checks if all required objects are
selected and notifies of what's missing. If nothing's missing, Shows a
dialog where you fill the metadata about the object(s) and select a preview.
Opens a save as dialog in ~/.kde/share/apps/kpovmodeler/library.

  What's missing:
	1. Dealing with a global library and a users library, since the
dialog can only start in one of the places
	2. Auxiliary files (bump maps, material maps or density files, for
example)

Problem 1.: 
	Please choose one of the following:
		a) Make Insert Library Object have a sub menu with two
options: Global Library and Local Library
		b) Add a toolbar button to switch between Local Library and
Global Library to the open file dialog.
		c) You're so incredibly stupid Luis, it's a wonder how you
know how to breathe! 
               Obviously, the solution is _______________________________.

Problem 2.:
	In order to find out which objects have auxiliary files, I will add
two methods to PMObject:
		/** Does the object need auxiliary files? */
		virtual bool needsAuxiliaryFiles( ) const { return false; }
		/** Returns the list of auxiliary files needed by the
object. */
		virtual QStringList auxiliaryFiles( ) const { return
QStringList( ); }

	If the objects need auxiliary files, these will be added to the
library object file. 

Regards,
Luis Carvalho

PS: Man, I missed writing these long ramblings. 
    Didn't you miss reading my long ramblings? 
    I missed writing them.
    *laughs histerically*

List archive and information: http://mail.kde.org/mailman/listinfo/kpovmodeler-devel