February 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] Pharo sprint - summary

by Tudor Girba

Hi, Here is a summary of what we discussed around Pharo issues. Topics: - The process to get to the mini image - Actionable tasks to improve the current situation - Current architecture - Future architecture Problems: - Building speed - Where do we work: Core or Dev - How to collaborate Actions: - Create the OnPharoHead group on Jenkins The goal is to provide a space in which curated projects (e.g., RB, Moose) are built against the head of Pharo. If the project-specific build gets red, the integrator of the project announces the Pharo core team about the origin of the problems. If the project-specific build gets green, the latest Pharo image is integrated in the official continuous integration - We need to speed up the creation of a dev image (core + decent tools) for core developers. To do this, we need to introduce an incremental job that loads the updates starting from the last https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/. This will make the load much faster (currently, the official build takes 20+ minutes), as the official one is based on an older seed image. - Grease does not load cleanly in Pharo 1.4 because some methods were integrated already. **Someone** has to create a ConfigurationOfGrease for Pharo 1.3, and a baseline for 1.4. - People seem to believe that Builder is not maintained. Lukas maintains it, but to integrate changes, he needs pull requests on Github. - The work on Filesystem should be synchronized. We need to establish the link with Colin. An email must be sent to him. Camillo can you send him an email? The squeaksource/fs repository contains renamings, that are not necessary. Camillo should get in the loop. - RB and AST are important pieces that should be integrated by one person. Lukas offers to play the integrator role. Note: An integrator is more than a maintainer in that he actively (and positively) works with contributors. To ensure an easier collaboration, RB and AST will get an official inbox repository. Lukas will ensure that the architecture of RB and AST remains clean, that the test coverage improves, as well as that new clients are satisfied. The AST extensions (new variable nodes for self, super, ...) leak semantics into the syntax AST. Furthermore they break rewrite rules, code critics and refactoring. Instead, the AST-Semantics package should be dispatched through (or a similar independent extension package). For the parametrization of the RB environment (related to the remote access), experiments with RB (and possibly other frameworks) should be conducted first. If these experiments prove RB to be the right tool for remote access, the changes can be submitted for inclusion. Doru, Lukas, Stef, Philippe, Fabrizio, Stefan and Jorge

Feb. 18, 2012

Re: [Pharo-project] HTTPS

by Jimmie Houchin

On 2/18/2012 8:02 AM, Sven Van Caekenberghe wrote: > For completeness, I should add that Zodiac delivers general purpose TLS/SSL streams. > These can then be used to implement for example HTTPS when combined with a suitable client such as Zinc HTTP Components. > It also works for some other use cases like mail. > However, ZnSecureSocketStream is binary only, unlike SocketStream which mixes both with encoding. Would it be possible to see an example of what is required and how I would send an email from Pharo through GMail's smtp servers? All of my email is through GMail, and I would love to be able to send messages from my images. But I haven't seen or learned how, despite seeing messages like this in any COTDC messages. "p.s. this message was sent from a pharo image. Did you know you could easily do that?!" I have searched the archives and haven't found the answer of how to do that. Since GMail requires TLS3 or SSL, I would have to be able to handle that as well. http://support.google.com/mail/bin/answer.py?hl=en&answer=13287 Any help, insight and wisdom greatly appreciated. Jimmie

Feb. 18, 2012

[Pharo-project] [update 1.4] #14339

by Marcus Denker

14339 ----- Issue 5323: PluggableListMorph problem when multiple selection and navigate with keyboard http://code.google.com/p/pharo/issues/detail?id=5323 Issue 5324: TestRunner red square of death http://code.google.com/p/pharo/issues/detail?id=5324 -- Marcus Denker -- http://marcusdenker.de

Feb. 18, 2012

Re: [Pharo-project] Nautilus with Refactorings

by Benjamin

On Feb 18, 2012, at 3:38 PM, Esteban Lorenzano wrote: > great work Ben! > > here my adds to feedback: > > - class button on traits: error - Done > - cmd+B on traits do nothing - For me, it works (open a new browser) > - I want to set Nautilus as default browser, and I can't (I don't want yet-another-browser on main menu either) - Nautilus now registers itself as default browser on installation. Moreover, the System menu entry has been removed Thanks for feedback, Ben > > Cheers, > Esteban > > El 18/02/2012, a las 11:13a.m., Benjamin escribiÃ³: > >> I fixed that yesterday, but the jenkins builds wasn't linked with the repository :) >> >> Now Marcus fixed that, so the builds should always be up to date :) >> >> >> Ben >> >> On Feb 18, 2012, at 10:54 AM, Andreas Wacknitz wrote: >> >>> >>> Am 18.02.2012 um 01:40 schrieb Benjamin: >>> >>>> Hi guys, >>>> >>>> I am glad to announce that refactorings (RBEngine) are now integrated into Nautilus :) >>>> >>>> >>>> You can also found the latest image on Jenkins: https://ci.lille.inria.fr/pharo/job/Nautilus%20with%20Refactorings/ >>>> >>>> I hope you will enjoy it, and as usual, any feedback is welcome :) >>>> >>>> >>>> (the next step is to do a nice changes browser :) ) >>>> Ben >>> I downloaded the Jenkins build this morning. >>> When I select the "Announcement-Tests-Core" package I will get a DNU False>>ifEmpty: >>> >>> Nevertheless, keep on your impressive work! >>> >>> Regards >>> Andreas >>> >> >

