March 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] How to rewrite self should: into self assert:

by Denis Kudriashov

2016-03-27 20:45 GMT+02:00 Mark Rizun <mrizun(a)gmail.com>: > Hi, Denis. > > We discussed this with Stef, created the rule for such transformation and > successfully applied it to many methods :) > The rule basically is: > self should: [ ``@object ] --> self assert: ``@object > Nice. Thank's

March 27, 2016

Re: [Pharo-users] How to rewrite self should: into self assert:

by Mark Rizun

Hi, Denis. We discussed this with Stef, created the rule for such transformation and successfully applied it to many methods :) The rule basically is: self should: [ ``@object ] --> self assert: ``@object Cheers, Mark 2016-03-27 21:22 GMT+03:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > I would like to see how you do this. > > 2016-03-26 9:41 GMT+01:00 stepharo <stepharo(a)free.fr>: > >> Hi guys >> >> I tried to tools of mark and failed miserably. >> Any suggestion is welcome. >> >> Stef >> >>

March 27, 2016

Re: [Pharo-users] How to rewrite self should: into self assert:

by Denis Kudriashov

I would like to see how you do this. 2016-03-26 9:41 GMT+01:00 stepharo <stepharo(a)free.fr>: > Hi guys > > I tried to tools of mark and failed miserably. > Any suggestion is welcome. > > Stef > >

March 27, 2016

is there a better way to browse the mail archives than

by Torsten Bergmann

>is there a better way to browse the mail archives http://lists.pharo.org => select the list and click on "Archives"

March 27, 2016

Re: [Pharo-users] Roassal2 on Ubuntu 64

by Offray Vladimir Luna CÃ¡rdenas

Hi, On 10/03/16 11:27, Peter UhnÃ¡k wrote: > > Sorry I don't explain myself properly. I was meaning a window with > this message instead of a error trace, which could be > intimidating. Something with the same message and buttons like > "Ok", "Launch debugger". In the workshops there are some Gnu/Linux > newbies and the hidding the error trace for a while seems to be > helpful to them. > > > This should be relatively simple to do: > > 1) create new "PreDebugger" that's user-friendly (currently we have > (GT)SpecPreDebugWindow that is started from > (GT)SpecDebugger>>openWithNotification:) > 2) let Debuggers ask for PreDebugWindow class through Smalltalk tools > 3) install your UserFirendlyPreDubugWindow to Smalltalk tools > > I think this would be a very useful addition for many people. (I > wanted to make this some time ago but haven't got around to do it yet.) > Thanks for the ideas. > No, but because we could build a wrapper for particular packages > that installs Nix, and then others (32 bits variants of libcairo > or sqlite, pandoc, etc) without caring about a particular Unix > variant (being them Mac or hundreds Gnu/Linux distros based on > dozen of "bases"), making the experience smother for the newbie, > providing he/she has root privileges. People will not see nix > anywhere, not even for installing > > > Mac is self-contained, so the main issue is linux. > If the user has a root privilege, then maybe we should push for pharo > directly in the package manager repository? What I would like is to push away the users from the environment and computing experience as little as possible, to make the experience work for them. That mean minimizing go to the web, go to command shell and so on for things like installing the stuff that make pharo/roassal work. > And sure, there are hundreds of distros, but you will cover majority > of the market withâ¦ maybe 5 distros? People that can't handle obscure > distros don't install them. > > But to get some motion: > 1) let's compile a list of majority distros > 2) let's see how hard it is to build packages for them (imho this > could be automated via CI), and we already have ubuntu package (or > maybe nix can be pushed to all distros?) Nix can be used on all Linux distros, Solaries, Mac and major close to Unix operative systems, so it is already dealing with the diversity without us reinventing that an using it where complex installations and dependencies are needed seems a sensible option. > 3) maybe consider all-in-one bundle for non-root targets (this would > work for cairo, but not for 64b systems in general, because the > dependency list there is monstrous) That bundle would be really helpful. Disk space is cheaper that user time/frustration. I'm starting some small installer for self-contained non-root apps that I need in grafoscopio (SQLite, fossil and pandoc), so when they're needed but not present, the systems deals with the installation in a smooth way, and the person keeps focused on the task (or can take a break while the installation of bigger stuff :-) ). > > So no need to be sarcastic here Peter. > > Sorry, I got carried away. I've got my fair share of dependency hell > and introducing another package manager always makes me shiver. > Don't worry. In my case, Nix has been a savior when a dependency hell can not be solved my my native package manager, so I see the things in the opposite way. Cheers, Offray

March 27, 2016

Re: [Pharo-users] Ideas of web services that I could script in a couple of lines?

by Offray Vladimir Luna CÃ¡rdenas

