- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Render images - Porting from Cincom VW to Pharo

by Sven Van Caekenberghe

On 12 Nov 2012, at 14:54, Emilia <maemco4(a)gmail.com> wrote: > Hello! I'm porting code from Cincom Smalltalk to Pharo. It's a web application so I've got several WAComponent instances and one component which inherits from WAFileLibrary that renders images. > In the original code ( the one that runned in VW) i had the following instance method in the component that inherits from WAFileLibrary: > > logoJpg > ^ByteArray asPackagedString: '?=#?8@@PR$YIQ @A@ D@X@A @@C?8P))QW!)Y @@RT$*@@ @@@@G@AHA@0@......etc etc' > > But now when i run it in Pharo the debbugger doesn't recognize #asPackagedString: message. > > Does anyone know which method should I use in order to render that image? > > Thanks in advance! > Mercy beaucoup! > > Emilia You could try to port ByteArray class>.#asPackagedString: from (VW?) to Pharo Smalltalk. It can't be that hard - is there a spec for this format ? -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Nov. 12, 2012

Re: [Pharo-project] Render images - Porting from Cincom VW to Pharo

by Henrik Sperre Johansen

On 12.11.2012 14:54, Emilia wrote: > Hello! I'm porting code from Cincom Smalltalk to Pharo. It's a web > application so I've got several WAComponent instances and one > component which inherits from WAFileLibrary that renders images. > In the original code ( the one that runned in VW) i had the following > instance method in the component that inherits from WAFileLibrary: > > logoJpg > ^ByteArray asPackagedString: '?=#?8@@PR$YIQ @A@ D@X@A > @@C?8P))QW!)Y @@RT$*@@ @@@@G@AHA@0@......etc etc' > > But now when i run it in Pharo the debbugger doesn't recognize > #asPackagedString: message. > > Does anyone know which method should I use in order to render that image? > > Thanks in advance! > Mercy beaucoup! > > Emilia > fromPackedString: uses a (proprietary?) format to store a bytearray in source code, there are no method for reading the string as is in Pharo directly. The equivalent in Pharo would probably be something like: ^Base64MimeConverter mimeDecodeToBytes: 'myImageInAStringThatsSafeToStoreInSource' readStream contents (See ThemeIcons use of xxxContents methods for an example) To convert, you'd have to serialize your images to disk first (leaving you with .jpg files), then read them in and convert (f.ex. using a Base64MimeConverter) to an appropriate format for storing image bytes as methods in Pharo. Cheers, Henry

Nov. 12, 2012

[Pharo-project] Render images - Porting from Cincom VW to Pharo

by Torsten Bergmann

>It's a web application so I've got several WAComponent instances The #asPackagedString: is VW specific and not available in Pharo. In Seaside on Pharo the resources like pictures are stored in methods returning a ByteArray with the bytes only. There is an easy way: just save the original resources from VW (for instance the JPG) in a folder and then reimport them again into the Pharo based Seaside image. Example: So you are using Seaside and have a subclass of WAFileLibrary for your own resources (for instance MyFileLibrary) Just open http://localhost:8080/config/files and select the Library (here "MyFileLibrary") and click on "Configure". Now you can upload the JPG again using the web interface and Seaside is (re)generating the method on class MyFileLibrary which should look like logoJpg ^#(1 2 3 ...) asByteArray containing the bytes that represent the JPG. If you have more than one you should note that the superclass of WAFileLibrary which is WAAbstractFileLibrary in latest Seaside provide some utility methods to automate importing of resources. Check for #addAllFilesIn: and #addFileAt: on the class side. Bye T.

Nov. 12, 2012

[Pharo-project] Unicode Fonts

by Sven Van Caekenberghe

