November 2016 - Pharo-users

Re: [Pharo-users] Where is the documentation of the base class libraries?

by Dimitris Chloupis

yes we try to collect all the documentation under one github organisation which includes all the books , both published and unpublishes https://github.com/SquareBracketAssociates You will find there 90% of the entire Pharo documentation, including the books I mentioned. Unlike Python we dont have 100% documentation of our standard image, I will say we are around at 60-70%. However only 50% of that documentation is up to date to pharo 5. Pharo 6 is still a WIP. On Sun, Nov 27, 2016 at 7:45 PM Derry Bryson <derrybryson(a)gmail.com> wrote: > Thanks for the helpful replies. I am working through Pharo By Example, I > was just hoping there was something like the Python documentation for Pharo. > > Derry > > On Sun, Nov 27, 2016 at 4:26 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > > Through my personal experience I have found 3 ways of learning things > > 1) Through Documentation and asking Questions, or been taught in a > course/class, this one is the most popular because is the one requiring > the least effort , but also the weakest form of learning because it offers > a very limited array of knowledge . Knowledge that is documented or from > people that can answer your questions if you can reach them. > > 2) Investigation. Investigation is basically the art of following the > clues, of piecing things together. Investigation is basically the > scientific method, you form assumptions, you test these assumptions , you > observe , you correct these assumptions according to your observations and > you repeat the process . Investigation unlike Documentation has no limits > to how far it goes however it has a big flaw too, it depends on your > ability to divide and conquer a problem. However if the problem is too > complex it will still work but it will be a very enduring process and quite > painful too. > > 3) Exploration. Exploration is abandoning any assumption or reliance to > documentation . Opening the mind to any possibility. Learning for the > purpose of true joy. No goals. No rules, No boundaries. Exploration is > great and its my favourite way of learning because it never disappoints and > never frustrates. Instead of being frustrated at a problem you have very > hard time finding documentation about or you have hard time investigating > you move to the next one. If investigation is about dividing a difficult > problem to much easier ones, Exploration is about going straight to easy > problems and let yourself through experience gradually progress to more > complex areas. I also prefer exploration because it offers a more structure > way of learning and builds confidence. The flaw of Exploration is that > there is such thing as having to much fun and you may find your self > wasting time on things that you enjoy on one hand but are not particularly > useful on another, you may lose track of your goals. > > All those 3 techniques I have opportunity practicing them when I took my > Law degree but they apply pretty much apply to everything. > > Even though the 3rd one is my favourite I use all of them when the > situation demands it. > > When it comes to Pharo > > - Documentation : Pharo By Example 5, Deep Into Pharo, Pharo for the > Enterprise , Pharo In Progress, asking question in mailing list like this > one, reading class and method comments, reading code of unit tests. > > - Investigation: Reading code directly, going through messages one by one, > creating and playing with unit tests, heavy usage of Class browser's > ability of finding senders or and implementors of a method, use of > GTSpotter for location of methods, taking a look at practical examples and > how they use the code you want to use. > > - Exploration: heavy usage of inspector , debugger and > workspace/Playground. Also heavy reliance on printing data on transcript. > An alternative way is to formulate your own data and send them an inspect > message this way you can avoid printing things and go directly to the > source. Coding inside the debugger instead of inside the browser is also > highly advisable. > > The way you work is like this > > 1) Is there Documentation of what you want to learn ? -> if yes use > Documentation > > 2) If No does reading code and its unit tests are easy enough to learn > what you want ? if yes use Investigation > > 3) If no then start making a ton of experiment in the workspace, print and > inspect many values to see exactly how the code works, move the code to > System browser through class definitions, introduce self halts > (breakpoints) and work the rest using the debugger and the inspector for > even deeper look into data processing and flow. Remember your purpose > unlike investigation is not how the code works but how the code affects the > data. > > Cannnot say if my method of learning will suit you, but take it as it is, > with a grain of salt. > > > On Sun, Nov 27, 2016 at 9:25 AM Derry Bryson <derrybryson(a)gmail.com> > wrote: > > Where can I find documentation of the base class libraries for Pharo > Smalltalk? Or is there some other way I should learn about the system? > > Thanks, > > Derry > > >

Nov. 27, 2016

Re: [Pharo-users] ZnClient GET, but just the content of the <head> tag?

by Jan KurÅ¡

