Section/Chapters and memory 2007-12-01 - By Bruno Lowagie
Back
Kris Raney wrote:
> Ah, good, I'm glad you like that. I found that necessary in order to
> be able to add my own elements (the Div, and the BPSSection.Start
> and .End elements.)
That's one reason.
Also if we ever decide to add new Element implementations
ourselves, it will come in handy. We won't have to worry
about adding an Element type where necessary.
And we don't need the ugly 'or' sequence anymore every time
an object is added.
> There are other places that do
> switch(element.type) where I feel it would be helpful to move the code
> from the case statements into a method of the element, also, but I
> tried not to go crazy with modifications.
;-)
I'm taking this step by step. Normally, the changes in your
diff file should be visible in the SVN repository in a few hours.
After that, I'll see where to go from there.
> * the table of contents works differently in HTML, PDF, and RTF. The
> section and chapter objects hide that completely from the user. If the
> user does that themselves, they will have to dig into the format-
> specific issues.
Good point.
> * Section hides the format-specific nuances of setting the style of
> titles from the user
OK.
> * Section also takes care of indentation for you - the work you're
> doing fixing the indentation bugs is something all users of the new
> Section style can benefit from; if you don't do it in the library,
> everyone who implements their own outline & titles will have to do it
> individually.
True.
These are 3 good arguments.
You've made me love the Chapter/Section functionality again ;-)
I'll have a look at them to see what I can do.
best regards,
Bruno
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- -----
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
__ ____ ____ ____ ____ ____ ____ ____ ____ ____
iText-questions mailing list
iText-questions@(protected)
https://lists.sourceforge.net/lists/listinfo/itext-questions
Buy the iText book: http://itext.ugent.be/itext-in-action/
|
|