I was playing with the following: http://en.wikipedia.org/wiki/Chess_symbols_in_Unicode '/tmp/chess.txt' asFileReference writeStreamDo: [ :stream | (16r2654 to: 16r265F) do: [ :each | stream nextPut: each asCharacter ] separatedBy: [ stream space ]. stream crlf ]. $ cat /tmp/chess.txt â â â â â â â â â â â â (this shows for me, in my terminal/mail, YMMV ;-) String streamContents: [ :stream | (16r2654 to: 16r265F) do: [ :each | stream nextPut: each asCharacter ] separatedBy: [ stream space ]. stream crlf ]. Is there a way to make this work, a font selection that show these Unicode characters in Pharo ? That would be cool. I tried using Freetype font Monaco, the same as my terminal where the right characters show, but that didn't help. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Nov. 12, 2012

Re: [Pharo-project] [ANN] Pharo Online Help 1.0

by Camillo Bruni

On 2012-11-12, at 15:56, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > You won I put a filter markdown to thrash on my mail sadly. ?? I do not parse > On Nov 12, 2012, at 3:11 PM, Camillo Bruni wrote: > >>>> It depends at which level. >>>> Can you tag on word in markdown to have bold, italic, index? >> >> stef, I already explained you that at least 4 times! Plus I gave you the solutions, >> the only thing I don't have is the time to complete the Markdown parser! >> >>>> If I would not have written 350 pages of seaside book with pier it would be a different story but >>>> so far pier syntax is good for doing everything: html, latex, even markdown. >>> >>> In Markdown, it is *italic* or _italic_ and **bold** and __bold__. >>> >>> Now for index entries, I don't know exactly - making an automatic index is a special post process function anyway. >>> I think you could do something like [ReadStream][index-entry]s are objects that you can read bytes or characters from. >>> >>> Making a book from several independent source files is quite a job that requires custom programming. It would be very cool if we could do all that in Smalltalk, using a good Markdown parser and a cool object representation. >>> >>> I have nothing against Pier, but it is something that only exists in our niche world, not in the larger world out there. >> >> my words! >> >> So we already had a Markdown / HelpSystem crossover for NativeBoost / ASMJit where we injected >> custom URLs to add method and class links, that worked pretty well. So I assume it will be >> not that much work on top to get section links ready. >> >> Something like book://section/subsection is very easy to do, a bit verbose maybe but very >> consistent. >> >> >> so, please support: >> https://github.com/dh83/PPMarkdown >> http://ss3.gemstone.com/ss/petitmarkdown.html/ > >

Nov. 12, 2012

Re: [Pharo-project] [ANN] Pharo Online Help 1.0

by StÃ©phane Ducasse

You won I put a filter markdown to thrash on my mail sadly. On Nov 12, 2012, at 3:11 PM, Camillo Bruni wrote: >>> It depends at which level. >>> Can you tag on word in markdown to have bold, italic, index? > > stef, I already explained you that at least 4 times! Plus I gave you the solutions, > the only thing I don't have is the time to complete the Markdown parser! > >>> If I would not have written 350 pages of seaside book with pier it would be a different story but >>> so far pier syntax is good for doing everything: html, latex, even markdown. >> >> In Markdown, it is *italic* or _italic_ and **bold** and __bold__. >> >> Now for index entries, I don't know exactly - making an automatic index is a special post process function anyway. >> I think you could do something like [ReadStream][index-entry]s are objects that you can read bytes or characters from. >> >> Making a book from several independent source files is quite a job that requires custom programming. It would be very cool if we could do all that in Smalltalk, using a good Markdown parser and a cool object representation. >> >> I have nothing against Pier, but it is something that only exists in our niche world, not in the larger world out there. > > my words! > > So we already had a Markdown / HelpSystem crossover for NativeBoost / ASMJit where we injected > custom URLs to add method and class links, that worked pretty well. So I assume it will be > not that much work on top to get section links ready. > > Something like book://section/subsection is very easy to do, a bit verbose maybe but very > consistent. > > > so, please support: > https://github.com/dh83/PPMarkdown > http://ss3.gemstone.com/ss/petitmarkdown.html/

Nov. 12, 2012

Re: [Pharo-project] [ANN] Pharo Online Help 1.0

by Camillo Bruni

