- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Metacello] Did Pharo 2.0 Update #20200 break Metacello bootstrapping?

by Dale Henrichs

I was trying to work with Pharo2.0 the other day and ran into weird modified package issues ... Metacello-Base was involved ... I was actually trying to get something else accomplished and don't have time to debug Pharo2.0 issues, since they are not likely to be directly caused by Metacello... Dale ----- Original Message ----- | From: "DeNigris Sean" <sean(a)clipperadams.com> | To: metacello(a)googlegroups.com, pharo-project(a)lists.gforge.inria.fr | Sent: Wednesday, July 11, 2012 9:47:21 AM | Subject: [Metacello] Did Pharo 2.0 Update #20200 break Metacello bootstrapping? | | (Posting to Metacello and Pharo-project lists) | | Metacello bootstraps in #20199, but not #20200, #20201, or #20202. | | Try: | Gofer new | url: 'http://ss3.gemstone.com/ss/Versionner'; | package: 'ConfigurationOfVersionner'; | load. | | (Smalltalk at: #ConfigurationOfVersionner) project development | load:#('Core' 'Spec'). | | When the dialog pops up about loading a package with unsaved changes, | if you choose merge and keep the current version for all the removed | classes and methods, it bootstraps. If you "Load" instead of Merge, | it fails with "MessageNotUnderstood: IdentitySet>>copyAfter:" | | Sean

July 11, 2012

[Pharo-project] Did Pharo 2.0 Update #20200 break Metacello bootstrapping?

by DeNigris Sean

(Posting to Metacello and Pharo-project lists) Metacello bootstraps in #20199, but not #20200, #20201, or #20202. Try: Gofer new url: 'http://ss3.gemstone.com/ss/Versionner'; package: 'ConfigurationOfVersionner'; load. (Smalltalk at: #ConfigurationOfVersionner) project development load:#('Core' 'Spec'). When the dialog pops up about loading a package with unsaved changes, if you choose merge and keep the current version for all the removed classes and methods, it bootstraps. If you "Load" instead of Merge, it fails with "MessageNotUnderstood: IdentitySet>>copyAfter:" Sean

July 11, 2012

[Pharo-project] [Jenkins] Work on Networking tonight and tomorrow night

by Marcus Denker

Hi, Because of networking work (physical) at the building, Jenkins can be unreachable tonight (11) and tomorrow (12th). Local time 18 onwards, downtime might extend to 9am the next morning. Mailinglist, gforge and website will not be affected. Marcus -- Marcus Denker -- http://marcusdenker.de

July 11, 2012

[Pharo-project] Issue 6340: [BUG]: Browsing changes on a slice

by Sean P. DeNigris

Type-Bug Milestone-2.0 Pharo2.0a Latest update: #20202 1. Change a package required by a slice: Example: Gofer it url: 'http://ss3.gemstone.com/ss/PharoInbox'; version: 'SLICE-Issue-6300-Detach-keymaping-shortcuts-SeanDeNigris.2'; load. KMFactory class compile: 'keymapContainer ^ KMRepository default.' 2. In an MC Browser, select the changed package (Keymapping-Core in the example), and click "Changes" You will see only the changes you made in step 1 3. In the MC Browser, select the Slice package and click "Changes" 4. Close the changes browser 5. Repeat step 2 Now you will see a huge change list, where most things have not in fact been changed -- View this message in context: http://forum.world.st/Issue-6340-BUG-Browsing-changes-on-a-slice-tp4639553.… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 11, 2012

Re: [Pharo-project] [Jenkins] New issue status for real problems.

by Henrik Sperre Johansen

On 11.07.2012 15:41, Camillo Bruni wrote: > On 2012-07-11, at 15:28, Henrik Sperre Johansen wrote: > >> On 11.07.2012 15:14, Camillo Bruni wrote: >>> On 2012-07-11, at 15:02, StÃ©phane Ducasse wrote: >>> >>>> On Jul 11, 2012, at 11:05 AM, Camillo Bruni wrote: >>>> >>>>> That was a weird bug... but I fixed it. >>>>> We need a Debugger for the announcement system! >>>> What do you mean? >>>> Because what I know is that debugging the test of announcement can be a pain because registrations are done in another world. >>> the problem is, that on:fork: and co are used in the WeakMessageSends >>> and thus lose the complete reference to where they came from.. >>> >>>>> I tried to refactoring a bit so you can get a clue what's going on when stepping through with the debuggerâ¦ >>>> What you describe is more related to the state of the debugger and yes it was on our todo to fix the debugger. >>> no no, when you do SubscriptionRegistry >> #deliver: >>> you create a complete copy of the subscriptions collection. >>> This is not very useful, since you can filter them while copying => less items to copy, easier to inspect >> Not threadsafely. > ? this has absolutely nothing to do with thread safeness.... You're right, I'd forgotten exactly what we'd done :) In my mind it still read something like: deliver: anAnnouncement subscriptions copy do: [:each | each deliver: anAnnouncement ], relying on atomicity implicit through copy primitives rather than explicitly with a mutex. Filtering with the standard collection methods leaves you with an IdentitySet though, so you'd have to either convert it afterwards, change the curtailing code in deliver:to: (which uses Sequenceable protocol). Either probably has some tradeoff in readability/performance compared to the current delivery. Cheers, Henry

July 11, 2012

Re: [Pharo-project] Spec questions

by Benjamin