Hi, PetitParser2 [1] supports parsing of streams. I have been experimenting with ZnClient and come up with the following solution: 1) Create a PP2 stream from ZnClient stream: byteStream := ZnClient new url: 'http://pharo.org'; streaming: true; get. stream := PP2CharacterStream on: byteStream encoder: ZnUTF8Encoder new. 2) Create a parser for header: head := '<head>' asPParser, #any asPParser starLazy, '</head>' asPParser. 3) Create a parser that reads everything up till header or body (in case header is not present) and parse the header: headStart := '<head' asPParser. bodyStart := '<body' asPParser. parser := (#any asPParser starLazy: (headStart / bodyStart)), head ==> #second. result := parser optimize parse: stream. 4) Finally, the contents of header is a collection of characters, I don't know what is the best way to convert it into a string, perhaps this: text := (result second inject: (WriteStream on: '') into: [ :stream :char | stream nextPut: char. stream ]) contents Cheers, Jan [1]: https://github.com/kursjan/petitparser2 On Sun, Nov 27, 2016 at 1:38 PM PBKResearch <peter(a)pbkresearch.co.uk> wrote: > Paul > > Not sure if this is helpful - I have not tried it out, but it may give you > a > pointer. > > As Sven says, you need to parse a stream and be able to stop when you reach > the desired point. If instead of Soup you use XMLHTMLParser, this has > streaming siblings called SAXHTMLHandler and SAX2HTMLParser. I think it > should be possible to use one or the other to stop when you reach the > </head> tag. > > Personally I find the output of XMLHTMLParser easier to follow than that of > Soup, but this may be a matter of taste. > > Hope this helps > > Peter Kenny > > -----Original Message----- > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf > Of > Sven Van Caekenberghe > Sent: 26 November 2016 18:19 > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] ZnClient GET, but just the content of the <head> > tag? > > Paul, > > > On 26 Nov 2016, at 18:31, PAUL DEBRUICKER <pdebruic(a)gmail.com> wrote: > > > > This is a micro optimization if there ever was one but I wondered if it > was possible to stop downloading and get the entity once the </head> tag > has > been received. > > > > Right now I download the whole page, parse it with Soup, then extract the > tags I want from the head. Which works fine. e.g. > > > > head:=((Soup fromString: (ZnEasy get: 'http://pharo.org') entity) > > findChildTag: 'html') findChildTag: 'head'. > > This would only be useful for large pages. Dealing with the content of > resources (like parsing HTML) is outside the scope of Zinc. However, I can > help you get started. > > What you want to do is use streaming. That gives you access to the content > of a resource using a direct stream, so you could decide to stop reading > (but then you have to close the connection, else you need to read > everything > anyway). > > Start by having a look at ZnClient>>#downloadTo: and ZnStreamingEntity. > What > you want to do is more or less the following. > > ZnClient new > url: 'http://pharo.org'; > streaming: true; > get. > > At this point, the request is done, the response is in, but the entity of > the response is not yet read. When you ask for the entity, you get a > ZnStreamingEntity which holds the stream that you then have to read from. > You can check the response (and its header) for meta info. > > Your next challenge then is to process this stream so that you can parse it > in a real streaming fashion. I don't know if Soup can do this. > > Sven > > > > >

Nov. 27, 2016

Re: [Pharo-users] Where is the documentation of the base class libraries?

by Derry Bryson

