- Pharo-users - lists.pharo.org

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

by Yuriy Tymchuk

I have not seen that you gave this to me :). Just make sure that itâs in Pharo, and QA should pick it up. Cheers. Uko > On 28 Mar 2016, at 10:31, stepharo <stepharo(a)free.fr> wrote: > > I gave this rule and assert: = -> assert: equals: to yuriy for inclusion in QA > > > Le 27/3/16 21:04, Denis Kudriashov a Ã©crit : >> >> 2016-03-27 20:45 GMT+02:00 Mark Rizun <mrizun(a)gmail.com <mailto:mrizun@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 28, 2016

Pharo days 2016, driving from the Netherlands

by Stephan Eggermont

I've been looking at options to get to Namur from the Netherlands. My current plans are to drive by car from Den Bosch on thursday morning, and drive back friday evening, as it would be twice as fast as going by public transport. Anyone else from the netherlands going in that direction? Or want to share a ride? Stephan Eggermont

March 28, 2016

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

by stepharo

I gave this rule and assert: = -> assert: equals: to yuriy for inclusion in QA Le 27/3/16 21:04, Denis Kudriashov a Ã©crit : > > 2016-03-27 20:45 GMT+02:00 Mark Rizun <mrizun(a)gmail.com > <mailto:mrizun@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 28, 2016

Re: [Pharo-users] Call for action for Roassal

by Offray Vladimir Luna CÃ¡rdenas

Hi, On the data input front, the main aspect in the workshops is "where the data comes from?". In the examples of the book, most of it comes from the Pharo/Moose image itself. Where providing external data sources (Tweets, medicine info, public spending) and we're creating custom objects to hold them, but some kind of "generic" spreadsheet for populating/viewing/editing data sources would be the best addition here. On the data output front, the HTML exporter generates a great impression. I think that improving it and including the support for some small "web applets" with sliders/menus/inbox would be the next step. Cheers, Offray On 24/02/16 03:51, Alexandre Bergel wrote: > Dear community, > > As you may have seen, Roassal has entered a stabilization phase. The book AgileVisualization.com will soon be released. After its release, Roassal will go over a new development phase. In order to prepare it, I am asking this question: > > What are the 3 aspects you would like to see improved in Roassal? > > You can answer publicly or by sending private messages. > > Kind regards, > Alexandre

March 27, 2016

Re: [Pharo-users] Running Pharo 5 on Ubuntu 16.04

by Stephan Eggermont

On 26-03-16 17:39, nacho wrote: > Hi guys, > I'm having some issues in trying to run Pharo 5 in Ubuntu 16.04 > 1) I've downloaded the sources, images and latest vm from pharo site > 2) Unpacked everything into a directory ~/Applications/Pharo > 3) chowned and chmoded everythin in that file Tell us about the dependencies you've loaded? Pharo needs some 32 bit libraries to run. Isn't 16.04 supposed to be releases next month? Stephan

March 27, 2016

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