New module for KPovModeler

[Shawn Gordon]

At 03:58 AM 12/31/2002, you wrote:
>Hi!
>
>Some weeks ago some developers suggested to move KPovModeler to a new module
>because of its specialization and its size.
>
>I merged our experimental branch during the feature freeze with the HEAD
>branch yesterday, so it would be a good time for us to move the application
>now.
>
>Two possibilities come to my mind: An own module named "kpovmodeler" (like
>kdevelop) or a generic 3d module. I would prefer a module kpovmodeler as I
>don't think there are or will be many kde application that would fit in a 3d
>module. Correct me if I am wrong.

what about k3studio?  I haven't looked at it in a while, but I was always 
very impressed with it.


>The code in the KDE_3_1_BRANCH has to remain in this branch, of course. Is it
>possible to move the code on the server to preserve the version history while
>not touching the 3.1 branch?
>
>We are developing a plugin framework, so we need a new directory structure 
>for
>the kpovmodeler part. If kpovmodeler gets its own module, the directory
>kdegraphics/kpovmodeler should be moved to kpovmodeler/part.
>If a 3d module is created, kdegraphics/kpovmodeler should be moved to
><new 3d module>/kpovmodeler/part
>The directories for i18n and docs have to be moved and adapted accordingly.
>
>Greetings, Andreas
>
>
>PS: An a happy new year to all
>
>--
>--------------------------------------------------
>  Andreas Zehender, Dipl. Ing. (BA)
>  Student, 10th semester computer science
>  http://www.azweb.de
>  az at azweb.de | zehender at kde.org
>--------------------------------------------------


Regards,

Shawn Gordon
President
theKompany.com
www.thekompany.com
949-713-3276