January 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] STON encoding of slashes

by Sven Van Caekenberghe

Hi Christophe, > On 18 Jan 2017, at 09:30, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > > Hi, > > I just noticed that STON encoding of forward slashes changed. > > STON toString: 'git@github.com:foo/bar.gitâ => ''git@github.com:foo\/bar.gitâ' > > It used to be ''git@github.com:foo/bar.gitââ. > > Is it on purpose? > > Thanks, > Christophe Yes, it was 'changed' in Name: STON-Core-SvenVanCaekenberghe.78 Author: SvenVanCaekenberghe Time: 20 November 2016, 7:48:23.799323 pm UUID: ee198da8-80e8-4944-ba9b-dffae331c57c Ancestors: STON-Core-SvenVanCaekenberghe.77 with as comment Fix the encoding of forward slash ($/). This was already in the (external) documentation. In other words, it was an implementation error (omission). Note that JSON also has this escape. Now, in retrospect, the question is 'should all possible escapes be done when writing ?', especially for $/ this is a maybe a bit too much, the same for tab. For the other named escapes, the case is clearer: they are either necessary $" and $\ or they make things clearer and less error prone, $b, $n, $f and $r. There is already the #asciiOnly option that decides whether non-ASCII Unicode characters are encoded with \uHHHH or not. I guess you are human editing STON config files, right ? Sven

Jan. 18, 2017

STON encoding of slashes

by Christophe Demarey

Hi, I just noticed that STON encoding of forward slashes changed. STON toString: 'git@github.com:foo/bar.gitâ => ''git@github.com:foo\/bar.gitâ' It used to be ''git@github.com:foo/bar.gitââ. Is it on purpose? Thanks, Christophe

Jan. 18, 2017

Re: [Pharo-users] Create png from pdf

by Sabine Manaa

Hi Henrik, Hi Olivier, thank you. I assume I have to stay at my old solution for the first time. Regards Sabine 2017-01-16 14:57 GMT+01:00 Olivier Auverlot [via Smalltalk] < ml-node+s1294792n4929731h56(a)n4.nabble.com>: > Hi Sabine, > > Converting a PDF into a PNG with Pharo is not an easy task because you > must write a PDF reader. > > With Artefact, the other approach is to draw on a form instead of > generating the PDF instructions. For geometrics items, It's relatively easy > but the respect of paper formats and the management of fonts could be very > complex. > > The difficulty is to have the same result between the PDF document and the > simulated document written in a PNG file. > > Best regards > Olivier > > 2017-01-16 12:05 GMT+01:00 Henrik Nergaard <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=4929731&i=0>>: > >> See Form protocol (*Graphics-files), #writePNGFileNamed: , and >> PNGReadWriter. >> ---------------------------------------------------- >> | canvas | >> canvas := FormCanvas extent: World extent. >> World fullDrawOn: canvas. >> canvas form writePNGFileNamed: 'imageOfWorld.png' >> ---------------------------------------------------- >> >> There are also some methods in morph (#exportAs:using: #exportAsPng), but >> these will ask for the filename via the file dialog. >> ---------------------------------------------------------------- >> World exportAsPng >> ---------------------------------------------------------------- >> >> >> Best regards, >> Henrik >> >> -----Opprinnelig melding----- >> Fra: Pharo-users [mailto:[hidden email] >> <http:///user/SendEmail.jtp?type=node&node=4929731&i=1>] PÃ¥ vegne av >> Sabine Manaa >> Sendt: 16 January 2017 10:26 >> Til: [hidden email] >> <http:///user/SendEmail.jtp?type=node&node=4929731&i=2> >> Emne: [Pharo-users] Create png from pdf >> >> Hi, >> >> currently, I create pdfs with Artefact and it works fine. >> For displaying previews of the pdf reports, I use Apache PDFBox to >> generate pngs from the pdfs. >> This works, too. >> >> But I would prefer to generate the pngs directly from pharo and do not >> call external libraries. >> >> Stephane told me that "there is a form in a morph and it can be converted >> in png". >> >> Can anyone give me a small entry point or has done similar and provide >> some code snippet? >> >> Regards >> Sabine >> >> >> >> >> >> -- >> View this message in context: http://forum.world.st/Create-p >> ng-from-pdf-tp4929722.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> >> > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://forum.world.st/Create-png-from-pdf-tp4929722p4929731.html > To start a new topic under Pharo Smalltalk Users, email > ml-node+s1294792n1310670h65(a)n4.nabble.com > To unsubscribe from Pharo Smalltalk Users, click here > <http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML > <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > -- View this message in context: http://forum.world.st/Create-png-from-pdf-tp4929722p4929757.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Jan. 17, 2017