Thanks for the helpful replies. I am working through Pharo By Example, I was just hoping there was something like the Python documentation for Pharo. Derry On Sun, Nov 27, 2016 at 4:26 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > Through my personal experience I have found 3 ways of learning things > > 1) Through Documentation and asking Questions, or been taught in a > course/class, this one is the most popular because is the one requiring > the least effort , but also the weakest form of learning because it offers > a very limited array of knowledge . Knowledge that is documented or from > people that can answer your questions if you can reach them. > > 2) Investigation. Investigation is basically the art of following the > clues, of piecing things together. Investigation is basically the > scientific method, you form assumptions, you test these assumptions , you > observe , you correct these assumptions according to your observations and > you repeat the process . Investigation unlike Documentation has no limits > to how far it goes however it has a big flaw too, it depends on your > ability to divide and conquer a problem. However if the problem is too > complex it will still work but it will be a very enduring process and quite > painful too. > > 3) Exploration. Exploration is abandoning any assumption or reliance to > documentation . Opening the mind to any possibility. Learning for the > purpose of true joy. No goals. No rules, No boundaries. Exploration is > great and its my favourite way of learning because it never disappoints and > never frustrates. Instead of being frustrated at a problem you have very > hard time finding documentation about or you have hard time investigating > you move to the next one. If investigation is about dividing a difficult > problem to much easier ones, Exploration is about going straight to easy > problems and let yourself through experience gradually progress to more > complex areas. I also prefer exploration because it offers a more structure > way of learning and builds confidence. The flaw of Exploration is that > there is such thing as having to much fun and you may find your self > wasting time on things that you enjoy on one hand but are not particularly > useful on another, you may lose track of your goals. > > All those 3 techniques I have opportunity practicing them when I took my > Law degree but they apply pretty much apply to everything. > > Even though the 3rd one is my favourite I use all of them when the > situation demands it. > > When it comes to Pharo > > - Documentation : Pharo By Example 5, Deep Into Pharo, Pharo for the > Enterprise , Pharo In Progress, asking question in mailing list like this > one, reading class and method comments, reading code of unit tests. > > - Investigation: Reading code directly, going through messages one by one, > creating and playing with unit tests, heavy usage of Class browser's > ability of finding senders or and implementors of a method, use of > GTSpotter for location of methods, taking a look at practical examples and > how they use the code you want to use. > > - Exploration: heavy usage of inspector , debugger and > workspace/Playground. Also heavy reliance on printing data on transcript. > An alternative way is to formulate your own data and send them an inspect > message this way you can avoid printing things and go directly to the > source. Coding inside the debugger instead of inside the browser is also > highly advisable. > > The way you work is like this > > 1) Is there Documentation of what you want to learn ? -> if yes use > Documentation > > 2) If No does reading code and its unit tests are easy enough to learn > what you want ? if yes use Investigation > > 3) If no then start making a ton of experiment in the workspace, print and > inspect many values to see exactly how the code works, move the code to > System browser through class definitions, introduce self halts > (breakpoints) and work the rest using the debugger and the inspector for > even deeper look into data processing and flow. Remember your purpose > unlike investigation is not how the code works but how the code affects the > data. > > Cannnot say if my method of learning will suit you, but take it as it is, > with a grain of salt. > > > On Sun, Nov 27, 2016 at 9:25 AM Derry Bryson <derrybryson(a)gmail.com> > wrote: > >> Where can I find documentation of the base class libraries for Pharo >> Smalltalk? Or is there some other way I should learn about the system? >> >> Thanks, >> >> Derry >> >

Nov. 27, 2016

Re: [Pharo-users] ZnClient GET, but just the content of the <head> tag?

by PBKResearch

Paul Not sure if this is helpful - I have not tried it out, but it may give you a pointer. As Sven says, you need to parse a stream and be able to stop when you reach the desired point. If instead of Soup you use XMLHTMLParser, this has streaming siblings called SAXHTMLHandler and SAX2HTMLParser. I think it should be possible to use one or the other to stop when you reach the </head> tag. Personally I find the output of XMLHTMLParser easier to follow than that of Soup, but this may be a matter of taste. Hope this helps Peter Kenny -----Original Message----- From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Sven Van Caekenberghe Sent: 26 November 2016 18:19 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] ZnClient GET, but just the content of the <head> tag? Paul, > On 26 Nov 2016, at 18:31, PAUL DEBRUICKER <pdebruic(a)gmail.com> wrote: > > This is a micro optimization if there ever was one but I wondered if it was possible to stop downloading and get the entity once the </head> tag has been received. > > Right now I download the whole page, parse it with Soup, then extract the tags I want from the head. Which works fine. e.g. > > head:=((Soup fromString: (ZnEasy get: 'http://pharo.org') entity) > findChildTag: 'html') findChildTag: 'head'. This would only be useful for large pages. Dealing with the content of resources (like parsing HTML) is outside the scope of Zinc. However, I can help you get started. What you want to do is use streaming. That gives you access to the content of a resource using a direct stream, so you could decide to stop reading (but then you have to close the connection, else you need to read everything anyway). Start by having a look at ZnClient>>#downloadTo: and ZnStreamingEntity. What you want to do is more or less the following. ZnClient new url: 'http://pharo.org'; streaming: true; get. At this point, the request is done, the response is in, but the entity of the response is not yet read. When you ask for the entity, you get a ZnStreamingEntity which holds the stream that you then have to read from. You can check the response (and its header) for meta info. Your next challenge then is to process this stream so that you can parse it in a real streaming fashion. I don't know if Soup can do this. Sven

Nov. 27, 2016

Re: [Pharo-users] Where is the documentation of the base class libraries?

by Dimitris Chloupis

