November 2017 - Pharo-users

ZIPArchive usage + FileSystem memory

by Juraj Kubelka

Hi, I can successfully use ZipArchive like the following -=-=- zip := ZipArchive new. { 'file1.txt'. 'file2.txt'. 'file3.txt' } do: [ :eachFile | | member | member := zip addString: eachFile, ' contents' as: eachFile. member desiredCompressionMethod: ZipArchive compressionDeflated ]. file := FileLocator temp / 'archive.zip'. zip writeTo: file writeStream. file. -=-=- What I should do to make it work while using FileSystem memory? -=-=- zip := ZipArchive new. { 'file1.txt'. 'file2.txt'. 'file3.txt' } do: [ :eachFile | | member | member := zip addString: eachFile, ' contents' as: eachFile. member desiredCompressionMethod: ZipArchive compressionDeflated ]. fileSystem := FileSystem memory. file := fileSystem root / 'archive.zip'. file writeStreamDo: [ :stream | zip writeTo: stream ]. -=-=- There is "Improper store into indexable objectâ as it tries to store a number in ByteString. Thanks! Juraj

Nov. 29, 2017

Re: [Pharo-users] files.pharo.org downloads => needs testers

by Stephane Ducasse

For the sake of it :) >From my slow connection % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 17.7M 100 17.7M 0 0 369k 0 0:00:49 0:00:49 --:--:-- 451k % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 17.7M 100 17.7M 0 0 364k 0 0:00:49 0:00:49 --:--:-- 228k % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 17.7M 100 17.7M 0 0 336k 0 0:00:53 0:00:53 --:--:-- 403k On Wed, Nov 29, 2017 at 8:58 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > This is a really excellent news! > > On Wed, Nov 29, 2017 at 10:57 AM, Christophe Demarey > <christophe.demarey(a)inria.fr> wrote: >> Thanks Ben and John for the first feedbacks. >> I also run a test on Travis CI: >> https://travis-ci.org/demarey/test-files-pharo-org/builds/308846128?utm_sou… >> Average speed difference is amazing â¦ >> I really wonder what could be the problem. On Travis, old files.phaor.org >> looks to be more than 10 times faster than the server hosted at Inria ...

Nov. 29, 2017

Re: [Pharo-users] files.pharo.org downloads => needs testers

by Stephane Ducasse

This is a really excellent news! On Wed, Nov 29, 2017 at 10:57 AM, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > Thanks Ben and John for the first feedbacks. > I also run a test on Travis CI: > https://travis-ci.org/demarey/test-files-pharo-org/builds/308846128?utm_sou… > Average speed difference is amazing â¦ > I really wonder what could be the problem. On Travis, old files.phaor.org > looks to be more than 10 times faster than the server hosted at Inria ...

Nov. 29, 2017

Re: [Pharo-users] Unable to update Glamour-Core

by Juraj Kubelka

