Difference between revisions of "User:Joekidd/OpenOffice.org/Internship/PDFImport/Tasks/Moving Proper paragraphs GlyphProcessor"

From Apache OpenOffice Wiki
Jump to: navigation, search
Line 1: Line 1:
−
GlyphProcessor is quite complex and makes PDFIProcessor untidy. The main reason of moving glyph processing to separate class was to avoid mess and make the code more scalable. It's required about 4 hours to move it to separate file, resolve all file dependencies and change makefile if required.
+
GlyphProcessor is quite complex and makes PDFIProcessor untidy. The main reason of moving glyph processing to separate class was to avoid mess and make the code more scalable. Moreover some additional changes in function like optimizeText from drawprocessing had to be changes.
  
 
== Solution ==
 
== Solution ==
  
−
The task didn't require separate task frankly and it's a part of importing proper paragraphs, but due to agile it gives better view of project progress. Now GlyphProcessor class is located in its own files, what makes the code easier to modify and to find needed functionalities.
+
GlyphProcessor and associated class have been moved to files glyphprocessor.hxx and glyphprocessor.cxx. Moreover function optimixeText was prepared to work with ParagraphLineElement instead of ParagraphElement.

Revision as of 19:25, 21 September 2010

GlyphProcessor is quite complex and makes PDFIProcessor untidy. The main reason of moving glyph processing to separate class was to avoid mess and make the code more scalable. Moreover some additional changes in function like optimizeText from drawprocessing had to be changes.

Solution

GlyphProcessor and associated class have been moved to files glyphprocessor.hxx and glyphprocessor.cxx. Moreover function optimixeText was prepared to work with ParagraphLineElement instead of ParagraphElement.

Retrieved from "https://wiki.openoffice.org/w/index.php?title=User:Joekidd/OpenOffice.org/Internship/PDFImport/Tasks/Moving_Proper_paragraphs_GlyphProcessor&oldid=184184"
Personal tools