>> It depends at which level. >> Can you tag on word in markdown to have bold, italic, index? stef, I already explained you that at least 4 times! Plus I gave you the solutions, the only thing I don't have is the time to complete the Markdown parser! >> If I would not have written 350 pages of seaside book with pier it would be a different story but >> so far pier syntax is good for doing everything: html, latex, even markdown. > > In Markdown, it is *italic* or _italic_ and **bold** and __bold__. > > Now for index entries, I don't know exactly - making an automatic index is a special post process function anyway. > I think you could do something like [ReadStream][index-entry]s are objects that you can read bytes or characters from. > > Making a book from several independent source files is quite a job that requires custom programming. It would be very cool if we could do all that in Smalltalk, using a good Markdown parser and a cool object representation. > > I have nothing against Pier, but it is something that only exists in our niche world, not in the larger world out there. my words! So we already had a Markdown / HelpSystem crossover for NativeBoost / ASMJit where we injected custom URLs to add method and class links, that worked pretty well. So I assume it will be not that much work on top to get section links ready. Something like book://section/subsection is very easy to do, a bit verbose maybe but very consistent. so, please support: https://github.com/dh83/PPMarkdown http://ss3.gemstone.com/ss/petitmarkdown.html/

Nov. 12, 2012

Re: [Pharo-project] [ANN] Pharo Online Help 1.0

by Sven Van Caekenberghe

On 11 Nov 2012, at 17:26, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > On Nov 10, 2012, at 9:41 PM, Sven Van Caekenberghe wrote: > >> On 10 Nov 2012, at 21:33, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>>> 3. Lets discuss how we want to describe the content "in-image" >>>> for "serving on the web". Maybe with a "Markup to HTML translator" >>>> - or a "WikiStyle to HTML" like help >>> >>> I want to use the pier syntax because I know that I can generate the correct latex >>> with it for the books, and of course any kind of html and other formats. >> >> I vote for Markdown, it is more like a defacto standard. > > I prefer pier since I can convert all the book macros (and I cannot do that in markdown). > I'm spending so much time writing that at least I want the result to look more than a bad documentation. > >> And you can convert Markdown into anything, there exit tons of tools for it. >> >> Remember that I sent you my Zinc & Zodiac docs converted to Latex ? Were they no good ? > > It depends at which level. > Can you tag on word in markdown to have bold, italic, index? > If I would not have written 350 pages of seaside book with pier it would be a different story but > so far pier syntax is good for doing everything: html, latex, even markdown. In Markdown, it is *italic* or _italic_ and **bold** and __bold__. Now for index entries, I don't know exactly - making an automatic index is a special post process function anyway. I think you could do something like [ReadStream][index-entry]s are objects that you can read bytes or characters from. Making a book from several independent source files is quite a job that requires custom programming. It would be very cool if we could do all that in Smalltalk, using a good Markdown parser and a cool object representation. I have nothing against Pier, but it is something that only exists in our niche world, not in the larger world out there. Sven

Nov. 12, 2012

[Pharo-project] Render images - Porting from Cincom VW to Pharo

by Emilia

Hello! I'm porting code from Cincom Smalltalk to Pharo. It's a web application so I've got several WAComponent instances and one component which inherits from WAFileLibrary that renders images. In the original code ( the one that runned in VW) i had the following instance method in the component that inherits from WAFileLibrary: logoJpg ^ByteArray asPackagedString: '?=#?8@@PR$YIQ @A@ D@X@A @@C?8P))QW!)Y @@RT$*@@ @@@@G@AHA@0@......etc etc' But now when i run it in Pharo the debbugger doesn't recognize #asPackagedString: message. Does anyone know which method should I use in order to render that image? Thanks in advance! Mercy beaucoup! Emilia

Nov. 12, 2012

Re: [Pharo-project] selectors vs. localSelectors in condenseChanges

by Marcus Denker

On Nov 12, 2012, at 9:45 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > in the condenseChanges method the message moveChangesTo: is heavily > called. And this method exports changes for all selectors of the > behavior. But I suppose that we want to process only local selectors > here. Can some traits guy confirm that we should replace call of the > message #selectors with #localSelectors here? Yes, I think so. Marcus -- Marcus Denker -- http://marcusdenker.de

Nov. 12, 2012