- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Swimming with the fish imagery

by Stephane Ducasse

Did you watch the What is Pharo videos of the mooc :) On Sat, Oct 7, 2017 at 3:16 AM, Ben Coman <btc(a)openinworld.com> wrote: > > "Swimming with the fish" is a catchy phrase that I like which seems to > encompass the strength of Pharo's tight development feedback loop that comes > from operating in a world of live objects. I had some imagery floating > through my head on this I thought worth sharing. Only time for a quick dump, > but I hope you can piece it together... > > > In the style of one of those fast paced cartoon product videos... > > Scene 1: > "The development process we all know..." > A neutral background with directed arcs in circle > "Debug-->Edit-->Compile-->Execute-->" > > > Scene 2: > "In most languages... debugging..." > Zoom in on Aquarium 1 to show a developer standing outside aquarium > window... > https://tinyurl.com/PharoSwimWithTheFish-Outside > > reaching in through quarantine-box-like-gloxes to use telescopic tools to > pick up and examine fish at a distance... > https://tinyurl.com/PharoSwimWithTheFish-OtherTool > > until the lightbulb moment... > https://tinyurl.com/PharoSwimWithTheFish-Lightbulb > > > Scene 3: > "In most languages... editing...." > Developer zooms out away from aquarium. It folds up into a tiny box and > drops in a bin. > Developer zooms in on an architectural drafting table with many drawings > with many different but simple flow diagrams on each. Quickly make required > edit to flow diagrams. > https://tinyurl.com/PharoSwimWithTheFish-OtherEdit > > > Scene 4: > "In most languages... compiling..." > Drawings pass through a photocopier into a box that is transferred to site > supervisor. > At an empty flat construction site, supervisor opens box pulling out > drawings to review them. > Trucks and machines arrive and start building the aquarium at his > direction... > Two buildings clash when they overlap the same space (compile error). Return > to Scene 3 to fix design then rerun Scene 4 through to completion. > > > Scene 5: > " In most languages... execution..." > Water trucks arrive and pour water into the pool, then more trucks arrive > adding the fish. > (i.e. initialization and getting to the point of the program you want check > again) > > > Scene 6: > "In most languages... debugging..." > Complete the loop by starting scene 3 again. > > > Scene 7: > "In Pharo.... debugging..." > Zoom out, over and into Aquarium 2 where a developer is swimming inside the > pool... > https://tinyurl.com/PharoSwimWithTheFish-Inside > http://blog.atlantisthepalm.com/wp-content/uploads/2017/05/different-in-wat… > > Developer grabs a fish, shifts it aside, lets it go to swim some more, grabs > it again, holds it up close to look a small detail. Out of nothing creates > a new fish to interact with the first fish. > Out of nothing creates some clay and then moulds a new scope-like tool from > it to look at the fish differently. > > Lightbulb moment... > https://tinyurl.com/PharoSwimWithTheFish-Lightbulb > > "In Pharo.... editing..." > Developer peers into brain of fish seeing many neurons, picks one out which > shows as simple flow diagram, makes a change to it. > > "In Pharo.... compiling..." > Laser beam quickly scans the simple flow diagram and packs neuron back into > the fish. > > "In Pharo.... execution..." > Fish swims off. > > "In Pharo.... debugging..." > Developer grabs another fish... > > > Scene 8: > Zoom out to show both aquariums. > In Aquarium 1, repetitively run through Scenes 2 through 6 > In Aquarium 2, repetitively run through Scene 7. > Play at 10x original speed. > > Fade in a "Debug-->Edit-->Compile-->Run-->" over each aquarium, showing > synced state transitions. > > Fade in "Come swim with the fish with Pharo" > Fade in "It will change the way you think about programming" > > > cheers -ben

Oct. 7, 2017

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

by Stephane Ducasse