Try to clean your cache with packages. I guess that you have Roassal2-akevalon.1718 package locally and this one is corrupted. Juraj > On Nov 29, 2017, at 15:16, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Hi, > > I tried again with a Pharo 6.1 image Latest update: #60510 and now I got this error below. I will try the install procedure after a system update, to debug it. > > Thanks, > > Offray > <leobbnflbacbeglc.png> > > > On 29/11/17 12:15, Juraj Kubelka wrote: >> I do not have this issue. Tested on 32bit Pharo 6.1 Latest update: #60523 >> >> Cheers, >> Juraj >> >>> On Nov 29, 2017, at 14:06, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com <mailto:offray.luna@mutabit.com>> wrote: >>> >>> Hi, >>> >>> I'm using the Roassal2 load script on Pharo 6.1 on Manjaro Gnu/Linux for 64 bits: >>> >>> ======== >>> >>> Gofer it >>> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; >>> configurationOf: 'Roassal2'; >>> loadStable. >>> ======== >>> That is the one, I presume, is trying to load "Glamour-Core-TudorGirba339" and generating the reported error. The quickest way to reproduce the error would be trying to install Roassal2 on Pharo 6.1. >>> >>> Cheers, >>> >>> Offray >>> >>> On 29/11/17 02:47, Tudor Girba wrote: >>>> Hi, >>>> >>>> I am not sure I understand your report. The Glamour-Core package is part of ConfigurationOfGlamourCore, and should not be updated separately. >>>> >>>> What script are you using for loading ConfigurationOfGlamourCore? >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>>> On Nov 29, 2017, at 3:53 AM, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> <mailto:offray.luna@mutabit.com> wrote: >>>>> >>>>> Hi, >>>>> >>>>> My image become unresponsive while making some debug, so I decided to >>>>> start fresh and reinstall Grafoscopio, but I have some problems, with >>>>> XML parser (so I disabled Soup temporarily) and with Glamour-Core, which >>>>> provides and important part of the Grafoscopio experience. I tried also >>>>> to install it from Monticello, without better results (to the version >>>>> Glamour-Core-TudorGirba339). In both cases I get "SubscriptOutOfBounds: >>>>> 17808" and this is the trace I get with the "Report" button (sorry I >>>>> don't know other way to report): >>>>> >>>>> https://pastebin.com/wWM24w01 <https://pastebin.com/wWM24w01> >>>>> >>>>> I will try with Pharo 7... The procedure is the same that was working >>>>> just last week. I know the pains and advantages of having a dynamic >>>>> system that is evolving quickly... hopefully a more stable platform will >>>>> be there while the upcoming one is evolving. >>>>> >>>>> Cheers, >>>>> >>>>> Offray >>>>> >>>>> >>>>> >>>> -- >>>> www.tudorgirba.com <http://www.tudorgirba.com/> >>>> www.feenk.com <http://www.feenk.com/> >>>> >>>> "Every now and then stop and ask yourself if the war you're fighting is the right one." >>>> >>>> >>>> >>>> >>>> >>>> >>> >> >

Nov. 29, 2017

Re: [Pharo-users] Unable to update Glamour-Core

by Offray Vladimir Luna CÃ¡rdenas

Hi, I tried again with a Pharo 6.1 image Latest update: #60510 and now I got this error below. I will try the install procedure after a system update, to debug it. Thanks, Offray On 29/11/17 12:15, Juraj Kubelka wrote: > I do not have this issue. Tested on 32bit Pharo 6.1 Latest update: #60523 > > Cheers, > Juraj > >> On Nov 29, 2017, at 14:06, Offray Vladimir Luna CÃ¡rdenas >> <offray.luna(a)mutabit.com <mailto:offray.luna@mutabit.com>> wrote: >> >> Hi, >> >> I'm using the Roassal2 load script on Pharo 6.1 on Manjaro Gnu/Linux >> for 64 bits: >> >> ======== >> >> |Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; >> configurationOf: 'Roassal2'; loadStable.| >> >> ======== >> >> That is the one, I presume, is trying to load >> "Glamour-Core-TudorGirba339" and generating the reported error. The >> quickest way to reproduce the error would be trying to install >> Roassal2 on Pharo 6.1. >> >> Cheers, >> >> Offray >> >> On 29/11/17 02:47, Tudor Girba wrote: >>> Hi, >>> >>> I am not sure I understand your report. The Glamour-Core package is part of ConfigurationOfGlamourCore, and should not be updated separately. >>> >>> What script are you using for loading ConfigurationOfGlamourCore? >>> >>> Cheers, >>> Doru >>> >>> >>>> On Nov 29, 2017, at 3:53 AM, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: >>>> >>>> Hi, >>>> >>>> My image become unresponsive while making some debug, so I decided to >>>> start fresh and reinstall Grafoscopio, but I have some problems, with >>>> XML parser (so I disabled Soup temporarily) and with Glamour-Core, which >>>> provides and important part of the Grafoscopio experience. I tried also >>>> to install it from Monticello, without better results (to the version >>>> Glamour-Core-TudorGirba339). In both cases I get "SubscriptOutOfBounds: >>>> 17808" and this is the trace I get with the "Report" button (sorry I >>>> don't know other way to report): >>>> >>>> https://pastebin.com/wWM24w01 >>>> >>>> I will try with Pharo 7... The procedure is the same that was working >>>> just last week. I know the pains and advantages of having a dynamic >>>> system that is evolving quickly... hopefully a more stable platform will >>>> be there while the upcoming one is evolving. >>>> >>>> Cheers, >>>> >>>> Offray >>>> >>>> >>>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "Every now and then stop and ask yourself if the war you're fighting is the right one." >>> >>> >>> >>> >>> >>> >> >

