November 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

by Pavel Krivanek

Well, we will revert the change -- Pavel 2016-11-13 17:33 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > > 2016-11-13 10:06 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> >> >> 2016-11-11 10:55 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: >> >>> Hi, >>> >>> the API of Pragma was changed in quite dangerous way. >>> In past we had: >>> - #selector to access to method selector >>> - #keyword to access to pragma selector >>> >>> now we have: >>> - #methodSelector to access to method selector >>> - #selector to access to pragma selector >>> >>> That means that the meaning of the message #selector was changed and it >>> can cause some problems (like some currently failing tests [1]). The >>> #selector message was deprecated in the middle of the transition process so >>> most of usages should be already rewritten to #methodSelector but we >>> need to be aware of it. >>> >>> [1] https://pharo.fogbugz.com/f/cases/19333/17-more-tests-fa >>> iling-due-to-MockSettings-class-Object-doesNotUnderstand-moc >>> ksystemsettings-SettingTreeBuilder-mocksystemse >>> >> >> And it broke finder. >> 19336 >> <https://pharo.fogbugz.com/f/cases/19336/Finder-broken-Can-not-search-for-pr…> >> Finder broken: Can not search for pragmas >> > > And FileList can not show .cs files anymore. > I think both has something to do with a lock (?) during the transform of > the autodeprecation. > > >> >> >>> >>> Cheers >>> -- Pavel >>> >> >> >

Nov. 14, 2016

Re: [Pharo-dev] baseline DNU in Pharo6?

by Cyril Ferlicot D.

On 14/11/2016 08:07, phil(a)highoctane.be wrote: > There is a DNU in the build for some reason. > > https://travis-ci.org/DuneSt/MaterialDesignLite/jobs/175623371 > > Works fine in 5.0 > > Clues? > > Phil > Hi! This is caused by the pragma API changes without deprecation. MDL uses the Cypress support from Metacello and thus load the latest Metacello if needed. But the latest Metacello does not have the changes for the pragma. It's for this kind of reason it would be cool to revert those changes and to go by a deprecation phase. -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Nov. 14, 2016

baseline DNU in Pharo6?

by phil＠highoctane.be

There is a DNU in the build for some reason. https://travis-ci.org/DuneSt/MaterialDesignLite/jobs/175623371 Works fine in 5.0 Clues? Phil

Nov. 14, 2016

Re: [Pharo-dev] Invoice management

by Paul DeBruicker

SmallPOS may have invoice management. It is a point-of-sale system. But I haven't used it. dario trussardi wrote > Ciao, > > I hope this email and relative question does not create problems to the > list. > > A dear friend asked me if I was able to handle the invoice management: > > 1 ) create the document with some items > > 2) print and save the document > > 3) have the possibility to make some queries on the documents > > Someone realized something in this direction based on Smalltalk ( Pharo > ) ? > > A base development with possibly to customize...... > > > Thanks for any considerations. > > > Dario -- View this message in context: http://forum.world.st/Invoice-management-tp4922741p4922864.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 14, 2016

Re: [Pharo-dev] pillar latex and code listings

by Nicolai Hess

2016-11-13 22:16 GMT+01:00 Damien Pollet <damien.pollet(a)gmail.com>: > On 13 November 2016 at 16:23, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > >> Hi Damien, I don't see how the layout from the EnterprisePharo could do >> labeled listings we could ref from the text. May it be that this is just >> not possible ? > > > I recall we discussed choices with the other Damien, and that there were > constraints due to listings.sty, but I think that's possible. I'd have to > have a look at the code, though, because it's very well possible that we > decided on a workaround instead. > > Can you catch me on Slack sometime this week, or open an issue on > https://github.com/cdlm/sbabook if not? > Ok, thanks. > > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet >

Nov. 13, 2016

Re: [Pharo-dev] pillar latex and code listings

by Damien Pollet

On 13 November 2016 at 16:23, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > Hi Damien, I don't see how the layout from the EnterprisePharo could do > labeled listings we could ref from the text. May it be that this is just > not possible ? I recall we discussed choices with the other Damien, and that there were constraints due to listings.sty, but I think that's possible. I'd have to have a look at the code, though, because it's very well possible that we decided on a workaround instead. Can you catch me on Slack sometime this week, or open an issue on https://github.com/cdlm/sbabook if not? -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Nov. 13, 2016