Through my personal experience I have found 3 ways of learning things 1) Through Documentation and asking Questions, or been taught in a course/class, this one is the most popular because is the one requiring the least effort , but also the weakest form of learning because it offers a very limited array of knowledge . Knowledge that is documented or from people that can answer your questions if you can reach them. 2) Investigation. Investigation is basically the art of following the clues, of piecing things together. Investigation is basically the scientific method, you form assumptions, you test these assumptions , you observe , you correct these assumptions according to your observations and you repeat the process . Investigation unlike Documentation has no limits to how far it goes however it has a big flaw too, it depends on your ability to divide and conquer a problem. However if the problem is too complex it will still work but it will be a very enduring process and quite painful too. 3) Exploration. Exploration is abandoning any assumption or reliance to documentation . Opening the mind to any possibility. Learning for the purpose of true joy. No goals. No rules, No boundaries. Exploration is great and its my favourite way of learning because it never disappoints and never frustrates. Instead of being frustrated at a problem you have very hard time finding documentation about or you have hard time investigating you move to the next one. If investigation is about dividing a difficult problem to much easier ones, Exploration is about going straight to easy problems and let yourself through experience gradually progress to more complex areas. I also prefer exploration because it offers a more structure way of learning and builds confidence. The flaw of Exploration is that there is such thing as having to much fun and you may find your self wasting time on things that you enjoy on one hand but are not particularly useful on another, you may lose track of your goals. All those 3 techniques I have opportunity practicing them when I took my Law degree but they apply pretty much apply to everything. Even though the 3rd one is my favourite I use all of them when the situation demands it. When it comes to Pharo - Documentation : Pharo By Example 5, Deep Into Pharo, Pharo for the Enterprise , Pharo In Progress, asking question in mailing list like this one, reading class and method comments, reading code of unit tests. - Investigation: Reading code directly, going through messages one by one, creating and playing with unit tests, heavy usage of Class browser's ability of finding senders or and implementors of a method, use of GTSpotter for location of methods, taking a look at practical examples and how they use the code you want to use. - Exploration: heavy usage of inspector , debugger and workspace/Playground. Also heavy reliance on printing data on transcript. An alternative way is to formulate your own data and send them an inspect message this way you can avoid printing things and go directly to the source. Coding inside the debugger instead of inside the browser is also highly advisable. The way you work is like this 1) Is there Documentation of what you want to learn ? -> if yes use Documentation 2) If No does reading code and its unit tests are easy enough to learn what you want ? if yes use Investigation 3) If no then start making a ton of experiment in the workspace, print and inspect many values to see exactly how the code works, move the code to System browser through class definitions, introduce self halts (breakpoints) and work the rest using the debugger and the inspector for even deeper look into data processing and flow. Remember your purpose unlike investigation is not how the code works but how the code affects the data. Cannnot say if my method of learning will suit you, but take it as it is, with a grain of salt. On Sun, Nov 27, 2016 at 9:25 AM Derry Bryson <derrybryson(a)gmail.com> wrote: > Where can I find documentation of the base class libraries for Pharo > Smalltalk? Or is there some other way I should learn about the system? > > Thanks, > > Derry >

Nov. 27, 2016

Re: [Pharo-users] Where is the documentation of the base class libraries?

by Hilaire

Hi Derry, Regarding the base class libraries, it is Smalltalk. I can suggest you some books about Smalltalk which was good resources when I learnt programming with Squeak, then Pharo: - Smalltalk By Example[1] - Smalltalk with style You can find free to print versions at http://stephane.ducasse.free.fr/FreeBooks.html There are probably other alternatives, but I found these two books complementary for a good starting experience. Have fun. Hilaire [1] Some chapters are implementation specific (mainly the GUI), you can safely skip them. Le 27/11/2016 Ã 08:24, Derry Bryson a Ã©crit : > Where can I find documentation of the base class libraries for Pharo > Smalltalk? Or is there some other way I should learn about the system? > -- Dr. Geo http://drgeo.eu

Nov. 27, 2016

Re: [Pharo-users] Where is the documentation of the base class libraries?

by stepharo

Hello Derry In complement to what sven said you can also read the Pharo by Example books. http://books.pharo.org Stef On Sun, 27 Nov 2016 08:24:36 +0100, Derry Bryson <derrybryson(a)gmail.com> wrote: > Where can I find documentation of the base class libraries for Pharo > Smalltalk? Or is there some other way I should learn about the system? > > Thanks, > > Derry -- Using Opera's mail client: http://www.opera.com/mail/

Nov. 27, 2016

Re: [Pharo-users] Where is the documentation of the base class libraries?