To participate, you can: - take a random tool and rewrite it using Spec :) - read the tech report, and tell where it's clear/unclear :) - write comments ^^ - just use it, and share your feedback. Then all together we can improve Spec - try to convince other people to participate :D Thank you in advance, Ben On Jul 11, 2012, at 4:22 PM, Goubier Thierry wrote: > How to participate then ? > > Will it be possible to do maybe a simple, but "live" painter ? > > My first contact with Morphic to do a few gui elements (such as rewritting the Nautilus GUI :-P) found the interface to be on the confusing side (multiple morphs doing the same thing, complex instantiation interface on average). > > Thierry > > Le 11/07/2012 14:58, StÃ©phane Ducasse a Ã©crit : >> The plan is the following: >> >> - focus on really added value: >> - dynamic spec (and ben did it already). We should be able to build mac os x like finder engine >> >> - focus on four/five items (buttons, list, trees, text area) >> - build a first complete UIPainter something that can be used to >> place widgets on the screen and wire them. >> - we started to look again at UIBuilder in 1.0 to get what could be reused >> (for now we will probably drop the event aspect) >> - ideally the panes for widgets settings should be generated automatically >> based on some kind of meta description or spec of the widgets so that we can >> move faster >> >> - continue to rewrite all the tools with Spec. ChangeSorter and dualChangeSorter got into >> production. >> >> - continue the chapter. >> - probably some videos. >> >> Now if people want to help, there are welcome. >> I think that we need more users. A typical task would be to rewrite the MC tools. >> >> >>> >>> Do we have Spec examples for >>> - menues >>> - lists with icons >>> - trees >>> >>> already? What is the state and overall >>> plan for the near future. >>> >>> Thx >>> T. >>> >> >> >> > > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > > >

July 11, 2012

Re: [Pharo-project] Spec questions

by Goubier Thierry

How to participate then ? Will it be possible to do maybe a simple, but "live" painter ? My first contact with Morphic to do a few gui elements (such as rewritting the Nautilus GUI :-P) found the interface to be on the confusing side (multiple morphs doing the same thing, complex instantiation interface on average). Thierry Le 11/07/2012 14:58, StÃ©phane Ducasse a Ã©crit : > The plan is the following: > > - focus on really added value: > - dynamic spec (and ben did it already). We should be able to build mac os x like finder engine > > - focus on four/five items (buttons, list, trees, text area) > - build a first complete UIPainter something that can be used to > place widgets on the screen and wire them. > - we started to look again at UIBuilder in 1.0 to get what could be reused > (for now we will probably drop the event aspect) > - ideally the panes for widgets settings should be generated automatically > based on some kind of meta description or spec of the widgets so that we can > move faster > > - continue to rewrite all the tools with Spec. ChangeSorter and dualChangeSorter got into > production. > > - continue the chapter. > - probably some videos. > > Now if people want to help, there are welcome. > I think that we need more users. A typical task would be to rewrite the MC tools. > > >> >> Do we have Spec examples for >> - menues >> - lists with icons >> - trees >> >> already? What is the state and overall >> plan for the near future. >> >> Thx >> T. >> > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

July 11, 2012

Re: [Pharo-project] bindWith: implementation missing

by Sabine KnÃ¶fel

I write a new application and will use format: now. Thanks;-) On Wed, Jul 11, 2012 at 4:03 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > #bindWith: is the same as using #format but not using "{x}" > syntax but "%x" syntax instead. > > In Pharo you we usualy write: > > 'foo {1} bar' format: {Date today} > > which returns 'foo 11 July 2012 bar' > > > I think it was VisualAge that used #bindWith: and % as marker, so > if you want to port code from that Smalltalk to Pharo > it may be helpful to add support for that. > > So it does the same - only a little bit different: > > 'foo %1 bar' bindWith: Date today aString > > Thats why it is now in http://ss3.gemstone.com/ss/PharoGoodies.html > Another option is to rewrite code to use #format: > > Bye > T. >

July 11, 2012

[Pharo-project] bindWith: implementation missing

by Torsten Bergmann

#bindWith: is the same as using #format but not using "{x}" syntax but "%x" syntax instead. In Pharo you we usualy write: 'foo {1} bar' format: {Date today} which returns 'foo 11 July 2012 bar' I think it was VisualAge that used #bindWith: and % as marker, so if you want to port code from that Smalltalk to Pharo it may be helpful to add support for that. So it does the same - only a little bit different: 'foo %1 bar' bindWith: Date today aString Thats why it is now in http://ss3.gemstone.com/ss/PharoGoodies.html Another option is to rewrite code to use #format: Bye T.

July 11, 2012

Re: [Pharo-project] bindWith: implementation missing

by StÃ©phane Ducasse

Ok thanks for the explanation. I never used it in VW. Stef On Jul 11, 2012, at 3:42 PM, Sabine KnÃ¶fel wrote: > Hi Stef, > > it is a helper method to put some strings together. > Instead of using commata, like this > > 'one: ','1',' two: ','2',' three: ','3' > ==>> 'one: 1 two: 2 three: 3' > > you use String>>bindWith:with:with: > > 'one: %1 two: %2 three: %3' > bindWith: '1' > with: '2' > with: '3' > > ==> 'one: 1 two: 2 three: 3' > > It is more readable (and writeable:-)) imho. > > I know this from ibm Smalltalk/VisualAge and as far as I remember, > Visual works has it, too. > > Greetings > Sabine > > On Wed, Jul 11, 2012 at 2:59 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Hi sabine >> >> what is bindWith:? >> >> Stef >> >> On Jul 10, 2012, at 4:49 PM, Sabine KnÃ¶fel wrote: >> >>> Hi All, >>> >>> I miss String>>bindWith: >>>>> bindWith: with: >>> etc. >>> >>> in Pharo. Is there a reason for that missing? >>> Has anyone an implementation for me? >>> I dont want to reinvent the wheel ;-) >>> >>> Greetings >>> Sabine >>> >> >> >

July 11, 2012