Nov. 29, 2017

Re: [Pharo-users] How do you store and manage small programs?

by Offray Vladimir Luna CÃ¡rdenas

Hi Andy, I don't want to sound presumptuous, but I think that we can do even better that Mathematica notebooks with the Pharo ecosystem. Grafoscopio, for example, is just starting (yes, its first commit was 3 years ago, but the development has been pretty sparse at the beginning and it was my first Pharo/Smalltalk "app") and we can do stuff that is difficult (or impossible) to do in platforms like Jupyter or Mathematica. For example, we adapted Grafoscopio for making the open sourced the Data Driven Journalism Handbook (DDJH), Spanish version[1], and we have a single self contained ~600Kb file that is able to produce a 13 Mb pdf of 300+ pages document with beautiful layout and design[2]. The self referential properties of the Pharo environment give us a pretty flexible DOM, and as you can see (in the screenshot below), all the commands to produce the Grafoscopio Manual or the DDJH are *inside* the notebook, so the way you tweak Pandoc to produce a particular PDF is expressed in plain Smalltalk, without relying on any external JSON or any other external format config files. And this is just the beginning if you consider reproducible research, because the image metaphor is an excellent way to preserve all computation state of any research output, including data and code, as told in the Panama Papers post on Data continuum environments[2a] and how we can package that in "pocket infrastructures". See, for example, my 10 years old research simulation and dynamic presentation, opening without any problem, a moth ago[3], using Etoys. [1] http://mutabit.com/repos.fossil/mapeda/ [2] http://mutabit.com/repos.fossil/mapeda/uv/mapeda.pdf [2a] http://mutabit.com/offray/blog/en/entry/panama-papers-1 [3] https://twitter.com/offrayLC/status/927313455543091200 http://mutabit.com/repos.fossil/mapeda/doc/tip/img/notebook.png So, if this is just what a (no son long) newbie can do while he is also doing the PhD research and writing, without any funding from academia, government or private sector, mostly in a hackerspace of the "Global South", just imagine what we can do, for interactive notebooks and reproducible research, with bigger community engagement and funding. Despite of the Pharo alternative being "under the radar", interactive notebooks, reproducible research and long lasting digital artifacts, virtual research environments are a hot topic today and in the upcoming future[4][5][6] and with things like the ones showed and the one upcoming (GT Documenter, Pharo 7, Iceberg Git/Fossil integration), we can have a privileged position in that developing ecosystem. [4] https://khinsen.wordpress.com/2015/09/ [5] http://opendreamkit.org/ [6] http://blogs.sub.uni-hamburg.de/ifla-newsmedia/wp-content/uploads/2016/04/B… Pharo/Smalltalk can take us further that any current platform and now is a empowering medium for prototyping such visions. Cheers, Offray On 27/11/17 19:10, Andy Burnett wrote: > Wow! What a great collection of answers. Thanks everyone, I learned a > lot from that relatively simple question. > > I have installed QuickAccess - that's very cool. And, I have also > tried the <script> pragma. Having the button is very nice. I will also > try out Grafoscope. I have been playing with Mathematica Notebooks, > and I think something similar within Pharo would be wonderful. > > Cheers > Andy > > > > Yes. Plenty of solutions, from just open your Playground in a scripts > folder, to QuickAccess, to objects, to embedding scripts into more > complete data narratives. They serve different purposes, so explore them > and see which ones serves better your taste and user case. > > Cheers, > > Offray > > > On 26/11/17 07:07, Stephane Ducasse wrote: > > Hi Andy > > > > As you saw there are plenty of solutions. > > > > Now what I learned is that it is often better in the long to have a > > little object because suddenly > > it opens your mind and you realise that you can teach him something more. > > > > So I often find myself realising that I created some class methods and > > that it was stupid > > better have a real little object because it can do more and in > > particular for open new path > > > > So now I do not use scripts but plain little classes with nice little > > printOn: methods and arguments > > to get customized. > > > > Stef > > > > On Sat, Nov 25, 2017 at 6:34 PM, Andy Burnett > > <andy.burnett(a)knowinnovation.com > <mailto:andy.burnett@knowinnovation.com>> wrote: > >> I have just created a couple of small playground scripts that do some useful > >> data wrangling. The chances are that I will reuse them from time to time, > >> but with tweaks. Does version 6 Have some way to store them? I think I am > >> after a sort of scripts catalogue. > >

