Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

Please read! Help needed.

 [1/5] from: agem:crosswinds at: 18-Aug-2001 22:17


RE: [REBOL] Please read! Help needed. wow! grat work! i like "font Times-Roman 4.23 justify with left margin 0" Here comes a dialect to show what dialects are for :) resulting page looks pretty cool. now something to split page automatic (or i missed it?), short thinking i suggest: how to format and calculate all boxes and give them back to the user in a block with sizes, positions and content, then let user script how to pagebreak? there could be some naming for boxes so user can check what to take to the next page? together with a pre-defined breaker, of course. also some naming for styles to specify macros, that could quick match to make-doc-labels? font-changing is somewhat large. then for encoding, i had a weird idea: somewhere encoding ä "" ü "" in the text. instead of giving an encoding-name and juggling with the editor to use it, we could parse this easy and decide which codes are used for special chars. + it could be done by hand, mark whatever is in the ä and replace it everywhere with your local char. do you think this could be usable? -Volker [g--santilli--tiscalinet--it] wrote:

 [2/5] from: g:santilli:tiscalinet:it at: 19-Aug-2001 13:10


Hello [agem--crosswinds--net]! On 18-Ago-01, you wrote: a> i like "font Times-Roman 4.23 justify with left margin 0" a> Here comes a dialect to show what dialects are for :) :-) a> now something to split page automatic (or i missed it?), With the current typesetter it would not be difficult; it just needs a check in EMIT-LINE to see if the current textbox is full and a way to define in the dialect a chain of textboxes and a single text that goes all over them in any page. But I'd like to make it smarter than this... e.g. the user should be able to say things like "this paragraph should not be rendered at the bottom of a page" or "this paragraph should not be broken" etc. a> how to format and calculate all boxes and give them back to a> the user in a block with sizes, positions and content, then a> let user script how to pagebreak? there could be some naming a> for boxes so user can check what to take to the next page? a> together with a pre-defined breaker, of course. I have been thinking about that. Maybe conditional rendering? a> also some naming for styles to specify macros, a> that could quick match to make-doc-labels? You can see in the doc I used compose to do macros. I have been thinking of a way to do it in the dialect, but it's not easy to make it general (so that you can put them anywhere). Maybe a preprocessor that works like compose? Or we should drop the idea of having them anywhere. :) a> font-changing is somewhat large. Yup. Maybe something like: r: font Times-Roman 4.23 i: font Times-Italic 4.23 r {roman } i {italic} r { roman again} ? a> then for encoding, i had a weird idea: [...] Nice! But then I think I should support other encodings than WinANSI (to make Mac users happy, it seems like everyone else uses WinANSI --- am I wrong?) Regards, Gabriele. -- Gabriele Santilli <[giesse--writeme--com]> - Amigan - REBOL programmer Amiga Group Italia sez. L'Aquila -- http://www.amyresource.it/AGI/

 [3/5] from: brett:codeconscious at: 20-Aug-2001 18:11


Hi Gabriele, Great work on pdf-maker!
> With the current typesetter it would not be difficult; it just > needs a check in EMIT-LINE to see if the current textbox is full
<<quoted lines omitted: 3>>
> things like "this paragraph should not be rendered at the bottom > of a page" or "this paragraph should not be broken" etc.
All of those would be impressive features. The chain of textboxes reminds me of desktop publishing programs.
> a> also some naming for styles to specify macros, > a> that could quick match to make-doc-labels?
<<quoted lines omitted: 3>>
> preprocessor that works like compose? Or we should drop the idea > of having them anywhere. :)
The Vid style of evaluating arguments, parens and of the do keyword has certainly seemed flexible for me - though I can't say whether this is a must have for pdf. Brett.

 [4/5] from: g:santilli:tiscalinet:it at: 20-Aug-2001 19:31


Hello Brett! On 20-Ago-01, you wrote: BH> Great work on pdf-maker! Thanks. I'm happy to see it is appreciated. :) BH> All of those would be impressive features. The chain of BH> textboxes reminds me of desktop publishing programs. Well, since before even knowing REBOL, I had dreamed about writing a better DTP software ; it should have allowed TeX-style typesetting for text, but the usual WYSIWYG approach to graphic layout. I think that dream still influences me. :) BH> The Vid style of evaluating arguments, parens and of the do BH> keyword has certainly seemed flexible for me - though I can't BH> say whether this is a must have for pdf. There are some cons in doing it the VID way that make me reluctant in doing so. (Have you seen the source of LAYOUT etc.?) Anyway, the more I think on it the more I see the VID way as the best compromise. I'll have to think about this some more time. Regards, Gabriele. -- Gabriele Santilli <[giesse--writeme--com]> - Amigan - REBOL programmer Amiga Group Italia sez. L'Aquila -- http://www.amyresource.it/AGI/

 [5/5] from: g:santilli:tiscalinet:it at: 18-Aug-2001 17:12


Please read! Help needed. Hello guys! I've just uploaded the latest version of pdf-maker.r. I wanted to wait until I finished the docs, but since that is taking some time, I didn't want you to wait :) and decided to release it. You will find it on: Desktop/Rebol.com/Sites/Rebol.it or Desktop/Rebol.com/Sites/R-Forces/Rebol.it Now I'd like to have some help from you all. I want you to test pdf-maker.r and give comments. I want you to correct my english in the docs, tell me is something is not explained well, etc. Can you help? ;-) (For Volker: I tried sending you an email but it bounced back...) Thanks in advance, Gabriele.

Notes
  • Quoted lines have been omitted from some messages.
    View the message alone to see the lines that have been omitted