Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
gemstoneport [2017/06/03 15:10]
christian [Processing steps]
gemstoneport [2017/06/03 15:41]
christian [Decision Matrix]
Line 42: Line 42:
 </th><th> Mangler (VW) </th><th> Mangler (VW)
 </th><th> Writer (VW) </th><th> Writer (VW)
 +</th><th> Format
 </th><th> Reader (GS) </th><th> Reader (GS)
 </th><th> Interpreter (GS) </th><th> Interpreter (GS)
 </th></tr> </th></tr>
-<tr bgcolor="#ccffcc"+<tr> 
-<td> VW XML fileOut +<td> fileOut30 
-</td><td> todo +</td><td bgcolor="#ffcccc"not extensible? 
-</td><td> OK +</td><td bgcolor="#ccffcc"> OK 
-</td><td> todo +</td><td bgcolor="#ffcccc"Chunk 
-</td><td> todo+</td><td bgcolor="#ffff99"> Monticello 
 +</td><td bgcolor="#ffff99"> todo
 </td></tr> </td></tr>
-<tr bgcolor="#ccffcc"+<tr> 
-<td> VW XML fileOut +<td> XML fileOut 
-</td><td> todo +</td><td bgcolor="#ffff99"> todo 
-</td><td> OK +</td><td bgcolor="#ccffcc"> OK 
-</td><td> todo +</td><td bgcolor="#ccffcc"XML 
-</td><td> todo+</td><td bgcolor="#ffcccc"> no XML reader 
 +</td><td bgcolor="#ffff99"> todo
 </td></tr> </td></tr>
-<tr bgcolor="#ccffcc"+<tr> 
-<td> VW XML fileOut +<td> Values 
-</td><td> todo +</td><td bgcolor="#ffff99"> todo 
-</td><td> OK +</td><td bgcolor="#ccffcc"> OK 
-</td><td> todo +</td><td bgcolor="#ffff99"Values 
-</td><td> todo+</td><td bgcolor="#ccffcc"> OK 
 +</td><td bgcolor="#ffff99"> todo
 </td></tr> </td></tr>
-<tr bgcolor="#ccffcc"+<tr> 
-<td> VW XML fileOut +<td> Topaz input 
-</td><td> todo +</td><td bgcolor="#ffff99"> todo 
-</td><td> OK +</td><td bgcolor="#ffff99"> OK? 
-</td><td> todo +</td><td bgcolor="#ccffcc"Topaz 
-</td><td> todo+</td><td bgcolor="#ccffcc"OK 
 +</td><td bgcolor="#ccffcc"> OK
 </td></tr> </td></tr>
 <tr></tbody></table> <tr></tbody></table>
 </html> </html>
 +
 +The chunk format used by Squeak and Pharo does not support extensions needed for Gemstone (pundles, treat namespaces, ...). It also depends on Monticello, which I don't understand. This is not further considered.
 +
 +XML fileOut would be nice if there would be an XML reader for Gemstone. Then, the fileOut could be extended with special tags for renamings and replacings etc.. On Gemstone, the XML structures need to be interpreted to setup namespaces and compile the source appropriately.
 +
 +The Values approach is the same as the XML fileOut except that the reader is there (once I ported the Values to Gemstone by hand). The drawback is that it is yet another format for code interchange... (although a good one, I think).
 +
 +Currently, I tend to favor the last solution where all the Gemstone code for input is generated solely from VW. There is a goodie in the public store (GemKitForStore (Copyright from OOCL)) which may have a Topaz input writer...
  
 ===== Processing steps ===== ===== Processing steps =====
  • gemstoneport.txt
  • Last modified: 2022/04/03 20:07
  • by christian