Just a comment on Pharo 5.0..

by sergio ruiz

Of all the great things i have seen added to pharo over the past years, the absolute coolest i have yet seen is the addition of a hotkey sequence for âSave Imageâ.. Thank you guys so much! ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com http://www.ThoseOptimizeGuys.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Jan. 16, 2017

Re: [Pharo-users] super super

by Hilaire

Thanks Henrik Le 15/01/2017 Ã 22:33, Henrik Nergaard a Ã©crit : > menu perform: #isMorph withArguments: #() inSuperclass: ProtoObject. "Error #isMorph not implemented" -- Dr. Geo http://drgeo.eu

Jan. 16, 2017

Re: [Pharo-users] About Git

by Offray Vladimir Luna CÃ¡rdenas

On 16/01/17 07:34, Pierce Ng wrote: > On Sun, Jan 15, 2017 at 08:09:28AM -0500, Offray Vladimir Luna CÃ¡rdenas wrote: >> That's the core idea of fossil. "GitHub alike in a box" DVCS with >> tickets, wiki, web server/GUI in 2 MB. > Hi Offray, > > Do you use Fossil with Pharo source code? Just store mcz files as blobs? > > Pierce > > Hi Pierce, I don't use Fossil with Pharo source code. I use fossil for all my DVCS needs, including storing Grafoscopio notebooks (which are plain text and diff friendly STON files) and StHub for all my Pharo code needs. What I like about StHub and Fossil is how they become unobtrusive in my work flow, that I almost don't think in them. Hopefully, Iceberg will bring a DVCS neutral way of keeping the same flow. Cheers, Offray

Jan. 16, 2017

Re: [Pharo-users] About Git

by Dimitris Chloupis

Several things I disagree with [1] 1) "Living in the image" , I think this is a usual smalltalker misconception in that just because you do not see something it means it does not exist. Obviously thats not the case with the Pharo image. The Pharo image is indeed a binary file and self contained enviroment but not user friendly by itself because the Pharo image only stores bytecode, which is hard to read. The actual source code you see inside the image which what we do 99% of the time is coming not from the image but a file called "sources" and yes its a text file and a typical smalltalk source code file. Of course this does not stop there and we have also the changes files, which is also a text file, for recovering lost changes. Even the more modern Epicea , heavily relies on text files and of course then you have other tools like GTPlayground who store the code snippets also as source code files and of course Monticello which uses mcz files which are nothing more than zip files containing standard smalltalk source filex, again text files. And the story does not end there that we live outside the image far more we are willing to admit , there is of course the VM which the image cannot access , hence why we want to move GUI support completely to the image. But also the foundation of the power of Pharo which is the C libraries it has to rely on to do all of the basic stuff, open, close and create files, read , play sounds, display graphic formats , access databases and a ton more are all outside the image and the image is able to communicate with them either via plugins or the UFFI. 2) I would not call a zip file containing text files a binary based VCS.Thats what a mcz is. Because if we do then so is Git since git as well is Zipping the files because like Monticello , it recognises that is a waste of space to upload uncompressed files. We know how valuable online space is cause pretty much anything online nowdays implements its own type of compression. By the way binary files storing byte code is not anything special , its actually the standard , Java has them in the form of .class file and python has them in .pyc where the first time you run code its compiled and stored to this files and then its those files that are executed , source code itself is never executed. It may have been special in the 70s and 80s but definitely not since 90s. What makes the image special however is the storing of the live state and live execution of code.... but even that is not special because modern applications always utilise a form of storing live data and live execution for means of convenience, but we as Pharo offer this outside the box. So yes the pharo image is special but not as special. Actually the real irony here is that the MCZ is image unfriendly because not only it contains text files but unlike Git cannot version control binary files, you can version control a Pharo image with Git but you cannot do it with Pharo VCS. So Git is more Pharo friendly than Pharo itself at least for that purpose. I always found it strange that monticello does not support version control for binary files , especially if you take into consideration how much value we put in the live state and live context of execution. Also Git has LFS which deals with large binary files and solve the problem of accumulation of wasted space via the git commits. Other than that, as always excellent talk, very easy to understand.... and you do not look like grandpa to me :D On Sun, Jan 15, 2017 at 10:47 PM Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > I gave a talk at Smalltalks 2016 entitled: "Dangerous Liaisons: > Smalltalk, files, and git"[1] and this thread is a perfect example the > dangers I was thinking about:). > > For "history buffs", here's a link for my talk at STIC 2012 entitled > "Practical Git for Smalltalk"[2]. > > Dale > > [1] http://fast.org.ar/talks/dangerous-liaisons-smalltalk-files-and-git > > [2] https://www.youtube.com/watch?v=ZIkoBQphtyM > > >

