Re: [Pharo-users] [ann] moose 5.1

Great to hear. Nice screen snapshot. cheers -ben On Thu, Jun 4, 2015 at 3:17 PM, Tudor Girba wrote: > We are happy to announce version 5.1 of the Moose Suite: > *http://moosetechnology.org/#install* > > >

Re: [Pharo-users] [ann] moose 5.1

Yiipie! Great news! Ricky — Sent from Mailbox On Thu, Jun 4, 2015 at 9:17 AM, Tudor Girba wrote: > We are happy to announce version 5.1 of the Moose Suite: > *http://moosetechnology.org/#install* > [image: Inline image 1] > Description > --- > This is a minor release. The key highlights are:

Re: [Pharo-users] [ann] moose 5.1

> On 04 Jun 2015, at 10:07, Aliaksei Syrel wrote: > > Juhu, thanks Doru! :) > Congratulations, Moose! +100 > Cheers, > Alex > On Jun 4, 2015 9:17 AM, "Tudor Girba" wrote: > We are happy to announce version 5.1 of the Moose Suite: > *http://moosetechnology.org/#install* > > > > Descript

Re: [Pharo-users] loading Coral from SmalltalkHub

On 04-06-15 01:46, Francisco Garau wrote: I've tried loading Coral by following the below instructions in its website but they failed when trying to load Readline. Gofer new url: 'http://ss3.gemstone.com/ss/coral'; package: 'Co

[Pharo-users] case-insensitive regexp

Hi, Some regular expression engines include support for /i flag that makes the regexp case-insensitive. In Pharo, regexp matcher can be setup to be case-insensitive (e.g. 'mypattern' asRegexIgnoringCase). But once a matcher is setup as case-senstive, can we provide a pattern to make its search ca

Re: [Pharo-users] case-insensitive regexp

I do not think this is possible. The problem is that the Regex compiles (parses) the pattern so once it's created you would have to reparse it. Theoretically speaking you could add ignoreCase accessors to RxMatcher but it is likely it would break things; or add method to RxMatcher that would return

Re: [Pharo-users] Monticello / OS deadlock ?

On Wed, Jun 03, 2015 at 05:03:18PM +0200, Jose San Leandro wrote: > Unfortunately it doesn't fix it, or at least I get the same sympthoms. Thanks for trying it. Sorry it did not help :-/ Dave > > Sending SIGUSR1 prints this: > > SIGUSR1 Wed Jun 3 16:53:50 2015 > > > /home/chous/toolbox/ph

Re: [Pharo-users] [ann] moose 5.1

Impressive!!! Wonderful team! Alexande -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jun 4, 2015, at 4:17 AM, Tudor Girba wrote: > > We are happy to announce version 5.1 of the Moose Suit

Re: [Pharo-users] case-insensitive regexp

Thanks Peter. On Thu, Jun 4, 2015 at 1:51 PM, Peter Uhnák wrote: > I do not think this is possible. The problem is that the Regex compiles > (parses) the pattern so once it's created you would have to reparse it. > Theoretically speaking you could add ignoreCase accessors to RxMatcher but > it i

Re: [Pharo-users] Visualizing a repository tree

Omg I just found out that if I click on the node representing an McVersionInfo it actually opens it in the inspector and I didn't even needed to implement anything special. That's really cool! Peter On Tue, Jun 2, 2015 at 6:59 PM, Alexandre Bergel wrote: > Interesting visualization! Keep going!

[Pharo-users] Roassal Camp Smalltalk

Dear Colleagues and Friends, We are happy to announce we will organize a CampSmalltalk about the Roassal visualization engine, on _Sunday 12 July_. As far as we have seen, the interests are multiple. Here is a list of topics we will happy to work on: - Port of Roassal on VisualWorks

Re: [Pharo-users] [Pharo-dev] Roassal Camp Smalltalk

Hi Alex, is it possible to add some discussion about stuff we did in roassal for dynacase to the list? Because I feel there is some duplication effort and also we could probably contribute some stuff we did back. Or perhaps even more general discussion about using roassal for more dynamic and modi