Nov. 29, 2017

Re: [Pharo-users] Unable to update Glamour-Core

by Juraj Kubelka

I do not have this issue. Tested on 32bit Pharo 6.1 Latest update: #60523 Cheers, Juraj > On Nov 29, 2017, at 14:06, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Hi, > > I'm using the Roassal2 load script on Pharo 6.1 on Manjaro Gnu/Linux for 64 bits: > > ======== > > Gofer it > smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; > configurationOf: 'Roassal2'; > loadStable. > ======== > That is the one, I presume, is trying to load "Glamour-Core-TudorGirba339" and generating the reported error. The quickest way to reproduce the error would be trying to install Roassal2 on Pharo 6.1. > > Cheers, > > Offray > > On 29/11/17 02:47, Tudor Girba wrote: >> Hi, >> >> I am not sure I understand your report. The Glamour-Core package is part of ConfigurationOfGlamourCore, and should not be updated separately. >> >> What script are you using for loading ConfigurationOfGlamourCore? >> >> Cheers, >> Doru >> >> >>> On Nov 29, 2017, at 3:53 AM, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> <mailto:offray.luna@mutabit.com> wrote: >>> >>> Hi, >>> >>> My image become unresponsive while making some debug, so I decided to >>> start fresh and reinstall Grafoscopio, but I have some problems, with >>> XML parser (so I disabled Soup temporarily) and with Glamour-Core, which >>> provides and important part of the Grafoscopio experience. I tried also >>> to install it from Monticello, without better results (to the version >>> Glamour-Core-TudorGirba339). In both cases I get "SubscriptOutOfBounds: >>> 17808" and this is the trace I get with the "Report" button (sorry I >>> don't know other way to report): >>> >>> https://pastebin.com/wWM24w01 <https://pastebin.com/wWM24w01> >>> >>> I will try with Pharo 7... The procedure is the same that was working >>> just last week. I know the pains and advantages of having a dynamic >>> system that is evolving quickly... hopefully a more stable platform will >>> be there while the upcoming one is evolving. >>> >>> Cheers, >>> >>> Offray >>> >>> >>> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> >> www.feenk.com <http://www.feenk.com/> >> >> "Every now and then stop and ask yourself if the war you're fighting is the right one." >> >> >> >> >> >> >

Nov. 29, 2017

Re: [Pharo-users] Unable to update Glamour-Core

by Offray Vladimir Luna CÃ¡rdenas

