Re: [Pharo-dev] Opal, Pharo 3.0 and popup raising for none existing methods

On 07 Nov 2013, at 16:41, Mariano Martinez Peck wrote: > Hi guys, > > In Pharo 2.0 we have the setting #warningAllowed in Parser. This allow us to > disable the popups each time you save a method with a selector that doesn't > exist. > In Pharo 3.0 with the new Opal this setting doesn't exist

Re: [Pharo-dev] did you noticed the nice fly by help?

Awesome! This soon? https://pharo.fogbugz.com/f/cases/7323/fly-by-help-showing-method-class-variable-comments On Fri, Nov 8, 2013 at 2:26 AM, Stéphane Ducasse wrote: > Guys > > have a look, now we can all know what is Soup, Seaside, Athens, Shout, …. ! > [image: Screen Shot 2013-11-07 at 16.14.2

Re: [Pharo-dev] Adding ballon text to tree or tree items

cool guille! On Thu, Nov 7, 2013 at 10:03 PM, Guillermo Polito wrote: > I extended it so we can set tooltips to the tree elements. > > But a second look is good :) > > > On Thu, Nov 7, 2013 at 5:28 PM, Alain Plantec wrote: > >> Hi Guillermo, >> I will have a look. >> Cheers >> Alain >> >> On 7

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/30555 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] a6c3be: 30555

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: a6c3be126099ffc22e1603edc117f24ed1f204da https://github.com/pharo-project/pharo-core/commit/a6c3be126099ffc22e1603edc117f24ed1f204da Author: Jenkins Build Server Date: 2013-11-07 (Thu, 07 Nov 2013

[Pharo-dev] Parsing expressions and Opal

Hello, we were working on the issue 10983 plus smart suggestion, specially for a class definition. In a moment I need to parse a class definition, I treat as the normal case: root := OpalCompiler new source: context code; useFaultyForParsing: true; parse. And as a result we obtain a Method Node, b

[Pharo-dev] 19 issues fixed :)

Thanks mariano, nicolas, hernan, skip, leonardo, gisela, hernan, lucas and 10Pines Stef

[Pharo-dev] [update 3.0] #30555

30555 - - Issue 11222: Date readFrom:pattern: (year 2 decimals not 20xx but 00xx) https://pharo.fogbugz.com/f/cases/11222 - Issue 12101: Selecting a package in the Monticello browser https://pharo.fogbugz.com/f/cases/12101 - Issue 12095:

Re: [Pharo-dev] Does "browse" make sense?

Hi Mariano, I would prefer to keep browse for everything. If it is a selector, it opens a browser on the only one implementation or the implementors windows. If it is a class name, it browses it. etc. my idea would be to have one keybinding and context disambiguation. Cheers, Luc #Luc 2

Re: [Pharo-dev] [update 3.0] #30554

Just to point out, for https://pharo.fogbugz.com/f/cases/12093 the validation properly pointed out 3 failing tests, unless of course the failing tests were introduced on purpose. On 2013-11-07, at 21:38, Camillo Bruni wrote: > Would it be possible to make sure that all issues pass the monkey

Re: [Pharo-dev] [update 3.0] #30554

Would it be possible to make sure that all issues pass the monkey first, before integration? I've seen that we too easily forget to set the proper milestone (3.0) otherwise the validation does not hit in. On 2013-11-07, at 21:35, Stéphane Ducasse wrote: > > 30554 > - > > - Issue 12096: >

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/30554 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 6e0a2c: 30554

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 6e0a2c8369408066fd701ef72a7d1b5d2ebd9683 https://github.com/pharo-project/pharo-core/commit/6e0a2c8369408066fd701ef72a7d1b5d2ebd9683 Author: Jenkins Build Server Date: 2013-11-07 (Thu, 07 Nov 2013

[Pharo-dev] [update 3.0] #30554

30554 - - Issue 12096: Bad use of polimorphic on openMessageList:name:autoSelect: method of MessageBrowser class. https://pharo.fogbugz.com/f/cases/12096 - Issue 12064: Selecting a package in the Monticello browser https://pharo.fogbugz.com/f/cases/1

Re: [Pharo-dev] Adding ballon text to tree or tree items

Hi Guillermo, I will have a look. Cheers Alain On 7 nov. 2013, at 19:46, Guillermo Polito wrote: > Hi guys! > > I'm trying to add contextual help through the ballon flying help to nautilus. > I was looking at how other tools do it, and it looks like sending the > #setBalloonText: does it, but

[Pharo-dev] Does "browse" make sense?

Hi guys, Currently (it was not like that before), if we search implementors and there is only one implementation, it will open a normal browser with that method. If there are more, it will open the classic implementors windows. "Browse" (for example in the FinderUI), does exactly the same as imple

[Pharo-dev] [update 3.0] #30553

30553 - - Issue 12091: Smart Suggestions is not working in message browser and debugger anymore https://pharo.fogbugz.com/f/cases/12091 - Issue 12100 Add shortcut for code formatting https://pharo.fogbugz.com/f/cases/12100 Diff information: http://smal