[Pharo-users] Proposed enhancements to get.pharo.org

I have a simple suggestion for the ZeroConf Bash scripts. The suggestion is to automatically discern the image that the scripts use. E.g. For the pharo script: https://gist.github.com/jacaetevha/7c4206d2cfadd54a492c#file-pharo For the pharo-ui script: https://gist.github.com/jacaetevha/7c4206d2cf

Re: [Pharo-users] Proposed enhancements to get.pharo.org

Hi jason Thanks. I have a simple suggestion for the ZeroConf Bash scripts. The suggestion is to automatically discern the image that the scripts use. E.g. For the pharo script: https://gist.github.com/jacaetevha/7c4206d2cfadd54a492c#file-pharo For the pharo-ui script: https://gist.github.c

Re: [Pharo-users] loading Coral from SmalltalkHub

Thanks Stefan Francisco there is nothing new in Coral we got stalled again because we focused on pillar. Stef Le 4/6/15 11:20, Stephan Eggermont a écrit : On 04-06-15 01:46, Francisco Garau wrote: I've tried loading Coral by following the below instructions in its website

[Pharo-users] collectionDo: vs. collection do:

Hi, is there some best practice about collectionDo: versus collection do: ? I see many times the first used (e.g. String>>linesDo:); I see a benefit if there is no accessor to the collection, but more times than not there actually is. >From my perspective it further pollutes the protocol and as a

Re: [Pharo-users] Pharo Video Tutorial: Package Tags

Guys I would not use sub-packages. Think about newbies please. We have packages and tags and ideally I would remove tags but we will not because else people will cry. Stef Le 3/6/15 12:30, Sergio Fedi a écrit : Since Tags have a different behaviour than Packages, I think we should. (speciall

Re: [Pharo-users] Pharo Video Tutorial: Package Tags

Le 04/06/2015 21:30, stepharo a écrit : Guys I would not use sub-packages. Think about newbies please. We have packages and tags and ideally I would remove tags but we will not because else people will cry. I would cry because I remember Pharo going through the RPackage without tags idea and

Re: [Pharo-users] collectionDo: vs. collection do:

Hi peter often xxx do: creates an intermediary collection while xxxDo: don't Stef Le 4/6/15 21:24, Peter Uhnák a écrit : Hi, is there some best practice about collectionDo: versus collection do: ? I see many times the first used (e.g. String>>linesDo:); I see a benefit if there is no access

Re: [Pharo-users] Pharo Video Tutorial: Package Tags

On Wed, Jun 3, 2015 at 1:19 PM, Sergio Fedi wrote: > If something is a tag, then you should be able to apply multiple tags to > something. > Well you sort-of can do that. Consider how many packages have tag "Tests" in it. They don't need to be globally unique and it makes sense to use the very s

Re: [Pharo-users] Visualizing a repository tree

You mean that when you click on a node while you inspecting the view you get a new pane to the right with that object? Doru On Thu, Jun 4, 2015 at 7:16 PM, Peter Uhnák wrote: > Omg I just found out that if I click on the node representing an > McVersionInfo it actually opens it in the inspector

Re: [Pharo-users] Visualizing a repository tree

> Objects are magical :) Yes, and this is absolutely mind blowing. Understanding that a mouse click is most of the time an action to inspect is absolutely a step forward. I feel we are still at the very beginning. It would be nice to see how this will evolve over the time... Alexandre > >

Re: [Pharo-users] Pharo Video Tutorial: Package Tags

how that would improve Pharo ? On Thu, Jun 4, 2015 at 10:30 PM stepharo wrote: > Guys > > I would not use sub-packages. Think about newbies please. > We have packages and tags and ideally I would remove tags but we will > not because else people will cry. > > Stef > > Le 3/6/15 12:30, Sergio Fe

Re: [Pharo-users] collectionDo: vs. collection do:

Considering one of the tenants of OO is information-hiding**, then #linesDo: seems preferable. But I guess the problem is consistently implementing *all* the collection protocols. It might be interesting to have a kind-of Trait that applies to a single instance variable, that prefixes the Trait's