[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gzz] Asko 2002-03-10
From: |
Tuomas Lukka |
Subject: |
Re: [Gzz] Asko 2002-03-10 |
Date: |
Mon, 10 Mar 2003 18:16:39 +0200 |
User-agent: |
Mutt/1.4i |
On Mon, Mar 10, 2003 at 05:36:27PM +0200, Asko Soukka wrote:
> 8h workday
> - replacing AbstractBgVob PEG with a new one
> - SolidBgVob -> SolidBackdropVob
> * gzz
> * libvob
>
> Benja: I didn't touch fenfire. AFAIK this affects Fenfire only
> after you update libvob.jar. Do you have make (ant) command
> for rebuilding Fenfire's libvob?
This would be a good place to start discussing these dependencies.
What model do we want to use?
> - Lego-controller photos should be placed to their own module
> for now on: fenfire/controllers
>
> Tuomas wrote:
> > Yes, we should talk priorities again now that the projects are split.
> > Should we try to focus on one project as a "swarm" and crank that one
> > project up one release or focus on different projects each?
>
> Sounds efficient, but how far is that reasonable?
Which one?
> I.e. I'm currently
> familiar only with libvob, loom and navidoc. Since gzz-version of navidoc
> works, it's not primary to project. Though, I still want to focus it after
> I have got something ready on UI said for a while.
Yes, and when you focus on it, do you think it would help if others focused
on it as well?
Or a small team?
Working on one of the projects alone feels to me a very slow way to make
progress (e.g. getting libvob up to gear would have been speeded up
by involving someone else).
> Btw, how crucial CullingCoordsys is currently? I've been avoiding it for a
> while, since I don't see any easy ways enhancing it. The benefit of more
> exact culling could be easy lost by longer calculation time.
Hmm, we could have a switch for how much the contents actually costs to
render...
However, it's not crucial before we have a benchmark that says it's a
bottleneck.
Tuomas