Re: [Pharo-dev] http://tracker.pharo.org down ?

by Esteban Lorenzano

no, but this is very easy :) just ssh to smalltalkhub and then /appli/catalog/start.sh of course, real problem is being able to ssh to smalltalkhub ;) Esteban > On 13 Nov 2016, at 18:23, stepharo <stepharo(a)free.fr> wrote: > > esteban do we have a how to somewhere? > > > Le 13/11/16 Ã 14:02, Esteban Lorenzano a Ã©crit : >> it was down, I restarted it (along with the catalog). >> >> Esteban >> >>> On 13 Nov 2016, at 10:28, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >>> >>> can not create a slice for an issue: >>> ZnHttpUnsuccessful: 503 Service Temporarily Unavailable >> >> > >

Nov. 13, 2016

Re: [Pharo-dev] http://tracker.pharo.org down ?

by stepharo

esteban do we have a how to somewhere? Le 13/11/16 Ã 14:02, Esteban Lorenzano a Ã©crit : > it was down, I restarted it (along with the catalog). > > Esteban > >> On 13 Nov 2016, at 10:28, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >> >> can not create a slice for an issue: >> ZnHttpUnsuccessful: 503 Service Temporarily Unavailable > >

Nov. 13, 2016

Re: [Pharo-dev] Pragma keyword / selector / methodSelector

by Nicolai Hess

2016-11-13 10:06 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > > 2016-11-11 10:55 GMT+01:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > >> Hi, >> >> the API of Pragma was changed in quite dangerous way. >> In past we had: >> - #selector to access to method selector >> - #keyword to access to pragma selector >> >> now we have: >> - #methodSelector to access to method selector >> - #selector to access to pragma selector >> >> That means that the meaning of the message #selector was changed and it >> can cause some problems (like some currently failing tests [1]). The >> #selector message was deprecated in the middle of the transition process so >> most of usages should be already rewritten to #methodSelector but we >> need to be aware of it. >> >> [1] https://pharo.fogbugz.com/f/cases/19333/17-more-tests-failing-due-to- >> MockSettings-class-Object-doesNotUnderstand-mocksystemsettings- >> SettingTreeBuilder-mocksystemse >> > > And it broke finder. > 19336 > <https://pharo.fogbugz.com/f/cases/19336/Finder-broken-Can-not-search-for-pr…> > Finder broken: Can not search for pragmas > And FileList can not show .cs files anymore. I think both has something to do with a lock (?) during the transform of the autodeprecation. > > >> >> Cheers >> -- Pavel >> > >

Nov. 13, 2016

Re: [Pharo-dev] pillar latex and code listings

by Nicolai Hess

2016-11-07 23:47 GMT+01:00 Damien Pollet <damien.pollet(a)gmail.com>: > On 7 November 2016 at 23:03, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > >> I look at the pdf for the update PBE and the references to code example >> don't >> work (just show ??, it works for figures). >> > > Could be that the reference or label simply don't matchâ¦ > > >> The code in the code example isn't highlight and >> does't have a dark background (as it is in the html output). >> > > Don't expect PDF and HTML to look the same. Pillar does its job at a > semantic level, not at form level. Both have their own independent way of > styling stuff. For LaTeX it relies on a specific document class setup, > including some macros to have a layer of decoupling between pillar's output > and what some packages offer. The listing environment you're mentioning is > an example; I haven't looked at pre-EnterprisePharo books in a while, but > it should indeed just be defined as an alias to the lstlisting provided by > listings.sty. > > BTW I'd recommend migrating the books to the EnterprisePharo layoutâ¦ but > that requires being somehow versed in the dark arts of LaTeX and ready to > spend a couple days checking for problems and matching format conventionsâ¦ > Hi Damien, I don't see how the layout from the EnterprisePharo could do labeled listings we could ref from the text. May it be that this is just not possible ? > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet >

Nov. 13, 2016