- Pharo-users - lists.pharo.org

Re: [Pharo-users] Make Smalltalk Great Again!

by phil＠highoctane.be

Nice. A mention of PharoJS makes sense in it as you mention Amber and PharoJS is another option. Not sure I want to make Smalltalk great "again" but we've been through this a few times. Phil On Sat, Oct 22, 2016 at 3:03 AM, horrido <horrido.hobbies(a)gmail.com> wrote: > Today, my Smalltalk article at TechBeacon > <http://techbeacon.com/how-learning-smalltalk-can-make- > you-better-developer> > surpassed 17,000 page views!!! I am so proud. My message has reached far > more businesses and IT professionals than I could've possibly imagined! > (TechBeacon is a âdigital hubâ for developer and tech professionals > sponsored by Hewlett Packard Enterprise.) > > #MakeSmalltalkGreatAgain > <https://twitter.com/hashtag/MakeSmalltalkGreatAgain?src=hash> at > Twitter. > > <http://forum.world.st/file/n4919686/gfm2.jpeg> > > > > -- > View this message in context: http://forum.world.st/Make- > Smalltalk-Great-Again-tp4919686.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > >

Oct. 22, 2016

Re: [Pharo-users] Other format to Filetree

by Dimitris Chloupis

Yeah I agree the format is unreadable for github users .The reason is like that is that it makes merges more fine grained. Indeed a fileout will give you what you want. You can also use gist which will make it easier for them to view and you won't have to version control it. The playground also has a way of posting snippets online. Downloading and using Pharo is an alternative. You can distribute your project via Catalog Browser which will make it a one click install, the it's just a matter of using the browse message. Or you can make a small piece of Smalltalk code that installs and opens the browser to the class and method you want to show. You could even hack the profstef tutorial for a small demonstration .

Oct. 22, 2016

Re: [Pharo-users] Other format to Filetree

by Charlie Robbats