[Pharo-dev] [pharo-project/pharo-core] 011c99: 30553

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 011c99de1d55877943774504562253e9851a2ae9 https://github.com/pharo-project/pharo-core/commit/011c99de1d55877943774504562253e9851a2ae9 Author: Jenkins Build Server Date: 2013-11-07 (Thu, 07 Nov 2013

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/30553 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] Adding ballon text to tree or tree items

Hi guys! I'm trying to add contextual help through the ballon flying help to nautilus. I was looking at how other tools do it, and it looks like sending the #setBalloonText: does it, but it does not work with the MorphTreeMorph. Does anybody have an idea? tx, Guille

Re: [Pharo-dev] Selecting a package in the Monticello browser

OK. We commited this: https://pharo.fogbugz.com/f/cases/12064/Selecting-a-package-in-the-Monticello-browser Now you are able to change the behavior, either from the settings browser or either from right clicking on the right panel (repositories) in the Monticello Browser (there is a checkbox). Ch

Re: [Pharo-dev] Scroll bug since ever. Someone?

It will be nice to have it ignored at least for now. Because for me it’s really hard to use Nautilus in Pharo 3. Cheers. Uko On 06 Nov 2013, at 17:03, Camillo Bruni wrote: > that happens only on the trackpad if you scroll diagonally ;) > Or well, when you scroll vertically and you are not full

[Pharo-dev] [update 3.0] #30552

30552 - - Issue 12081: Show the package in the senders and implementors window https://pharo.fogbugz.com/f/cases/12088/ - Issue 12093: Make RGComment polymorphic to RGMEthod for packages https://pharo.fogbugz.com/f/cases/12093 Diff information: http://smalltal

Re: [Pharo-dev] Deep Into Pharo: PPExpressionParser

Thanks, that's exactly what I was wondering. That would be a valuable clarification in the book. Is there an issue tracker? Original message From: "Damien Cassou [via Smalltalk]" Date: 11/07/2013 7:38 AM (GMT-05:00) To: "Sean P. DeNigris" Subject: Re: Deep Into Pharo: PP

Re: [Pharo-dev] Deep Into Pharo: PPExpressionParser

On Thu, Nov 7, 2013 at 5:31 PM, Sean P. DeNigris wrote: > Thanks, that's exactly what I was wondering. That would be a valuable > clarification in the book. Is there an issue tracker? no issue tracker. We encourage people to change the text directly :-D -- Damien Cassou http://damiencassou.sea

[Pharo-dev] [pharo-project/pharo-core] 424e82: 30552

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 424e82b31a6f19d6665e09a3dd0e280c8a1c8e36 https://github.com/pharo-project/pharo-core/commit/424e82b31a6f19d6665e09a3dd0e280c8a1c8e36 Author: Jenkins Build Server Date: 2013-11-07 (Thu, 07 Nov 2013

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/30552 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [update 3.0] #30552

30552 - - Issue 12081: Show the package in the senders and implementors window https://pharo.fogbugz.com/f/cases/12088/ - Issue 12093: Make RGComment polymorphic to RGMEthod for packages https://pharo.fogbugz.com/f/cases/12093 Diff information: http://smallta

[Pharo-dev] [FEEDBACK] [FIX] Cannot locate the sources file named /Applications/PharoV20.sources.

Dear Mac OS X users, could you load this slice from Pharo30Inbox in a Pharo 3.0 image, save your image, and launch it again. SLICE-Issue-12092-Pharo-cant-find-sources-files-when-embedded-in-an-app-application-DamienCassou.2 Do you still have the error "Cannot locate the sources file named /Ap

Re: [Pharo-dev] Selecting a package in the Monticello browser

On Thu, Nov 7, 2013 at 1:12 PM, Camillo Bruni wrote: > I do not like it either... but if there are more than one repository group > (like before 1 per package) we have to make sure the repositories are > unique > per URL, otherwise you end up with different repositories which look the > same > but

Re: [Pharo-dev] Selecting a package in the Monticello browser

I do not like it either... but if there are more than one repository group (like before 1 per package) we have to make sure the repositories are unique per URL, otherwise you end up with different repositories which look the same but for instance do not have the same credentials, which was the p

Re: [Pharo-dev] Selecting a package in the Monticello browser

So we were discussing this here in the sprint. People say this is a feature. To be this is a bug. The change is in repositoryGroup ^ workingCopy ifNil: [MCRepositoryGroup default] ifNotNil: [workingCopy repositoryGroup] which right now it is as repositoryGroup ^ MCRepositoryGroup default So we

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/30551 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 86fb0e: 30551

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 86fb0e5ae8999d15ddc7fa7f895f6d8aad6e6a2f https://github.com/pharo-project/pharo-core/commit/86fb0e5ae8999d15ddc7fa7f895f6d8aad6e6a2f Author: Jenkins Build Server Date: 2013-11-07 (Thu, 07 Nov 2013

