====== The Gemstone port ====== The fileOuts are on [[https://github.com/PortingPDFtalk/PDFtalk-for-Gemstone|GitHub]]. The origin of the code is VisualWorks and the target is Gemstone. ===== Log ===== Sunday, the 3rd of April The [[https://github.com/PortingPDFtalk/PDFtalk-for-Gemstone/releases/tag/2.5.3.1|latest version (2.5.3.1)]] loads without errors. Big thanks to Richard Sargent, who discovered all the defects and fixed them! Tests (on Gemstone 3.5.x and 3.6.x): PDFtalk: 499 run, 499 pass, 0 fail, 0 errors Report4PDF: 156 run, 11 pass, 145 fail, 0 errors ---- ===== older... ===== There are a number of possible approaches: * fileOut VW XML format * no XML reader available? * nicely extensible with custom tags * todo * extend in VW * write an XML loader in Gemstone * interpret in GS * fileOut30 ST80 chunk format * may load with Monticello? * looses namespace and pundle infos * todo * mangle in VW * load with Monticello * fileOut GS Topaz input format * need to write a writer for this format * todo * writer in VW * fileout Values * add transfer values * nicely extensible * todo * define transfer values in VW and GS (same) * interpret in GS Not considered * Using GemBuilder for Gemstone (GBS) * easy way to move code to Gemstone * but, since GBS is commercial, porting and maintaining should not depend on this * use it for porting Values? ===== Decision Matrix =====
Approach | Mangler (VW) | Writer (VW) | Format | Reader (GS) | Interpreter (GS) |
---|---|---|---|---|---|
fileOut30 | not extensible? | OK | Chunk | Monticello | todo |
XML fileOut | todo | OK | XML | XMLParser | todo |
Values | todo | OK | Values | OK | todo |
Topaz input | todo | OK? | Topaz | OK | OK |