Re: API documentation

Hi!

On Thursday 19 September 2002 22:22, luis wrote:
> Hello Andreas,
>
> Most of my classes have very basic documentation has they are not
> infrastructural. Mainly they are just loads of gets and sets, as you can
> imagine. (Scene elements)
>
> The exception is the layout editor and one or two utility methods in some
> objects.
>
> Theoretically, if both of us make the exact same change, cvs usually
> detects it and ignores it. It will say the changes have already been
> included in my file. Happened once or twice already. However, I'm not sure
> it will behave that well with complex changes.
>
> Just apply your script to the files and commit. Then I'll update from cvs
> and complete what needs to be completed.
>
> Send me a mail when you've completed that conversion.

No, you got me wrong :-)
I will not commit the changes due to the CVS freeze now.
Although it is a trivial change, no release coordinator has the time to look 
at the quite huge diff.

My concerns are for the time when the CVS will be open for new feature 
commits. We will get some conflicts anyway. Just didn't want to get 
unnecessary ones.

Btw: Maybe I will create a new branch (say, KPOVMODELER_1.1_EXPERIMENTAL) when 
I finished my first big architecture improvements (that is when I got rid of 
the PMObjectType type and finished the rule based system). I have already 
finished the rules file this afternoon, just the system that interprets the 
rules is missing :-)
Do you need an open CVS branch? I will then ask on the kde-core-devel list if 
one is allowed to add new branches. I don't think this will be a problem.

Andreas
-- 
--------------------------------------------------
 Andreas Zehender, Dipl. Ing. (BA)
 Student, 10th semester computer science
 http://www.azweb.de
 [email protected] | [email protected]      
--------------------------------------------------


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