- Pharo-dev - lists.pharo.org

[Pharo-project] How programatically collapse main pharo window?
by Denis Kudriashov June 29, 2010

June 29, 2010

Hello. How programatically collapse main pharo window? How it can be done?

1 0

[Pharo-project] Fwd: Emploi Smalltalk
by StÃ©phane Ducasse June 29, 2010

June 29, 2010

>> From: Franck BUDAIL <FBU(a)gconsept.com> >> Date: 28 juin 2010 15:35:28 HAEC >> To: "bouraqadi(a)ensm-douai.fr" <bouraqadi(a)ensm-douai.fr> >> Subject: smalltalk et forum entreprise >> >> Monsieur Bouraqadi, >> >> Suite Ã notre Ã©change tÃ©lÃ©phonique, je reviens vers vous sur nos recherches de profils Â« Smalltalk Â», >> Nous recherchons donc 3-4 personnes pour des projets de plusieurs annÃ©es basÃ©s au Mans. >> >> Les rÃ©munÃ©rations vont de 30 Ã 45kâ¬ suivant les profils (dÃ©veloppeurs, concepteurs, analystes, CP, architectes) >> NâhÃ©sitez pas Ã diffuser nos besoins auprÃ¨s de votre rÃ©seau, >> Les personnes intÃ©ressÃ©es peuvent me joindre directement par email ou sur mon portable. >> >> Jâattends vos Ã©lÃ©ments en parallÃ¨le sur le forum entreprise >> >> Dans lâattente de votre retour >> Cordialement >> >> >> >> Franck BUDAIL >> Directeur DÃ©veloppements >> >> >> >> Zac des hauts de CouÃ«ron. >> rue des forgerons >> 44220 COUERONwww.gconsept.com >> >> >> TÃ©l.: +33 (0)2 51 83 03 00 >> Fax: +33 (0)2 51 83 03 01 >> Mob: +33 (0)6 25 31 24 57 >> Email : fbu(a)gconsept.com >> >> Ã¼ N'imprimez ce mail que si nÃ©cessaire. >> Ce message peut contenir des informations confidentielles protÃ©gÃ©es par le secret professionnel. Au cas oÃ¹ il ne vous serait pas destinÃ©, nous vous remercions de bien vouloir nous en aviser immÃ©diatement et de le supprimer. >> >> >> > > > > Noury > http://csl.ensm-douai.fr/noury > ---- > -18th International Smalltalk Joint Conference, September 13 -17 2010 Barcelona, Spain. > http://www.esug.org/Conferences/2010 > > -18Ã¨me JournÃ©es Francophones des SystÃ¨mes Multi-Agents (JFSMA), 18-20 october 2010, Mahdia, Tunisia. > http://www.ltim.org/jfsma10/accueil.php > > -4th Argentinian Smalltalks Conference November 11th - 13th, 2010, ConcepciÃ³n del Uruguay, Entre RÃos, Argentina > http://www.fast.org.ar/ >

1 0

[Pharo-project] Fwd: [Pharo-users] [SPAM] Re: WebClient
by StÃ©phane Ducasse June 28, 2010

June 28, 2010

> > StÃ©phane, > > On 11 Jun 2010, at 23:09, StÃ©phane Ducasse wrote: > >> Hi sven >> >>> Hi, >>> >>> Andreas Raab's 'new' WebClient/WebServer seems quite nice, as he says himself: >>> >>> As a result, we now have what I think is a pretty decent HTTP server and client implementation for Squeak 4.1 and hopefully we can nuke HTTPSocket sometime soon. WebClient is superior in every respect. >>> >>> Is this something that will / should fit seamlessly into Pharo ? Or even become preinstalled ? >> >> could be but not at the price to have concatenation of string and numbers. >> So this means that somebody would have to do a pass on the code and produce a pharo version that squeakers may want or not. > > I went over the code and produced a version of WebClient-Core (and WebClient-Test) that passes all units tests in Pharo 1.1 rc 2: > > Filename: WebClient-Core-SvenVanCaekenberghe.24.mcz > Author: Sven Van Caekenberghe > Timestamp: 14 June 2010 4:24:21 pm > UUID: 92b7f407-8df1-4472-962b-45d99f2364b8 > Ancestors: WebClient-Core-ar.23.mcz > > Filename: WebClient-Tests-SvenVanCaekenberghe.12.mcz > Author: Sven Van Caekenberghe > Timestamp: 14 June 2010 4:25 pm > UUID: f495c2cd-54bb-42a9-a6d7-f380cd656f3f > Ancestors: WebClient-Tests-ar.11.mcz > > Both at http://www.squeaksource.com/ADayAtTheBeach. > > The only remaining method needed from the old WebClient-Pharo package is String#squeakToUtf8 > > squeakToUtf8 > "Convert the receiver into a UTF8-encoded string" > > ^self convertToWithConverter: UTF8TextConverter new. > > There are only 4 callers so I could change that as well, should I ? I checked the references to UTF8TextConverter and it feels as if you don't want a method like #squeakToUtf8 (apart from the name ;-) If I remember correctly mike changed them because there were no use anymore. >>> I didn't try his ConfigurationOfWebClient since the last version was unreadable and it seemed like an experiment, while his textual explanation was easy to follow. >>> >>> To load it into and to make the unit tests run in Pharo 1.0 I had to make a couple of fixes (to WebCookie#printOn: and WebServer class#serverString). Who should I sent these changes to ? >> >> to andreas? >> may be ask him if he wants to have a version working also for pharo but without String#, override > > I will contact Andreas directly once I know your position on the last remaining item. Good > Sven > > BTW, Is there a way to make a (old school) ChangeSet (or even another 'patch' package) out of the differences between versions in Monticello ? Click on changes>history> and you can get the delta. Stef