Feb. 18, 2012

[Pharo-project] [update 1.3] #13322

by Marcus Denker

13322 ----- Issue 4753: Implementors browser doesnt show decompiled source http://code.google.com/p/pharo/issues/detail?id=4753 -- Marcus Denker -- http://marcusdenker.de

Feb. 18, 2012

Re: [Pharo-project] Nautilus with Refactorings

by Benjamin

Done :) Ben On Feb 18, 2012, at 3:22 PM, Esteban Lorenzano wrote: > could you add a message in Nautilus project on squeaksource saying that it is deprecated and pointing to the correct one? > 'cause stupids like me can try to get newer changes on old repositories :) > > best, > Esteban > > El 18/02/2012, a las 11:13a.m., Benjamin escribiÃ³: > >> I fixed that yesterday, but the jenkins builds wasn't linked with the repository :) >> >> Now Marcus fixed that, so the builds should always be up to date :) >> >> >> Ben >> >> On Feb 18, 2012, at 10:54 AM, Andreas Wacknitz wrote: >> >>> >>> Am 18.02.2012 um 01:40 schrieb Benjamin: >>> >>>> Hi guys, >>>> >>>> I am glad to announce that refactorings (RBEngine) are now integrated into Nautilus :) >>>> >>>> >>>> You can also found the latest image on Jenkins: https://ci.lille.inria.fr/pharo/job/Nautilus%20with%20Refactorings/ >>>> >>>> I hope you will enjoy it, and as usual, any feedback is welcome :) >>>> >>>> >>>> (the next step is to do a nice changes browser :) ) >>>> Ben >>> I downloaded the Jenkins build this morning. >>> When I select the "Announcement-Tests-Core" package I will get a DNU False>>ifEmpty: >>> >>> Nevertheless, keep on your impressive work! >>> >>> Regards >>> Andreas >>> >> >

Feb. 18, 2012

Re: [Pharo-project] Nautilus with Refactorings

by Benjamin

