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

Re: [Pharo-dev] [Ann] Calypso system browser

by Denis Kudriashov

2017-01-09 13:02 GMT+01:00 Bernhard Pieber <bernhard(a)pieber.com>: > I just played a bit with Calypso. I love the possibility to easily show > the inherited methods. I would love to stay in a Calypso browser when I use > Cmd-b to browse classes referenced in method source. Maybe I misunderstood you. Do you want cmd-b open selected class in same browser window?

Jan. 9, 2017

Re: [Pharo-dev] happy and bold new year

by Tudor Girba

Hi Hilaire, GT is essentially a project that takes the relevant parts of Moose and make them applicable to plain Pharo. Pharo ships with only the core tools, but the complete configuration of GT also brings with it Roassal and a couple of other goodies. There are still more interesting things in Moose, but you can get quite far with only GT. About your particular question, itâs true that Pharo does not have static types, but that does not make it harder to understand. Only different. The first thing to realize is that Pharo is not about code, but about objects. That is why my advice is to not try too long to understand Pharo code statically because this is not where the power of Pharo is. You are in a much better position to understand a system when itâs running. So, the tools that I use the most are the inspector when I need to understand structural relationships or contracts between objects, and the debugger when I need to understand some algorithmic steps. Even when I look for code structure patterns, I mostly use the inspector because it allows me to query. Then you augment these tools with custom views and you get quite far. I know this sounds abstract, but I am practicing this since several years and I still find it amazing. I tried to provide a hint of how it works in the ESUG 2016 talk. Cheers, Doru > On Jan 9, 2017, at 2:02 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > > Hello Doru, > > I am curious. > Yesterday I had a look to MessageBrowser, and realize I understand > nothing of it. I saw there is a mix of SpecXXX, models, Navigation > browser, Announcement, etc, then I knew I will have to spend a lot of > time browsing (multiple window again) to understand a bit how these > objects are related, and may be be able to change it in the way I want. > Does the Moose & al tools could help me understand code I don't know about? > > Given the fact Pharo/Smalltalk are not typed makes it harder for code > analysis, don't you? > > Happy new year to you too. > > Hiaire > > Le 09/01/2017 Ã 10:30, Tudor Girba a Ã©crit : >> Happy New Year, everyone! >> >> Over the last year, I went through a rather extensive tour and I directly exposed Moose, GT and Pharo to some 2000+ technical people through various sessions and trainings at conferences and companies. The tour will continue this year. >> >> Most of the sessions are not directly about Moose, GT or Pharo, but about broader topics that are served through what we do around here. These topics can relate to solving problems without reading code, to steering agile architecture, or more recently, to even broader topics like software environmentalism. If you are wondering what software environmentalism is, please take a look at this talk: >> https://youtu.be/N3l3eB62oSw?list=PLqvTNJtc942Cs9Qo4ikCGrUNtAw93Q0JA >> >> I now have the confirmation that there is a whole space which is unaddressed by mainstream technologies. Often people find themselves frustrated having to build their systems on top of opaque technologies with not much hope of understanding what is going on under the hood both because they do not have access to what is behind and because they are provided lack the tools to investigate. You see, developers are suppose to have the coolest job on the planet, and many of them are unhappy. This has to change, and we can do that. >> >> In a conversation I had with a highly respected researcher, after explaining how our tools allow us to work, he noted reluctantly âso, you are claiming that you are practicing a fundamentally different software engineering?â. This question took me a little by surprise because the only answer I found myself being able to provide was âyesâ. I sent him this talk: >> https://youtu.be/XWOOJa3kEa0?list=PLqvTNJtc942Cs9Qo4ikCGrUNtAw93Q0JA >> >> It is strange to be in the position to tell the world that we are constructing something fundamentally better, but I really do believe that we are. >> >> I wish you a happy and bold new year! >> >> Cheers, >> Doru >> > > -- > Dr. Geo > http://drgeo.eu -- www.tudorgirba.com www.feenk.com "If you can't say why something is relevant, it probably isn't."

Jan. 9, 2017

Re: [Pharo-dev] [Ann] Calypso system browser

by Denis Kudriashov

Hi Bernhard 2017-01-09 13:02 GMT+01:00 Bernhard Pieber <bernhard(a)pieber.com>: > Hi Denis, > > I just played a bit with Calypso. I love the possibility to easily show > the inherited methods. I would love to stay in a Calypso browser when I use > Cmd-b to browse classes referenced in method source. > I not hook yet into text editor commands. So they are global ones. And now only way to achieve what you want is to make Calypso default browser. ClySystemBrowser beDefaultBrowser. But I guess it is too early to make it default for general usage. Anyway I will reimplement text editor commands in Calypso way. So it will be possible to open Calypso and stay inside it without global tool replacement.