[Pharo-dev] [update 3.0] #30551

30551 - From buenos aires sprint - Issue 12088: Show the package in the senders and implementors window https://pharo.fogbugz.com/f/cases/12088/ - Issue 12060: The Quit menu entry is not asking for a confirmation anymore? https://pharo.fogbugz.com/f/cases/1206

[Pharo-dev] Opal, Pharo 3.0 and popup raising for none existing methods

Hi guys, In Pharo 2.0 we have the setting #warningAllowed in Parser. This allow us to disable the popups each time you save a method with a selector that doesn't exist. In Pharo 3.0 with the new Opal this setting doesn't exist anymore. Is there a way to get this behavior??? Thanks, -- Mariano h

Re: [Pharo-dev] extracting a pier book into pillar files

I know the syntax is the same. I was just asking if there is a ready made script that *just* do the migration :). Should I understand that you are working on this? Any timeline? Doru On Thu, Nov 7, 2013 at 2:45 PM, Damien Cassou wrote: > I put the Magritte/Pier mailing list on copy. > > On Wed

Re: [Pharo-dev] Checking RB rules? manifest browser?

On 6 nov. 2013, at 22:43, Alexandre Bergel wrote: > Hi! > > We have some rules we would like to check against our code (Amber slime > rules). How can we do that? > Do we need the manifest browser? How to load it? I searched for "manifest" in > smalltalkhub and I got no result. Your rules sho

Re: [Pharo-dev] [FEEDBACK] Install Pharo on MacOSX

just go to system preferences and check to download the sources automatically, that advice worked for me should work for you. Damien I will try the new dmg when I get home, cause all my macs are home. On Thu, Nov 7, 2013 at 4:42 PM, Matias Garcia Isaia wrote: > Hi there! > > Worked like a charm

Re: [Pharo-dev] [FEEDBACK] Install Pharo on MacOSX

I tried on win7 64bit and works like a charm as far i can see, even the problem with launching images has been fixed. Sweet ! On Thu, Nov 7, 2013 at 4:42 PM, Matias Garcia Isaia wrote: > Hi there! > > Worked like a charm in Mavericks here. > > The Pharo Loader looks superb :) > > > I've installe

Re: [Pharo-dev] [FEEDBACK] Install Pharo on MacOSX

Hi there! Worked like a charm in Mavericks here. The Pharo Loader looks superb :) I've installed the app with no trouble, and downloaded the latest Pharo2 image. After launching it, the image showed a notification with this message: "Information Pharo cannot locate the sources file named /Appl

Re: [Pharo-dev] extracting a pier book into pillar files

I put the Magritte/Pier mailing list on copy. On Wed, Nov 6, 2013 at 2:24 PM, Tudor Girba wrote: > > Is there existing support to extract an existing Pier-based book into Pillar > files? > > I would be interested in moving the Moose book to this format. I'm not finished yet with the Pier-Book m

Re: [Pharo-dev] Support understanding changes

Le 07/11/2013 13:00, Martin Dias a écrit : Hi On Wed, Nov 6, 2013 at 1:38 PM, Goubier Thierry mailto:thierry.goub...@cea.fr>> wrote: Le 06/11/2013 13:20, Stéphane Ducasse a écrit : Now that we have epicea I would really love to have a tool that does not show me stupidly

Re: [Pharo-dev] [FEEDBACK] Install Pharo on MacOSX

On Tue, Nov 5, 2013 at 12:10 PM, Mark Bestley wrote: > This is due to Gatekeeper I think. I managed to open it by choosing Open > in the right click menu in Finder. see > I think you need to sign the app thank you for the reference. I will have a look. I want

Re: [Pharo-dev] Deep Into Pharo: PPExpressionParser

On Wed, Nov 6, 2013 at 12:41 PM, Sean P. DeNigris wrote: > Thanks! I'm clear on how to use them, just not on why to choose one over the > other.. I would say you can instantiate a PPExpressionParser if you want to do a small parser for small task. Now, if you have a grammar that's composed of man

Re: [Pharo-dev] Support understanding changes

Hi On Wed, Nov 6, 2013 at 1:38 PM, Goubier Thierry wrote: > > > Le 06/11/2013 13:20, Stéphane Ducasse a écrit : > > Now that we have epicea I would really love to have a tool that does not >> show me stupidly a diff but >> take into account the actions that have been performed like rename class,

Re: [Pharo-dev] Deep Into Pharo: PPExpressionParser

Norbert wrote: >You may have a look at PParser>>#delimitedBy: Thank you. Stephan

[Pharo-dev] [pharo-project/pharo-core] abc422: 30550

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: abc4223ca00772a462c1258f45047f40bc4a0e9d https://github.com/pharo-project/pharo-core/commit/abc4223ca00772a462c1258f45047f40bc4a0e9d Author: Jenkins Build Server Date: 2013-11-07 (Thu, 07 Nov 2013

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/30550 Home: https://github.com/pharo-project/pharo-core