pdf:porting
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
pdf:porting [2015/03/30 17:13] – created christian | pdf:porting [2015/04/02 16:34] (current) – christian | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Porting PDF4Smalltalk to other Smalltalk dialects ====== | ||
+ | |||
+ | |||
The main parts to port is the runtime code (see [[PackageStructure]]). | The main parts to port is the runtime code (see [[PackageStructure]]). | ||
Line 11: | Line 14: | ||
Generally, I am quite opposed to adding prefixes to every class (it hurts the eyes, hinders understanding, | Generally, I am quite opposed to adding prefixes to every class (it hurts the eyes, hinders understanding, | ||
- | * Boolean | + | |
- | + | * Number | |
- | * Number | + | * Integer |
- | + | * String | |
- | * Integer | + | * Date |
- | + | * Dictionary | |
- | * String | + | * Rectangle |
- | + | ||
- | * Date | + | |
- | + | ||
- | * Dictionary | + | |
- | + | ||
- | * Rectangle | + | |
maybe also: | maybe also: | ||
- | * Stream | + | |
- | + | * Font (there are 2: Fonts.Font and PDF.Font) | |
- | * Font (there are 2: Fonts.Font and PDF.Font) | + | * Document |
- | + | * File | |
- | * Document | + | * Link |
- | + | * Function | |
- | * File | + | * Name |
- | + | * Operator | |
- | * Link | + | * Type |
- | + | * Version | |
- | * Function | + | |
- | + | ||
- | * Name | + | |
- | + | ||
- | * Operator | + | |
- | + | ||
- | * Type | + | |
- | + | ||
- | * Version | + | |
I did Array... | I did Array... | ||
Line 60: | Line 48: | ||
For the foreseeable future, I will stick with VW and the VW version will be the source of my development. If ports wish to stay close to that (not necessary, since its free and anybody can do their own thing with it), it may be better to invest in a file-out goodie which could write the source for the destination dialect from VW. All adaptations could be included there: | For the foreseeable future, I will stick with VW and the VW version will be the source of my development. If ports wish to stay close to that (not necessary, since its free and anybody can do their own thing with it), it may be better to invest in a file-out goodie which could write the source for the destination dialect from VW. All adaptations could be included there: | ||
- | * replace namespaces with prefixes (run in VW, all references can be reliably found) | + | |
- | + | * replace packages/ | |
- | * replace packages/ | + | * replace VW syntax specialties - even complex rewrites would be doable with the RBRewrite tool! |
- | + | * what else? (other issues will come up, but I am sure that they can be solved in this approach). | |
- | * replace VW syntax specialties - even complex rewrites would be doable with the RBRewrite tool! | + | |
- | + | ||
- | * what else? (other issues will come up, but I am sure that they can be solved in this approach). | + | |
There would be special " | There would be special " | ||
Line 88: | Line 73: | ||
Porting PDF and Fonts is not a project for an afternoon. It would require some effort. | Porting PDF and Fonts is not a project for an afternoon. It would require some effort. | ||
- | My opinions above may be all wrong. I have not ported any sizable portions of code to other dialects yet. So, I you think that I see it wrong, please educate me - if you have good arguments, I may change my mind :-) | + | My opinions above may be all wrong. I have not ported any sizable portions of code to other dialects yet. So, if you think that I see it wrong, please educate me - if you have good arguments, I may change my mind :-) |
What do you think? | What do you think? |
/var/www/virtual/code4hl/html/dokuwiki/data/attic/pdf/porting.1427728438.txt.gz · Last modified: 2015/03/30 17:13 by christian