Jan. 9, 2017

Which package includes GVGraphViz?

by Bernhard Pieber

I just saw found the class DAGraphVizGenerator in Tool-DependencyAnalyser. It references a class GVGraphViz by name. What package do I have to load to get it? The GraphViz package in the Pharo Project Catalog does not use the GV prefix. Cheers, Bernhard

Jan. 9, 2017

NBMacShell still used in GraphViz

by Bernhard Pieber

Happy New Year! The GraphViz project in the Pharo Project Catalog has the tag Pharo5.0 but still uses NBMacShell which seems to have been removed in Pharo 5. What is the right replacement for NBMacShell run: string in newer Pharo versions? Cheers, Bernhard

Jan. 9, 2017

Re: [Pharo-dev] happy and bold new year

by Tudor Girba

Hi Phil, Indeed, I believe that losing site of meaning is a spectacular waste of opportunity. I often hear people arguing that it is hard to find meaning in a technology space, and as a consequence they also stop looking for it. In this situations, I tend to point people to the work of Viktor Frankl who found meaning in the Auschwitz concentration camp, and as a result he founded a whole psychology domain (logotherapy): https://en.wikipedia.org/wiki/Man's_Search_for_Meaning If he could find meaning there, we certainly can do the same in the comfort of our amazingly privileged life. It is to this end that I also argue that we should bring storytelling closer to our technical reality. For example, see this slightly older talk (notice the place of Pharo in that talk, too): https://vimeo.com/131632605 Cheers, Doru > On Jan 9, 2017, at 11:11 AM, philippe.back(a)highoctane.be <philippe.back(a)gmail.com> wrote: > > Doru, > > Wow. > > I have to say that in the face of other technologies there is often the force that lures me back go them. But they do not have the same feel. This ability to understand and be able to dig down is unmatched. > > I was reading this mail this morning and it echoes your point pretty nicely: > "I hear a lot about "seeking meaning," especially in the face of tragedy and uncertainty. But how would you know it if you tripped over it? I doubt it's like the justice's definition of pornographyâI'll know it when I see it. > I'd think our brief time here is about creating meaning, first and foremost for ourselves. When we have a lighted path, a goal for our journey (whether or not we reach our destination), we tend to serve a greater purpose. "Journey" comes from the French jornee which means a day, or a day's travels. It refers to our daily activity. > > When we we are engaged in neither meaning nor happiness, we waste our days. When we are engaged in meaning but not happiness, we are sacrificing our days. When we are engaged in high happiness but little meaning, we are in a stimulating or addictive environment. Only when we are immersed in both happiness and meaning do we create an optimal, contributing life. > > I don't know about you, but I'd prefer to take both my meaning and happiness out of others' hands, and create them both myself".--Alan Weiss > > Definitely applies to our tech. > > Happy New Year! > > > > Phil > > > > > Le 9 janv. 2017 10:31, "Tudor Girba" <tudor(a)tudorgirba.com> a Ã©crit : > Happy New Year, everyone! > > Over the last year, I went through a rather extensive tour and I directly exposed Moose, GT and Pharo to some 2000+ technical people through various sessions and trainings at conferences and companies. The tour will continue this year. > > Most of the sessions are not directly about Moose, GT or Pharo, but about broader topics that are served through what we do around here. These topics can relate to solving problems without reading code, to steering agile architecture, or more recently, to even broader topics like software environmentalism. If you are wondering what software environmentalism is, please take a look at this talk: > https://youtu.be/N3l3eB62oSw?list=PLqvTNJtc942Cs9Qo4ikCGrUNtAw93Q0JA > > I now have the confirmation that there is a whole space which is unaddressed by mainstream technologies. Often people find themselves frustrated having to build their systems on top of opaque technologies with not much hope of understanding what is going on under the hood both because they do not have access to what is behind and because they are provided lack the tools to investigate. You see, developers are suppose to have the coolest job on the planet, and many of them are unhappy. This has to change, and we can do that. > > In a conversation I had with a highly respected researcher, after explaining how our tools allow us to work, he noted reluctantly âso, you are claiming that you are practicing a fundamentally different software engineering?â. This question took me a little by surprise because the only answer I found myself being able to provide was âyesâ. I sent him this talk: > https://youtu.be/XWOOJa3kEa0?list=PLqvTNJtc942Cs9Qo4ikCGrUNtAw93Q0JA > > It is strange to be in the position to tell the world that we are constructing something fundamentally better, but I really do believe that we are. > > I wish you a happy and bold new year! > > Cheers, > Doru > > > -- > www.tudorgirba.com > www.feenk.com > > "Every thing should have the right to be different." > > > > > -- www.tudorgirba.com www.feenk.com "Some battles are better lost than fought."

