August 2015 - Pharo-users - lists.pharo.org

Garage, Glorp, PostgreSQL and Cursors

by Tommaso Dal Sasso

Hello, I was trying the version of Glorp ported to Garage, and I must say it runs smoothly, nice job! I am reading large amount of data from a Postgres db, and I was curious about the use of cursors. I remember that the old version of Glorp for Pharo did not support cursors in Postgresql, has this changed in Garage? I tried to run some tests, using a query like: (Query readManyOf: MyClass) collectionType: GlorpCursoredStream; yourself. but with a large number of rows (~300k), the whole image crashes. Is this still not supported, or am I doing something wrong? Thanks, Tommaso

Aug. 3, 2015

Re: [Pharo-users] Pillar hyperref and refs numbering

by Ferlicot D. Cyril

Le 03/08/2015 12:44, Peter UhnÃ¡k a Ã©crit : > Hi, > Hi > I have two questions: > > 1. > Would it be possible to add \usepackage{hyperref} to Pillar pdf output? > Because currently all links are invisible (well, not invisible but they > look like regular text so if the). > > So if you have sentence like "Then create a directory named "pharo-vm" > and unzip the VM for windows that you can get on the pharo website > (windows virtual machine) ." (Section "installing pillar on windows." > nobody will notice that it's a link). > Having hyperref for print doesn't make sense but if people are viewing > it on their computer it's useful. > I tried to add what you write but I do not see the difference. Do I have to add something else? (I did not used much LaTeX before so I'm not familiar with LaTeX templates.) > > 2. > Why does HTML and PDF numbering differ? > > For example the first figure in HTML is "15.1", whilst in PDF its "1.1". > > This is further exemplified in the second sentence of the chapter > "Pillar is currently used to write the Enterprise Pharo book and other > projects (see Section 1.1)." > or > "Pillar is currently used to write the Enterprise Pharo book > <https://github.com/SquareBracketAssociates/EnterprisePharo> and other > projects (see Section 15.1.2 > <https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf…>)." > > Where in PDF it's actually referring to the whole chapter instead of the > proper part. But this may be result of the subsections not being > numbered (unlike html, which numbered is). > This is because you check only 1 chapter. If you check the whole book on "book-result" you will see that it's "15.1". See: http://puu.sh/jnEyC/8952285cee.png If you compile only 1 chapter in LaTeX then you will only have the numbering of the chapter. If you compile the whole book you will have the numbering of all chapters. Cyril

Aug. 3, 2015

Pillar hyperref and refs numbering

by Peter UhnÃ¡k