On Feb 18, 2012, at 11:22 AM, Mariano Martinez Peck wrote: > Hi Ben. What you did is very very cool. I was waiting for it since a lot of time. So...I had no excuses left to use it ;) You asked for feedback? Ok, I have a long pass. I hope you can get something useful from it. I would like to provide more help but this is all I can offer right now: > > > - When you are in a pane, say Class column, you press the right arow -> and the focus goes to the next column, so if you do down arrow now you start to move between methods. However, when you move from column, the first row (protocols in this case) of the right column is not highlighted so you don't really know if you are there or not until you start to move (like arrow down). So, I would autoselect/autohighlight first row of next column in that case. The selected list is surrounded by a light blue rectangle. I think the width of this border should be increase a bit, but it depends of the theme :) > > - file out in menu of protocols or methods does nothing -> if file out of single protocols is not supported it should be removed from the menu. On methods, it works for me :) On protocols, I fixed it :) > > - multiple select in protocols does not add methods in methods pane. The new protocol is just highlighted, its methods are shown in the method column, but we lost the previous one, even if the previous category is still selected. - Done :) > - when selecting several methods and try to remove them, do not ask each method individuallyâ¦ "it has xx senders.. what do you want to do?" â¦ give options according to the fact that there are several methods, but it only once. For example: "remove all and see all senders" "or just remove all". If you ask that for each methodâ¦then it is not a bulk remove but again, having to remove method by methodâ¦ I should, but it's some work :) > - Sometimes the icon for the tests appear even if those methods are not tests. Look attached file notTestMethods. Here, the test icon is displayed because there is a corresponding test. (In your example, it means that the method BehaviorTest>>#testAllMethods exists :) > > - When you are showing extensions to a class, I would not show the whole class, but intead just the extensions from the package I am browsing. Look attached NotShowFullClass. First I thought about that too, but then I figured out that when you are writing an extension, it's really useful to be able to know the whole set of available methods in a glance :) > > - It would be very very cool if from the Class Search popup we have a shortcut to not change the current browse but instead open it in another one. This should be done on Class Search, but indeed, it will be cool ;) > > - When you are in the class column and you do right click and create a class, the class column where you are is not refreshed automatically and you don't see the just created class. You need to go to another package and then come back to see itâ¦.I guess you need to trigger a refresh or invalidate some cache. - Fixed :) > > - When viewing hierarchy package and class columns are swappedâ¦confusing. - Yes I know, but there are a set of good arguments behind ^^ > > - Bug somehow using the left arrow "<". Find attached PharoDebugBug1.log Can't reproduce it :s > > - Bug: select a package. Right click, find package, cancel. DNU. Find attached PharoDebugBug2.log - Fixed > > - Does it make sense to show "Run tests" when we are in a package where we have not even one single test? For example, go to the package 'Zinc-HTTP-Streaming' right click..and you will see Run testsâ¦ I would only let that option for the cases that you KNOW there are tests inside. - Done > > -In the code pane, the extended search doesn't work and instead it just opens the same menu again. THis is a petty because I use "method source with it" quite a lot ;) - A submenu has been added :) > > - Bug: select the package 'Multilingual-Tests-TextConversion'. Find PharoDebug3.log attached. - Fixed too > > - When selecting a package (but no classes yet), wouldn't make sense to set the package name as the title in the windows rather than Nautilus? - Fixed :) > > > Well, that's all so far. It is a very cool browser and I plan to start using it as my default :) > Please continue!!! > Thanks A LOT for your feedback :) Ben > > > > > > On Sat, Feb 18, 2012 at 10:54 AM, Andreas Wacknitz <a.wacknitz(a)gmx.de> wrote: > > Am 18.02.2012 um 01:40 schrieb Benjamin: > >> Hi guys, >> >> I am glad to announce that refactorings (RBEngine) are now integrated into Nautilus :) >> >> >> You can also found the latest image on Jenkins: https://ci.lille.inria.fr/pharo/job/Nautilus%20with%20Refactorings/ >> >> I hope you will enjoy it, and as usual, any feedback is welcome :) >> >> >> (the next step is to do a nice changes browser :) ) >> Ben > I downloaded the Jenkins build this morning. > When I select the "Announcement-Tests-Core" package I will get a DNU False>>ifEmpty: > > Nevertheless, keep on your impressive work! > > Regards > Andreas > > > > > -- > Mariano > http://marianopeck.wordpress.com > > <NautilusFeedback.zip>

Feb. 18, 2012

[Pharo-project] [update 1.4] #14338

by StÃ©phane Ducasse

14338 ----- - Issue 3547: Have a look at the new match: implementation. Thanks BernardoContreras. http://code.google.com/p/pharo/issues/detail?id=3547

Feb. 18, 2012

Re: [Pharo-project] Nautilus with Refactorings

by Esteban Lorenzano

great work Ben! here my adds to feedback: - class button on traits: error - cmd+B on traits do nothing - I want to set Nautilus as default browser, and I can't (I don't want yet-another-browser on main menu either) Cheers, Esteban El 18/02/2012, a las 11:13a.m., Benjamin escribiÃ³: > I fixed that yesterday, but the jenkins builds wasn't linked with the repository :) > > Now Marcus fixed that, so the builds should always be up to date :) > > > Ben > > On Feb 18, 2012, at 10:54 AM, Andreas Wacknitz wrote: > >> >> Am 18.02.2012 um 01:40 schrieb Benjamin: >> >>> Hi guys, >>> >>> I am glad to announce that refactorings (RBEngine) are now integrated into Nautilus :) >>> >>> >>> You can also found the latest image on Jenkins: https://ci.lille.inria.fr/pharo/job/Nautilus%20with%20Refactorings/ >>> >>> I hope you will enjoy it, and as usual, any feedback is welcome :) >>> >>> >>> (the next step is to do a nice changes browser :) ) >>> Ben >> I downloaded the Jenkins build this morning. >> When I select the "Announcement-Tests-Core" package I will get a DNU False>>ifEmpty: >> >> Nevertheless, keep on your impressive work! >> >> Regards >> Andreas >> >

Feb. 18, 2012

Re: [Pharo-project] Nautilus with Refactorings

by Esteban Lorenzano

could you add a message in Nautilus project on squeaksource saying that it is deprecated and pointing to the correct one? 'cause stupids like me can try to get newer changes on old repositories :) best, Esteban El 18/02/2012, a las 11:13a.m., Benjamin escribiÃ³: > I fixed that yesterday, but the jenkins builds wasn't linked with the repository :) > > Now Marcus fixed that, so the builds should always be up to date :) > > > Ben > > On Feb 18, 2012, at 10:54 AM, Andreas Wacknitz wrote: > >> >> Am 18.02.2012 um 01:40 schrieb Benjamin: >> >>> Hi guys, >>> >>> I am glad to announce that refactorings (RBEngine) are now integrated into Nautilus :) >>> >>> >>> You can also found the latest image on Jenkins: https://ci.lille.inria.fr/pharo/job/Nautilus%20with%20Refactorings/ >>> >>> I hope you will enjoy it, and as usual, any feedback is welcome :) >>> >>> >>> (the next step is to do a nice changes browser :) ) >>> Ben >> I downloaded the Jenkins build this morning. >> When I select the "Announcement-Tests-Core" package I will get a DNU False>>ifEmpty: >> >> Nevertheless, keep on your impressive work! >> >> Regards >> Andreas >> >

Feb. 18, 2012