Hello! It's probably not too late to consider some trivial optimization of fo tree in redesign code. In a typical fo document probably about 30% of elements have no children or have only one child (text node usually), so instead of eager protected ArrayList children = new ArrayList(); in FObj.java we can consider lazy polymorphic member protected Object children = null; 1) For no chidren case it remains to be null. 2) For 1 child case it is FONode object. 3) For children case it is ArrayList. This means some additional logic must be implmented at addChild() and getChildren() methods.
Any thoughts? -- Oleg Tkachenko Multiconn International, Israel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
