January 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] ToolBuilder improvements....
by StÃ©phane Ducasse Jan. 29, 2010

Jan. 29, 2010

Hi guys to relax I spent some time and I checked all the Toolbuilder-Kernel, ToolBuilder-Morphic changes in Squeak. Most of them looks good so I produced a slice. Slice-1895 Issue 1895: ToolBuilder squeak integration and related If one of you want to have a look go ahead and let me know. Stef

1 0

[Pharo-project] [update 1.1] #11185 and 1186
by StÃ©phane Ducasse Jan. 29, 2010

Jan. 29, 2010

[update 1.1] #11185 11186 ----- Issue 1880: nextChunk speedup part one and part two Thanks a lot henrik Stef PS: Miguel I did not check yet your fix because I wanted to do something relaxing to recharge my battery :)

1 0

[Pharo-project] video in Pharo
by laurent laffont Jan. 29, 2010

Jan. 29, 2010

Hi, Is it possible to play a video in Pharo ? How ? I'm thinking about writing a Pharo interface to Pharocasts, maybe integrated to ProfStef. It can be funny. Laurent

5 10

[Pharo-project] Fwd: [Esug-list] 2 young Smalltalk developers for Germany
by Mariano Martinez Peck Jan. 29, 2010

Jan. 29, 2010

Ok...it is not Pharo, but it is Smalltalk ! ---------- Forwarded message ---------- From: Nowak, Helge <hnowak(a)cincom.com> Date: Fri, Jan 29, 2010 at 5:37 PM Subject: [Esug-list] 2 young Smalltalk developers for Germany To: esug-list(a)lists.esug.org, vwnc(a)cs.uiuc.edu Dear Smalltalkers, one of our customers looks out for 2 young Smalltalkers for his experienced team to carry Smalltalk into the future at his company. German is a must. Please forward this message to anybody who you think might be interested. People interested should email me. Iâll put you in direct contact with our customer. Thank you in advance! Helge **************************************************************** *Helge K. Nowak* Technical Account Manager Cincom Smalltalk Cincom Systems GmbH & Co. oHG Am Kronberger Hang 4 D-65824 Schwalbach/Ts. Tel.: +49-(0)89-89664494 Mobil: +49-(0)172-7400402 Fax: +49-(0)89-89664495 Email: mailto:hnowak@cincom.com <hnowak(a)cincom.com> Web: http://www.cincom.com <http://smalltalk.cincom.com> *All about Cincom Smalltalk:* http://www.cincomsmalltalk.com <http://smalltalk.cincom.com> *A standpoint is an intellectual horizon of radius zero.* *-- Albert Einstein* GeschÃ¤ftsfÃ¼hrer/Managing Directors: Thomas M. Nies, Gerald L. Shawhan oHG mit Sitz/based in Schwalbach/Ts. (Amtsgericht KÃ¶nigstein/Ts. HRA 2653) Pers. haftender Gesellschafter/Partner liable to unlimited extent: Cincom Systems Verwaltungsgesellschaft mbH (Amtsgericht KÃ¶nigstein/Ts. HRB 5069)** **************************************************************** _______________________________________________ Esug-list mailing list Esug-list(a)lists.esug.org http://lists.esug.org/listinfo/esug-list

1 0

[Pharo-project] Cycle dependency between ImageSegment and Multilingual
by Mariano Martinez Peck Jan. 29, 2010

Jan. 29, 2010

Hi folks. Jannik pointed to me a cycle dependency between ImageSegment and Multilingual. When you create a segment, there is a way to export the complete segment (segment in itself but also the outpointers) to a file, using SmartRefStream (ImageSegment >> writeForExportOn: ) Now...you can load the that file in another image. When this is done, SmartRefStream calls the method comeFullyUpOnReload: So.... in ImageSegment >> comeFullyUpOnReload: we a bigggggg method, which this lines (a part, of course): importedObject is just one of all the objects that are in the SmartRefStream. (importedObject isKindOf: TTCFontSet) ifTrue: [ existing := TTCFontSet familyName: importedObject familyName pointSize: importedObject pointSize. "supplies default" existing == importedObject ifFalse: [importedObject becomeForward: existing]. ]. Does someone know why this piece of code should be necessary ? Of course, and I guess all agree, this shouldn't be in the core of ImageSegment but in other place. But anyway, I don't see a reason why this should be done. I vote for remove it. I remember John saying something about the menus or fonts...but I am not sure. What do you think ? Mariano

2 1

[Pharo-project] PluggableTreeMorph sends nil to setSelectedSelector callback
by Danny Chan Jan. 29, 2010

Jan. 29, 2010

Hi! I found out that when you have a PluggableTreeMorph and click on an item twice, the item is deselected and the callback registered with setSelectedSelector: receives nil. This is somehow not intuitive for me, and it is also not documented. Can we change this? Danny

1 0

[Pharo-project] [ANN] seasidehosting.st for Pharo
by Adrian Lienhard Jan. 29, 2010

Jan. 29, 2010

Hi all, I'm happy to announce that seasidehosting.st now supports Pharo! There are no special settings or configurations needed. Get a Pharo/Seaside image, for instance from www.seaside.st/download/pharo, install your application, and upload it to seasidehosting.st. Before, Pharo was not supported because the special VM used did not run closure images. Since many people asked for support of Pharo, we updated the VM now. It took some time, but as promised, we managed to finish it before the upcoming Pharo 1.0 release. I'd like to thank ESUG and netstyle.ch for their continuous support of Seasidehosting! Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/