Jan. 9, 2017

Re: [Pharo-dev] happy and bold new year

by Hilaire

Hello Doru, I am curious. Yesterday I had a look to MessageBrowser, and realize I understand nothing of it. I saw there is a mix of SpecXXX, models, Navigation browser, Announcement, etc, then I knew I will have to spend a lot of time browsing (multiple window again) to understand a bit how these objects are related, and may be be able to change it in the way I want. Does the Moose & al tools could help me understand code I don't know about? Given the fact Pharo/Smalltalk are not typed makes it harder for code analysis, don't you? Happy new year to you too. Hiaire Le 09/01/2017 Ã 10:30, Tudor Girba a Ã©crit : > Happy New Year, everyone! > > Over the last year, I went through a rather extensive tour and I directly exposed Moose, GT and Pharo to some 2000+ technical people through various sessions and trainings at conferences and companies. The tour will continue this year. > > Most of the sessions are not directly about Moose, GT or Pharo, but about broader topics that are served through what we do around here. These topics can relate to solving problems without reading code, to steering agile architecture, or more recently, to even broader topics like software environmentalism. If you are wondering what software environmentalism is, please take a look at this talk: > https://youtu.be/N3l3eB62oSw?list=PLqvTNJtc942Cs9Qo4ikCGrUNtAw93Q0JA > > I now have the confirmation that there is a whole space which is unaddressed by mainstream technologies. Often people find themselves frustrated having to build their systems on top of opaque technologies with not much hope of understanding what is going on under the hood both because they do not have access to what is behind and because they are provided lack the tools to investigate. You see, developers are suppose to have the coolest job on the planet, and many of them are unhappy. This has to change, and we can do that. > > In a conversation I had with a highly respected researcher, after explaining how our tools allow us to work, he noted reluctantly âso, you are claiming that you are practicing a fundamentally different software engineering?â. This question took me a little by surprise because the only answer I found myself being able to provide was âyesâ. I sent him this talk: > https://youtu.be/XWOOJa3kEa0?list=PLqvTNJtc942Cs9Qo4ikCGrUNtAw93Q0JA > > It is strange to be in the position to tell the world that we are constructing something fundamentally better, but I really do believe that we are. > > I wish you a happy and bold new year! > > Cheers, > Doru > -- Dr. Geo http://drgeo.eu

Jan. 9, 2017

Re: [Pharo-dev] [Ann] Calypso system browser

by Bernhard Pieber

Hi Denis, I just played a bit with Calypso. I love the possibility to easily show the inherited methods. I would love to stay in a Calypso browser when I use Cmd-b to browse classes referenced in method source. Thanks for your contribution! Cheers, Bernhard > Am 27.12.2016 um 17:12 schrieb Denis Kudriashov <dionisiydk(a)gmail.com>: > > Hi > > I am glad announce first initial version of new system browser called Calypso. > It is implemented from scratch with idea to build model suitable for remote scenario. > But as result it leads to more important goal: provide clean implementation of browser which people could understand and evolve. > > Calypso supports most features from Nautilus but also miss many of them. And there are many not nicely looking parts of UI which require more work. > But in same time Calypso provides many new cool features with clean implementation underhood. I put many things from other smalltalks and old browsers which I always miss. > > I release Calypso in the state where I finish most design decisions which I think important for project evolution. > Of course there are a lot of things to do and improve. But browser is fully working. And now it is important to community to participate in project and make browser great again :). We need escape from Nautilus pasta world. > Please report any ideas/bugs on github page https://github.com/dionisiydk/Calypso/issues. I already fill it with my wishes. > > Next step I will work on documentation/class comments and I will publish couple of posts about Calypso internals. > > Read more details on my blog. It includes pictures, videos and loading script. > > Best regards, > Denis

Jan. 9, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60340 Home: https://github.com/pharo-project/pharo-core

Jan. 9, 2017