4 4

Re: [Pharo-project] [Seaside] New structure for Seaside30, Magritte2, and Pier2 Metacello configurations
by Mariano Martinez Peck June 28, 2010

June 28, 2010

Hi Dale. I didn't test it, but from the theorical point of view, I really like it. I hope other people too. I think we have to take advantage of Metacello features to do this kind of stuff. It is very interesting to have two groups: one for the core (and probably deployment) and one for development. If you do this changes, please update the workspace of ConfigurationOfSeaside explaining this :) (sorry if you already did it) Cheers mariano On Sun, Jun 27, 2010 at 7:54 PM, Dale Henrichs <dhenrich(a)vmware.com> wrote: > I am looking for a little feedback on the changes that I have made to the > latest configurations of Seaside30, Magritte2, and Pier2. I have new > versions for each of these configurations queued up for release > (#development blessing), but before releasing them I'd like to hear if the > changes I've made will cause trouble for folks using Magritte2 and/or Pier2 > in their applications. > > In the past, when you referenced Seaside30 from a configuration, the entire > Seaside3.0 release would be loaded, including development tools, examples, > both adaptors (on Squeak/Pharo and GemStone)...basically the whole kitchen > sink. > > With the 3.0.0-alpha5.15 release I've defined several groups for Seaside3.0 > (with feedback from the Seaside devs:): Base, Base Tests, Development and > Development Tests. I will also add a One-click group to shdow the one-click > release. Without going into too much detail, the Base group defines the set > of packages that are needed for a production release, while the Development > group defines the set of packages that are useful in development (on top of > the Base). > > To see how these new groups work out, I have created new versions of the > configurations for Magritte2 and Pier2 that reference the Base group (plus > any other packages that were needed) instead of bringing in the entire > Seaside3.0 release...This is the big change. After loading the Magritte2 or > Pier2 configuration you will need to load from the Seaside30 configuration > any and all packages that you may need for your own application. > > I haven't released the changes yet, but if you are curious or concerned you > can try out the releases ahead of time ... depending upon feedback I may go > with a different scheme. > > In a fresh image, you can see what will be loaded for production by > executing one or more of the following expressions (note you need to get the > latest version of each of the configs from the SqueakSource > MetacelloRepository...oh and for best results use Metacello 1.0-beta.27.1): > > (ConfigurationOfMagritte2 project version: '2.0.5') load. > (ConfigurationOfPier2 project version: '2.0.6') load. > (ConfigurationOfPierAddOns2 project version: '2.0.6') load. > > Once you've loaded one of these configs, there will be no development tools > nor any adaptors so at a minimum you'll need to load one of the following > depending upon which adaptor you want to use: > > "All platforms" > (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15') > load: #('Seaside-Adaptors-Swazoo'). > "Squeak and Pharo" > (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15') > load: #('Seaside-Adaptors-Comanche'). > "GemStone" > (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15') > load: #('Seaside-Adaptors-FastCGI'). > > If you want to load in the Seaside development environment then you would > evaluate the following expression: > > (ConfigurationOfSeaside30 project version: '3.0.0-alpha5.15') > load: #('Development'). > > So at this point you can see the direction I'm going with this ... the > Magritte2 and Pier2 configurations are currently aimed at loading the bare > minimum needed for functionality from Seaside3.0 for Magritte2 and Pier2 > with the idea that you'd load the additional functionality that you want by > dealing directly with Seaside30 configuration (like loading adaptors and > development)... > > Pier2 already depends upon the following javascript packages: > > 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' 'JQuery-UI' > > but if you're currently using Magritte2 and javascript, then you'll need to > explicitly load the javascript package(s) that you are using. > > There are other ways that the configs could be structured. This approach > minimizes the coupling between the Seaside3.0 and Magritte2/Pier2 > configurations, which I think is a good thing. > > I've taken the bare minimum step: loading what is required... it would be > reasonable to add 'Dev' groups to both Magritte2 and Pier2 that would bring > in Seaside30 dev support on the other hand, I don't think it is reasonable > to add support for loading the various Adaptors to Magritte2 and Pier2, so > if you're going to have to deal with the Seaside30 config directly anyway > why bother with adding dev groups ... > > Anyway this is what _I_ think and I am interested in what you folks > think... > > For GemStone folks ... the answer is yes, Magritte2 and Pier2 have been > ported to GemStone/S 64 2.4 finally:). If you've been working with > Seaside3.0 already, you can load the Magritte2/Pier2/PierAddOns2 configs > into a fresh 1.0-beta.8....otherwise I'll ask you to wait until I > announcement. > > Dale > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >

2 1

[Pharo-project] [update 1.2] #12023
by StÃ©phane Ducasse June 28, 2010

June 28, 2010

12023 ----- - Issue 2577: Duplicate primInitializeNetwork: method I found the bug in Scriptloader too :) Stef

1 0

[Pharo-project] Xtreme Pharo hacker needed :)
by laurent laffont June 28, 2010

June 28, 2010

Hi, I struggle for a functionality I want to add on Autotest. Suppose a class with two methods A and B, such as A senders of B Zork>>methodA self methodB And unit tests: ZorkTest>>testSomething ..... Zork new methodA ... self assert: .... If I change methodA, Autotest detects it, search all senders of methodA in tests and run. As ZorkTest>>testSomething is sender of Zork>>methodA, it will find and run it. Now if I change methodB and there's no senders in tests, the previous heuristic won't work. So I added as last heuristic: if no method found, search all TestCases that references the changed method class and run. So here it will find ZorkTest and run all its tests. The problem is that I don't really know if the method I've changed has been actually "hit" by the tests. I just see that tests has been run. I don't know if my method has been called when running the tests. So I want to detect this. One way of doing this seems to use MethodContext>>runSimulated:contextAtEachStep:. I've found this looking at MessageTally. Is it the best solution ? So in Autotest>>findRunAndShowTestsOf: I try something like this Autotest>>findRunAndShowTestsOf:changedMethod | testMethods aTestResult methodHit | "Finds the test related to changedMethod, run them and tell the view to update" testMethods := search methodsFor: changedMethod. methodHit := false. thisContext sender runSimulated: [aTestResult := runner run: testMethods] contextAtEachStep: [:current| (current method = changedMethod) "<--- here I detect if changedMethod has been hit" ifTrue: [methodHit := true]]. ..... but using this debugger opens with "SimulationGuardException: triggered by BlockClosure>>newProcess" in MethodContext>>doPrimitive:method:receiver:args: As I don't (yet :) understand all this stuff, I want to know if it's the right way to do it and what should I check. Thanks Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

10 19

[Pharo-project] [update 1.2] #12020...#12022
by StÃ©phane Ducasse June 28, 2010

June 28, 2010

12020 ----- - Issue-2448-WideStringDisplayMangled. Part one. Thanks Henrik 12021 ----- - Issue-2448-WideStringDisplayMangled. Part Two of slice, now with inst var in super, and refactored methods. Part ONE (ie version 3) needs to be loaded before this one. (ie. this is needs two separate patches). Thanks Henrik 12022 ----- - Issue 2597: Versions Browser diff checkboxes. Thanks Gary Stef

1 2

[Pharo-project] squeak.org (and expecially source.squeak.org) is down - resolved
by Torsten Bergmann June 28, 2010

June 28, 2010

FYI http://lists.squeakfoundation.org/pipermail/squeak-dev/2010-June/151637.html -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

1 0

[Pharo-project] Panic
by Mariano Martinez Peck June 28, 2010

June 28, 2010

Hi folks. <OT> In my university were I was graduated, used to teach with Dolphin few years ago, then squeak and this semester they will probably start to teach with Pharo. The good thing is that they have like 6 courses, with 50 students each course....so, it is good :) I hope several of them join the community. Carla, anything to say about PDP? ;) </OT> I was talking with them, and they missed (me too) a little utility that was in Dolphin and that I remember in VAST: the panic button. In dolphin is "panic", in VAST I don't remember exactly. But basically, what it does is to close ALL what it is open. All kind of windows, popups or anything. Right now, we have a "Delete unchanged windows" but: - it only takes into account windows. I want to close everything: transcripts, workspaces, popups, etc. Even more, OCompletion sometimes lets some popups alive and users (mostly beginners) don't know how to remove them. - I want to close ALL windows, I don't care if you were editing or not. - I dont like the name "Delete unchanged Windows". Can we renamed to "*Close * unchanged windows" ? So...I can add it to the "Windows" -> "Panic" I am not sure if Panic is the best name. Do you have better ideas? Basically, it does this: World submorphs reject: [:m | m == LogoImageMorph default ] thenDo: [:each | each delete] (remove all World submorphs but the Pharo logo) The first question is, do you like the idea? should I add it ? The second is, how can I delete a SystemWindows that has been being edited without saving ? because right now, the popup raises saying "Changes has not been saved....". I want to delete them without asking. I have no idea how to do this. Help ? maybe there is a preference or notifier that I can turn of before the execution and then put it back ? I searched in Morph to see if there is a deleteWithoutAsking or similar but I didn't find anything. Thanks Mariano

10 18

[Pharo-project] GLORP in Pharo
by Alberto Bacchelli June 28, 2010

June 28, 2010

Hi, What is the current situation of GLORP in Pharo? Is there any working porting? Otherwise are there reliable alternatives to it? Thank you. Cheers, Alberto

4 3