Hi, I'm using the Roassal2 load script on Pharo 6.1 on Manjaro Gnu/Linux for 64 bits: ======== |Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; configurationOf: 'Roassal2'; loadStable.| ======== That is the one, I presume, is trying to load "Glamour-Core-TudorGirba339" and generating the reported error. The quickest way to reproduce the error would be trying to install Roassal2 on Pharo 6.1. Cheers, Offray On 29/11/17 02:47, Tudor Girba wrote: > Hi, > > I am not sure I understand your report. The Glamour-Core package is part of ConfigurationOfGlamourCore, and should not be updated separately. > > What script are you using for loading ConfigurationOfGlamourCore? > > Cheers, > Doru > > >> On Nov 29, 2017, at 3:53 AM, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: >> >> Hi, >> >> My image become unresponsive while making some debug, so I decided to >> start fresh and reinstall Grafoscopio, but I have some problems, with >> XML parser (so I disabled Soup temporarily) and with Glamour-Core, which >> provides and important part of the Grafoscopio experience. I tried also >> to install it from Monticello, without better results (to the version >> Glamour-Core-TudorGirba339). In both cases I get "SubscriptOutOfBounds: >> 17808" and this is the trace I get with the "Report" button (sorry I >> don't know other way to report): >> >> https://pastebin.com/wWM24w01 >> >> I will try with Pharo 7... The procedure is the same that was working >> just last week. I know the pains and advantages of having a dynamic >> system that is evolving quickly... hopefully a more stable platform will >> be there while the upcoming one is evolving. >> >> Cheers, >> >> Offray >> >> >> > -- > www.tudorgirba.com > www.feenk.com > > "Every now and then stop and ask yourself if the war you're fighting is the right one." > > > > > >

Nov. 29, 2017

Using ZIP file system

by Juraj Kubelka

Hi, Do I use the ZIP file system correctly? I do the following: -=-=-=- zipFile := FileLocator temp / 'file.zip'. zipFileSystem := (FileSystem zip: zipFile) open. (zipFileSystem root / 'dir1') createDirectory. (zipFileSystem root / 'dir1' / 'file.txt') writeStreamDo: [ :stream | stream << 'Hello World!' ]. zipFileSystem close. zipFile contents. -=-=-=- And zipFileSystem close produces an error. Thanks for any advice. Juraj

Nov. 29, 2017

Re: [Pharo-users] Behold Pharo: The Modern Smalltalk

by Offray Vladimir Luna CÃ¡rdenas