[pharo-project/pharo-core] b18aad: 60340

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: b18aadb4a6ff0489602b0904d647fd736aa08823 https://github.com/pharo-project/pharo-core/commit/b18aadb4a6ff0489602b0904… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-01-09 (Mon, 09 Jan 2017) Changed paths: M ConfigurationOfEpicea.package/ConfigurationOfEpicea.class/instance/scripting/version20StartLogging.st M ConfigurationOfEpicea.package/ConfigurationOfEpicea.class/instance/scripting/version33StartLogging.st M ConfigurationOfEpicea.package/ConfigurationOfEpicea.class/instance/scripting/version41StartLogging.st M ConfigurationOfEpicea.package/ConfigurationOfEpicea.class/instance/scripting/version50StartLogging.st M ConfigurationOfEpicea.package/ConfigurationOfEpicea.class/instance/scripting/version54StartLogging.st M ConfigurationOfEpicea.package/ConfigurationOfEpicea.class/instance/tags/stable_.st A ConfigurationOfEpicea.package/ConfigurationOfEpicea.class/instance/versions/version805_.st M ConfigurationOfUnifiedFFI.package/ConfigurationOfUnifiedFFI.class/instance/symbolic versions/stable_.st A ConfigurationOfUnifiedFFI.package/ConfigurationOfUnifiedFFI.class/instance/versions/v0%5F25%5F1_.st A EpiceaBrowsers.package/EpIconVisitor.class/instance/private/iconNamed_.st R EpiceaBrowsersTests.package/EpFilteredViewTest.class/instance/resources/newLog.st R EpiceaBrowsersTests.package/EpLogBrowserViewTest.class/class/accessing/resources.st M EpiceaBrowsersTests.package/EpLogBrowserViewTest.class/definition.st M EpiceaBrowsersTests.package/EpLogBrowserViewTest.class/instance/resources/newLog.st M EpiceaBrowsersTests.package/EpLogBrowserViewTest.class/instance/running/setUp.st A EpiceaBrowsersTests.package/EpLogBrowserViewTest.class/instance/running/tearDown.st M EpiceaBrowsersTests.package/EpOmbuExporterTest.class/README.md M EpiceaBrowsersTests.package/EpOmbuExporterTest.class/definition.st R EpiceaBrowsersTests.package/EpOmbuExporterTest.class/instance/accessing/resources.st M EpiceaBrowsersTests.package/EpOmbuExporterTest.class/instance/running/setUp.st M EpiceaBrowsersTests.package/EpOmbuExporterTest.class/instance/running/tearDown.st R EpiceaBrowsersTests.package/EpOnePageViewTest.class/instance/resources/newLog.st R EpiceaBrowsersTests.package/EpTwoPagesViewTest.class/instance/resources/newLog.st M EpiceaTests.package/EpEnabledIntegrationTest.class/README.md R EpiceaTests.package/EpLogBuilder.class/README.md R EpiceaTests.package/EpLogBuilder.class/definition.st R EpiceaTests.package/EpLogBuilder.class/instance/accessing/log.st R EpiceaTests.package/EpLogBuilder.class/instance/accessing/logHeadReference.st R EpiceaTests.package/EpLogBuilder.class/instance/building/logAbsentInitial.st R EpiceaTests.package/EpLogBuilder.class/instance/building/logChildren_.st R EpiceaTests.package/EpLogBuilder.class/instance/building/logChildren_triggerReference_.st R EpiceaTests.package/EpLogBuilder.class/instance/building/logEvent_.st R EpiceaTests.package/EpLogBuilder.class/instance/building/logEvent_triggerReference_.st R EpiceaTests.package/EpLogBuilder.class/instance/building/logInitial.st R EpiceaTests.package/EpLogBuilder.class/instance/initialization/initialize.st R EpiceaTests.package/EpLogBuilder.class/instance/initialization/newLog.st R EpiceaTests.package/EpLogBuilder.class/instance/initialization/newStore.st R EpiceaTests.package/EpLogBuilder.class/instance/releasing/release_.st M EpiceaTests.package/EpLogTest.class/README.md R EpiceaTests.package/EpLogTest.class/class/accessing/resources.st M EpiceaTests.package/EpLogTest.class/definition.st R EpiceaTests.package/EpLogTest.class/instance/instance-creation/newLog.st M EpiceaTests.package/EpLogTest.class/instance/running/setUp.st A EpiceaTests.package/EpLogTest.class/instance/running/tearDown.st R EpiceaTests.package/EpLogTestResource.class/README.md R EpiceaTests.package/EpLogTestResource.class/definition.st R EpiceaTests.package/EpLogTestResource.class/instance/accessing/oneTriggerWithFourChildrenLog.st R EpiceaTests.package/EpLogTestResource.class/instance/accessing/oneTriggerWithOneChildLog.st R EpiceaTests.package/EpLogTestResource.class/instance/accessing/threeEntriesWithAbsentPrior.st R EpiceaTests.package/EpLogTestResource.class/instance/running/setUp.st R EpiceaTests.package/EpLogTestResource.class/instance/running/setUpOneTriggerWithFourChildrenLog.st R EpiceaTests.package/EpLogTestResource.class/instance/running/setUpOneTriggerWithOneChildLog.st R EpiceaTests.package/EpLogTestResource.class/instance/running/setUpThreeEntriesWithAbsentPrior.st R EpiceaTests.package/EpLogTestResource.class/instance/running/setUpTwoTriggersWithThreeChildrenLog.st R EpiceaTests.package/EpLogTestResource.class/instance/running/tearDown.st R EpiceaTests.package/EpLogTestResource.class/instance/running/tearDownOneTriggerWithFourChildrenLog.st R EpiceaTests.package/EpLogTestResource.class/instance/running/tearDownOneTriggerWithOneChildLog.st R EpiceaTests.package/EpLogTestResource.class/instance/running/tearDownThreeEntriesWithAbsentPrior.st M EpiceaTests.package/EpMonitorIntegrationTest.class/README.md M EpiceaTests.package/EpMonitorIntegrationTest.class/definition.st R EpiceaTests.package/EpMonitorIntegrationTest.class/instance/running/newLog.st M EpiceaTests.package/EpMonitorIntegrationTest.class/instance/running/setUp.st M EpiceaTests.package/EpMonitorIntegrationTest.class/instance/running/tearDown.st A EpiceaTests.package/EpTestLogBuilder.class/README.md A EpiceaTests.package/EpTestLogBuilder.class/definition.st A EpiceaTests.package/EpTestLogBuilder.class/instance/accessing/directory.st A EpiceaTests.package/EpTestLogBuilder.class/instance/accessing/directory_.st A EpiceaTests.package/EpTestLogBuilder.class/instance/accessing/log.st A EpiceaTests.package/EpTestLogBuilder.class/instance/accessing/logHeadReference.st A EpiceaTests.package/EpTestLogBuilder.class/instance/building/logAbsentInitial.st A EpiceaTests.package/EpTestLogBuilder.class/instance/building/logChildren_.st A EpiceaTests.package/EpTestLogBuilder.class/instance/building/logChildren_triggerReference_.st A EpiceaTests.package/EpTestLogBuilder.class/instance/building/logEvent_.st A EpiceaTests.package/EpTestLogBuilder.class/instance/building/logEvent_triggerReference_.st A EpiceaTests.package/EpTestLogBuilder.class/instance/building/logInitial.st A EpiceaTests.package/EpTestLogBuilder.class/instance/initialization/initialize.st A EpiceaTests.package/EpTestLogBuilder.class/instance/initialization/newLog.st A EpiceaTests.package/EpTestLogBuilder.class/instance/initialization/newStore.st A EpiceaTests.package/EpTestLogBuilder.class/instance/releasing/cleanUp.st A EpiceaTests.package/EpTestLogBuilder.class/instance/releasing/releaseLog_.st A EpiceaTests.package/EpTestLogBuilder.class/instance/samples/oneTriggerWithFourChildrenLog.st A EpiceaTests.package/EpTestLogBuilder.class/instance/samples/oneTriggerWithOneChildLog.st M Morphic-Base.package/MenuMorph.class/instance/events/popUpAdjacentTo_forHand_from_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60339.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60340.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60339.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60340.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M UnifiedFFI.package/extension/ByteArray/instance/readString.st M UnifiedFFI.package/extension/ExternalData/instance/readString.st M UnifiedFFI.package/extension/ExternalData/instance/readStringUTF8.st Log Message: ----------- 60340 19529 Mouseover an empty submenu causes UI lockdown https://pharo.fogbugz.com/f/cases/19529 19526 readString should check NULL condition https://pharo.fogbugz.com/f/cases/19526 19520 Epicea: Tests lacking files cleanup https://pharo.fogbugz.com/f/cases/19520 http://files.pharo.org/image/60/60340.zip

Jan. 9, 2017