World: r3wp

these are the TT equivalents of the standard PS fonts

OK, I'll try that, thanks

my code is ugly, but it's not a beauty contest ...

Just got to get it working :)

it converts PS to DRAW? or does it create DRAW and PS from the same 
dialect?

latter...

Much better now.

But I never got round to finishing the conversion to ps yet ...

ie. for the text flow as I need to read up a bit more on postscript 
justification routines etc.

So, I can use it to generate graphs, and ordinary text for printing 
.. but fancy flowing text needs more work.

Henrik, I can't see why your preview takes 2 seconds to render.

What PC are you using?

celeron 700 with a 1 MB graphicscard

works ok on my test machine, but on the target machine, it's too 
slow...

yes, that is a slow PC.

I find View runs quite slowly on anything less than 1Ghz

are you drawing your barcode and translating it to final location?

huh, really, does it? I found View ok on Pentium 133MHz ;-)

you're probably not running large applications then.

well, old View, as new one does not support W95 anymore ..... but 
it looked ok for small things :-)

my encapped apps won't run on those slow PCs.

well, of course ... but then what is large application in View then? 
RebGui, tonnes of tabs?

app that runs about 20Mb in ram.

isn't the problem of tab style that all tabs are in memory actually?

yeah, it can take a while to initialize

My EMR runs about 60Mb in ram.

ok then .... never tried complex app. Hopefully, however, R3 is being 
said as more resources savy in View area, so ....

the slowness problem with view could be connected to that the event 
system has no throttling. I think I've mentioned that a couple of 
times :-)

I'm sure dos runs okay on 486 ...

1HGz PCs are not problem nowadays, really old machines, the thing 
is worse once we move to embedded machines/PDAs (400MHz, 64MB RAM) 
one day ....

which are like old dos machines really

Henrik - try eat events script or what was the name ... done by Romano 
or/and Gabriele ....

pekr, made my own system so problem temporarily solved, but it's 
still a problem for those with a fast sampling mouse

I tried running view on my old A4000/040 25 Mhz once. it was utterly 
useless.

graham, the barcode is drawn as an image and then pasted into the 
preview

Henrik - View was several times optimised. E.g. all-over events it 
used initially, and later on, Holger did some other improvements. 
But yes, Graham may be right, that for complex apps it is slow. OTOH 
we could see things really optimised by gurus. E.g. when I last looked 
at EMR, it was based upon many tabs. If all tabs are in fact in memory, 
then it could be a resource hog.

I doubt that windows 98/95 has the graphics heap to support it

graham, how long does it take for you to print the first page of 
the 20000 leagues... test page in your demo?

oh... was a postscript error.

>> do http://www.compkarori.com/reb/psd2draw5.r
** PostScript error at: [
    flow-translate 50x0
    flowbox 0x140 250x720
    grestore
    gsave
    flow-translate 310x0
    flowbox
]

the error comes when I try to print

geomol, can you post the links to your postscript docs again?

http://home.tiscali.dk/john.niclasen/postscript/postscript.r
http://home.tiscali.dk/john.niclasen/postscript/test.txt
http://home.tiscali.dk/john.niclasen/postscript/test.png

I didn't make documentation.

Henrik, I mentioned above that I ran out of time to finish the translation 
to postscript

I need to read up on postscript justification routines

graham, sorry I missed it

geomol, thanks. maybe it's worth mentioning on rebol weekly?

sure, I'll make a post in rebolweek group.

Some old news.

REBOL PostScript dialect: http://home.tiscali.dk/john.niclasen/postscript/postscript.r

Example of use:http://home.tiscali.dk/john.niclasen/postscript/test.txt

Result should look like this:http://home.tiscali.dk/john.niclasen/postscript/test.png

The dialect is useful for simple postscript output, even if I think, 
it has some design flaws. It require too many blocks, I think. I 
haven't had time to evolve the dialect further, but anyone is welcome 
to pick it up. There's no documentation, so you have to look in the 
source to figure out the keywords.