Yes it would be good that class description do not use category else we will never be able to clean. Denis multiple tags for methods. when we will stop to add new features and stabilise what we have? Yes I'm not in a good mood because I see that I will have to migrate all calypso in the future to brick. Stef On Sat, Oct 7, 2017 at 10:08 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Tim > > we talk about this format of methods year ago and we will like it and > we will not discuss it anymore. > For the record a method is a named block so it fits and we do not have > to have {} for method delimiters. > > Stef > > On Fri, Oct 6, 2017 at 11:34 PM, Tim Mackinnon <tim(a)testit.works> wrote: >> Gosh - It actually work quite well to be able to easily browse code online >> in a more traditional format of seeing an entire class. Hopefully this leads >> to us being able to share solutions to common language agnostic problems. >> >> One small observation - I quickly grokâd the use of class { â¦. } (with the >> curly braces) - but given that smalltalk methods often have lots of [ ] >> (square braces in them), I was a bit surprised to see that method >> declarations in tonal donât use { â¦ } (curly braces) to denote them, but >> instead use [ ] - which feels slightly strange given the class declaration >> above has. {}. >> >> Was it easier to parse this way, or is there some subtlety I missed? I would >> have been tempted to use {} for classes and methods and [] for the >> protocols as this more closely matches what other languages do - and it >> might actually make it more easily readable for other programmers. Given we >> have to learn this new format anyway - Iâd be prepared to give a nod to what >> others doâ¦ >> >> Possibly this observation comes to late - and maybe there is compelling >> reason to go the route we have gone - but maybe its worth a quick double >> check as its an exciting development. >> >> Tim >> >> On 6 Oct 2017, at 18:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> Hi all, >> >> I released Iceberg version 0.6. It includes a lot of small tweaks and fixes, >> but the most important inclusion is tonel file format which aims to replace >> file tree. >> >> What is Tonel? (https://github.com/pharo-vcs/tonel) >> Tonel is a file-per-class file format for monticello repositories. Itâs >> purpose is to reduce the amount of files touched each operation, make the IO >> faster an compact the repositories database. >> It has also as an objective to offer an âeasy-to-readâ format, so people >> wanting to understand a chunk of code will recognise it easily. >> For testing, I migrated several of my projects to Tonel and Iâve been using >> it, you can see some as examples: >> >> https://github.com/estebanlm/MUDClient >> https://github.com/estebanlm/pharo-tonel (this was just an example and it >> has some minimal errors already fixed) >> >> We plan to migrate Pharo development to tonel to address some problems we >> have: >> >> - since it has to read/write a lot of files, IO operations are slow >> - and even much more slow in Windows >> - Windows also has a problem with longpaths. >> >> Iceberg 0.6 will be integrated to Pharo7 soon :) >> To update Pharo 6.1, there are instructions in the readme: >> https://github.com/pharo-vcs/iceberg/blob/master/README.md >> now, if you wan to migrate your projects to Tonel (from FileTree), here is a >> script you can use: >> https://github.com/pharo-vcs/tonel/blob/master/MigrateFromFileTree.md >> >> btw, tonel is independent of Iceberg and can be used with plain Monticello >> (but it is a metadaless format, history will reside on git, not on >> monticello). >> >> cheers, >> Esteban >> >>

Oct. 7, 2017

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

by Stephane Ducasse