2 1

Re: [Pharo-project] ConfigurationOfSeaside available
by Dale Henrichs Jan. 28, 2010

Jan. 28, 2010

Miguel, There were several factors: 1) It isn't possible to upgrade from Seaside2.8 to Seaside3.0. In a single configuration, I expect to be able to #load: '2.0' and later #load: '2.4' and have the right thing happen 2) 2.8 and 3.0 are more like separate web frameworks. If you use #loadLatestVersion you will get 3.0 every time. There needs to be a way to #loadLatestVersion for 2.8 independent of 3.0 3) The code bases for Magritte and Pier have forked as well. And the issues in point 1 and 2 apply to Magritte and Pier. 4) ConfigurationOfSeaside detects whether 2.8 or 3.0 is loaded and will not allow you to "mix the streams". This would be doable but much more complex if it was necessary to add the same logic to all 8 configs involved. 5) To load Magritte/Pier one must choose which version of Seaside to use, so I think it is much more obvious layed out in ConfigurationOfSeaside, especially with the doits. I think that the simple Seaside workspace makes the complex problem understandable. 6) ConfigurationOfSeaside has many parrallels to ConfigurationOfPharo or ConfigurationOfGLASS. You need a simple starting point and once you understand what you want to do, you can clone ConfigurationOfSeaside and pare it down to the projects important to you and add in your own projects as well. In the end I think it is a good strategy to create a "configuration of projects" (like ConfigurationOfPharo) to bring the collection of related projects together. There probably should be a ConfigurationofWebFrameworks that provides one stop shopping for Aida, Iliad, and Seaside and any other web frameworks... Dale ----- "Miguel Enrique CobÃ¡ Martinez" <miguel.coba(a)gmail.com> wrote: | El mar, 26-01-2010 a las 17:14 -0800, Dale Henrichs escribiÃ³: | > First load the configuration: | > Gofer new | > squeaksource: 'MetacelloRepository'; | > package: 'ConfigurationOfSeaside'; | > load. | > | > Then pick the Seaside variant you want to load: | > | > "Seaside 2.8" | > ConfigurationOfSeaside project latestVersion load: 'Seaside 2.8'. | > ConfigurationOfSeaside project latestVersion load: 'Seaside 2.8 | Examples'. | > ConfigurationOfSeaside project latestVersion load: 'Magritte'. | > ConfigurationOfSeaside project latestVersion load: 'Magritte | Tests'. | > ConfigurationOfSeaside project latestVersion load: 'Pier'. | > ConfigurationOfSeaside project latestVersion load: 'Pier Tests'. | > ConfigurationOfSeaside project latestVersion load: 'Pier AddOns'. | > | > "Seaside 3.0" | > ConfigurationOfSeaside project latestVersion load: 'Seaside 3.0'. | > ConfigurationOfSeaside project latestVersion load: 'Seaside 3.0 | Tests'. | > ConfigurationOfSeaside project latestVersion load: 'Magritte2'. | > ConfigurationOfSeaside project latestVersion load: 'Magritte2 | Tests'. | > ConfigurationOfSeaside project latestVersion load: 'Pier2'. | > ConfigurationOfSeaside project latestVersion load: 'Pier2 Tests'. | > ConfigurationOfSeaside project latestVersion load: 'Pier2 | AddOns'. | > | > I've tested the various loads with PharoCore-1.0-10508rc2. Should | work fine in Dev variants as well... | > | | Hi Dale, | | first I thought that you had merged the ConfigurationOfSeaside28 and | ConfigurationOfSeaside30 in a single configuration but I saw, when | loading this new config, that it only references the old ones. | There is a reason to do this and not to unify them in a single | package? | | I must say that externally isn't a problem, it works perfect. Just | want | to know the "how-to" part of this. Maybe there is some guideline | underlying here that I would like to know :) | | Thanks | | | | > Dale | > | > _______________________________________________ | > Pharo-project mailing list | > Pharo-project(a)lists.gforge.inria.fr | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | | -- | Miguel CobÃ¡ | http://miguel.leugim.com.mx

2 1

[Pharo-project] Monticello diff between chosen revisions is broken
by Stefan Marr Jan. 28, 2010

Jan. 28, 2010

Hi: In the current dev image (10508), Monticello is broken with respect to showing the differences of between chosen revisions. However, that seems to be broken already in 10496. (and maybe earlier) To reproduce: 1. Open Monticello Browser 2. Select a repo 3. click open 4. Select a revision, not the latest one 5. Click diff 6. chose an ancestor from the list Now you got a window 'Version: ...5' Saying (Diff against ...2) Here I would expect the changes button to open a window showing the changes between the chosen revisions, but it always diffs against the latest version. Best Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525

6 17

Jan. 28, 2010

Hi all I was reading a bit squeak and PopUpMorph is only used in MVCUiManager. So this reminded me that we should - replace PopUpMenu by UIManager default... - UIManager... uses MenuMorph - Remove PopUpMenu - funnel some MenuMorph usage to UIManager default. What the ui guys think? Stef

3 2