That would certainly close the circle, because I used Help System source code as an inspiration on how tree-like documentation could be implemented inside the image, but adding more interactivity and flexibility. In the attachment you can see the piece where I talk about this and full text is in [1]. [1] http://mutabit.com/repos.fossil/grafoscopio/doc/tip/Docs/Es/Articulos/Liber… Pharo allows me to explore old ideas [2] about exploratory computing, interactive documents and writing [2] http://mutabit.com/offray/static/blog/output/posts/on-deepness-and-complexi… Thanks for that :-), Offray On 16/03/16 00:00, Ben Coman wrote: > Looks cool. I wonder if this would make a good basis for the main > Image help system? > cheers -ben > > On Wed, Mar 16, 2016 at 10:15 AM, Offray Vladimir Luna CÃ¡rdenas > <offray.luna(a)mutabit.com <mailto:offray.luna@mutabit.com>> wrote: > > Hi, > > The last version of the tutorial grafoscopio notebook now includes > these cool examples (credit is done with a Thanks line). Here is a > cool preview ;-): > > > > You can get this interactive documentation by installing > grafoscopio [1] and then choosing from the docking bar "Actualizar > > DocumentaciÃ³n > Tutorial" (Sorry, for now interface and > documentation are only in Spanish) > > [1] http://smalltalkhub.com/#!/~Offray/Grafoscopio/ > <http://smalltalkhub.com/#%21/%7EOffray/Grafoscopio/> > > Thanks for these great examples, they're a nice addition to the > interactive documentation. > > Cheers, > > Offray > > On 14/03/16 01:33, Sven Van Caekenberghe wrote: >> (ZnEasy getJpeg: ((NeoJSONReader fromString: >> > (ZnClient new >> > url: 'http://www.omdbapi.com/'; >> > queryAt: 't' put: 'The Terminator'; >> > get; >> > contents)) at: #Poster)) inspect > >

March 27, 2016

is there a better way to browse the mail archives than

by stepharo

Hi I would like the reread the thread on || and pragmas and I have difficulty using the interface of http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html is there a better way to browse the mail archives it? Stef

March 27, 2016

Re: [Pharo-users] [Metacello] Apparent loop in before / after ....

by Damien Pollet

looks like you forgot something :D On 26 March 2016 at 21:56, stepharo <stepharo(a)free.fr> wrote: > hi dale > > I'm working a pretty large configuration and I got the following error > messsage (and I do not understand I cannot debug). > Do you have any suggestion because I did not even know that this error > exist before. > I disabled the validation of the config because it validates packages that > I cannot modify such as XML or SMark. > > Stef > > > >

March 26, 2016

Re: [Pharo-users] [Metacello] about required list

by Cyril Ferlicot Delbecque

On 26/03/2016 22:00, stepharo wrote: > Hi > > using the dependency analyser I see that may packages have the following > dependencies > > for example > > package: 'Math-DistributionGamma' with: [ spec requires: > #('Math-Core' 'Math-DHB-Numerical' 'Math-Series' > 'Math-Core-Distribution') ]; > > package: 'Math-DistributionBeta' with: [ spec requires: > #('Math-DistributionGamma' 'Math-Core' 'Math-Core-Distribution' > 'Math-DHB-Numerical' 'Math-Series') ]; > > so I wrote the requirement this way > > > Now does it have an impact on Metacello and should I keep only the > direct depend. > Hi, Since Math-DistributionBeta depend on Math-DistributionGamma you can do: package: 'Math-DistributionGamma' with: [ spec requires: #('Math-Core' 'Math-DHB-Numerical' 'Math-Series' 'Math-Core-Distribution') ]; package: 'Math-DistributionBeta' with: [ spec requires: #('Math-DistributionGamma') ]; You can do this if beta really cannot work without gamma and if gamma will keep the same dependencies. And it is important I think because imagine Math-DisctirbutionBeta depend on Ston. You can create a group gamma and a group beta. If you load the group gamma, you will not get the ston dependency because it only concern gamma. > > package: 'Math-DistributionBeta' with: [ spec requires: > #('Math-DistributionGamma' ) ]; > > This is annoying because I have 50 packages and doing that manually is a > pain. > > Stef > > -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

March 26, 2016

[Metacello] about required list

by stepharo

Hi using the dependency analyser I see that may packages have the following dependencies for example package: 'Math-DistributionGamma' with: [ spec requires: #('Math-Core' 'Math-DHB-Numerical' 'Math-Series' 'Math-Core-Distribution') ]; package: 'Math-DistributionBeta' with: [ spec requires: #('Math-DistributionGamma' 'Math-Core' 'Math-Core-Distribution' 'Math-DHB-Numerical' 'Math-Series') ]; so I wrote the requirement this way Now does it have an impact on Metacello and should I keep only the direct depend. package: 'Math-DistributionBeta' with: [ spec requires: #('Math-DistributionGamma' ) ]; This is annoying because I have 50 packages and doing that manually is a pain. Stef

March 26, 2016