Hi, I have two questions: 1. Would it be possible to add \usepackage{hyperref} to Pillar pdf output? Because currently all links are invisible (well, not invisible but they look like regular text so if the). So if you have sentence like "Then create a directory named "pharo-vm" and unzip the VM for windows that you can get on the pharo website (windows virtual machine) ." (Section "installing pillar on windows." nobody will notice that it's a link). Having hyperref for print doesn't make sense but if people are viewing it on their computer it's useful. 2. Why does HTML and PDF numbering differ? For example the first figure in HTML is "15.1", whilst in PDF its "1.1". This is further exemplified in the second sentence of the chapter "Pillar is currently used to write the Enterprise Pharo book and other projects (see Section 1.1)." or "Pillar is currently used to write the Enterprise Pharo book <https://github.com/SquareBracketAssociates/EnterprisePharo> and other projects (see Section 15.1.2 <https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf…> )." Where in PDF it's actually referring to the whole chapter instead of the proper part. But this may be result of the subsections not being numbered (unlike html, which numbered is). Thanks, Peter

Aug. 3, 2015

Re: [Pharo-users] Pillar automatic anchors

by Peter UhnÃ¡k

> > Hi Petter! > > I begun a transformer some time ago. His name is "PRAnchorOfSection" > that inherit from "PRNodeTransformer". > For now this transformer is not enable because we need to check some > problems. > Yeah, I started studying this. > For example this works bad if we put a link inside the title. Maybe combination of using ==PRHeader text== (instead of ==PRHeader children first text== which doesn't work when there's formatting involved... like ! ==PRTransformer==) and then id filtering could solve this? It will be messy, but not if we also give user the ability to specify anchors explicitly... see further down. But I see a different problem which I don't think can be solved with generic Transformer... And that is that in HTML it is customary to place anchor ABOVE or before the target, so when you click on a link it it will show also the name of the chapter, so the user knows where he is. While in LaTeX it's usually placed underneath. So this would require having an extra HTML-only specific transformer (or something) that would swap them. Or what do > we do if we have two times the same title? As "Introduction"? > Well ideally user would still be able to specify an explicit anchor, in which case the default one is not generated. So by default it can append a number or something, but user could override it. I think there's a lot to be learned from Sphinx. Peter

Aug. 3, 2015

Re: [Pharo-users] Pillar automatic anchors

by Ferlicot D. Cyril

Le 31/07/2015 20:06, Peter UhnÃ¡k a Ã©crit : > Hi, > > I would like to resolve this issue: > Automatic section anchors: Each section title should automatically > generate an implicit hyperlink target (aka, anchor) pointing to the > section. The text of the hyperlink target (the "reference name") is the > same as that of the section title. > > however since I'm not familiar with Pillar I don't know how acceptable > this solution could be > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > PRHTMLWriter>>visitHeader: aHeader > | level | > level := self configuration headingLevelOffset + aHeader level."h1 to h7 > exist." > level := level min: 7 max: 1. > canvas tag > name: 'h' , level asString; > parameterAt: 'id' put: (self createIdForHeader: aHeader); "<<< addition" > with: [ > self writeCounterForHeader: aHeader. > super visitHeader: aHeader ]. > canvas newLine > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > and > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > createIdForHeader: aHeader > | id | > id := aHeader text. > id := id asLowercase. > "replace banned characters with dashes" > id := '[^0-9a-z\-]' asRegex copy: id replacingMatchesWith: '-'. > "merge multiple dashes" > id := '-{2,}' asRegex copy: id replacingMatchesWith: '-'. > "remove dashes from beginning/end of the id" > id := '^-|-$' asRegex copy: id replacingMatchesWith: ''. > ^ id > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Strictly speaking HTML 5 is very permissive with the value of id, but > the question is whether we really want to permit everything. E.g. > unicode in url is always asking for trouble. > > Thanks, > Peter > > Hi Petter! I begun a transformer some time ago. His name is "PRAnchorOfSection" that inherit from "PRNodeTransformer". For now this transformer is not enable because we need to check some problems. For example this works bad if we put a link inside the title. Or what do we do if we have two times the same title? As "Introduction"? Cyril

Aug. 3, 2015

Re: [Pharo-users] ICFP contest 4th of August

by Sebastian Heidbrink

Sorry wrong key it is on the 7th... On 2015-08-02 10:05 PM, Sebastian Heidbrink wrote: > Hi! > > Just in case somebody might have missed this: > > http://icfpcontest.org/ > > Seabstian > >

Aug. 3, 2015

ICFP contest 4th of August

by Sebastian Heidbrink

Hi! Just in case somebody might have missed this: http://icfpcontest.org/ Seabstian

Aug. 3, 2015

Re: [Pharo-users] [ann] jdt2famix - an open-source java importer project

by Tudor Girba

Hi (again), The project below is made possible by JNIPort. Thanks, Joachim! Cheers, Doru On Sun, Aug 2, 2015 at 11:26 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I would like to announce the jdt2famix project. This aims to be an > open-source solution for importing Java projects into Moose: > http://www.smalltalkhub.com/#!/~Moose/Jdt2Famix > > The project is based on: > - JDT for raw parsing. This is implemented in Java. > - JNIPort for delegating to Pharo the Java methods that visit the Java AST. > > Installation details can be found on the main project page. > > The current importing logic is rudimentary, but the first goal was to > setup the whole ping-pong between Pharo and Java. This one works, and I am > quite happy about that. You can take a look at the JdtImporterTest. > > CAVEATS: > - Due to a problem in JNIPort, currently, this project only works in Moose > 5.0. > - Also, for now it works out of the box only for Mac OS X. > - And, on top of that, it requires Java 1.6 for now (until we will get the > Spur VM on 64 bits). > > There are still quite some challenges left, but once we get this going, we > would also be able to use deep AST analysis live, and to do incremental > model update when something changes on disk. Furthermore, if it scales, > this would not be based on an intermediary MSE file anymore. > > I would like to ask for help in several directions: > 1. Implement the full model import. This would require diving into JDT and > implementing the corresponding mapping logic. I spent a few days on this. > It is hairy, but it is not that impossible (only it has a ton of edge > cases). This should be test driven, in that, for each case, we need to have > a corresponding sample. > 2. Fix JNIPort to work in Pharo 5. > 3. Get the whole thing to work out of the box for Linux and Windows. > 4. Check scalability. > > Please let me know your opinions, and let me know if you would like to > participate. > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 2, 2015

Re: [Pharo-users] Comparison for SequencableCollection

by Joachim Tuchel

I think nobody's arguing that comparison of Collections is wrong per se. It's just that such an extension should not be part of the core libraries, or put differently, Smalltalk should not be extended in that direction, because the assumptions about what may or may not be the meaning of comparing two SequencableCollections are not universal. To me, JavaScript is far from being a positive argument ;-) Joachim > Am 02.08.2015 um 21:50 schrieb webwarrior <reg(a)webwarrior.ws>: > > Your use case (comparing containers using pluggable comparison for > items) is pretty common. > > And what I was suggesting won't solve that problem. > > However, it will make sequencable collections with comparable items > comparable. That's it. If we have comparison defined for Point, why not > have it for arrays? > > And no one forces you to define #= or #< for your objects if you don't > want to. > > > On 02.08.2015 20:23, Peter UhnÃ¡k [via Smalltalk] wrote: > > > > ... snip ... > > > > View this message in context: Re: Comparison for SequencableCollection > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 2, 2015

Re: [Pharo-users] Comparison for SequencableCollection

by webwarrior

Your use case (comparing containers using pluggable comparison for items) is pretty common. And what I was suggesting won't solve that problem. However, it will make sequencable collections with comparable items comparable. That's it. If we have comparison defined for Point, why not have it for arrays? And no one forces you to define #= or #< for your objects if you don't want to. On 02.08.2015 20:23, Peter UhnÃ¡k [via Smalltalk] wrote: > > ... snip ... > -- View this message in context: http://forum.world.st/Comparison-for-SequencableCollection-tp4840704p484072… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 2, 2015