On 13/10/17 08:52, Vitor Medina Cruz wrote: > I completely agree with Ben. > > As for Dimitris, I have some points: > [...] > > The fact is , we love pain, we love barriers, we love doors that > slam into our face. We love challange. But only if we find it > interesting. > > > See, I think thatâs not the point, the point is that people are very > resistant to any change in their habits, so much thatâs usually better > to short-circuit into their habits to make a change instead of trying > to force a hard change on them. That is why I think Ben point of view > is not flawed at all, on the contrary, removing barriers is a way to > make Pharo seems more like what people are habituated, > short-circuiting peoples habits into Pharo usage. Withing time, people > better understanding of Pharo may trigger small, but incremental, > changes to itâs habits to get the âA-ha!!!â moment where live code and > all wonders of Pharo make sense. > > I frankly read very loosely the rest of you answer ( :) :P ), but I > get you are not interested in making Pharo popular rather than get > really interested, open minded people on borad so to make it even more > amazing, but I also disagree here (in partÂ :) ). There are lotâs of > people who could do better for the community if the entrance were > easier, more popularity could means more opportunity in job field and, > in a more philosophical matter, a way to make the whole current > programming field better. Of course, with more popularity comes > disadvantages as well, some of which you already said, which can be > addressed, but if this is price to pay I personally think it is worth it. > [...] > On Fri, Oct 13, 2017 at 4:00 AM, Dimitris Chloupis > <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: > > > That is a familiar path, but still an obstacle for people to > get over in trying Pharo - i.e. its a barrier of entry.Â I've > previously referred to this article by JoelOnSoftware, but to > pull out a key part... "Think of these barriers as an obstacle > course that people have to run before you can count them as > your customers. If you start out with a field of 1000 runners, > about half of them will trip on the tires; half of the > survivors wonât be strong enough to jump the wall; half of > those survivors will fall off the rope ladder into the mud, > and so on, until only 1 or 2 people actually overcome all the > hurdles. With 8 or 9 barriers, everybody will have one > non-negotiable deal killer.Â This calculus means that > eliminating barriers to switching is the most important thing > you have to do if you want to take over an existing market, > because eliminating just one barrier will likely double your > sales. Eliminate two barriers, and youâll double your sales > again." > > [...] > Â > > The learning curve of Smalltalk and Lisp are plain insane. Made > learningh DOS Assembly a walk in the park in comparison.Â > > But frankly thats half of the fun.Â > > Many obstacles, many challanges.Â > > And there lies my point that an obstacle is a good thing when it > becomes an interesting challange. You have to have at least a > degree of masochism to learn how to code in any language. Of > course the question is what makes an interesting challange and > welcome to the abyss that is called "human brain". None knows and > we are not anywhere close in finding out.Â > > What we know is that documentation is super important , whether > you are a masochist or not, you need it to progress. Problems is > that documentation is hard to create and maintain, again masochism > required. So we should not just worry about making it easier for > people to reach documentation we should make it easier for people > to maintain it. Because even masochism has its limits. Those > limits are as far it is a pleasureable pain.Â > > So congratulations to anyone reading this long post , you already > proven my point. > I read it the same way as Vitor did also (I don't know why my mail client marked some part of this thread as unread), so answering Dimitris mail is not a probe of being pain lovers ( :-P ). > A huge plus also for Pharo is the community and how welcoming it > is, we take for granted but my experience with Python was not the > best either. I joined the IRC channel, other than having to endure > the stupidity of "say lol 3 times and you are banned" , too many > wars over languages and how superior Python is than anything else. > Guido is god and blah blah blah... No thanks.Â > > People here are open minded, still "religious" about Smaltalk but > they actually want to help , not to teach, actually help.Â > > I think we are a bit too obsessed on how to make Pharo popular, > Smalltalkers suffer from this insecurity of the "failure" of the > "best language of the world" not only to become popular but also > to convince coders that "is not a a relic of the past".Â Â > > But we are fine, documentation is doing grear, Pharo is improving > rapidly , the community is welcoming as ever. All we need is > embrace our successes and our failures, reject the hype, consider > the crticism and accept it or reject it and generally carry on > doing what we all love.Â > > Improving Pharo.Â > > ;) > > I think, as I have said and mentioned in the thread, that the issue is having the proper community size (but I don't know how to calculate that). This, in my case means to show Pharo to non-developers (like myself): activists, journalist, (non-software) researchers and so on, and show them something similar (not equal) to what they know, but with advantages. So we start by learning Markdown, using Grafoscopio to write structured documents with markdown, then using it to learn how to create the same visualizations that you could do in a spreadsheet (pie and bar charts), , but with coding and then using coding to create visualization you can not get in as premade in any point and click interface. That path from what they know (mostly spreed sheets and word processing) to what is possible with coding has being worthy and more pleasant to traverse that the classical (and dumb) "hello world!" introductions to programming or even other "data science" course that are tools focused. We use the idea of moldable tools to "escape the tools". That means that you need to learn how to think symbolically (coding) to express the features you want the tool to have. Documentation is going well. In fact the stuff that kept me away of Squeak, despite of its potential was the lack of documentation. "The artifact is the curriculum" was to powerful but too heavy. You need a way to understand how to deconstruct and navigate the artifact that is usually anchored with the culture you have (books and reading) instead of only launching inspectors os browsing the code. Grafoscopio is my attempt to fill that gap between the world of objects/simulations and the world of scripts/documents. Cheers, Offray

Nov. 29, 2017