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

From Apache OpenOffice Wiki
Jump to: navigation, search
(Created page with '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…')
 
(Solved task)
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. It's required about 4 hours to move it to separate file, resolve all file dependencies and change makefile if required.
 +
 +
== 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.

Revision as of 16:52, 20 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. It's required about 4 hours to move it to separate file, resolve all file dependencies and change makefile if required.

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.

Personal tools