Object Libraries

CARVALHO Luis Passos <[email protected]>
Newsgroups gmane.comp.kde.devel.kpovmodeler
Message-ID <[email protected]>
Hi!

Just to let you all know: I now have a working "import library object". 

It opens a file browser which previews the library object to be inserted.
I'm not limiting the import to just declares. In fact, I attempt to insert
the objects contained in the library file in the position i'm in, just like
a paste action.

We can limit the creation of library objects to just declares, but I'm not
sure that's the way to go.
As it is now we could even create a library object that contains a default
scene, or maybe a set of cameras without much trouble.

I intend to have the following menu structure

Insert
      <All other objects>
	Library object
		From global library (as installed by kde)
		From user library	  (objects added in the users .kde
directory)
Library
	Create library object from selection
	Search library

What do you think?

Everything is still loosely validated. For instance: I have added an object
type to the objectdescription.xml, but it's just a descriptive string that
the user is free to fill with whatever he likes. In fact, every field of the
object description is like that. They will be just different ways of
searching the libraries. When you select a library object, kpovmodeler
attempts to paste it on the scene and may show an error, just like a paste.
What do you think of this approach?

If everything goes well, when the cvs opens up for new features again, we'll
have a working library the same day. :)

Also, the default scene should not be generated at runtime, IMHO. I think we
should have a template scene that is loaded at startup. Like word loads a
template. Should be simple and it's more customizable by the user.
Particularly in the default render modes.

Regards
Luis

List archive and information: http://mail.kde.org/mailman/listinfo/kpovmodeler-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.