Tim we talk about this format of methods year ago and we will like it and we will not discuss it anymore. For the record a method is a named block so it fits and we do not have to have {} for method delimiters. Stef On Fri, Oct 6, 2017 at 11:34 PM, Tim Mackinnon <tim(a)testit.works> wrote: > Gosh - It actually work quite well to be able to easily browse code online > in a more traditional format of seeing an entire class. Hopefully this leads > to us being able to share solutions to common language agnostic problems. > > One small observation - I quickly grokâd the use of class { â¦. } (with the > curly braces) - but given that smalltalk methods often have lots of [ ] > (square braces in them), I was a bit surprised to see that method > declarations in tonal donât use { â¦ } (curly braces) to denote them, but > instead use [ ] - which feels slightly strange given the class declaration > above has. {}. > > Was it easier to parse this way, or is there some subtlety I missed? I would > have been tempted to use {} for classes and methods and [] for the > protocols as this more closely matches what other languages do - and it > might actually make it more easily readable for other programmers. Given we > have to learn this new format anyway - Iâd be prepared to give a nod to what > others doâ¦ > > Possibly this observation comes to late - and maybe there is compelling > reason to go the route we have gone - but maybe its worth a quick double > check as its an exciting development. > > Tim > > On 6 Oct 2017, at 18:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi all, > > I released Iceberg version 0.6. It includes a lot of small tweaks and fixes, > but the most important inclusion is tonel file format which aims to replace > file tree. > > What is Tonel? (https://github.com/pharo-vcs/tonel) > Tonel is a file-per-class file format for monticello repositories. Itâs > purpose is to reduce the amount of files touched each operation, make the IO > faster an compact the repositories database. > It has also as an objective to offer an âeasy-to-readâ format, so people > wanting to understand a chunk of code will recognise it easily. > For testing, I migrated several of my projects to Tonel and Iâve been using > it, you can see some as examples: > > https://github.com/estebanlm/MUDClient > https://github.com/estebanlm/pharo-tonel (this was just an example and it > has some minimal errors already fixed) > > We plan to migrate Pharo development to tonel to address some problems we > have: > > - since it has to read/write a lot of files, IO operations are slow > - and even much more slow in Windows > - Windows also has a problem with longpaths. > > Iceberg 0.6 will be integrated to Pharo7 soon :) > To update Pharo 6.1, there are instructions in the readme: > https://github.com/pharo-vcs/iceberg/blob/master/README.md > now, if you wan to migrate your projects to Tonel (from FileTree), here is a > script you can use: > https://github.com/pharo-vcs/tonel/blob/master/MigrateFromFileTree.md > > btw, tonel is independent of Iceberg and can be used with plain Monticello > (but it is a metadaless format, history will reside on git, not on > monticello). > > cheers, > Esteban > >

Oct. 7, 2017

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

by Denis Kudriashov

How method history will be supported with Tonel? 2017-10-06 19:18 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi all, > > I released Iceberg version 0.6. It includes a lot of small tweaks and > fixes, but the most important inclusion is tonel file format which aims to > replace file tree. > > What is Tonel? (https://github.com/pharo-vcs/tonel) > Tonel is a file-per-class file format for monticello repositories. Itâs > purpose is to reduce the amount of files touched each operation, make the > IO faster an compact the repositories database. > It has also as an objective to offer an âeasy-to-readâ format, so people > wanting to understand a chunk of code will recognise it easily. > For testing, I migrated several of my projects to Tonel and Iâve been > using it, you can see some as examples: > > https://github.com/estebanlm/MUDClient > https://github.com/estebanlm/pharo-tonel (this was just an example and it > has some minimal errors already fixed) > > We plan to migrate Pharo development to tonel to address some problems we > have: > > - since it has to read/write a lot of files, IO operations are slow > - and even much more slow in Windows > - Windows also has a problem with longpaths. > > Iceberg 0.6 will be integrated to Pharo7 soon :) > To update Pharo 6.1, there are instructions in the readme: > https://github.com/pharo-vcs/iceberg/blob/master/README.md > now, if you wan to migrate your projects to Tonel (from FileTree), here is > a script you can use: https://github.com/pharo-vcs/tonel/blob/master/ > MigrateFromFileTree.md > > btw, tonel is independent of Iceberg and can be used with plain Monticello > (but it is a metadaless format, history will reside on git, not on > monticello). > > cheers, > Esteban >

Oct. 7, 2017

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

by Denis Kudriashov

Hi Esteban 2017-10-06 19:18 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi all, > > I released Iceberg version 0.6. It includes a lot of small tweaks and > fixes, but the most important inclusion is tonel file format which aims to > replace file tree. > > What is Tonel? (https://github.com/pharo-vcs/tonel) > Tonel is a file-per-class file format for monticello repositories. Itâs > purpose is to reduce the amount of files touched each operation, make the > IO faster an compact the repositories database. > It has also as an objective to offer an âeasy-to-readâ format, so people > wanting to understand a chunk of code will recognise it easily. > For testing, I migrated several of my projects to Tonel and Iâve been > using it, you can see some as examples: > > https://github.com/estebanlm/MUDClient > https://github.com/estebanlm/pharo-tonel (this was just an example and it > has some minimal errors already fixed) > Did you accept format changes? Because it still uses category for the class. Really, we are moving away from it. Class has package and tags. Method also needs support for multiple tags. While you are not agree on using tags terminology Tonel still uses single category for this. I think it is important for the new format to not use deprecated names and add support for upcoming features. Instead we will be forced to maintain old Tonel format at some point. And what about slots and class extensions? Do you have example for them? > > We plan to migrate Pharo development to tonel to address some problems we > have: > > - since it has to read/write a lot of files, IO operations are slow > - and even much more slow in Windows > - Windows also has a problem with longpaths. > > Iceberg 0.6 will be integrated to Pharo7 soon :) > To update Pharo 6.1, there are instructions in the readme: > https://github.com/pharo-vcs/iceberg/blob/master/README.md > now, if you wan to migrate your projects to Tonel (from FileTree), here is > a script you can use: https://github.com/pharo-vcs/tonel/blob/master/ > MigrateFromFileTree.md > > btw, tonel is independent of Iceberg and can be used with plain Monticello > (but it is a metadaless format, history will reside on git, not on > monticello). > > cheers, > Esteban >

Oct. 7, 2017

Re: [Pharo-dev] Pulling Web XML data into spreadsheet

by Ben Coman

On Sat, Oct 7, 2017 at 9:32 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Ben Coman wrote > > Unfortunately due to IT lock down I cannot use Pharo at work, > > Not even off a jump drive? Nope. You prompted me to try once again ==> This program is blocked by group policy. For more information, contact your system administrator. Even renaming pharo.exe to notepad.exe doesn't work. It seems they are using signature based white-listing[1]. >From an Ops security perspective I applaud such policy. First place I've seen it used. Its the only real protection. Much better than a virus scanner which only maybePossibly notices based on heuristics observing behaviour after the malware is already running. >From a practical/user perspective, uurgh,aarggh! [1] https://www.bleepingcomputer.com/tutorials/create-an-application-whitelist-… cheers -ben

Oct. 7, 2017

Re: [Pharo-dev] Pulling Web XML data into spreadsheet

by Sean P. DeNigris

Ben Coman wrote > Unfortunately due to IT lock down I cannot use Pharo at work, Not even off a jump drive? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 7, 2017

Swimming with the fish imagery

by Ben Coman

"Swimming with the fish" is a catchy phrase that I like which seems to encompass the strength of Pharo's tight development feedback loop that comes from operating in a world of live objects. I had some imagery floating through my head on this I thought worth sharing. Only time for a quick dump, but I hope you can piece it together... In the style of one of those fast paced cartoon product videos... Scene 1: "The development process we all know..." A neutral background with directed arcs in circle "Debug-->Edit-->Compile-->Execute-->" Scene 2: "In most languages... debugging..." Zoom in on Aquarium 1 to show a developer standing outside aquarium window... https://tinyurl.com/PharoSwimWithTheFish-Outside reaching in through quarantine-box-like-gloxes to use telescopic tools to pick up and examine fish at a distance... https://tinyurl.com/PharoSwimWithTheFish-OtherTool until the lightbulb moment... https://tinyurl.com/PharoSwimWithTheFish-Lightbulb Scene 3: "In most languages... editing...." Developer zooms out away from aquarium. It folds up into a tiny box and drops in a bin. Developer zooms in on an architectural drafting table with many drawings with many different but simple flow diagrams on each. Quickly make required edit to flow diagrams. https://tinyurl.com/PharoSwimWithTheFish-OtherEdit Scene 4: "In most languages... compiling..." Drawings pass through a photocopier into a box that is transferred to site supervisor. At an empty flat construction site, supervisor opens box pulling out drawings to review them. Trucks and machines arrive and start building the aquarium at his direction... Two buildings clash when they overlap the same space (compile error). Return to Scene 3 to fix design then rerun Scene 4 through to completion. Scene 5: " In most languages... execution..." Water trucks arrive and pour water into the pool, then more trucks arrive adding the fish. (i.e. initialization and getting to the point of the program you want check again) Scene 6: "In most languages... debugging..." Complete the loop by starting scene 3 again. Scene 7: "In Pharo.... debugging..." Zoom out, over and into Aquarium 2 where a developer is swimming inside the pool... https://tinyurl.com/PharoSwimWithTheFish-Inside http://blog.atlantisthepalm.com/wp-content/uploads/2017/05/different-in-wat… Developer grabs a fish, shifts it aside, lets it go to swim some more, grabs it again, holds it up close to look a small detail. Out of nothing creates a new fish to interact with the first fish. Out of nothing creates some clay and then moulds a new scope-like tool from it to look at the fish differently. Lightbulb moment... https://tinyurl.com/PharoSwimWithTheFish-Lightbulb "In Pharo.... editing..." Developer peers into brain of fish seeing many neurons, picks one out which shows as simple flow diagram, makes a change to it. "In Pharo.... compiling..." Laser beam quickly scans the simple flow diagram and packs neuron back into the fish. "In Pharo.... execution..." Fish swims off. "In Pharo.... debugging..." Developer grabs another fish... Scene 8: Zoom out to show both aquariums. In Aquarium 1, repetitively run through Scenes 2 through 6 In Aquarium 2, repetitively run through Scene 7. Play at 10x original speed. Fade in a "Debug-->Edit-->Compile-->Run-->" over each aquarium, showing synced state transitions. Fade in "Come swim with the fish with Pharo" Fade in "It will change the way you think about programming" cheers -ben

Oct. 7, 2017

Re: [Pharo-dev] [Pharo-users] ZnClient in Pharo 6.1 not working for Https on Windows

by Ben Coman

First pass approximation... * https://www.microsoft.com/en-us/wdsi/filesubmission * https://answers.microsoft.com/en-us/protect/forum/all/windows-defender-win-… cheers -ben On Sat, Oct 7, 2017 at 12:54 AM, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com > wrote: > Le 06/10/2017 Ã 18:32, Stephane Ducasse a Ã©crit : > > both now I do not see what we can do if a third party tools consider > > that we are a virus. > > > > > > Done. > > I don't know how to not be detected but Windows Defender is the default > anti-virus on windows. The majority of windows user use it now. If it is > possible to improve this, it would be cool. Maybe someone has experience > in that area? > > > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France > >

Oct. 6, 2017

Pulling Web XML data into spreadsheet

by Ben Coman

Unfortunately due to IT lock down I cannot use Pharo at work, but the first 1:30 of video [1] demonstrates a nice use case to aim for DataFrame + FastTable. Similar functionality in Pharo would make a compelling video, to the degree it may even be worthwhile including this out-of-the-box to make a great "first ten minutes" experience for newcomers, or at least a one-click install from the catalog (linked from the help file). What parts do we have for putting together something like this? [1] https://www.youtube.com/watch?v=6H7tBL97orE cheers -ben

Oct. 6, 2017