I'd like to suggest you teach people Smalltalk natively, so they don't get distracted by the false view of a filetree of classes. One huge differentiator of Smalltalk, from any other language out there, is the live object environment. You should use that environment to teach from or the nuance will be lost and they may well give up. Consider, is there any Java IDE that allows any expression anywhere to be evaluated and inspected with a mouse click or shortcut? So host your mcz on github but provide an install doc to have them install Pharo and load your code, for the lessons. They will look at Smalltalk code naturally in Pharo browsers and be exposed to an IDE they have never before experienced, as well. In the process you can webinar your navigations that they can follow along. Nebraska around? Those who consider it worthy will stay. Keep doing what you are doing! Charlie On 10/21/2016 8:51 PM, Vitor Medina Cruz wrote: > Thank you for the answers! Actually my question has a rather silly > reason: I find it difficult to navigate and peek at code in the > current format. I would like to show ST code to other people through > GitHub â it is pretty common for me to discuss implementations of > katas, for example, from multiple platforms only looking at the GitHub > project â, but the format get in the way. People usually give up of > looking it because it is hard to navigate through the directory tree > and understand all the separate pieces as a whole, and so I must > explain my solution verbally and people get suspicious of ST and > unwilling to try the environment for the first time. :( > > I think I am going to commit a fileout of the project, maybe people > will find easier to peek at. Do you have other suggestion? > > Thanks! > Vitor > > On Fri, Oct 21, 2016 at 4:36 PM, Dimitris Chloupis > <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: > > Do you have something specific in your mind ? > > What are your needs and desires for an alternate Filetree format ? > What you want to see changed in Filetreee ? > > > On Fri, Oct 21, 2016 at 7:02 PM Vitor Medina Cruz > <vitormcruz(a)gmail.com <mailto:vitormcruz@gmail.com>> wrote: > > Hello, > > I was wondering: is there another format available for Filetree? > > Regards, > Vitor > >

Oct. 22, 2016

Make Smalltalk Great Again!

by horrido

Today, my Smalltalk article at TechBeacon <http://techbeacon.com/how-learning-smalltalk-can-make-you-better-developer> surpassed 17,000 page views!!! I am so proud. My message has reached far more businesses and IT professionals than I could've possibly imagined! (TechBeacon is a âdigital hubâ for developer and tech professionals sponsored by Hewlett Packard Enterprise.) #MakeSmalltalkGreatAgain <https://twitter.com/hashtag/MakeSmalltalkGreatAgain?src=hash> at Twitter. <http://forum.world.st/file/n4919686/gfm2.jpeg> -- View this message in context: http://forum.world.st/Make-Smalltalk-Great-Again-tp4919686.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Oct. 22, 2016

Re: [Pharo-users] Other format to Filetree

by Martin McClure

On 10/21/2016 05:51 PM, Vitor Medina Cruz wrote: > Thank you for the answers! Actually my question has a rather silly > reason: I find it difficult to navigate and peek at code in the current > format. I would like to show ST code to other people through GitHub â it > is pretty common for me to discuss implementations of katas, for > example, from multiple platforms only looking at the GitHub project â, > but the format get in the way. People usually give up of looking it > because it is hard to navigate through the directory tree and understand > all the separate pieces as a whole, and so I must explain my solution > verbally and people get suspicious of ST and unwilling to try the > environment for the first time. :( This is exactly the kind of thing that the file-per-class format is aimed at. It will be closer to what non-ST people are used to, and tools like the ones GitHub offers will work better when files contain more. But it's not available yet. I'm working towards it, though. > > I think I am going to commit a fileout of the project, maybe people will > find easier to peek at. Do you have other suggestion? That may be easier for now. Good luck getting them to look at it! Spreading Smalltalk is good. Regards, -Martin

Oct. 22, 2016

Re: [Pharo-users] Other format to Filetree

by Vitor Medina Cruz

Thank you for the answers! Actually my question has a rather silly reason: I find it difficult to navigate and peek at code in the current format. I would like to show ST code to other people through GitHub â it is pretty common for me to discuss implementations of katas, for example, from multiple platforms only looking at the GitHub project â, but the format get in the way. People usually give up of looking it because it is hard to navigate through the directory tree and understand all the separate pieces as a whole, and so I must explain my solution verbally and people get suspicious of ST and unwilling to try the environment for the first time. :( I think I am going to commit a fileout of the project, maybe people will find easier to peek at. Do you have other suggestion? Thanks! Vitor On Fri, Oct 21, 2016 at 4:36 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > Do you have something specific in your mind ? > > What are your needs and desires for an alternate Filetree format ? What > you want to see changed in Filetreee ? > > > On Fri, Oct 21, 2016 at 7:02 PM Vitor Medina Cruz <vitormcruz(a)gmail.com> > wrote: > >> Hello, >> >> I was wondering: is there another format available for Filetree? >> >> Regards, >> Vitor >> >

Oct. 22, 2016

Re: [Pharo-users] Other format to Filetree

by Dimitris Chloupis

Do you have something specific in your mind ? What are your needs and desires for an alternate Filetree format ? What you want to see changed in Filetreee ? On Fri, Oct 21, 2016 at 7:02 PM Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > Hello, > > I was wondering: is there another format available for Filetree? > > Regards, > Vitor >

Oct. 21, 2016

Re: [Pharo-users] Other format to Filetree

by Martin McClure

Vitor Medina Cruz wrote: > I was wondering: is there another format available for Filetree? Hi Vitor, I'm not sure exactly what you're looking for. The current package formats in Pharo are, as you probably know, Filetree and MCZ (Monticello archives). I find Filetree easier to use, managing source code in Git. >From Filetree was developed Cypress, which is very similar, and intended to be compatible across different Smalltalk dialects. I'm working on a second version of the Cypress standard, which will have two basic formats: file-per-method, similar to the current Cypress, and a file-per-class format. The two formats will be logically equivalent, but each has strengths and weaknesses regarding the tools they work with. I hope this answers some of what you were looking for. Further questions are welcome. Regards, -Martin

Oct. 21, 2016

Other format to Filetree

by Vitor Medina Cruz

Hello, I was wondering: is there another format available for Filetree? Regards, Vitor

Oct. 21, 2016

Xtreams: Debugging Grammars

by Chris Cunnington

>When I evaluate: > parser := PEGParser parserPEG parse: 'Grammar' stream: PEGParser grammarEmailAddress actor: PEGParserParser new. >I get: KeyNotFound: key 'quotedstring' not found in Dictionary >How am I supposed to debug that to find the typo in my giant string above?! Hi Sean, Your error is saying is that there is no key called 'quotedstring' in the dictionary in the grammar ivar of your parser. In each parser is a grammar ivar. It contains a dictionary. The values of the dictionary are graphs of compiled blocks. Each node of the graph is a block with arguments that are blocks that have arguments that are blocks, etc. It's a graph of compiled blocks. Try this. Add in PEGParser class. grammar3Names " a grammar to create a parser to sort three names as per page 24 of Grune's book Parsing Techniques (1990)" ^'Sentence <- NAME NAME <- "tom" / "dick" / "harry" ' Now execute this. (PEGParser parserBootstrap) parse: 'Grammar' stream: PEGParser grammar3Names reading actor: PEGParserGenerator new. That will show you the code that will create the dictionary in the grammar ivar. Now make a change. myparser := (PEGParser parserBootstrap) parse: 'Grammar' stream: PEGParser grammar3Names reading actor: PEGParserParser new. You generated the parser, not the code for the parser. To use the parser. myparser parse: 'Sentence' stream: 'harry' reading actor: nil Now let's look at the same thing in three ways. PEGParser>>#grammarPEG this is the grammar PEGParser>>#parserBootstrap this is the code generated by the PEGParserGenerator from grammarPEG PEGParser>>#parserPEG this is the parser returned by PEGParserParser from grammarPEG You will see that PEGParser parserBootstrap and PEGParser parserPEG are interchangeable anywhere. In fact, if the goal is to populate the grammar ivar with a dictionary to make a parser, then #parserPEG starts to grate on one's nerves, because you already have what you need in the grammar ivar by evaluating PEGParser parserBootstrap. #parserPEG compiles the grammarPEG using PEGParserParser into the grammar ivar to make a parser, but it's the exact same as what was already there. It's irritating. I'll release some examples in a package called Xtreamly some time before Christmas to help start understanding Xtreams-Parsing. HTH, Chris

Oct. 21, 2016