by Sven Van Caekenberghe

Hi Derry, Welcome to Pharo. > On 27 Nov 2016, at 08:24, Derry Bryson <derrybryson(a)gmail.com> wrote: > > Where can I find documentation of the base class libraries for Pharo Smalltalk? Or is there some other way I should learn about the system? > > Thanks, > > Derry The primary way you learn about Pharo is by using it and browsing around in the image (all the source code, documentation, examples & tests are included, as well as all tools and the IDE itself). But that maybe creates a chicken/egg problem. You definitively have to start with the Pharo By Example book (see book.pharo.org) There is also a nice online course you could take, http://files.pharo.org/mooc/ Good luck, have fun and keep coming back with questions. Regards, Sven

Nov. 27, 2016

Where is the documentation of the base class libraries?

by Derry Bryson

Where can I find documentation of the base class libraries for Pharo Smalltalk? Or is there some other way I should learn about the system? Thanks, Derry

Nov. 27, 2016

Re: [Pharo-users] [SmaCC] Partial Installation

by Thierry Goubier

Le 25/11/2016 Ã 23:16, Dimitris Chloupis a Ã©crit : > The version does not matter, the configuration get the github repo as is > . So it always get the latest code. I tested also with metacello > command, same problem. Ok, I think I found out why when debugging the script. Maybe Dale can confirm. You may import only one baseline (i.e. in the debug, I see only Nireas as imported baseline). Dale, how do we do to import from more than one Baseline in another baseline? Thierry > On Sat, 26 Nov 2016 at 00:12, Thierry Goubier <thierry.goubier(a)gmail.com > <mailto:thierry.goubier@gmail.com>> wrote: > > Le 25/11/2016 Ã 17:10, Dimitris Chloupis a Ã©crit : > > Are you on Pharo 6 latest image and latest VM ? > > > > Curl get.pharo.org/alpha+vmLatest > <http://get.pharo.org/alpha+vmLatest> > <http://get.pharo.org/alpha+vmLatest> > > > > Then open package browser and try to install Ephestos > > The configuration browser is still pointing at an older version of > Ephestos (or I should not try to load the stable version?). > > Thierry > > > On Fri, 25 Nov 2016 at 17:15, Thierry Goubier > <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com> > > <mailto:thierry.goubier@gmail.com > <mailto:thierry.goubier@gmail.com>>> wrote: > > > > 2016-11-25 14:34 GMT+01:00 Dimitris Chloupis > <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com> > > <mailto:kilon.alios@gmail.com <mailto:kilon.alios@gmail.com>>>: > > > > I am afraid it does not work , I updated as you described my > > baseline > > > > > https://github.com/kilon/Ephestos/blob/master/BaselineOfEphestos.package/Ba… > > > > and it gives me > > > > Error: Name not found: SmaCC-Python > > > > > > That's strange. As far as I can see, I use the exact same code > in a > > baseline of mine without errors. > > > > I'll try some tests over the week-end. > > > > Thierry > > > > > > > > > > On Fri, Nov 25, 2016 at 2:31 PM Thierry Goubier > > <thierry.goubier(a)gmail.com > <mailto:thierry.goubier@gmail.com> <mailto:thierry.goubier@gmail.com > <mailto:thierry.goubier@gmail.com>>> > > wrote: > > > > Hi Kilon, > > > > 2016-11-25 12:13 GMT+01:00 Dimitris Chloupis > > <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com> > <mailto:kilon.alios@gmail.com <mailto:kilon.alios@gmail.com>>>: > > > > Hey there , I would like to install from SmaCC only > > Python and C++ parsers , any idea how to add that > to my > > baseline as a dependency ? > > > > > > Just load the SmaCC-Python package. There is no C++ > parser. > > > > Use the following: > > > > spec > > baseline: 'SmaCC' > > with: [ spec repository: > > 'github://ThierryGoubier/SmaCC' ]; > > import: 'SmaCC'. > > spec package: <yourPackage> with: [ spec requires: > > #('SmaCC-Python') ] > > > > Regards, > > > > Thierry > > > > > > > > > > --- > > ÎÏÏÏ ÏÎ¿ e-mail ÎµÎ»ÎÎ³ÏÎ¸Î·ÎºÎµ Î³Î¹Î± Î¹Î¿ÏÏ Î±ÏÏ ÏÎ¿ ÏÏÏÎ³ÏÎ±Î¼Î¼Î± > Avast > > antivirus. > > https://www.avast.com/antivirus > > > > > > > >

Nov. 26, 2016