> Because of a cancelled meeting, I've got a few hours to look > at the problem this afternoon. I haven't opened the jar with > the extensions yet, but the concept isContent() and isNestable() > you're using in the diffs is appealing. I'll see if it's something > I can introduce.
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.) 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 still not convinced if that's worth the effort, as the > Chapter/Section objects aren't really necessary: you can easily > create your own outline and titles. I'll see how it goes. > Maybe I can find some simple way to do it (without breaking > any existing code). I must admit that I noticed I hadn't adequately addressed indentation as I worked on RTF, and the solution seemed tricky. So, I'm sympathetic to what you say, but I still think it's a good idea to make memory-friendly Section and Chapter helpers available, for a variety of reasons: * 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. * Section hides the format-specific nuances of setting the style of titles from the user * 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. I mentioned that for me, a killer feature of iText is independence from the resulting document format. I like that I build the document out of abstract Elements, that get mapped to something appropriate for PDF or HTML or RTF or all three at once. (In fact I am also adding an XlsWriter, and a ZipWriter that outputs a zip containing text files and CSV.) I think the abstract Section concept is critical for that use. But I recognize that I may not represent the common user, and you have other priorities to consider. Still, even if this is not appropriate for 2.1, maybe it can make the roadmap for some release down the line. Kris Raney [EMAIL PROTECTED] ------------------------------------------------------------------------- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://itext.ugent.be/itext-in-action/
