Keiron Liddle wrote:
Hi Victor,

I'm lost for ideas.
I'm getting the feeling that this project is simply too large for this
situation. Which is why I want the effort to be focused and not wasting
time sorting out things that don't get us anywhere.
It's a big task. Tangentially speaking, I still haven't finished work on properties, but as I proceed, I get more insight into the existing design and implementation, and more respect for it. A newcomer has no shortcuts to this situation. There's a Catch-22 here for complex open source projects. Resources are, by definition, in short supply. No matter what your working environment, the first thing to suffer from such shortages is documentation. But open source needs documentation (and the panoply of skills transfer mechanisms) more than a normal project.


The only realistic merge that I can see is bringing across the following
to the branch:
- pdf lib
- svg
- image handling

- renderers
- area tree

There isn't really that much on the branch that is relevant to the
trunk. The thing the branch has is that the layout works (sort of) and
it is a complex beast to do properly.

Maybe the simplest is to move the old layout to the trunk, get that
working and put the new layout in a branch. But it needs to be agreed
How difficult would this be? Would it be you who did most of this, or could you successfully direct others to assist?

"Lord, to whom shall we go?"

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to