- Pharo-dev - lists.pharo.org

[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

[Pharo-project] clarifying PopUpMenu vs. MenuMorph
by StÃ©phane Ducasse Jan. 28, 2010

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

[Pharo-project] What happens with new preferences?
by Mariano Martinez Peck Jan. 28, 2010

Jan. 28, 2010

Hi Alain. I have a simple question. I know you migrated all preferences from 1.0 to 1.1 to your new cool scheme. Now....what happened with the new preferences that we crated in 1.0 since you did the migration ? Is there a list of "pending" migrations so that we are aware to put them then in 1.1 ? Right now I remember two: - Enable/disable the update stream - Use old / new NetNameResolver. Cheers Mariano

2 1

[Pharo-project] [ANN] Video Course on Smalltalk
by Davide Varvello Jan. 28, 2010

Jan. 28, 2010

I apologize for this brief announcement, but I'm really happy to tell you that I've been working on a video course on Smalltalk. Now the first video is available and all the lessons can be pre-ordered here http://it.thinkcode.tv/catalogo/programmare-in-smalltalk/ Actually the course is in Italian, but there will be an English version soon. I mainly use Pharo so the community should be happy :-). Thanks Davide

5 13

[Pharo-project] Behaviour of the FileDialogWindow (Was: How do I save the contents of a Workspace?)
by George Herolyants Jan. 28, 2010

Jan. 28, 2010

2010/1/25 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: > Gary, > > IMHO, the correct result is the file name. First, Squeak's streams are, how do I put this nicely... Second, there are some plaform dependencies re ownership. Finally, somebody might want to try Nile. > > Bill > Exactly! Another use case might be when I just don't want to save a file immediately. So, I agree with Bill, the correct behaviour for the FileDialogWindow is to return the full file name and let its user do what it want. The same for the opening of a file. Maybe even these cases can be merged into the one. > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Gary Chambers > Sent: Monday, January 25, 2010 9:57 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] [newbee] How do I save the contentsofaWorkspace? > > Actually rather more complicated than that... > You'll want the full path I expect, also the correct OK button enablement... > > Any reason not to have the FileStream? > > Regards, Gary > > ----- Original Message ----- > From: "Gary Chambers" <gazzaguru2(a)btinternet.com> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Monday, January 25, 2010 2:50 PM > Subject: Re: [Pharo-project] [newbee] How do I save the contentsofaWorkspace? > > >> Not at present. >> Have a look at FileDialogWindow. >> Perhaps you could add a couple of methods... >> >> saveSelectedFile >> "Answer the name of the selected file or new filename or nil if blank." >> >> |d f| >> d := self selectedFileDirectory ifNil: [^nil]. >> f := self selectedFileName ifNil: [self fileNameText withBlanksTrimmed]. >> ^f ifEmpty: [nil]. >> >> answerSaveFileName >> "Set the receiver to answer the selected/entered file name." >> >> self actionSelector: #saveSelectedFileName. >> self changed: #okEnabled >> >> >> Then, to open one... >> >> |fd| >> fd := FileDialogWindow new >> title: title; >> answerSaveFileName. >> ^(modalParentMorph openModal: fd) answer >> >> Choosing an appropriate modal owner. >> If you want, you could add the convenience methods to TEasilyThemed >> also... >> >> Regards, Gary >> >> ----- Original Message ----- >> From: "George Herolyants" <george.herolyants(a)gmail.com> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Monday, January 25, 2010 12:37 PM >> Subject: Re: [Pharo-project] [newbee] How do I save the contents >> ofaWorkspace? >> >> >>> 2010/1/25 Gary Chambers <gazzaguru2(a)btinternet.com>: >>>> The base UIManager code has no accessors for file saving, though >>>> Polymorph does support such a dialog... >>>> >>>> Try >>>> >>>> UITheme builder fileSave: "Your dialog title here' >>> >>> Thanks Gary! But is there a way to force this dialog to return just >>> file name and not to create a file stream? >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

3 3

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

Jan. 28, 2010

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... Dale

2 1

[Pharo-project] Code Formatting
by Mike Hales Jan. 28, 2010

Jan. 28, 2010

I'm cross posting this because my question is both about Squeak Trunk and Pharo. Feel free to respond only in your respective lists if you want. I'm running on Snow Leopard. I'm getting a package ready that I want to publish, and I wanted to test it on both on Pharo and Squeak Trunk, and both are bothering me a little. Squeak - I'm using the latest pre-built trunk image, updated with the update button. The command-r (pretty print) shortcut only seems to work if the selectors list has the mouse focus, not the code pane. Then after pretty printing, to save the source, I have to move the mouse focus back to the code pane, where command-s will save the change. If I have to move the mouse around what good is the shortcut? Pharo - I using the latest Pharo 1.0 release candidate (dev not core) It seems like the coloring, and automatic completion work right out of the box, but when I choose "format" from the code pane context menu, nothing happens. Do I need to load something else? Also, if it were to work, what would I have to do to get a keyboard shortcut for it. Since so many of you write so much more code than me, I imagine that there are simple solutions. And while we're here, I wouldn't mind some suggestions regarding how to "pimp my image" so to speak, to make the development flow better. Thanks, Mike Mike Hales Engineering Manager KnowledgeScape www.kscape.com

3 2