Jan. 16, 2017

Re: [Pharo-users] Big List of Naughty Strings

by Sven Van Caekenberghe

> On 16 Jan 2017, at 14:39, Ben Coman <btc(a)openInWorld.com> wrote: > > Obligatory comic - Bobby Tables, Exploits of a Mum > https://xkcd.com/327/ Always hilarious ! > cheers -ben > > On Mon, Jan 16, 2017 at 6:19 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> This might be interesting to some people for testing purposes. You all heard stories how certain input caused certain systems to crash. Here is someone who collected lots of these strings. >> >> Big List of Naughty Strings >> >> https://github.com/minimaxir/big-list-of-naughty-strings >> >> Luckily, Pharo can at least read them all in, without problems, as far as I can see. >> >> 'https://raw.githubusercontent.com/minimaxir/big-list-of-naughty-strings/mas…' asUrl retrieveContents lines. >> >> Sven >> >> PS: You won't see all the weird/exotic Unicode characters (choosing a different font like Arial Unicode MS shows a lot more). >> >> >

Jan. 16, 2017

Re: [Pharo-users] Create png from pdf

by olivier auverlot

Hi Sabine, Converting a PDF into a PNG with Pharo is not an easy task because you must write a PDF reader. With Artefact, the other approach is to draw on a form instead of generating the PDF instructions. For geometrics items, It's relatively easy but the respect of paper formats and the management of fonts could be very complex. The difficulty is to have the same result between the PDF document and the simulated document written in a PNG file. Best regards Olivier 2017-01-16 12:05 GMT+01:00 Henrik Nergaard <draagren(a)outlook.com>: > See Form protocol (*Graphics-files), #writePNGFileNamed: , and > PNGReadWriter. > ---------------------------------------------------- > | canvas | > canvas := FormCanvas extent: World extent. > World fullDrawOn: canvas. > canvas form writePNGFileNamed: 'imageOfWorld.png' > ---------------------------------------------------- > > There are also some methods in morph (#exportAs:using: #exportAsPng), but > these will ask for the filename via the file dialog. > ---------------------------------------------------------------- > World exportAsPng > ---------------------------------------------------------------- > > > Best regards, > Henrik > > -----Opprinnelig melding----- > Fra: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] PÃ¥ vegne av > Sabine Manaa > Sendt: 16 January 2017 10:26 > Til: pharo-users(a)lists.pharo.org > Emne: [Pharo-users] Create png from pdf > > Hi, > > currently, I create pdfs with Artefact and it works fine. > For displaying previews of the pdf reports, I use Apache PDFBox to > generate pngs from the pdfs. > This works, too. > > But I would prefer to generate the pngs directly from pharo and do not > call external libraries. > > Stephane told me that "there is a form in a morph and it can be converted > in png". > > Can anyone give me a small entry point or has done similar and provide > some code snippet? > > Regards > Sabine > > > > > > -- > View this message in context: http://forum.world.st/Create- > png-from-pdf-tp4929722.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > >

Jan. 16, 2017

Re: [Pharo-users] About Git

by werner kassens

On 01/16/2017 12:20 PM, Peter Uhnak wrote: > Usually it's better to keep the discussion contained on the mailing list, and not extend it to private conversations. Hi Peter, after your message i considered the the thread to be essentially closed. > My point was that not only you don't understand git, but you also don't understand monticello - as explained with how contributions are actually managed under monticello. i'd venture the guess that, should there really be a strong desire to automate that procedure under monticello, it would not be too difficult to implement that for monticello too, eg a repository could have a "onlyPushes" attribute and then monticello sends uploads automatically to a separate inbox, if you dont have the password, and an email to the maintainer who can move it or whatever > That's why I wanted a Q&A so people can make informed decisions. sure, makes sense. werner

Jan. 16, 2017