[Pharo-dev] [update 3.0] #30411
30411 - 11603 Better name for Critics UI https://pharo.fogbugz.com/f/cases/11603 11638 remove not used class variables in WeakFinalizationList https://pharo.fogbugz.com/f/cases/11638 11636 Fix Form #asGrayScaleWithAlpha https://pharo.fogbugz.com/f/cases/11636 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Tests-Core-MarcusDenker.80.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Pharo-Platform-MarcusDenker.4.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Critics-MarcusDenker.70.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Core-MarcusDenker.219.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Manifest-CriticBrowser-MarcusDenker.116.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Graphics-Display Objects-MarcusDenker.128.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Collections-Weak-MarcusDenker.84.diff signature.asc Description: Message signed with OpenPGP using GPGMail
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=win/515/ 1 regressions found. Zinc.Zodiac.ZnHTTPSTests.testGetPharoVersion
Re: [Pharo-dev] Please help us by buying the book
On Thu, Sep 19, 2013 at 10:36 PM, kilon theki...@yahoo.co.uk wrote: Just ordered the book in Lulu. Please don't spend all my money on beer :D thank you very much kilon -- Damien Cassou http://damiencassou.seasidehosting.st Success is the ability to go from one failure to another without losing enthusiasm. Winston Churchill
Re: [Pharo-dev] about the memory leak in Pharo2/Pharo3
thanks It will help us. We got some internal reorganisation right now because fernando is leaving the team. stef On Sep 19, 2013, at 10:42 PM, GOUBIER Thierry thierry.goub...@cea.fr wrote: Ok, I've added issue 11639 for the backport. I'll make a try tonight. Thierry De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de Esteban Lorenzano [esteba...@gmail.com] Date d'envoi : jeudi 19 septembre 2013 17:33 À : Pharo Development List Objet : Re: [Pharo-dev] about the memory leak in Pharo2/Pharo3 is a really annoying combination of problems: 1) the abuse of on:do: for register announcers, usually in SystemAnnouncer singleton, who then register immortal announcements. 2) the abuse of weak message in places where is not needed (like in non global announcements who then will be collected when owner collected) 3) a weird case when instead a WeakAnnouncementSubscription, system was registering LegacyWeakSubscription, and this one uses WeakRegistry (which is a singleton too)... so, if combined with #on:do:, the subscriptions were becoming immortal too. So far, we think that is all the problem. You need two steps (the 3rd was because I forgot to commit something :p) because after changing somethign in the finalization process, you then need to restart it to be able to remove old/not used methods. cheers, Esteban On Sep 19, 2013, at 5:30 PM, Goubier Thierry thierry.goub...@cea.fr wrote: Le 19/09/2013 17:20, Esteban Lorenzano a écrit : Hi, I just submitted and integrated a fix for the leak problem. That should fix the problem we are having in Pharo3... now we need to work on a backport for Pharo2... any takers? :) I need some explanations :) Thierry Esteban -- 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
Re: [Pharo-dev] CI for OSWin
I got the problem, ZeroConf scripts use the find command and there was a PATH problem on the slave running your job. It used the windows find command and not the mingw one. It is now fixed and your job is now better ... but not yet green. It misses the test XML output file. It may be to a wrong regexp OSWindows.* for your test packages. Regards, Christophe. Le 20 sept. 2013 à 09:55, Christophe Demarey a écrit : Hello, To see what happens, you need to first click on a specific build in the matrix job, then you can browse a particular build and is console output. ex: https://ci.inria.fr/pharo-contribution/job/OSWindows/12/PHARO=30,VERSION=stable,VM=vm,Windows%20Slaves%20only=win/console Here the problem seems to come from the definition of the Windows Slaves label that generates a directory with this name. I would rather put a fixed value and replace export JOB_NAME=`dirname $JOB_NAME` by export JOB_NAME=OSWindows I did some changes and triggered a new build manually. But it also failed. It looks like the zeroConf script is broken on windows. We will take a look at it. Regards, Christophe. Le 20 sept. 2013 à 09:31, Torsten Bergmann a écrit : I created a CI project for OS-Windows according to the written steps on the creation page. It failed - and I checked the CI scripts. Since it was named OS-Windows and there was a $JOB_NAME variable in the script I better changed the script to use OSWindow for image name, ... (to avoid problems with character -. https://ci.inria.fr/pharo-contribution/job/OSWindows/ Still it fails - telling me something about no workspace. I now renamed it to OSWindows and situation is the same. Note that the tests should run only on Pharo 3.0 with a windows slave - that is how the configuration is currently setup. There is a ConfigurationOfOSWindows with #stable and #development, so ConfigurationOfOSWindows project version: #development ConfigurationOfOSWindows project version: #stable return something to load. Also the repo is correctly setup. Dont know what's missing - maybe someone with access can have a look. Thanks T. smime.p7s Description: S/MIME cryptographic signature
[Pharo-dev] [update 3.0] #30412
30412 - 11637 Special Object Array not in sync with VM https://pharo.fogbugz.com/f/cases/11637 11642 Small Code-Critic cleanup of FilePackage https://pharo.fogbugz.com/f/cases/11642 11640 Guard pretty printing of AST when using RBLiteralNode for non-Literals https://pharo.fogbugz.com/f/cases/11640 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-MarcusDenker.914.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-FilePackage-MarcusDenker.101.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1616.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/AST-Core-MarcusDenker.193.diff signature.asc Description: Message signed with OpenPGP using GPGMail
[Pharo-dev] Dynamically adding nodes to Roassal
Hi, I was playing around with Roassal (in particular, a tree map) and I have a question: Is there a way to dynamically adding nodes? I mean, once the view is generated to update the #nodes by adding a new node (and associations as well, i.e., edges) and have the visualization re- Thanks in advance. Roby
Re: [Pharo-dev] Dynamically adding nodes to Roassal
*and have the visualization re-layouted? On Sep 20, 2013, at 11:24 AM, roberto.mine...@usi.ch roberto.mine...@usi.ch wrote: Hi, I was playing around with Roassal (in particular, a tree map) and I have a question: Is there a way to dynamically adding nodes? I mean, once the view is generated to update the #nodes by adding a new node (and associations as well, i.e., edges) and have the visualization re- Thanks in advance. Roby
Re: [Pharo-dev] Dynamically adding nodes to Roassal
In Roassal calling the method #signalUpdate to the view should show those new nodes. If you want to re-layout the nodes you should apply a new layout to the nodes before the #signalUpdate. Another pretty interesting feature is the method ROContainercallback: aCallback. The idea is that every time an element is added inside the container the callback is called. Now how you can use this: element callback: (ROContainerCallbackLayout new layout: (ROGridLayout new gapSize: 2)). Remember that you must send signalUpdate to the view if you want to see the changes. Another thing bothering me is that you mentioned the method #nodes, thats from the ROMondrianViewBuilder, which I think is not that friendly with dynamic stuff. It is a little bit ugly but you can always get the ROView from ROMondrianViewBuilder sending the message #view and over that do all kind of Roassal magic stuff, like adding the callback with the TreeLayout the the ROView itself. Also for adding new nodes you should add them directly to the ROView, or at least I haven't found the way to do that without having to add all the nodes again to the Builder. Hope that help you. 2013/9/20 roberto.mine...@usi.ch roberto.mine...@usi.ch *and have the visualization re-layouted? On Sep 20, 2013, at 11:24 AM, roberto.mine...@usi.ch roberto.mine...@usi.ch wrote: Hi, I was playing around with Roassal (in particular, a tree map) and I have a question: Is there a way to dynamically adding nodes? I mean, once the view is generated to update the #nodes by adding a new node (and associations as well, i.e., edges) and have the visualization re- Thanks in advance. Roby
Re: [Pharo-dev] Stability of 3.0
Le 20/09/2013 12:20, Stéphane Ducasse a écrit : On Sep 20, 2013, at 12:16 PM, Goubier Thierry thierry.goub...@cea.fr wrote: That's a problem with one of the fixes I have to carry around on 3.0. I'll update it, thanks. ok let us knw how we can help. Hum, fix 11102/11142? There is a partial fix in 11528 which was integrated, but I don't feel confortable with it, so I prefer overwritting it in my image. Thierry Stef Thierry Le 20/09/2013 11:54, Stéphane Ducasse a écrit : thierry do you have a scenario that I could reproduce. stef On Sep 19, 2013, at 5:36 PM, Goubier Thierry thierry.goub...@cea.fr wrote: TranslucentPatterns is undefined. Error: Instances of UndefinedObject are not indexable in FormCanvastranslucentMaskFor:depth: Thierry Le 19/09/2013 17:24, Stéphane Ducasse a écrit : On Sep 19, 2013, at 5:24 PM, Goubier Thierry thierry.goub...@cea.fr wrote: Hi all, is it me or what? The latest 3.0 gives me a lot of red squares a bit everywhere around the place, making working with it a bit (a lot!) painful. I do not know because busy with lecture writing and managing mess. Can you grab the debug button (I know this is unclear) but if you get the faulty morph you can get a debugger and we can see what is the message that is failing. It saved lot of work and frsutration because you know why you get the red cross of death. Stef I'm on 30407, frech from get.pharo.org. Thierry -- 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 -- 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 -- 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 -- 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
Re: [Pharo-dev] Dynamically adding nodes to Roassal
Thanks Alejandro, I will try what you propose! What do you mean by Another thing bothering me is that you mentioned the method #nodes, thats from the ROMondrianViewBuilder, which I think is not that friendly with dynamic stuff. How would you construct a view without using the ROMondrianViewBuilder? I am used to start as in the Roassal Easel like rawView := ROView new. view := ROMondrianViewBuilder view: rawView And then adding nodes to the view, calling view nodes: myNodes Cheers, R On Sep 20, 2013, at 1:49 PM, Alejandro Infante alejandroinfant...@gmail.com wrote: In Roassal calling the method #signalUpdate to the view should show those new nodes. If you want to re-layout the nodes you should apply a new layout to the nodes before the #signalUpdate. Another pretty interesting feature is the method ROContainercallback: aCallback. The idea is that every time an element is added inside the container the callback is called. Now how you can use this: element callback: (ROContainerCallbackLayout new layout: (ROGridLayout new gapSize: 2)). Remember that you must send signalUpdate to the view if you want to see the changes. Another thing bothering me is that you mentioned the method #nodes, thats from the ROMondrianViewBuilder, which I think is not that friendly with dynamic stuff. It is a little bit ugly but you can always get the ROView from ROMondrianViewBuilder sending the message #view and over that do all kind of Roassal magic stuff, like adding the callback with the TreeLayout the the ROView itself. Also for adding new nodes you should add them directly to the ROView, or at least I haven't found the way to do that without having to add all the nodes again to the Builder. Hope that help you. 2013/9/20 roberto.mine...@usi.ch roberto.mine...@usi.ch *and have the visualization re-layouted? On Sep 20, 2013, at 11:24 AM, roberto.mine...@usi.ch roberto.mine...@usi.ch wrote: Hi, I was playing around with Roassal (in particular, a tree map) and I have a question: Is there a way to dynamically adding nodes? I mean, once the view is generated to update the #nodes by adding a new node (and associations as well, i.e., edges) and have the visualization re- Thanks in advance. Roby
Re: [Pharo-dev] Grease conflicts #packages with RPackage
On Fri, Sep 20, 2013 at 7:53 AM, Stéphane Ducasse stephane.duca...@inria.fr wrote: I do not understand why it would be a GreasePackage What are grease package? if grease override the packages messages then I do not see why it would be a pharo bug. This is like if you redefine class and returns something else. Indeed. It is as simple as that. Grease is overriding a class side method #packages which is a collision to Pharo core and hence fails the load because #packages for that class answers its own type of packages rather than the expected by Pharo. Again, a simply rename of GRPackage class packages would be enough. And it has only one sender (a test) in the image I have Stef On Sep 6, 2013, at 3:21 PM, Mariano Martinez Peck marianop...@gmail.com wrote: Anyone? On Wed, Aug 28, 2013 at 2:12 PM, Mariano Martinez Peck marianop...@gmail.com wrote: Hi guys, I was trying to build a new image with latest Pharo 2.0 with all the frameworks I use. While installing, I get a dnu in: packageFromOrganizer: anRPackageOrganizer This method returns the package this method belongs to. It takes into account classes and traits. If the method is in no package, returns nil by now self flag: 'TODO: use anRPackageOrganizer, or better delegate to anRPackageOrganizer'. ^self origin packages detect: [ :each | (each includesSelector: self selector ofClassName: self origin theNonMetaClass originalName) or: [ each includesSelector: self selector ofMetaclassName: self origin theNonMetaClass originalName]] ifNone: [ nil ] because each (which was GRPackage) dnu #includesSelector:ofClassName: Problem is that self origin answers GRPackage. And GRPackage DOES implement a CLASS side method #packages that answers instances of GRPackage.not RPackage... So...which one do we prefix? GRPackage class #packages to #greasePackages? BTW, there are yet more class side implementations of #packages, which are basically subclasses for the HelpSystem (CustomHelp). So we have for example SUnitAPIDocumentation, RegexAPIDocumentation, ProfStefAPIHelp, HelpAPIDocumentation, AnnouncementsAPIDocumentation. Guess we should update the HelpSystem as well? Let me know and I open issues/submit fixes. Cheers, -- Mariano http://marianopeck.wordpress.com -- Mariano http://marianopeck.wordpress.com -- Mariano http://marianopeck.wordpress.com
[Pharo-dev] [update 3.0] #30413
30413 - 11607 Small Code Critic cleanup of Morphic-Base https://pharo.fogbugz.com/f/cases/11607 11634 diffmorph icons should not use generic names https://pharo.fogbugz.com/f/cases/11634 11643 add replacement methods for #isLiteral in IRLiteral and OCLiteralVariable https://pharo.fogbugz.com/f/cases/11643 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/SmartSuggestions-MarcusDenker.108.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Core-MarcusDenker.221.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-MarcusDenker.919.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Tools-Diff-MarcusDenker.117.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Core-MarcusDenker.405.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-MarcusDenker.112.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/EventModel-MarcusDenker.3.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Compiler-MarcusDenker.529.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/AST-Tests-Core-MarcusDenker.37.diff signature.asc Description: Message signed with OpenPGP using GPGMail
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=mac/518/ 1 regressions found. Tests.Release.ReleaseTest.testUndeclared
[Pharo-dev] [regression reporter]regression occurred
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=win/518/ 1 regressions found. Tests.Release.ReleaseTest.testUndeclared
Re: [Pharo-dev] Dynamically adding nodes to Roassal
roberto.mine...@usi.ch wrote: *and have the visualization re-layouted? On Sep 20, 2013, at 11:24 AM, "roberto.mine...@usi.ch" roberto.mine...@usi.ch wrote: Hi, I was playing around with Roassal (in particular, a tree map) and I have a question: Is there a way to dynamically adding nodes? I mean, once the view is generated to update the #nodes by adding a new node (and associations as well, i.e., edges) and have the visualization re- Thanks in advance. Roby Have a look at [1], section 5.6.2 LEKCimDynamicTreeLayout Note however that my project was based entirely on using raw ROView, rather than ROMondrianViewBuilder. [1] http://files.openinworld.com/LEKtrek/BenjaminTerrenceCOMAN-LEKtrek-2013-08-21.pdf
Re: [Pharo-dev] Dynamically adding nodes to Roassal
Thanks Alejandro, Yes I went through the examples and I understood the difference between the examples using the builder (which are easier) and with pure Roassal, which are..let's say.. less user friendly.. I am trying, in pure Roassal, to do a tree map and add another node to the ROView then calling signalUpdate. No luck 'till now.. Cheers, R On Sep 20, 2013, at 3:01 PM, Alejandro Infante alejandroinfant...@gmail.com wrote: Well, If you started with the Easel then you must have seen the examples. Well at first you see two boxes with examples inside (one on the top and the other below (If you dont see the second one just drag the view). The first one has a label at the top-left corner that says ROMondrianExample, and this were done using the ROMondrianViewBuilder API, and you can see that you interact mainly with the view variable. The second box is called ROExample and then you interact mainly with the rawView variable which is pure Roassal. The difference between them is that the ROMondrianViewBuilder is a nice and friendly API, but doing really complex stuff it's not possible. So we go one level below to pure Roassal. Here you have the Collection class hierarchy in Roassal: |rawView| rawView := ROView new. Collection withAllSubclasses do: [ :c | | el | el := ROBorder elementOn: c. el @ ROPopup. rawView add: el ]. Draw edges rawView addAll: (ROEdge buildEdgesFromElements: rawView elements from: [ :cls | cls superclass ] to: #yourself using: ROLine new). ROTreeLayout on: rawView elementsNotEdge edges: rawView elementsAsEdge. rawView open. I recommend you to see the ROExamples and if there is something that you don't know just ask to the mailing list. You may like to see the ROExamplesinteractionsaddingOnClick example. 2013/9/20 roberto.mine...@usi.ch roberto.mine...@usi.ch Thanks Alejandro, I will try what you propose! What do you mean by Another thing bothering me is that you mentioned the method #nodes, thats from the ROMondrianViewBuilder, which I think is not that friendly with dynamic stuff. How would you construct a view without using the ROMondrianViewBuilder? I am used to start as in the Roassal Easel like rawView := ROView new. view := ROMondrianViewBuilder view: rawView And then adding nodes to the view, calling view nodes: myNodes Cheers, R On Sep 20, 2013, at 1:49 PM, Alejandro Infante alejandroinfant...@gmail.com wrote: In Roassal calling the method #signalUpdate to the view should show those new nodes. If you want to re-layout the nodes you should apply a new layout to the nodes before the #signalUpdate. Another pretty interesting feature is the method ROContainercallback: aCallback. The idea is that every time an element is added inside the container the callback is called. Now how you can use this: element callback: (ROContainerCallbackLayout new layout: (ROGridLayout new gapSize: 2)). Remember that you must send signalUpdate to the view if you want to see the changes. Another thing bothering me is that you mentioned the method #nodes, thats from the ROMondrianViewBuilder, which I think is not that friendly with dynamic stuff. It is a little bit ugly but you can always get the ROView from ROMondrianViewBuilder sending the message #view and over that do all kind of Roassal magic stuff, like adding the callback with the TreeLayout the the ROView itself. Also for adding new nodes you should add them directly to the ROView, or at least I haven't found the way to do that without having to add all the nodes again to the Builder. Hope that help you. 2013/9/20 roberto.mine...@usi.ch roberto.mine...@usi.ch *and have the visualization re-layouted? On Sep 20, 2013, at 11:24 AM, roberto.mine...@usi.ch roberto.mine...@usi.ch wrote: Hi, I was playing around with Roassal (in particular, a tree map) and I have a question: Is there a way to dynamically adding nodes? I mean, once the view is generated to update the #nodes by adding a new node (and associations as well, i.e., edges) and have the visualization re- Thanks in advance. Roby
[Pharo-dev] How to browse SmalltalkHub ?
I see in smalltalkhub there is an explore button, but it only displays a very small fragment of available projects. Is there a way to explore smalltalkhub and find all the available projects ? -- View this message in context: http://forum.world.st/How-to-browse-SmalltalkHub-tp4709355.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] Dynamically adding nodes to Roassal
I started yesterday to read the chapter. I bought the book at ESUG. :D On Sep 20, 2013, at 3:13 PM, Alejandro Infante alejandroinfant...@gmail.com wrote: Also I forgot to tell you that the new book Deep into Pharo has a chapter for Roassal and another for Mondrian. Maybe that's the best place to start from, the link of the book is http://rmod.lille.inria.fr/pbe2/. 2013/9/20 roberto.mine...@usi.ch roberto.mine...@usi.ch Thanks Alejandro, Yes I went through the examples and I understood the difference between the examples using the builder (which are easier) and with pure Roassal, which are..let's say.. less user friendly.. I am trying, in pure Roassal, to do a tree map and add another node to the ROView then calling signalUpdate. No luck 'till now.. Cheers, R On Sep 20, 2013, at 3:01 PM, Alejandro Infante alejandroinfant...@gmail.com wrote: Well, If you started with the Easel then you must have seen the examples. Well at first you see two boxes with examples inside (one on the top and the other below (If you dont see the second one just drag the view). The first one has a label at the top-left corner that says ROMondrianExample, and this were done using the ROMondrianViewBuilder API, and you can see that you interact mainly with the view variable. The second box is called ROExample and then you interact mainly with the rawView variable which is pure Roassal. The difference between them is that the ROMondrianViewBuilder is a nice and friendly API, but doing really complex stuff it's not possible. So we go one level below to pure Roassal. Here you have the Collection class hierarchy in Roassal: |rawView| rawView := ROView new. Collection withAllSubclasses do: [ :c | | el | el := ROBorder elementOn: c. el @ ROPopup. rawView add: el ]. Draw edges rawView addAll: (ROEdge buildEdgesFromElements: rawView elements from: [ :cls | cls superclass ] to: #yourself using: ROLine new). ROTreeLayout on: rawView elementsNotEdge edges: rawView elementsAsEdge. rawView open. I recommend you to see the ROExamples and if there is something that you don't know just ask to the mailing list. You may like to see the ROExamplesinteractionsaddingOnClick example. 2013/9/20 roberto.mine...@usi.ch roberto.mine...@usi.ch Thanks Alejandro, I will try what you propose! What do you mean by Another thing bothering me is that you mentioned the method #nodes, thats from the ROMondrianViewBuilder, which I think is not that friendly with dynamic stuff. How would you construct a view without using the ROMondrianViewBuilder? I am used to start as in the Roassal Easel like rawView := ROView new. view := ROMondrianViewBuilder view: rawView And then adding nodes to the view, calling view nodes: myNodes Cheers, R On Sep 20, 2013, at 1:49 PM, Alejandro Infante alejandroinfant...@gmail.com wrote: In Roassal calling the method #signalUpdate to the view should show those new nodes. If you want to re-layout the nodes you should apply a new layout to the nodes before the #signalUpdate. Another pretty interesting feature is the method ROContainercallback: aCallback. The idea is that every time an element is added inside the container the callback is called. Now how you can use this: element callback: (ROContainerCallbackLayout new layout: (ROGridLayout new gapSize: 2)). Remember that you must send signalUpdate to the view if you want to see the changes. Another thing bothering me is that you mentioned the method #nodes, thats from the ROMondrianViewBuilder, which I think is not that friendly with dynamic stuff. It is a little bit ugly but you can always get the ROView from ROMondrianViewBuilder sending the message #view and over that do all kind of Roassal magic stuff, like adding the callback with the TreeLayout the the ROView itself. Also for adding new nodes you should add them directly to the ROView, or at least I haven't found the way to do that without having to add all the nodes again to the Builder. Hope that help you. 2013/9/20 roberto.mine...@usi.ch roberto.mine...@usi.ch *and have the visualization re-layouted? On Sep 20, 2013, at 11:24 AM, roberto.mine...@usi.ch roberto.mine...@usi.ch wrote: Hi, I was playing around with Roassal (in particular, a tree map) and I have a question: Is there a way to dynamically adding nodes? I mean, once the view is generated to update the #nodes by adding a new node (and associations as well, i.e., edges) and have the visualization re- Thanks in advance.
Re: [Pharo-dev] [PBE] May be we should first just change PBE in git in Latex.
Stphane Ducasse wrote: Hi yuri May be we should first just change PBE in git in Latex. I do not know how to tag a new branch but I like the description made by ben. Thanks Stef. It was unfortunate that I didn't get as far as I would have liked, before I got over committed with work and study. Now that most of my Masters out of the way I was thinking of having another go, but still a few things to clean up. cheers -ben I should add, I got as far as completing the first chapter, which can be pulled from [1]. Check out [2] to get started. [1] https://github.com/bencoman/PharoByExample-english [2] http://blog.openinworld.com/2012/05/contributing-to-pbe/ What I'm doing is collecting a list of changes from the sbe archive list https://docs.google.com/document/d/1lVOTw2d5Bqv_49XPZ9MwUF6zDbsLWf8l7ev2NAgHhhg/edit stef
Re: [Pharo-dev] Dynamically adding nodes to Roassal
Thanks for the reference! On Sep 20, 2013, at 3:02 PM, b...@openinworld.com wrote: Have a look at [1], section 5.6.2 LEKCimDynamicTreeLayout Note however that my project was based entirely on using raw ROView, rather than ROMondrianViewBuilder. [1] http://files.openinworld.com/LEKtrek/BenjaminTerrenceCOMAN-LEKtrek-2013-08-21.pdf
Re: [Pharo-dev] Stability of 3.0
if the problem is caused by you then its good news, much easier to fix ;) So what caused the problem in the first place ? Goubier Thierry wrote That was why I asked, to see if the problem was with my config or general. It was with my stuff :( Thierry Le 20/09/2013 15:14, kilon a écrit : I dont have such problem. The problem I had was code completion having several errors while it tried to autocomplete and once I froze pharo because I changed a live object while the morph was displaying , that method was somewhat recycled (HelpBrowser class) so that may have been normal. But no problem with red boxes from what I can see, I am on 30402. -- View this message in context: http://forum.world.st/Stability-of-3-0-tp4709185p4709358.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. -- 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 -- View this message in context: http://forum.world.st/Stability-of-3-0-tp4709185p4709364.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] Stability of 3.0
On Sep 20, 2013, at 3:41 PM, kilon theki...@yahoo.co.uk wrote: if the problem is caused by you then its good news, much easier to fix ;) So what caused the problem in the first place ? issue with fileSystem handling non readable folder or something like that. Goubier Thierry wrote That was why I asked, to see if the problem was with my config or general. It was with my stuff :( Thierry Le 20/09/2013 15:14, kilon a écrit : I dont have such problem. The problem I had was code completion having several errors while it tried to autocomplete and once I froze pharo because I changed a live object while the morph was displaying , that method was somewhat recycled (HelpBrowser class) so that may have been normal. But no problem with red boxes from what I can see, I am on 30402. -- View this message in context: http://forum.world.st/Stability-of-3-0-tp4709185p4709358.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. -- 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 -- View this message in context: http://forum.world.st/Stability-of-3-0-tp4709185p4709364.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] Stability of 3.0
I see, much more simple than I expected :) -- View this message in context: http://forum.world.st/Stability-of-3-0-tp4709185p4709370.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] Stability of 3.0
I see, well if you want a macos platform to test I offer myself as a Guinea Pig :) Macos has even a diffirent filesystem to Linux and Windoom. Making our life easier to porting stuff :D Maybe a solution would be to find a cross platform C lib that works the same in all major 3 OS. Goubier Thierry wrote Le 20/09/2013 15:41, kilon a écrit : if the problem is caused by you then its good news, much easier to fix ;) So what caused the problem in the first place ? I carry around an old fix for 2.0 and 3.0 for a red square of death in the file browser (red square only in 3.0). Since this fix is a change to a GUI element, it conflicts everytime the main package is changed. And the last one was the TranslucentColor thing :( In truth, it carries along a more serious fix, but that I have only done partially, which makes Pharo correctly handle file permissions. I did a Linux-only fix relying on NativeBoost for the time being, given that: - I dont have a Mac OSX machine to check it (have to use a different C API. I thought the Unix platform means Linux, but it seems to also cover OSX) - I had a no go from Igor for my ideas about solving a NativeBoost difficulty on startup, and I gave up writing a more complex fix that I don't need at the moment and which won't be integrated anyway. I'll write it if I need it :P In the mean-time, I get the benefits: in my developpement, if I test that a file is readable, it really is :) However, I need to be carefull tracking down 3.0 progress, that's all, and failures are not allways obvious (this one wasn't). Thierry Goubier Thierry wrote That was why I asked, to see if the problem was with my config or general. It was with my stuff :( Thierry Le 20/09/2013 15:14, kilon a écrit : I dont have such problem. The problem I had was code completion having several errors while it tried to autocomplete and once I froze pharo because I changed a live object while the morph was displaying , that method was somewhat recycled (HelpBrowser class) so that may have been normal. But no problem with red boxes from what I can see, I am on 30402. -- View this message in context: http://forum.world.st/Stability-of-3-0-tp4709185p4709358.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. -- 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 -- View this message in context: http://forum.world.st/Stability-of-3-0-tp4709185p4709364.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. -- 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 -- View this message in context: http://forum.world.st/Stability-of-3-0-tp4709185p4709372.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] Stability of 3.0
Can you tell me if the result of DiskStore current is a MacStore ? Thierry Le 20/09/2013 16:07, kilon a écrit : I see, well if you want a macos platform to test I offer myself as a Guinea Pig :) Macos has even a diffirent filesystem to Linux and Windoom. Making our life easier to porting stuff :D Maybe a solution would be to find a cross platform C lib that works the same in all major 3 OS. Goubier Thierry wrote Le 20/09/2013 15:41, kilon a écrit : if the problem is caused by you then its good news, much easier to fix ;) So what caused the problem in the first place ? I carry around an old fix for 2.0 and 3.0 for a red square of death in the file browser (red square only in 3.0). Since this fix is a change to a GUI element, it conflicts everytime the main package is changed. And the last one was the TranslucentColor thing :( In truth, it carries along a more serious fix, but that I have only done partially, which makes Pharo correctly handle file permissions. I did a Linux-only fix relying on NativeBoost for the time being, given that: - I dont have a Mac OSX machine to check it (have to use a different C API. I thought the Unix platform means Linux, but it seems to also cover OSX) - I had a no go from Igor for my ideas about solving a NativeBoost difficulty on startup, and I gave up writing a more complex fix that I don't need at the moment and which won't be integrated anyway. I'll write it if I need it :P In the mean-time, I get the benefits: in my developpement, if I test that a file is readable, it really is :) However, I need to be carefull tracking down 3.0 progress, that's all, and failures are not allways obvious (this one wasn't). Thierry Goubier Thierry wrote That was why I asked, to see if the problem was with my config or general. It was with my stuff :( Thierry Le 20/09/2013 15:14, kilon a écrit : I dont have such problem. The problem I had was code completion having several errors while it tried to autocomplete and once I froze pharo because I changed a live object while the morph was displaying , that method was somewhat recycled (HelpBrowser class) so that may have been normal. But no problem with red boxes from what I can see, I am on 30402. -- View this message in context: http://forum.world.st/Stability-of-3-0-tp4709185p4709358.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. -- 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 -- View this message in context: http://forum.world.st/Stability-of-3-0-tp4709185p4709364.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. -- 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 -- View this message in context: http://forum.world.st/Stability-of-3-0-tp4709185p4709372.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. -- 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
Re: [Pharo-dev] Stability of 3.0
we will bring this issue during our next meeting. Now we should reorganise a bit ourselves because the texteditor should be finished. stef On Sep 20, 2013, at 4:05 PM, Goubier Thierry thierry.goub...@cea.fr wrote: Le 20/09/2013 15:41, kilon a écrit : if the problem is caused by you then its good news, much easier to fix ;) So what caused the problem in the first place ? I carry around an old fix for 2.0 and 3.0 for a red square of death in the file browser (red square only in 3.0). Since this fix is a change to a GUI element, it conflicts everytime the main package is changed. And the last one was the TranslucentColor thing :( In truth, it carries along a more serious fix, but that I have only done partially, which makes Pharo correctly handle file permissions. I did a Linux-only fix relying on NativeBoost for the time being, given that: - I dont have a Mac OSX machine to check it (have to use a different C API. I thought the Unix platform means Linux, but it seems to also cover OSX) - I had a no go from Igor for my ideas about solving a NativeBoost difficulty on startup, and I gave up writing a more complex fix that I don't need at the moment and which won't be integrated anyway. I'll write it if I need it :P In the mean-time, I get the benefits: in my developpement, if I test that a file is readable, it really is :) However, I need to be carefull tracking down 3.0 progress, that's all, and failures are not allways obvious (this one wasn't). Thierry Goubier Thierry wrote That was why I asked, to see if the problem was with my config or general. It was with my stuff :( Thierry Le 20/09/2013 15:14, kilon a écrit : I dont have such problem. The problem I had was code completion having several errors while it tried to autocomplete and once I froze pharo because I changed a live object while the morph was displaying , that method was somewhat recycled (HelpBrowser class) so that may have been normal. But no problem with red boxes from what I can see, I am on 30402. -- View this message in context: http://forum.world.st/Stability-of-3-0-tp4709185p4709358.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. -- 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 -- View this message in context: http://forum.world.st/Stability-of-3-0-tp4709185p4709364.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. -- 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
Re: [Pharo-dev] [PROVENANCE INTERNET] Re: Stability of 3.0
And try something like '/usr' asFileReference isWritable (I hope that /usr is rw for root on Mac OSX, and ro for everybody else :)) Without the fix, it will say true. It should say false. Thierry Le 20/09/2013 16:27, Goubier Thierry a écrit : Can you tell me if the result of DiskStore current is a MacStore ? Thierry Le 20/09/2013 16:07, kilon a écrit : I see, well if you want a macos platform to test I offer myself as a Guinea Pig :) Macos has even a diffirent filesystem to Linux and Windoom. Making our life easier to porting stuff :D Maybe a solution would be to find a cross platform C lib that works the same in all major 3 OS. Goubier Thierry wrote Le 20/09/2013 15:41, kilon a écrit : if the problem is caused by you then its good news, much easier to fix ;) So what caused the problem in the first place ? I carry around an old fix for 2.0 and 3.0 for a red square of death in the file browser (red square only in 3.0). Since this fix is a change to a GUI element, it conflicts everytime the main package is changed. And the last one was the TranslucentColor thing :( In truth, it carries along a more serious fix, but that I have only done partially, which makes Pharo correctly handle file permissions. I did a Linux-only fix relying on NativeBoost for the time being, given that: - I dont have a Mac OSX machine to check it (have to use a different C API. I thought the Unix platform means Linux, but it seems to also cover OSX) - I had a no go from Igor for my ideas about solving a NativeBoost difficulty on startup, and I gave up writing a more complex fix that I don't need at the moment and which won't be integrated anyway. I'll write it if I need it :P In the mean-time, I get the benefits: in my developpement, if I test that a file is readable, it really is :) However, I need to be carefull tracking down 3.0 progress, that's all, and failures are not allways obvious (this one wasn't). Thierry Goubier Thierry wrote That was why I asked, to see if the problem was with my config or general. It was with my stuff :( Thierry Le 20/09/2013 15:14, kilon a écrit : I dont have such problem. The problem I had was code completion having several errors while it tried to autocomplete and once I froze pharo because I changed a live object while the morph was displaying , that method was somewhat recycled (HelpBrowser class) so that may have been normal. But no problem with red boxes from what I can see, I am on 30402. -- View this message in context: http://forum.world.st/Stability-of-3-0-tp4709185p4709358.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. -- 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 -- View this message in context: http://forum.world.st/Stability-of-3-0-tp4709185p4709364.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. -- 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 -- View this message in context: http://forum.world.st/Stability-of-3-0-tp4709185p4709372.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. -- 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
[Pharo-dev] squeaksource
If I read correctly on http://squeaksource.com/ it should be read-only by now? What is the time-frame? signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [Pharo-dev] Dynamically adding nodes to Roassal
Hi, It's me again.. I managed to have something *almost* working, but the behavior of the ROTreeMapLayout is not clear to me. Using the ROMondrianViewBuilder I can specify the size of the Tree map, but then I am not able to dynamically add nodes. Well, at least I did not manage to do that. So I moved to pure Roassal, as suggested by Alejandro. Here's how my actual code looks like: http://ws.stfx.eu/CFM522Z9X3ES I am a beginner with Roassal, so I spend some time to figure out how to draw the tree map in this way. I did not really quite understand why I have to add the ROBox new size: 200 to the ROElement, but I'll figure it out. The thing is when I try to add the new node. Following, again, Alejandro's advice I am writing something like: I add a new node, re-layout the view, and signalUpdate rawView add: ((ROElement on: 10) + (ROBox new size: 200)). (ROTreeMapLayout withWeightBlock: [ :e | e model ]) applyOn: rawView elements. rawView signalUpdate . The result is quite strange, the view is indeed updated but I cannot understand why all sizes are messed up. My questions, in short are: How can I fix the overall size of the tree map? Am I doing everything correct till now? Thanks again for your help, Roby On Sep 20, 2013, at 11:24 AM, roberto.mine...@usi.ch wrote: Hi, I was playing around with Roassal (in particular, a tree map) and I have a question: Is there a way to dynamically adding nodes? I mean, once the view is generated to update the #nodes by adding a new node (and associations as well, i.e., edges) and have the visualization re- Thanks in advance. Roby
Re: [Pharo-dev] Deprecated selector #metaclass on Smalltalkhub
In my packages I use the metaclass message but not from the pharo meta-level ;) On Fri, Sep 20, 2013 at 8:34 PM, Stephan Eggermont step...@stack.nl wrote: These projects and packageversions on Smalltalkhub use the #metaclass selector. This might refer to a deprecated selector, replaced by #theMetaClass The packageversions were selected as latest+not merged gokr/DeltaStreams System-gk.143 StephaneDucasse/ArchiveTraits TraitsUI-al.19 StephaneDucasse/ArchiveTraits TraitsUI-al.21 StephaneDucasse/ArchiveTraits TraitsUI-al.2 StephaneDucasse/ArchiveTraits System-al.55 StephaneDucasse/ArchiveTraits System-al.85 StephaneDucasse/ArchiveTraits System-al.52 StephaneDucasse/ArchiveTraits System-al.63 AnneEtien/RingJET Ring-History-Definitions-VeronicaUquillas.104 AnneEtien/RingJET Ring-Core-Kernel-MarcusDenker.90 BenjaminVanRyseghem/NemoNemo-BenjaminVanRyseghem.21 andrehora/FindBugs Refactoring-Critics-AndreHora.18 andrehora/HoraExp Moose-Tests-SmalltalkImporter-Core-AndreHora.29 andrehora/HoraExpTemp Moose-Tests-SmalltalkImporter-Core-AndreHora.30 AlainPlantec/Platypus2 Platypus2-AlainPlantec.93 CipT/TalkFFITalkFFI-SmalltalkBinding-CiprianTeodorov.16 CipT/TalkFFITalkFFI-NativeBoostBinding-CiprianTeodorov.23 CipT/TalkFFITalkFFI-NativeBoostBinding-CiprianTeodorov.4 CipT/TalkFFITalkFFI-NativeBoostBinding-CiprianTeodorov.15 Guille/Seed Seed-Basic-GuillermoPolito.8 Guille/Seed Seed-PharoCandle-GuillermoPolito.46 Guille/Seed Seed-PharoCandle-GuillermoPolito.14.6 Guille/Seed Seed-Mappings-GuillermoPolito.7 Guille/Seed Seed-Mappings-GuillermoPolito.6 Guille/Seed Seed-HazelBuilder-GuillermoPolito.197 Guille/Seed Seed-HazelBuilder-GuillermoPolito.129 Guille/Seed Seed-HazelBuilder-GuillermoPolito.125 Guille/Seed Seed-HazelBuilder-GuillermoPolito.13.127 Guille/Seed Seed-SeedLoader-GuillermoPolito.6 Guille/Seed Seed-Pharo-GuillermoPolito.10 Guille/Seed Seed-MetaLevel-GuillermoPolito.16 Guille/ObjectSpace OzObjectSpace-GuillermoPolito.33 Guille/ObjectSpace OzObjectSpace-GuillermoPolito.17 Guille/ObjectSpace AtomObjectSpace-GuillermoPolito.25 Guille/ObjectSpace Seed-MetaLevel-GuillermoPolito.16 Guille/ObjectSpace AtomAtoms-GuillermoPolito.1
[Pharo-dev] Deprecated selector #metaclass on Smalltalkhub
These projects and packageversions on Smalltalkhub use the #metaclass selector. This might refer to a deprecated selector, replaced by #theMetaClass The packageversions were selected as latest+not merged gokr/DeltaStreams System-gk.143 StephaneDucasse/ArchiveTraits TraitsUI-al.19 StephaneDucasse/ArchiveTraits TraitsUI-al.21 StephaneDucasse/ArchiveTraits TraitsUI-al.2 StephaneDucasse/ArchiveTraits System-al.55 StephaneDucasse/ArchiveTraits System-al.85 StephaneDucasse/ArchiveTraits System-al.52 StephaneDucasse/ArchiveTraits System-al.63 AnneEtien/RingJET Ring-History-Definitions-VeronicaUquillas.104 AnneEtien/RingJET Ring-Core-Kernel-MarcusDenker.90 BenjaminVanRyseghem/NemoNemo-BenjaminVanRyseghem.21 andrehora/FindBugs Refactoring-Critics-AndreHora.18 andrehora/HoraExp Moose-Tests-SmalltalkImporter-Core-AndreHora.29 andrehora/HoraExpTemp Moose-Tests-SmalltalkImporter-Core-AndreHora.30 AlainPlantec/Platypus2 Platypus2-AlainPlantec.93 CipT/TalkFFITalkFFI-SmalltalkBinding-CiprianTeodorov.16 CipT/TalkFFITalkFFI-NativeBoostBinding-CiprianTeodorov.23 CipT/TalkFFITalkFFI-NativeBoostBinding-CiprianTeodorov.4 CipT/TalkFFITalkFFI-NativeBoostBinding-CiprianTeodorov.15 Guille/Seed Seed-Basic-GuillermoPolito.8 Guille/Seed Seed-PharoCandle-GuillermoPolito.46 Guille/Seed Seed-PharoCandle-GuillermoPolito.14.6 Guille/Seed Seed-Mappings-GuillermoPolito.7 Guille/Seed Seed-Mappings-GuillermoPolito.6 Guille/Seed Seed-HazelBuilder-GuillermoPolito.197 Guille/Seed Seed-HazelBuilder-GuillermoPolito.129 Guille/Seed Seed-HazelBuilder-GuillermoPolito.125 Guille/Seed Seed-HazelBuilder-GuillermoPolito.13.127 Guille/Seed Seed-SeedLoader-GuillermoPolito.6 Guille/Seed Seed-Pharo-GuillermoPolito.10 Guille/Seed Seed-MetaLevel-GuillermoPolito.16 Guille/ObjectSpace OzObjectSpace-GuillermoPolito.33 Guille/ObjectSpace OzObjectSpace-GuillermoPolito.17 Guille/ObjectSpace AtomObjectSpace-GuillermoPolito.25 Guille/ObjectSpace Seed-MetaLevel-GuillermoPolito.16 Guille/ObjectSpace AtomAtoms-GuillermoPolito.1
Re: [Pharo-dev] How to browse SmalltalkHub ?
there is no official way to explore. the explore page will be an entry point for that, but so far, no time to implement it... but well, SmalltalkHub is an opensource project. If someone has the willing and the time... go ahead! :) Esteban On Sep 20, 2013, at 8:21 PM, Esteban A. Maringolo emaring...@gmail.com wrote: Is that a way to explore it or just a cheatsheet? :) Esteban A. Maringolo 2013/9/20 Stephan Eggermont step...@stack.nl: Kilon wrote: Is there a way to explore smalltalkhub and find all the available projects ? Yes there is. Missing are the projects of teams (Pharo, Moose, etc) pdebruic/ABTesting NorbertHartl/ASN1 philippeback/AWS-SWF abergel/AceWikiExporter maxi/Aconcagua SergeStinckwich/Actalk abergel/Adore ajlopez/AjUnit CipT/AlienGraphViz ThierryGoubier/Alt30 ThierryGoubier/AltBrowser LaurentLaffont/AmberOneClick pdebruic/AmberSlime ewernli/Amop AurelienNeveux/AnalogInput BaptisteSubhi/AnalogInput AndreiChis/AnnouncerCentricDebugger rbistolfi/ApiManager hernan/ApplicationSecurity StephaneDucasse/ArchiveTraits dTriangle/ArgBackward jfabry/AspectMaps Guille/AtomInterpreter goonsh/Aulos abergel/AutoBugFinder StephaneDucasse/AutomaticMethodCategorizer LaurentLaffont/Autotest abergel/AvatoxMooseImporter abergel/Avispa StefanMarr/AweSOM ThierryGoubier/BRLTTY hfierro/BSpline zeroflag/BabyMock TomasCarrasco/Bagheera TorstenBergmann/Barcode lanza/Beholder timrowledge/Benchmarking cdlm/BenderQuest hernan/BioSmalltalk CipT/Blif AlainPlantec/Bloc StephaneDucasse/Bob MartinWalk/Boids cdlm/Bokeh StephaneDucasse/Breakout estebanlm/Broadcast andrehora/BugMaps abergel/CAnalyzer LaurentLaffont/CLFParser leopardary/CS528 hernan/CSV JohanBrichau/CSVParser JanVrany/CalipeL-S TorstenBergmann/CameraPlugin FabrizioPerin/Carrack sebnozzi/CategorySaver pdebruic/CenteredIntervalTree maxi/Chalten CipT/CiSics LeoVanderdonckt/Cipher BenjaminVanRyseghem/CircularMenu gisela/ClassDefEnhaceTree doreen/Classes JanVanDeSandt/Cloudfork-Couch RichardWettel/CodeCity hernan/CodeGenerator onierstrasz/CodePhoo MicheleLanza/CodeRevolver andrehora/CohCopExperiments StephaneDucasse/Comix FabrizioPerin/ConceptualSchema LaurentLaffont/Conduite JurajKubelka/Configuration Osvaldo/ConfigurationOfDDSTPAnual mabinogi/Conman pdebruic/Country SubletMaxime/Cour7TERREIER_SUBLET johnsmith/Cours7 GautVon/Cours7Gene SimonAllier/CriticBrowserRuleComment SimonAllier/CriticRanking tonyg/Crypto-Bencode tonyg/Crypto-Nacl tonyg/Crypto-Scrypt philippeback/Cursor DamienCassou/DBus Osvaldo/DDSTPAnual pdebruic/DHBNumerical statonjr/DLWebmachine DavidMartin/DMTestProject HwaJong/DaliotsPlayground GastonDallOglio/DataTables NahuelGarbezza/DataTables-Seaside gokr/DeltaStreams StephanEggermont/DeltaWerken hernan/DependencyWalker StephanEggermont/DeprecationFinder RobertoMinelli/DevFlow hernan/Diacritics DiegoLont/Dima BenjaminVanRyseghem/DirtyExperiments BenjaminVanRyseghem/DocTest hkleinsorgen/DojoToolkit HilaireFernandes/DrGeo philippeback/DripfeedIt CipT/EBNFParser estebanlm/EclipsePack onierstrasz/Enigma kilon/Ephestos MartinDias/Epicea lgiudice/EraDeImperios pablitar/Estrategia hernan/EventsMonitor AubAurelAntho/Exercice MatthieuLefebvre/Exercice7_Lefebvre_Bonhomme nicolasAnquetil/ExperimentalStuff StephaneDucasse/Expr YuriyTymchuk/FAST usman/FBCrawler DaveMason/FFI-Parse vonpupp/FLOdactic SergeStinckwich/FRP CipT/Fame-Textual abergel/Familiar nicolasAnquetil/FamixAdditionalMetrics andrehora/FamixBugEntity AnneEtien/FamixDiff andrehora/FamixXML andrehora/FeaturedText dh83/FileSystemS3 dh83/FileSystemST andrehora/FindBugs JFLefevre/FindTheFat hernan/FixedDecimal gisela/Flamel cdlm/Flatland CipT/FoBung girba/FreeFonts NahuelGarbezza/Fulbacho BenjA/FullTextSearch StephaneDucasse/FunBook hernan/FuzzySearcher kilon/GLTutorial girba/GPlay ainfante/GadgetProfiler shakedown/Galclone jeanbaptistearnaud/GameBoyEmulator AubAurelAntho/Generateur AndreasGarcon/Generateur_ultra_puissant Chrystopher/Generator pdebruic/Geolocation ericclack/GettingThingsDone NahuelGarbezza/Gobstones-Helvetia estebanlm/GoogleAnalyticsTracker DanielAvivNotario/Graph-ET pdebruic/Gravatar hernan/Grease GastonDallOglio/Gridster melkyades/Gv philippeback/HOExperiments philippeback/HOPomodoro philippeback/HOSeaside philippeback/HOWebStack TorstenBergmann/HPDF pdebruic/HTTPAPIClient AndreiChis/Hackathon-SATToSE2013 TorstenBergmann/HelpSystem philippeback/HighOctane philippeback/HighOctane-Boxes andrehora/Highcharts deorn/Hikomsys andrehora/HoraExp andrehora/HoraExpTemp andrehora/HoraExpTemp2 andrehora/HoraExpTemp3 sbragagnolo/HybridTyper gokr/HyperDex NahuelGarbezza/ID3 TorstenBergmann/INIFile hernan/INIParser juampi/IORM NicolasPetton/Iliad gokr/ImageBuilder ErwanDouaille/ImageLauncher TorstenBergmann/Infinity hkleinsorgen/InfoVis GlennCavarle/InheritanceExperiments hernan/InstanceEncoder
[Pharo-dev] Spec Question: DropListModel
What is the idea behind the #displayBlock: in DropListModel? I expected it to be something that is stored in the DropListModel and re-evaluated each time the items change. But from the implementation I get that this is a one-time action. signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [Pharo-dev] Should I contribute to Pharo or should I keep things separate ?
Do it the git way :) Propose your slice and let the people in charge of Pharo decide if they want it or not :) Each time you take an image and work in it, you do a branch. Proposing a slice is just a pull-request :) Ben On Sep 20, 2013, at 9:47 PM, kilon theki...@yahoo.co.uk wrote: As you may or may not know, I am working on the pharo help tool. I already see areas that I could improve it. I have started my own help browser tool called Prometheas subclassing the existing one. However I also see that I would like to extend and modify the existing HelpTopic class. Implementing Prometheas I found that I don't like the way TreeMorph works. It practically make it impossible for me to navigate by code through the tree and activate/select the corresponding node. It works if the father node is expanded. If it is not, the node is not selected even after I expand the father node, I have to resend the message to work. Also for some strange reason owner returns none and children returns only the first child. So it looks like there are several issues with TreeMorph from this first look. My question is how to proceed ? I have read the docs about submiting slices after I opened the relevant issue in fogbuz, but should I do that ? I am very new to pharo and hence my hesitation . I dont want to mess things up and frustrate people. I would also like to document TreeMorph , methods that are not commented. -- View this message in context: http://forum.world.st/Should-I-contribute-to-Pharo-or-should-I-keep-things-separate-tp4709427.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] Spec Question: DropListModel
On 2013-09-20, at 18:44, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote: It's a bit weird. Sean and I should do another pass on this, because it's far too disturbing now haha, ok, well I got it's easy to get it working the other way around ;), but yeah slightly counter intuitive. Second question: How can I display a morph in the dropdown list? (aka icon + label). signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [Pharo-dev] [SOLVED]ConfigurationOfGlorpDBX for Pharo2.0
Mariano: Would you share the script you use to load the last stable Glorp with native Postgres drivers into a Pharo 2 image? I want to give it a try this weekend. Regards, Esteban A. Maringolo 2013/9/19 Mariano Martinez Peck marianop...@gmail.com: On Thu, Sep 19, 2013 at 2:22 PM, Guillermo Polito guillermopol...@gmail.com wrote: On Thu, Sep 19, 2013 at 5:16 AM, Federico.Balaguer federico.balag...@gmail.com wrote: It actually worked, the image was unresponsive for a couple minutes but after that everything (so far) seems to be working. That is probably because of something in the progress bar only:). And yes, loading glorp in generally takes some time. Thanks again! Federico Thanks to you! Can you keep us updated if you have any problem? At some point I should update the configuration :). Mariano, you are using glorp in 20 also, aren't you? Yes, but not that much and so far with the native Postgres driver ;) But no problem so far. -- View this message in context: http://forum.world.st/ConfigurationOfGlorpDBX-for-Pharo2-0-tp4709086p4709094.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. -- Mariano http://marianopeck.wordpress.com
