Hi,
On Wed, 2007-06-06 at 13:34 -0500, Allen Bierbaum wrote:
> Dirk Reiners wrote:
> > Hi All,
> >
> > Gerrit Voss wrote:
> >>>>>> I agree with this statement and it scares me quite a bit. The 1.x and
> >>>>>> 2.0 code branches are diverging and I don't see an end to it in sight.
> >>>>>> IMHO we have to find a way to end the 1.x series otherwise the 2.0
> >>>>>> series will never really get going.
> >>> Diverging may be an understatement.
> >> It is not as bad as it sounds.
> >
> > That's the optimist's way of looking at it. ;) I somewhat agree with it,
> > though,
> > the changes in 1 are mostly minor.
> >
> >> Which in particular ??, we do not merge on a regular basis but usually
> >> all these minor fixes get pulled over once we merge (as far as they
> >> apply). Also some things inside 1.x need to be redesigned before they
> >> end up in 2.x as the current 1.x implementation is more than ugly ;-).
> >
> > Anything in particular?
One thing I would like to move to stages is some of the viewport mess,
maybe the display filters too.
> >>>> Note: I don't speak for the OpenSG team. I may commit code once in a
> >>>> while, but I am not a core developer. I proposed August as a time for
> >>>> an alpha 2.0 because we are already using it and it seems at least alpha
> >>>> quality to me. ;)
> >> Kind of agree, but there is a roadblock ;-(, the pieces that are there
> >> are close to alpha, there should be some cleanup but August could be a
> >> reasonable time frame for an alpha iff we finally manage decide on the
> >> pointer stuff ASAP.
> >>
> >> Both implementations are there and running. Dirk wanted to work on it a
> >> while back but I don't have any feedback on the status right now.
>
> It sounds like we need to get this done. IMHO, if we are going to keep
> OpenSG 2.0 moving forward, we need to set a date for this work to be
> completed to the point we can start testing it. Since one of the key
> people is going to be gone all of July, I propose we set a date of June
> 30th to have a first pass at the cptr implementation complete.
>
> With that said, is that date reasonable and what can the rest of us in
> the community do to help make it happen?
I'm more thinking about end of next week, because the implementation is
there and running. It's mainly about removing the fcptr code and
starting to KISS.
> >
> >> So if we agree on C pointer I could go ahead and remove the fcptr
> >> pointer code along with the mixin cleanup I did a while back. Once we
> >> have this part out of the way we can go ahead and look into the ref
> >> pointer problem.
> >
> > One of my goals with CPtr was to seriously simplify the code, which is why
> > I
> > wanted to do it myself. If you could turn your head/hat inside out and look
> > at
> > it with the KISS view instead of the elegance view I would be very happy if
> > you
> > could move on that one a little bit.
I can try ;-). At least I can remove a lot of the overhead from the CPtr
stuff and collapse the mixins again. After that it might be easier for
somebody to look at it again and see if it is simple enough ;-))
One thing that still bothers me is the vtbl free fields, but this can be
a second step after the rest clears up ;-)
> >
> >> s***, I am a core developer ;-).
> >
> > Ouch! How did that happen? Does it hurt? ;)
somebody said 'Oh Gerrit, schoen dich zu sehen, hast du mal ne
Sekunde' ;-)).
regards,
gerrit
--
It's Emergent[*], you see.
[*] [adj] A word favored by computer nerds; mandatory for DARPA research
applications; on recent evidence, a synonym for 'doomed'.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Opensg-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-core
