November 2017 - Pharo-users

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

by Alistair Grant

Hi Sean, On 14 November 2017 at 19:06, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Alistair Grant wrote >> I've committed some fixes to the development branch: > > Thanks! > > I tried your example, but apparently the OSXProcess class, which is > referenced in openChromeWith: is missing. Also, no class in the image seems > to define #createProcess:, which is sent to OSXProcess there This looks like you are using an old (cached?) version. Maybe try "Pull incoming commits" from Iceberg? You should have (minus the broken formatting from pasting): OSXChromePlatform>>openChromeWith: arguments | executableLocation process | executableLocation := self defaultExecutableLocation copyReplaceAll: ' ' with: '\ '. process := AKGOSProcess command: executableLocation arguments: arguments. process run. ^process HTH, Alistair

Nov. 14, 2017

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

by Sean P. DeNigris

Alistair Grant wrote > I've committed some fixes to the development branch: Thanks! I tried your example, but apparently the OSXProcess class, which is referenced in openChromeWith: is missing. Also, no class in the image seems to define #createProcess:, which is sent to OSXProcess there ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 14, 2017

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

by Offray Vladimir Luna CÃ¡rdenas

Thanks both, Alex and Doru for your quick answers. I'm using Manjaro Cinnamon Edition[1]. If you need any help with 32 bits over 64 bits systems, let me know. [1] https://manjaro.org/community-editions/ Cheers, Offray On 14/11/17 12:46, Aliaksei Syrel wrote: > Offray, which edition of Manjaro do you have? (XFCE, KDE or Gnome) > > Cheers, > Alex > > On 14 November 2017 at 18:41, Aliaksei Syrel <alex.syrel(a)gmail.com > <mailto:alex.syrel@gmail.com>> wrote: > > Hi Offray, > > I agree with your point of view. It is in our best interests to > make it work as smoothly as possible, ideally automagically :) > Now I will try to install Pharo6.1 onÂ Manjaro Linux in order to > see if there is something that needs to be noted in README.md. > > One of the biggest problems on linux for me is installation of > 32bit libs on 64 bit distro. That is why I will test 64bit Pharo > on 64bitÂ Manjaro Linux with Moz2D and without it. > I will let you know > > Cheers, > Alex > > On 14 November 2017 at 18:25, Offray Vladimir Luna CÃ¡rdenas > <offray.luna(a)mutabit.com <mailto:offray.luna@mutabit.com>> wrote: > > Alex, > > I understand that frustration on installation could be > motivated by other issues instead of GT Documenter, but if the > team ask to use "|Iceberg enableMetacelloIntegration: true." > |in the project readme, where it also says that is supported > for Pharo 6.1 and 7.0, is natural to think that something is > wrong with documentation and/or in the project's expectations > about its intended users and their will to invest the effort, > time and motivation for "living in the edge". I understand > that if we want stuff to be improved it should be tested, but > also that not all the people that is willing to test stuff for > Pharo 6.1 needs to live in such edge. Or the project is > sending a message that is not giving the bests firsts > impressions, or is going to users which are not intended . I > would go for a smooth install first and then for collaboration > with git. I'll make a pull request with the proposal for a > better documentation, but my understanding about how you can > go from the first (user of GT Documenter) to the second > (developer using Git integration) is not clear. > > GT Tools has been pretty empowering. I have told that several > times and I don't think that I have wrote a single line of > code in their repos. But is getting more difficult just to > test and use them and I think that is related with the idea > that my user *needs* to be also my co-developer, starting with > their ssh git key pair. If we don't make easier to contribute > by just making easier to install, there will be no evolution > either. > > Cheers, > > Offray > > > On 14/11/17 11:45, Aliaksei Syrel wrote: >> Hi Offray, >> >> I understand your frustration, but with all respect, the fact >> that you have problems with Iceberg does not mean that GT >> Documenter or any other GT tool is responsible for described >> problems. >> >> Most complains about bloc, brick, whatever is because of >> unrelated stuff. It is a little bit disappointing. Especially >> for me, as one of the maintainers. But it is ok, I got used >> to it :) >> >> I donât remember when last time I used stable Pharo (not >> because it does not exist), simply live on the edge since >> Pharo4. If no one will use Git and report problems Iceberg >> will never progress. If no one will use Bloc it will never >> get âthereâ. Unfortunately, living on the edge is dangerous, >> requires effort, motivation and time. >> >> The script that Doru provided works flawlessly on OSX, we >> load it almost everyday. !! Bloc is tested on CI and builds >> are green on Windows, Linux and OSX !!. If computer (CI) >> manages to install it, I am pretty sure human can do it too. >> Looks like there is something missing in your configuration, >> something tiny :) Error handling in Iceberg can be definitely >> improved, but it is a different story. >> >> P.S. Documenter can be installed without enabled Iceberg >> integration. This is how CI does it. You will just not be >> able to contribute. >> >> Cheers, >> Alex >> >> On Tue, 14 Nov 2017 at 16:37, Offray Vladimir Luna CÃ¡rdenas >> <offray.luna(a)mutabit.com <mailto:offray.luna@mutabit.com>> wrote: >> >> I have been just trying to install GT Documenter and is >> really frustrating (I have been unable to install it even >> for the first time!). >> >> This was the list of errors I got and steps I followed, >> in almost sequential order, just to get a (bittersweet!) >> taste of GT Documenter: >> >> * 1st: LGit_GIT_ERROR: No ssh-agent suitable >> credentials found. So I go to GitHub, follow the five >> pages of documentation to get my SSH credentials that >> start at [1], then, because I still get the same >> error, go to the Iceberg FAQ [2], try to surpass the >> erro,r via command line and doesn't work, so I go to >> the Iceberg settings and try the manual >> configuration, going to the next item >> >> [1] >> https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-… >> <https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-…> >> [2] >> https://github.com/pharo-vcs/iceberg/blob/master/README.md >> <https://github.com/pharo-vcs/iceberg/blob/master/README.md> >> >> * Now I get "Instance of LGitCredentialsSSH class did >> not understand #ifTrue:ifFalse:". I try to make sense >> of it in the debugger, but is something I cannot. >> Anyway, I rerun it and now I get: LGit_GIT_EEXISTS: >> '/home/offray/Programas/Pharo/6.1a/Dev24/pharo-local/iceberg/feenkcom/gtoolkit' >> exists and is not an empty directory. I delete that >> directory and try an installation... again >> * Now I get: "Instance of FileReference did not >> understand #notEmpty". I try to make sense of it in >> the debugger. My user is git, my public and private >> ssh keys are not empty. Despite of not making sense >> of all I understand that is trying to clone something >> at git@github.com:feenkcom/gtoolkit.git >> <mailto:git@github.com:feenkcom/gtoolkit.git>. I go >> to my image dir and then to >> `iceberg/feenkcom/gtoolkit/`. There is a git >> repository there, but is empty. >> * Now I wonder, maybe if I can just clone the directory >> there, but how I say Iceberg to load it? So I run now >> only the Metacello part. Same error and solution that >> the last time but now for gtoolkit-visualizer, Brick, >> gtoolkit-examples, Bloc and Sparta. >> * After getting my ssh keys, overcome config problems >> in shell and the Pharo settings, chasing these errors >> and solving them by cloning the repositories >> manually, I'm, a couple of hours later, ready to test >> GT Documenter, but with the last Iceberg's duplicated >> repository message about Sparta I give up. Is not >> nice to start your day accumulating frustration... >> that sets a bad mood for the rest of it, and you need >> to actively fight against. >> >> I have thought that Git is overcomplicated for most of >> the developers' tasks and communities. I don't know if >> the root of previous issues is in the "Iceberg >> enableMetacelloIntegration: true" line, but having to get >> your pair of keys working to just install software is >> overkill for the common user (and when LibGit errors are >> present, the documented solutions don't work seamlessly). >> Maybe a more sensitive solution would be just to use >> libgit, without any ssh auth to clone repositories and >> its prerequisites or even better, some download that goes >> to the files in the tip (or other) version without all >> this overhead. >> >> Anyway, as I said, I have been unable to test GT >> Documenter properly and getting feedback over GT Tools >> from the team usually requires a lot of effort in my case >> (insisting on getting answers or getting none). And that >> is just to test a promising tech that still doesn't offer >> saving features (just and awesome preview). I think that >> a more sensible approach for a good documentation toolkit >> for now is on Spec and creating custom syntax >> highlighters with SmaCC[3], that is well documented and >> works today. >> >> [3] >> https://medium.com/@juliendelplanque/hacking-a-simple-syntactic-highlighter… >> <https://medium.com/@juliendelplanque/hacking-a-simple-syntactic-highlighter…> >> >> I understand that community is trying its best, but >> expressing how current offerings are not mature and >> constructive criticism can help on that. At the moment my >> feeling is that if you want to try the new shinny alpha >> stuff from GT Documenter, you will need to be prepared >> for a lot of frustration and silence. >> >> Cheers, >> >> Offray >> >> >> On 10/11/17 12:41, Tudor Girba wrote: >>> Hi, >>> >>> As shown at ESUG, GT Documenter offers an advanced viewer (and editor) for Pillar working on top of Bloc. >>> >>> You can get it by loading: >>> >>> Iceberg enableMetacelloIntegration: true. >>> Metacello new >>> baseline: 'GToolkit'; >>> repository: 'github://feenkcom/gtoolkit/src'; >>> load. >>> >>> For example, you can then inspect: >>> 'PATH_TO_ICEBERG/feenkcom/gtoolkit/doc/transcript/index.pillarâ asFileReference >>> >>> Cheers, >>> Doru >>> >>> >>>> On Nov 10, 2017, at 12:58 PM, H. Hirzel <hannes.hirzel(a)gmail.com> <mailto:hannes.hirzel@gmail.com> wrote: >>>> >>>> A note: >>>> >>>> Tudor Girba wrote: >>>> <tudor(a)tudorgirba.com> <mailto:tudor@tudorgirba.com> Fri, Aug 25, 2017 at 1:31 PM >>>> Reply-To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >>>> <mailto:pharo-users@lists.pharo.org> >>>> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >>>> <mailto:pharo-users@lists.pharo.org> >>>> >>>> Hi, >>>> >>>> As mentioned in an announcement about 10 days ago, we are building a >>>> Pillar editor with inline viewing abilities in Bloc. Here is how it >>>> looked like. Please note the embedded picture. We continued working on >>>> it since then and we will probably announce the next version this >>>> weekend: >>>> >>>> >>>> Maybe there is now enough progress to do simple presentations in Bloc? >>>> >>>> >>>> On 11/10/17, H. Hirzel <hannes.hirzel(a)gmail.com> <mailto:hannes.hirzel@gmail.com> wrote: >>>>> Hello >>>>> >>>>> In the thread 'including Pillar in Pharo image by default' it was >>>>> suggested by Stephane Ducasse to include a subset of Pillar in the >>>>> Pharo image[1] . >>>>> >>>>> I'd like to extend that proposal a little bit it in order to do very >>>>> simple presentations. This should allow to describe at least part of >>>>> the slides used in the MOOC course [3]. >>>>> >>>>> This will be _a possible_ solution to the question brought up in the >>>>> thread 'Writing "powerpoint" like presentations in Pharo?'. >>>>> >>>>> Another use is to write instructions with executable content within >>>>> the image ("Assistants"). >>>>> >>>>> So below is the a proposal for a Pillar syntax _subset_ for class >>>>> comments and _simple_ presentations. >>>>> The numbering scheme follows the 'Pillar syntax cheat sheet' [2] >>>>> >>>>> >>>>> >>>>> >>>>> MINI PILLAR SYNTAX (a subset of Pillar) >>>>> >>>>> 1. Headers >>>>> >>>>> !Header 1 >>>>> !!Header 2 >>>>> !!!Header 3 >>>>> >>>>> >>>>> 2. Lists >>>>> >>>>> - Unordered List >>>>> # Ordered list >>>>> >>>>> >>>>> >>>>> 5. Emphasis >>>>> >>>>> ""bold"" >>>>> >>>>> >>>>> 6. Code blocks >>>>> >>>>> [[[ >>>>> Transcript show: 'Hello World'. >>>>> \]]] >>>>> >>>>> >>>>> 9. Annotation >>>>> >>>>> ${slide:title=About Pharo}$ >>>>> >>>>> >>>>> >>>>> >>>>> Next week I plan to implement the rendering of this 'Mini Pillar' in >>>>> Morphic using the Morphic API subset that works in Pharo and Squeak. >>>>> >>>>> A renderer using Bloc would also be nice. [4] >>>>> >>>>> Comments, suggestions, code snippets and other help is welcome. >>>>> >>>>> Regards >>>>> Hannes >>>>> >>>>> >>>>> >>>>> >>>>> -------------------------------------------------------------------------------------------------- >>>>> [1] Pillar subset for class comments >>>>> >>>>> Stephane Ducasse >>>>> <stepharo.self(a)gmail.com> <mailto:stepharo.self@gmail.com> Fri, Aug 11, 2017 at 7:09 PM >>>>> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >>>>> <mailto:pharo-users@lists.pharo.org> >>>>> >>>>> Tx cyril >>>>> >>>>> For class comment I image that we want >>>>> >>>>> ! >>>>> >>>>> - >>>>> - >>>>> *url* >>>>> and bold >>>>> [[[ >>>>> >>>>> ]]] >>>>> >>>>> Did I miss something. >>>>> >>>>> Stef >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -------------------------------------------------------------------------------------------------- >>>>> [2] >>>>> http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet >>>>> <http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet> >>>>> -------------------------------------------------------------------------------------------------- >>>>> >>>>> >>>>> 1. Headers >>>>> >>>>> !Header 1 >>>>> !!Header 2 >>>>> !!!Header 3 >>>>> !!!!Header 4 >>>>> !!!!!Header 5 >>>>> !!!!!!Header 6 >>>>> >>>>> 2. Lists >>>>> >>>>> - Unordered List >>>>> # Ordered list >>>>> >>>>> 3. Table >>>>> >>>>> |! Left |! Right |! Centered >>>>> |{Left |}Right| Centered >>>>> >>>>> >>>>> 4. Description >>>>> Note >>>>> on a new line >>>>> >>>>> ;head >>>>> :item >>>>> >>>>> >>>>> 5. Emphasis >>>>> >>>>> ""bold"" >>>>> ''italic'' >>>>> --strikethrough-- >>>>> __underscore__ >>>>> ==inline code== >>>>> @@subscript@@ >>>>> ^^sub-script^^ >>>>> >>>>> 6. Code blocks >>>>> >>>>> [[[labÂel=ÂhelÂloSÂcriÂpt|ÂcapÂtioÂn=How to print Hello >>>>> World|ÂlanÂguaÂge=ÂSmaÂlltalk >>>>> Transcript show: 'Hello World'. >>>>> \]]] >>>>> >>>>> >>>>> 7. Raw >>>>> >>>>> >>>>> {{{latex: >>>>> this is how you inject raw \LaTeX in your output file >>>>> }}} >>>>> >>>>> {{{marÂkdown: >>>>> this is how you inject raw `markdown` in your output file >>>>> }}} >>>>> >>>>> {{{html: >>>>> this is how you inject raw ÂhtmÂl</Âb> in your output file >>>>> }}} >>>>> >>>>> >>>>> 8. Links >>>>> >>>>> Anchor @anchor (new line) >>>>> Internal link *anchor* >>>>> External link *Google>http://google.com* >>>>> Image +Caption>file://image.png|width=50|label=label+ >>>>> >>>>> >>>>> 9. Annotation >>>>> Note >>>>> on a new line >>>>> >>>>> Annotation @@note this is a note >>>>> Todo item @@todo this is to do >>>>> >>>>> >>>>> 10. Comments >>>>> >>>>> % each line starting with % is commented >>>>> >>>>> >>>>> 11. References >>>>> >>>>> This document is copied from >>>>> http://www.cheatography.com/benjaminvanryseghem/cheat-sheets/pillar/ >>>>> <http://www.cheatography.com/benjaminvanryseghem/cheat-sheets/pillar/> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> ---------------------------------------------------------------------- >>>>> [3] Example pillar code for slides >>>>> ---------------------------------------------------------------------- >>>>> >>>>> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T… >>>>> <https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T…> >>>>> >>>>> { >>>>> "title":"To the Roots of Objects", >>>>> "subtitle":"Learning from beauty", >>>>> "author":"Stephane Ducasse", >>>>> "complement":"http://stephane.ducasse.free.fr/ \\\\ >>>>> stephane.ducasse(a)inria.fr" >>>>> <http://stephane.ducasse.free.fr/%5C%5C%5C%5Cstephane.ducasse@inria.fr> >>>>> } >>>>> >>>>> >>>>> ${toc:depthLevel=2|level=0|highlight=0}$ >>>>> >>>>> %Les sections ne sont pas des titres de slide mais dÃ©finnissent la >>>>> structure du doucment. Il est possible de rajouter >>>>> "renderStructureAsSlide":false dans pillar.conf pour ne pas crÃ©er de >>>>> slide Ã partir d'un titre. >>>>> >>>>> >>>>> ${slide:title=License}$ >>>>> >>>>> +>file://figures/CreativeCommons.png|width=50|label=figCreativeCommons+ >>>>> >>>>> >>>>> ! Introduction >>>>> >>>>> % >>>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>>> >>>>> >>>>> ${slide:title=Really?!|label=really}$ >>>>> >>>>> ${columns}$ >>>>> >>>>> ${column:width=50}$ >>>>> >>>>> %the width parameter take an Int between 1 and 100 >>>>> %For now we have to pass a line before and after an annotation, I'll >>>>> correct that soon in Pillar. >>>>> - No primitive types >>>>> - No hardcoded constructs for conditional >>>>> - Only messages >>>>> - Only objects >>>>> >>>>> ${column:width=50}$ >>>>> >>>>> - and this works? >>>>> - I mean really? >>>>> - Not even slow? >>>>> - Can't be real! >>>>> >>>>> ${endColumns}$ >>>>> >>>>> ${slide:title=Motto}$ >>>>> >>>>> - Let's open our eyes, look, understand, and deeply understand the >>>>> underlying design aspects of object-oriented programming. >>>>> >>>>> >>>>> *@really* >>>>> >>>>> *TEST !>@really* >>>>> >>>>> ${slide:title=Booleans}$ >>>>> >>>>> [[[language=smalltalk >>>>> 3 > 0 >>>>> ifTrue: ['positive'] >>>>> ifFalse: ['negative'] >>>>> -> 'positive' >>>>> ]]] >>>>> >>>>> ${slide:title=Yes ifTrue\:ifFalse\: is a message!}$ >>>>> >>>>> [[[language=smalltalk >>>>> Weather isRaining >>>>> ifTrue: [self takeMyUmbrella] >>>>> ifFalse: [self takeMySunglasses] >>>>> ]]] >>>>> >>>>> - Conceptually ==ifTrue:ifFalse:== is a message sent to an object: a >>>>> boolean! >>>>> - ==ifTrue:ifFalse:== is in fact radically optimized by the compiler >>>>> but you can implement another one such ==siAlors:sinon:== and check. >>>>> >>>>> ${slide:title=Booleans}$ >>>>> >>>>> In Pharo booleans have nothing special >>>>> - & | not >>>>> - or: and: (lazy) >>>>> - xor: >>>>> - ifTrue:ifFalse: >>>>> - ifFalse:ifTrue: >>>>> - ... >>>>> >>>>> ${slide:title=Lazy Logical Operators}$ >>>>> >>>>> *LINK>@frm:really* >>>>> >>>>> [[[language=smalltalk >>>>> false and: [1 error: 'crazy'] >>>>> -> false and not an error >>>>> ]]] >>>>> >>>>> ! Exercices >>>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>>> >>>>> !! Exercise 1: Implement not >>>>> >>>>> ${slide:title=Exercise 1\: Implement not}$ >>>>> >>>>> - Propose an implementation of not in a world where you do not have >>>>> Booleans. >>>>> - You only have objects and messages. >>>>> [[[language=smalltalk >>>>> false not >>>>> -> true >>>>> >>>>> true not >>>>> -> false >>>>> ]]] >>>>> >>>>> !!Exercise 2: Implement | (Or) ifTrue: ifFalse: >>>>> >>>>> ${toc:depthLevel=2|level=0|highlight=1}$ >>>>> >>>>> ${slide:title=Exercise 2\: Implement \| (Or)}$ >>>>> >>>>> - Propose an implementation of or in a world where you do not have >>>>> Booleans. >>>>> - You only have objects and messages. >>>>> >>>>> [[[language=smalltalk >>>>> true | true -> true >>>>> true | false -> true >>>>> true | anything -> true >>>>> >>>>> false | true -> true >>>>> false | false -> false >>>>> false | anything -> anything >>>>> ]]] >>>>> >>>>> ${slide:title=Exercise2\: Variation - Implement ifTrue\:ifFalse\:}$ >>>>> >>>>> - Propose an implementation of not in a world where you do not have >>>>> Booleans. >>>>> - You only have objects, messages and closures. >>>>> >>>>> [[[language=smalltalk >>>>> false ifTrue: [ 3 ] ifFalse: [ 5 ] >>>>> -> 5 >>>>> true ifTrue: [ 3 ] ifFalse: [ 5 ] >>>>> -> 3 >>>>> ]]] >>>>> >>>>> ! Boolean Implementation >>>>> >>>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>>> >>>>> ${slide:title=Booleans Implementation Hint One}$ >>>>> >>>>> - The solution does not use conditionals >>>>> - else we would obtain a recursive definition of ==ifTrue:ifFalse:== >>>>> >>>>> ${slide:title=Boolean Implementation Hint Two}$ >>>>> >>>>> - The solution uses three classes: ==Boolean==, ==True== and ==False== >>>>> - ==false== and ==true== are unique instances described by their own >>>>> classes >>>>> - ==false== is an instance of the class ==False== >>>>> - ==true== is an instance of the class ==True== >>>>> >>>>> +Boolean Hierarchy>file://figures/BooleanHiearchyAndInstances.png|width=50+ >>>>> >>>>> ${slide:title=How do we express choice in OOP?}$ >>>>> >>>>> - We send messages to objects >>>>> >>>>> [[[language=smalltalk >>>>> aButton color >>>>> -> Color red >>>>> >>>>> aPane color >>>>> -> Color blue >>>>> >>>>> aWindow color >>>>> -> Color grey >>>>> ]]] >>>>> >>>>> - Let's the receiver decide >>>>> >>>>> - Do not ask, tell >>>>> >>>>> ${slide:title=Boolean not implementation}$ >>>>> >>>>> - Class ==Boolean== is an abstract class that implements behavior >>>>> common to true and false. Its subclasses are ==True== and ==False==. >>>>> Subclasses must implement methods for logical operations ==&==, >>>>> ==not==, and controls ==and:==, ==or:==, ==ifTrue:==, ==ifFalse:==, >>>>> ==ifTrue:ifFalse:==, ==ifFalse:ifTrue:== >>>>> >>>>> [[[language=smalltalk >>>>> Boolean>>not >>>>> "Negation. Answer true if the receiver is false, answer false if the >>>>> receiver is true." >>>>> self subclassResponsibility >>>>> ]]] >>>>> >>>>> ${slide:title=Not implementation in two methods}$ >>>>> >>>>> [[[language=smalltalk >>>>> False>>not >>>>> "Negation -- answer true since the receiver is false." >>>>> ^ true >>>>> ]]] >>>>> >>>>> [[[language=smalltalk >>>>> True>>not >>>>> "Negation--answer false since the receiver is true." >>>>> ^ false >>>>> ]]] >>>>> >>>>> ${slide:title=Not implementation in two methods}$ >>>>> >>>>> +Not >>>>> implementation.>file://figures/BooleanHiearchyAndInstancesWithNotMethods.png|width=80+ >>>>> >>>>> ${slide:title=\| (Or)}$ >>>>> [[[language=smalltalk >>>>> >>>>> true | true -> true >>>>> true | false -> true >>>>> true | anything -> true >>>>> >>>>> false | true -> true >>>>> false | false -> false >>>>> false | anything -> anything >>>>> >>>>> ]]] >>>>> >>>>> ${slide:title=Boolean>> \| aBoolean}$ >>>>> >>>>> [[[language=smalltalk >>>>> Boolean>> | aBoolean >>>>> "Evaluating disjunction (OR). Evaluate the argument. Answer true if >>>>> either the receiver or the argument is >>>>> true." >>>>> self subclassResponsibility >>>>> ]]] >>>>> >>>>> ${slide:title=False>> \| aBoolean}$ >>>>> >>>>> [[[language=smalltalk >>>>> false | true -> true >>>>> false | false -> false >>>>> false | anything -> anything >>>>> ]]] >>>>> >>>>> [[[language=smalltalk >>>>> False >> | aBoolean >>>>> "Evaluating disjunction (OR) -- answer with the argument, aBoolean." >>>>> ^ aBoolean >>>>> ]]] >>>>> >>>>> ${slide:title=True>> \| aBoolean}$ >>>>> >>>>> [[[language=smalltalk >>>>> true | true -> true >>>>> true | false -> true >>>>> true | anything -> true >>>>> ]]] >>>>> >>>>> [[[language=smalltalk >>>>> True>> | aBoolean >>>>> "Evaluating disjunction (OR) -- answer true since the receiver is true." >>>>> ^ self >>>>> ]]] >>>>> >>>>> ${slide:title=Or implementation in two methods}$ >>>>> >>>>> +>file://figures/BooleanHiearchyAndInstancesWithOrMethods.png|width=80+ >>>>> >>>>> ${slide:title=Implementing ifTrue\:ifFalse\:}$ >>>>> >>>>> - Do you see the pattern? >>>>> - Remember that a closure freezes execution and that value launches >>>>> the execution of a frozen code. >>>>> >>>>> [[[language=smalltalk >>>>> True>>ifTrue: aTrueBlock ifFalse: aFalseBlock >>>>> ^ aTrueBlock value >>>>> ]]] >>>>> >>>>> [[[language=smalltalk >>>>> False>>ifTrue: aTrueBlock ifFalse: aFalseBlock >>>>> ^ aFalseBlock value >>>>> ]]] >>>>> >>>>> ${slide:title=Implementation Note}$ >>>>> >>>>> - Note that the Virtual Machine shortcuts calls to boolean such as >>>>> condition for speed reason. >>>>> - But you can implement your own conditional method and debug to see >>>>> that sending a message is dispatching to the right object. >>>>> >>>>> ! So what ? >>>>> >>>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>>> >>>>> ${slide:title=Ok so what?}$ >>>>> >>>>> - You will probably not implement another Boolean classes >>>>> - So is it really that totally useless? >>>>> >>>>> >>>>> ${slide:title=Message sends act as case statements}$ >>>>> >>>>> - The execution engine will select the right method in the class of the >>>>> receiver >>>>> - The case statements is dynamic in the sense that it depends on the >>>>> classes loaded and the objects to which the message is sent. >>>>> - Each time you send a message, the system will select the method >>>>> corresponding to the receiver. >>>>> >>>>> >>>>> ${slide:title=A Class Hierarchy is a Skeleton for Dynamic Dispatch}$ >>>>> >>>>> - If we would have said that the ==Boolean== would be composed of only >>>>> one class, we could not have use dynamic binding. >>>>> - A class hierarchy is the exoskeleton for dynamic binding >>>>> >>>>> - Compare the solution with one class vs. a hierarchy. >>>>> >>>>> +One single class vs. a nice >>>>> hierarchy.>file://figures/Design-FatVsDispatch.png|width=70+ >>>>> >>>>> - The hierarchy provides a way to specialize behavior. >>>>> - It is also more declarative in the sense that you only focus on one >>>>> class. >>>>> - It is more modular in the sense that you can package different >>>>> classes in different packages. >>>>> >>>>> ${slide:title=Avoid Conditionals}$ >>>>> >>>>> - Use objects and messages, when you can >>>>> - The execution engine acts as a conditional switch: Use it! >>>>> - Check the AntiIfCampaign. >>>>> >>>>> ${slide:title=Follow-up: Implement ternary logic}$ >>>>> >>>>> - Boolean: ==true==, ==false==, ==unknown== >>>>> +Ternaru Logic decision table >>>>>> file://figures/ArrayBoolean.png|width=30|label=fig:ternLogic+ >>>>> - Implementing in your own classes. >>>>> >>>>> ! Summary >>>>> >>>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>>> >>>>> ${slide:title=Summary}$ >>>>> - Tell, do not ask >>>>> - Let the receiver decide >>>>> - Message sends as potential dynamic conditional >>>>> - Class hiearchy builds a skeleton for dynamic dispatch >>>>> - Avoid conditional >>>>> >>>>> >>>>> >>>>> >>>>> ----------------------------------------- >>>>> [4] Bloc >>>>> Load Bloc with executing in a playground (Pharo 6.1) >>>>> >>>>> Metacello new >>>>> baseline: 'Bloc'; >>>>> repository: 'github://pharo-graphics/Bloc:pharo6.1/src'; >>>>> load: #core >>>>> >>>>> >>>>> A tutorial to use bloc is available on >>>>> http://files.pharo.org/books/ >>>>> Bloc Memory Game (alpha) is a first tutorial on Bloc the new graphics >>>>> core for Pharo. Booklet written by A. Chis, S. Ducasse, A. Syrel. >>>>> >>>>> http://files.pharo.org/books-pdfs/booklet-Bloc/2017-11-09-memorygame.pdf >>>>> <http://files.pharo.org/books-pdfs/booklet-Bloc/2017-11-09-memorygame.pdf> >>>>> >>>>> To load the memory game >>>>> >>>>> Metacello new >>>>> baseline: 'BlocTutorials'; >>>>> repository: 'github://pharo-graphics/Tutorials/src'; >>>>> load >>>>> >>>>> >>>>> A similar booklet could be done for the title >>>>> 'Doing a presentation / slide show / assitant with Bloc' (or similar, >>>>> adapt .....) >>>>> >>> -- >>> www.tudorgirba.com <http://www.tudorgirba.com> >>> www.feenk.com <http://www.feenk.com> >>> >>> "Obvious things are difficult to teach." >>> >>> >>> >>> >>> >>> >> >> -- >> Cheers, >> Alex > > >

Nov. 14, 2017

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

by Aliaksei Syrel

Offray, which edition of Manjaro do you have? (XFCE, KDE or Gnome) Cheers, Alex On 14 November 2017 at 18:41, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > Hi Offray, > > I agree with your point of view. It is in our best interests to make it > work as smoothly as possible, ideally automagically :) > Now I will try to install Pharo6.1 on Manjaro Linux in order to see if > there is something that needs to be noted in README.md. > > One of the biggest problems on linux for me is installation of 32bit libs > on 64 bit distro. That is why I will test 64bit Pharo on 64bit Manjaro > Linux with Moz2D and without it. > I will let you know > > Cheers, > Alex > > On 14 November 2017 at 18:25, Offray Vladimir Luna CÃ¡rdenas < > offray.luna(a)mutabit.com> wrote: > >> Alex, >> >> I understand that frustration on installation could be motivated by other >> issues instead of GT Documenter, but if the team ask to use "Iceberg >> enableMetacelloIntegration: true." in the project readme, where it also >> says that is supported for Pharo 6.1 and 7.0, is natural to think that >> something is wrong with documentation and/or in the project's expectations >> about its intended users and their will to invest the effort, time and >> motivation for "living in the edge". I understand that if we want stuff to >> be improved it should be tested, but also that not all the people that is >> willing to test stuff for Pharo 6.1 needs to live in such edge. Or the >> project is sending a message that is not giving the bests firsts >> impressions, or is going to users which are not intended . I would go for a >> smooth install first and then for collaboration with git. I'll make a pull >> request with the proposal for a better documentation, but my understanding >> about how you can go from the first (user of GT Documenter) to the second >> (developer using Git integration) is not clear. >> >> GT Tools has been pretty empowering. I have told that several times and I >> don't think that I have wrote a single line of code in their repos. But is >> getting more difficult just to test and use them and I think that is >> related with the idea that my user *needs* to be also my co-developer, >> starting with their ssh git key pair. If we don't make easier to contribute >> by just making easier to install, there will be no evolution either. >> >> Cheers, >> >> Offray >> >> On 14/11/17 11:45, Aliaksei Syrel wrote: >> >> Hi Offray, >> >> I understand your frustration, but with all respect, the fact that you >> have problems with Iceberg does not mean that GT Documenter or any other GT >> tool is responsible for described problems. >> >> Most complains about bloc, brick, whatever is because of unrelated stuff. >> It is a little bit disappointing. Especially for me, as one of the >> maintainers. But it is ok, I got used to it :) >> >> I donât remember when last time I used stable Pharo (not because it does >> not exist), simply live on the edge since Pharo4. If no one will use Git >> and report problems Iceberg will never progress. If no one will use Bloc it >> will never get âthereâ. Unfortunately, living on the edge is dangerous, >> requires effort, motivation and time. >> >> The script that Doru provided works flawlessly on OSX, we load it almost >> everyday. !! Bloc is tested on CI and builds are green on Windows, Linux >> and OSX !!. If computer (CI) manages to install it, I am pretty sure human >> can do it too. Looks like there is something missing in your configuration, >> something tiny :) Error handling in Iceberg can be definitely improved, but >> it is a different story. >> >> P.S. Documenter can be installed without enabled Iceberg integration. >> This is how CI does it. You will just not be able to contribute. >> >> Cheers, >> Alex >> >> On Tue, 14 Nov 2017 at 16:37, Offray Vladimir Luna CÃ¡rdenas < >> offray.luna(a)mutabit.com> wrote: >> >>> I have been just trying to install GT Documenter and is really >>> frustrating (I have been unable to install it even for the first time!). >>> >>> This was the list of errors I got and steps I followed, in almost >>> sequential order, just to get a (bittersweet!) taste of GT Documenter: >>> >>> - 1st: LGit_GIT_ERROR: No ssh-agent suitable credentials found. So I >>> go to GitHub, follow the five pages of documentation to get my SSH >>> credentials that start at [1], then, because I still get the same error, go >>> to the Iceberg FAQ [2], try to surpass the erro,r via command line and >>> doesn't work, so I go to the Iceberg settings and try the manual >>> configuration, going to the next item >>> >>> [1] https://help.github.com/articles/generating-a-new-ssh-key-an >>> d-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key >>> <https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-…> >>> [2] https://github.com/pharo-vcs/iceberg/blob/master/README.md >>> >>> - Now I get "Instance of LGitCredentialsSSH class did not understand >>> #ifTrue:ifFalse:". I try to make sense of it in the debugger, but is >>> something I cannot. Anyway, I rerun it and now I get: LGit_GIT_EEXISTS: >>> '/home/offray/Programas/Pharo/6.1a/Dev24/pharo-local/iceberg/feenkcom/gtoolkit' >>> exists and is not an empty directory. I delete that directory and try an >>> installation... again >>> - Now I get: "Instance of FileReference did not understand >>> #notEmpty". I try to make sense of it in the debugger. My user is git, my >>> public and private ssh keys are not empty. Despite of not making sense of >>> all I understand that is trying to clone something at >>> git@github.com:feenkcom/gtoolkit.git >>> <git@github.com:feenkcom/gtoolkit.git>. I go to my image dir and >>> then to `iceberg/feenkcom/gtoolkit/`. There is a git repository there, but >>> is empty. >>> - Now I wonder, maybe if I can just clone the directory there, but >>> how I say Iceberg to load it? So I run now only the Metacello part. Same >>> error and solution that the last time but now for gtoolkit-visualizer, >>> Brick, gtoolkit-examples, Bloc and Sparta. >>> - After getting my ssh keys, overcome config problems in shell and >>> the Pharo settings, chasing these errors and solving them by cloning the >>> repositories manually, I'm, a couple of hours later, ready to test GT >>> Documenter, but with the last Iceberg's duplicated repository message about >>> Sparta I give up. Is not nice to start your day accumulating frustration... >>> that sets a bad mood for the rest of it, and you need to actively fight >>> against. >>> >>> I have thought that Git is overcomplicated for most of the developers' >>> tasks and communities. I don't know if the root of previous issues is in >>> the "Iceberg enableMetacelloIntegration: true" line, but having to get your >>> pair of keys working to just install software is overkill for the common >>> user (and when LibGit errors are present, the documented solutions don't >>> work seamlessly). Maybe a more sensitive solution would be just to use >>> libgit, without any ssh auth to clone repositories and its prerequisites or >>> even better, some download that goes to the files in the tip (or other) >>> version without all this overhead. >>> >>> Anyway, as I said, I have been unable to test GT Documenter properly and >>> getting feedback over GT Tools from the team usually requires a lot of >>> effort in my case (insisting on getting answers or getting none). And that >>> is just to test a promising tech that still doesn't offer saving features >>> (just and awesome preview). I think that a more sensible approach for a >>> good documentation toolkit for now is on Spec and creating custom syntax >>> highlighters with SmaCC[3], that is well documented and works today. >>> >>> [3] https://medium.com/@juliendelplanque/hacking-a-simple-syntac >>> tic-highlighter-around-specs-textmodel-44ba2e2b1ab9 >>> I understand that community is trying its best, but expressing how >>> current offerings are not mature and constructive criticism can help on >>> that. At the moment my feeling is that if you want to try the new shinny >>> alpha stuff from GT Documenter, you will need to be prepared for a lot of >>> frustration and silence. >>> >>> Cheers, >>> >>> Offray >>> >>> >>> On 10/11/17 12:41, Tudor Girba wrote: >>> >>> Hi, >>> >>> As shown at ESUG, GT Documenter offers an advanced viewer (and editor) for Pillar working on top of Bloc. >>> >>> You can get it by loading: >>> >>> Iceberg enableMetacelloIntegration: true. >>> Metacello new >>> baseline: 'GToolkit'; >>> repository: 'github://feenkcom/gtoolkit/src'; >>> load. >>> >>> For example, you can then inspect: >>> 'PATH_TO_ICEBERG/feenkcom/gtoolkit/doc/transcript/index.pillarâ asFileReference >>> >>> Cheers, >>> Doru >>> >>> >>> >>> On Nov 10, 2017, at 12:58 PM, H. Hirzel <hannes.hirzel(a)gmail.com> <hannes.hirzel(a)gmail.com> wrote: >>> >>> A note: >>> >>> Tudor Girba wrote:<tudor(a)tudorgirba.com> <tudor(a)tudorgirba.com> Fri, Aug 25, 2017 at 1:31 PM >>> Reply-To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> <pharo-users(a)lists.pharo.org> >>> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> <pharo-users(a)lists.pharo.org> >>> >>> Hi, >>> >>> As mentioned in an announcement about 10 days ago, we are building a >>> Pillar editor with inline viewing abilities in Bloc. Here is how it >>> looked like. Please note the embedded picture. We continued working on >>> it since then and we will probably announce the next version this >>> weekend: >>> >>> >>> Maybe there is now enough progress to do simple presentations in Bloc? >>> >>> >>> On 11/10/17, H. Hirzel <hannes.hirzel(a)gmail.com> <hannes.hirzel(a)gmail.com> wrote: >>> >>> Hello >>> >>> In the thread 'including Pillar in Pharo image by default' it was >>> suggested by Stephane Ducasse to include a subset of Pillar in the >>> Pharo image[1] . >>> >>> I'd like to extend that proposal a little bit it in order to do very >>> simple presentations. This should allow to describe at least part of >>> the slides used in the MOOC course [3]. >>> >>> This will be _a possible_ solution to the question brought up in the >>> thread 'Writing "powerpoint" like presentations in Pharo?'. >>> >>> Another use is to write instructions with executable content within >>> the image ("Assistants"). >>> >>> So below is the a proposal for a Pillar syntax _subset_ for class >>> comments and _simple_ presentations. >>> The numbering scheme follows the 'Pillar syntax cheat sheet' [2] >>> >>> >>> >>> >>> MINI PILLAR SYNTAX (a subset of Pillar) >>> >>> 1. Headers >>> >>> !Header 1 >>> !!Header 2 >>> !!!Header 3 >>> >>> >>> 2. Lists >>> >>> - Unordered List >>> # Ordered list >>> >>> >>> >>> 5. Emphasis >>> >>> ""bold"" >>> >>> >>> 6. Code blocks >>> >>> [[[ >>> Transcript show: 'Hello World'. >>> \]]] >>> >>> >>> 9. Annotation >>> >>> ${slide:title=About Pharo}$ >>> >>> >>> >>> >>> Next week I plan to implement the rendering of this 'Mini Pillar' in >>> Morphic using the Morphic API subset that works in Pharo and Squeak. >>> >>> A renderer using Bloc would also be nice. [4] >>> >>> Comments, suggestions, code snippets and other help is welcome. >>> >>> Regards >>> Hannes >>> >>> >>> >>> >>> -------------------------------------------------------------------------------------------------- >>> [1] Pillar subset for class comments >>> >>> Stephane Ducasse<stepharo.self(a)gmail.com> <stepharo.self(a)gmail.com> Fri, Aug 11, 2017 at 7:09 PM >>> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> <pharo-users(a)lists.pharo.org> >>> >>> Tx cyril >>> >>> For class comment I image that we want >>> >>> ! >>> >>> - >>> - >>> *url* >>> and bold >>> [[[ >>> >>> ]]] >>> >>> Did I miss something. >>> >>> Stef >>> >>> >>> >>> >>> >>> -------------------------------------------------------------------------------------------------- >>> [2]http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet >>> -------------------------------------------------------------------------------------------------- >>> >>> >>> 1. Headers >>> >>> !Header 1 >>> !!Header 2 >>> !!!Header 3 >>> !!!!Header 4 >>> !!!!!Header 5 >>> !!!!!!Header 6 >>> >>> 2. Lists >>> >>> - Unordered List >>> # Ordered list >>> >>> 3. Table >>> >>> |! Left |! Right |! Centered >>> |{Left |}Right| Centered >>> >>> >>> 4. Description >>> Note >>> on a new line >>> >>> ;head >>> :item >>> >>> >>> 5. Emphasis >>> >>> ""bold"" >>> ''italic'' >>> --strikethrough-- >>> __underscore__ >>> ==inline code== >>> @@subscript@@ >>> ^^sub-script^^ >>> >>> 6. Code blocks >>> >>> [[[labÂel=ÂhelÂloSÂcriÂpt|ÂcapÂtioÂn=How to print Hello >>> World|ÂlanÂguaÂge=ÂSmaÂlltalk >>> Transcript show: 'Hello World'. >>> \]]] >>> >>> >>> 7. Raw >>> >>> >>> {{{latex: >>> this is how you inject raw \LaTeX in your output file >>> }}} >>> >>> {{{marÂkdown: >>> this is how you inject raw `markdown` in your output file >>> }}} >>> >>> {{{html: >>> this is how you inject raw ÂhtmÂl</Âb> in your output file >>> }}} >>> >>> >>> 8. Links >>> >>> Anchor @anchor (new line) >>> Internal link *anchor* >>> External link *Google>http://google.com* >>> Image +Caption>file://image.png|width=50|label=label+ >>> >>> >>> 9. Annotation >>> Note >>> on a new line >>> >>> Annotation @@note this is a note >>> Todo item @@todo this is to do >>> >>> >>> 10. Comments >>> >>> % each line starting with % is commented >>> >>> >>> 11. References >>> >>> This document is copied fromhttp://www.cheatography.com/benjaminvanryseghem/cheat-sheets/pillar/ >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> ---------------------------------------------------------------------- >>> [3] Example pillar code for slides >>> ---------------------------------------------------------------------- >>> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T… >>> >>> { >>> "title":"To the Roots of Objects", >>> "subtitle":"Learning from beauty", >>> "author":"Stephane Ducasse", >>> "complement":"http://stephane.ducasse.free.fr/ \\\\ >>> stephane.ducasse(a)inria.fr" <http://stephane.ducasse.free.fr/%5C%5C%5C%5Cstephane.ducasse@inria.fr> >>> } >>> >>> >>> ${toc:depthLevel=2|level=0|highlight=0}$ >>> >>> %Les sections ne sont pas des titres de slide mais dÃ©finnissent la >>> structure du doucment. Il est possible de rajouter >>> "renderStructureAsSlide":false dans pillar.conf pour ne pas crÃ©er de >>> slide Ã partir d'un titre. >>> >>> >>> ${slide:title=License}$ >>> >>> +>file://figures/CreativeCommons.png|width=50|label=figCreativeCommons+ >>> >>> >>> ! Introduction >>> >>> % >>> ${toc:depthLevel=1|level=0|highlight=1}$ >>> >>> >>> ${slide:title=Really?!|label=really}$ >>> >>> ${columns}$ >>> >>> ${column:width=50}$ >>> >>> %the width parameter take an Int between 1 and 100 >>> %For now we have to pass a line before and after an annotation, I'll >>> correct that soon in Pillar. >>> - No primitive types >>> - No hardcoded constructs for conditional >>> - Only messages >>> - Only objects >>> >>> ${column:width=50}$ >>> >>> - and this works? >>> - I mean really? >>> - Not even slow? >>> - Can't be real! >>> >>> ${endColumns}$ >>> >>> ${slide:title=Motto}$ >>> >>> - Let's open our eyes, look, understand, and deeply understand the >>> underlying design aspects of object-oriented programming. >>> >>> >>> *@really* >>> >>> *TEST !>@really* >>> >>> ${slide:title=Booleans}$ >>> >>> [[[language=smalltalk >>> 3 > 0 >>> ifTrue: ['positive'] >>> ifFalse: ['negative'] >>> -> 'positive' >>> ]]] >>> >>> ${slide:title=Yes ifTrue\:ifFalse\: is a message!}$ >>> >>> [[[language=smalltalk >>> Weather isRaining >>> ifTrue: [self takeMyUmbrella] >>> ifFalse: [self takeMySunglasses] >>> ]]] >>> >>> - Conceptually ==ifTrue:ifFalse:== is a message sent to an object: a >>> boolean! >>> - ==ifTrue:ifFalse:== is in fact radically optimized by the compiler >>> but you can implement another one such ==siAlors:sinon:== and check. >>> >>> ${slide:title=Booleans}$ >>> >>> In Pharo booleans have nothing special >>> - & | not >>> - or: and: (lazy) >>> - xor: >>> - ifTrue:ifFalse: >>> - ifFalse:ifTrue: >>> - ... >>> >>> ${slide:title=Lazy Logical Operators}$ >>> >>> *LINK>@frm:really* >>> >>> [[[language=smalltalk >>> false and: [1 error: 'crazy'] >>> -> false and not an error >>> ]]] >>> >>> ! Exercices >>> ${toc:depthLevel=1|level=0|highlight=1}$ >>> >>> !! Exercise 1: Implement not >>> >>> ${slide:title=Exercise 1\: Implement not}$ >>> >>> - Propose an implementation of not in a world where you do not have >>> Booleans. >>> - You only have objects and messages. >>> [[[language=smalltalk >>> false not >>> -> true >>> >>> true not >>> -> false >>> ]]] >>> >>> !!Exercise 2: Implement | (Or) ifTrue: ifFalse: >>> >>> ${toc:depthLevel=2|level=0|highlight=1}$ >>> >>> ${slide:title=Exercise 2\: Implement \| (Or)}$ >>> >>> - Propose an implementation of or in a world where you do not have >>> Booleans. >>> - You only have objects and messages. >>> >>> [[[language=smalltalk >>> true | true -> true >>> true | false -> true >>> true | anything -> true >>> >>> false | true -> true >>> false | false -> false >>> false | anything -> anything >>> ]]] >>> >>> ${slide:title=Exercise2\: Variation - Implement ifTrue\:ifFalse\:}$ >>> >>> - Propose an implementation of not in a world where you do not have >>> Booleans. >>> - You only have objects, messages and closures. >>> >>> [[[language=smalltalk >>> false ifTrue: [ 3 ] ifFalse: [ 5 ] >>> -> 5 >>> true ifTrue: [ 3 ] ifFalse: [ 5 ] >>> -> 3 >>> ]]] >>> >>> ! Boolean Implementation >>> >>> ${toc:depthLevel=1|level=0|highlight=1}$ >>> >>> ${slide:title=Booleans Implementation Hint One}$ >>> >>> - The solution does not use conditionals >>> - else we would obtain a recursive definition of ==ifTrue:ifFalse:== >>> >>> ${slide:title=Boolean Implementation Hint Two}$ >>> >>> - The solution uses three classes: ==Boolean==, ==True== and ==False== >>> - ==false== and ==true== are unique instances described by their own >>> classes >>> - ==false== is an instance of the class ==False== >>> - ==true== is an instance of the class ==True== >>> >>> +Boolean Hierarchy>file://figures/BooleanHiearchyAndInstances.png|width=50+ >>> >>> ${slide:title=How do we express choice in OOP?}$ >>> >>> - We send messages to objects >>> >>> [[[language=smalltalk >>> aButton color >>> -> Color red >>> >>> aPane color >>> -> Color blue >>> >>> aWindow color >>> -> Color grey >>> ]]] >>> >>> - Let's the receiver decide >>> >>> - Do not ask, tell >>> >>> ${slide:title=Boolean not implementation}$ >>> >>> - Class ==Boolean== is an abstract class that implements behavior >>> common to true and false. Its subclasses are ==True== and ==False==. >>> Subclasses must implement methods for logical operations ==&==, >>> ==not==, and controls ==and:==, ==or:==, ==ifTrue:==, ==ifFalse:==, >>> ==ifTrue:ifFalse:==, ==ifFalse:ifTrue:== >>> >>> [[[language=smalltalk >>> Boolean>>not >>> "Negation. Answer true if the receiver is false, answer false if the >>> receiver is true." >>> self subclassResponsibility >>> ]]] >>> >>> ${slide:title=Not implementation in two methods}$ >>> >>> [[[language=smalltalk >>> False>>not >>> "Negation -- answer true since the receiver is false." >>> ^ true >>> ]]] >>> >>> [[[language=smalltalk >>> True>>not >>> "Negation--answer false since the receiver is true." >>> ^ false >>> ]]] >>> >>> ${slide:title=Not implementation in two methods}$ >>> >>> +Not >>> implementation.>file://figures/BooleanHiearchyAndInstancesWithNotMethods.png|width=80+ >>> >>> ${slide:title=\| (Or)}$ >>> [[[language=smalltalk >>> >>> true | true -> true >>> true | false -> true >>> true | anything -> true >>> >>> false | true -> true >>> false | false -> false >>> false | anything -> anything >>> >>> ]]] >>> >>> ${slide:title=Boolean>> \| aBoolean}$ >>> >>> [[[language=smalltalk >>> Boolean>> | aBoolean >>> "Evaluating disjunction (OR). Evaluate the argument. Answer true if >>> either the receiver or the argument is >>> true." >>> self subclassResponsibility >>> ]]] >>> >>> ${slide:title=False>> \| aBoolean}$ >>> >>> [[[language=smalltalk >>> false | true -> true >>> false | false -> false >>> false | anything -> anything >>> ]]] >>> >>> [[[language=smalltalk >>> False >> | aBoolean >>> "Evaluating disjunction (OR) -- answer with the argument, aBoolean." >>> ^ aBoolean >>> ]]] >>> >>> ${slide:title=True>> \| aBoolean}$ >>> >>> [[[language=smalltalk >>> true | true -> true >>> true | false -> true >>> true | anything -> true >>> ]]] >>> >>> [[[language=smalltalk >>> True>> | aBoolean >>> "Evaluating disjunction (OR) -- answer true since the receiver is true." >>> ^ self >>> ]]] >>> >>> ${slide:title=Or implementation in two methods}$ >>> >>> +>file://figures/BooleanHiearchyAndInstancesWithOrMethods.png|width=80+ >>> >>> ${slide:title=Implementing ifTrue\:ifFalse\:}$ >>> >>> - Do you see the pattern? >>> - Remember that a closure freezes execution and that value launches >>> the execution of a frozen code. >>> >>> [[[language=smalltalk >>> True>>ifTrue: aTrueBlock ifFalse: aFalseBlock >>> ^ aTrueBlock value >>> ]]] >>> >>> [[[language=smalltalk >>> False>>ifTrue: aTrueBlock ifFalse: aFalseBlock >>> ^ aFalseBlock value >>> ]]] >>> >>> ${slide:title=Implementation Note}$ >>> >>> - Note that the Virtual Machine shortcuts calls to boolean such as >>> condition for speed reason. >>> - But you can implement your own conditional method and debug to see >>> that sending a message is dispatching to the right object. >>> >>> ! So what ? >>> >>> ${toc:depthLevel=1|level=0|highlight=1}$ >>> >>> ${slide:title=Ok so what?}$ >>> >>> - You will probably not implement another Boolean classes >>> - So is it really that totally useless? >>> >>> >>> ${slide:title=Message sends act as case statements}$ >>> >>> - The execution engine will select the right method in the class of the >>> receiver >>> - The case statements is dynamic in the sense that it depends on the >>> classes loaded and the objects to which the message is sent. >>> - Each time you send a message, the system will select the method >>> corresponding to the receiver. >>> >>> >>> ${slide:title=A Class Hierarchy is a Skeleton for Dynamic Dispatch}$ >>> >>> - If we would have said that the ==Boolean== would be composed of only >>> one class, we could not have use dynamic binding. >>> - A class hierarchy is the exoskeleton for dynamic binding >>> >>> - Compare the solution with one class vs. a hierarchy. >>> >>> +One single class vs. a nice >>> hierarchy.>file://figures/Design-FatVsDispatch.png|width=70+ >>> >>> - The hierarchy provides a way to specialize behavior. >>> - It is also more declarative in the sense that you only focus on one >>> class. >>> - It is more modular in the sense that you can package different >>> classes in different packages. >>> >>> ${slide:title=Avoid Conditionals}$ >>> >>> - Use objects and messages, when you can >>> - The execution engine acts as a conditional switch: Use it! >>> - Check the AntiIfCampaign. >>> >>> ${slide:title=Follow-up: Implement ternary logic}$ >>> >>> - Boolean: ==true==, ==false==, ==unknown== >>> +Ternaru Logic decision table >>> >>> file://figures/ArrayBoolean.png|width=30|label=fig:ternLogic+ >>> >>> - Implementing in your own classes. >>> >>> ! Summary >>> >>> ${toc:depthLevel=1|level=0|highlight=1}$ >>> >>> ${slide:title=Summary}$ >>> - Tell, do not ask >>> - Let the receiver decide >>> - Message sends as potential dynamic conditional >>> - Class hiearchy builds a skeleton for dynamic dispatch >>> - Avoid conditional >>> >>> >>> >>> >>> ----------------------------------------- >>> [4] Bloc >>> Load Bloc with executing in a playground (Pharo 6.1) >>> >>> Metacello new >>> baseline: 'Bloc'; >>> repository: 'github://pharo-graphics/Bloc:pharo6.1/src'; >>> load: #core >>> >>> >>> A tutorial to use bloc is available onhttp://files.pharo.org/books/ >>> Bloc Memory Game (alpha) is a first tutorial on Bloc the new graphics >>> core for Pharo. Booklet written by A. Chis, S. Ducasse, A. Syrel. >>> http://files.pharo.org/books-pdfs/booklet-Bloc/2017-11-09-memorygame.pdf >>> >>> To load the memory game >>> >>> Metacello new >>> baseline: 'BlocTutorials'; >>> repository: 'github://pharo-graphics/Tutorials/src'; >>> load >>> >>> >>> A similar booklet could be done for the title >>> 'Doing a presentation / slide show / assitant with Bloc' (or similar, >>> adapt .....) >>> >>> >>> --www.tudorgirba.comwww.feenk.com >>> >>> "Obvious things are difficult to teach." >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >> Cheers, >> Alex >> >> >> >

Nov. 14, 2017

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

by Aliaksei Syrel

Hi Offray, I agree with your point of view. It is in our best interests to make it work as smoothly as possible, ideally automagically :) Now I will try to install Pharo6.1 on Manjaro Linux in order to see if there is something that needs to be noted in README.md. One of the biggest problems on linux for me is installation of 32bit libs on 64 bit distro. That is why I will test 64bit Pharo on 64bit Manjaro Linux with Moz2D and without it. I will let you know Cheers, Alex On 14 November 2017 at 18:25, Offray Vladimir Luna CÃ¡rdenas < offray.luna(a)mutabit.com> wrote: > Alex, > > I understand that frustration on installation could be motivated by other > issues instead of GT Documenter, but if the team ask to use "Iceberg > enableMetacelloIntegration: true." in the project readme, where it also > says that is supported for Pharo 6.1 and 7.0, is natural to think that > something is wrong with documentation and/or in the project's expectations > about its intended users and their will to invest the effort, time and > motivation for "living in the edge". I understand that if we want stuff to > be improved it should be tested, but also that not all the people that is > willing to test stuff for Pharo 6.1 needs to live in such edge. Or the > project is sending a message that is not giving the bests firsts > impressions, or is going to users which are not intended . I would go for a > smooth install first and then for collaboration with git. I'll make a pull > request with the proposal for a better documentation, but my understanding > about how you can go from the first (user of GT Documenter) to the second > (developer using Git integration) is not clear. > > GT Tools has been pretty empowering. I have told that several times and I > don't think that I have wrote a single line of code in their repos. But is > getting more difficult just to test and use them and I think that is > related with the idea that my user *needs* to be also my co-developer, > starting with their ssh git key pair. If we don't make easier to contribute > by just making easier to install, there will be no evolution either. > > Cheers, > > Offray > > On 14/11/17 11:45, Aliaksei Syrel wrote: > > Hi Offray, > > I understand your frustration, but with all respect, the fact that you > have problems with Iceberg does not mean that GT Documenter or any other GT > tool is responsible for described problems. > > Most complains about bloc, brick, whatever is because of unrelated stuff. > It is a little bit disappointing. Especially for me, as one of the > maintainers. But it is ok, I got used to it :) > > I donât remember when last time I used stable Pharo (not because it does > not exist), simply live on the edge since Pharo4. If no one will use Git > and report problems Iceberg will never progress. If no one will use Bloc it > will never get âthereâ. Unfortunately, living on the edge is dangerous, > requires effort, motivation and time. > > The script that Doru provided works flawlessly on OSX, we load it almost > everyday. !! Bloc is tested on CI and builds are green on Windows, Linux > and OSX !!. If computer (CI) manages to install it, I am pretty sure human > can do it too. Looks like there is something missing in your configuration, > something tiny :) Error handling in Iceberg can be definitely improved, but > it is a different story. > > P.S. Documenter can be installed without enabled Iceberg integration. This > is how CI does it. You will just not be able to contribute. > > Cheers, > Alex > > On Tue, 14 Nov 2017 at 16:37, Offray Vladimir Luna CÃ¡rdenas < > offray.luna(a)mutabit.com> wrote: > >> I have been just trying to install GT Documenter and is really >> frustrating (I have been unable to install it even for the first time!). >> >> This was the list of errors I got and steps I followed, in almost >> sequential order, just to get a (bittersweet!) taste of GT Documenter: >> >> - 1st: LGit_GIT_ERROR: No ssh-agent suitable credentials found. So I >> go to GitHub, follow the five pages of documentation to get my SSH >> credentials that start at [1], then, because I still get the same error, go >> to the Iceberg FAQ [2], try to surpass the erro,r via command line and >> doesn't work, so I go to the Iceberg settings and try the manual >> configuration, going to the next item >> >> [1] https://help.github.com/articles/generating-a-new-ssh-key- >> and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key >> <https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-…> >> [2] https://github.com/pharo-vcs/iceberg/blob/master/README.md >> >> - Now I get "Instance of LGitCredentialsSSH class did not understand >> #ifTrue:ifFalse:". I try to make sense of it in the debugger, but is >> something I cannot. Anyway, I rerun it and now I get: LGit_GIT_EEXISTS: >> '/home/offray/Programas/Pharo/6.1a/Dev24/pharo-local/iceberg/feenkcom/gtoolkit' >> exists and is not an empty directory. I delete that directory and try an >> installation... again >> - Now I get: "Instance of FileReference did not understand >> #notEmpty". I try to make sense of it in the debugger. My user is git, my >> public and private ssh keys are not empty. Despite of not making sense of >> all I understand that is trying to clone something at >> git@github.com:feenkcom/gtoolkit.git >> <git@github.com:feenkcom/gtoolkit.git>. I go to my image dir and then >> to `iceberg/feenkcom/gtoolkit/`. There is a git repository there, but is >> empty. >> - Now I wonder, maybe if I can just clone the directory there, but >> how I say Iceberg to load it? So I run now only the Metacello part. Same >> error and solution that the last time but now for gtoolkit-visualizer, >> Brick, gtoolkit-examples, Bloc and Sparta. >> - After getting my ssh keys, overcome config problems in shell and >> the Pharo settings, chasing these errors and solving them by cloning the >> repositories manually, I'm, a couple of hours later, ready to test GT >> Documenter, but with the last Iceberg's duplicated repository message about >> Sparta I give up. Is not nice to start your day accumulating frustration... >> that sets a bad mood for the rest of it, and you need to actively fight >> against. >> >> I have thought that Git is overcomplicated for most of the developers' >> tasks and communities. I don't know if the root of previous issues is in >> the "Iceberg enableMetacelloIntegration: true" line, but having to get your >> pair of keys working to just install software is overkill for the common >> user (and when LibGit errors are present, the documented solutions don't >> work seamlessly). Maybe a more sensitive solution would be just to use >> libgit, without any ssh auth to clone repositories and its prerequisites or >> even better, some download that goes to the files in the tip (or other) >> version without all this overhead. >> >> Anyway, as I said, I have been unable to test GT Documenter properly and >> getting feedback over GT Tools from the team usually requires a lot of >> effort in my case (insisting on getting answers or getting none). And that >> is just to test a promising tech that still doesn't offer saving features >> (just and awesome preview). I think that a more sensible approach for a >> good documentation toolkit for now is on Spec and creating custom syntax >> highlighters with SmaCC[3], that is well documented and works today. >> >> [3] https://medium.com/@juliendelplanque/hacking-a-simple- >> syntactic-highlighter-around-specs-textmodel-44ba2e2b1ab9 >> I understand that community is trying its best, but expressing how >> current offerings are not mature and constructive criticism can help on >> that. At the moment my feeling is that if you want to try the new shinny >> alpha stuff from GT Documenter, you will need to be prepared for a lot of >> frustration and silence. >> >> Cheers, >> >> Offray >> >> >> On 10/11/17 12:41, Tudor Girba wrote: >> >> Hi, >> >> As shown at ESUG, GT Documenter offers an advanced viewer (and editor) for Pillar working on top of Bloc. >> >> You can get it by loading: >> >> Iceberg enableMetacelloIntegration: true. >> Metacello new >> baseline: 'GToolkit'; >> repository: 'github://feenkcom/gtoolkit/src'; >> load. >> >> For example, you can then inspect: >> 'PATH_TO_ICEBERG/feenkcom/gtoolkit/doc/transcript/index.pillarâ asFileReference >> >> Cheers, >> Doru >> >> >> >> On Nov 10, 2017, at 12:58 PM, H. Hirzel <hannes.hirzel(a)gmail.com> <hannes.hirzel(a)gmail.com> wrote: >> >> A note: >> >> Tudor Girba wrote:<tudor(a)tudorgirba.com> <tudor(a)tudorgirba.com> Fri, Aug 25, 2017 at 1:31 PM >> Reply-To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> <pharo-users(a)lists.pharo.org> >> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> <pharo-users(a)lists.pharo.org> >> >> Hi, >> >> As mentioned in an announcement about 10 days ago, we are building a >> Pillar editor with inline viewing abilities in Bloc. Here is how it >> looked like. Please note the embedded picture. We continued working on >> it since then and we will probably announce the next version this >> weekend: >> >> >> Maybe there is now enough progress to do simple presentations in Bloc? >> >> >> On 11/10/17, H. Hirzel <hannes.hirzel(a)gmail.com> <hannes.hirzel(a)gmail.com> wrote: >> >> Hello >> >> In the thread 'including Pillar in Pharo image by default' it was >> suggested by Stephane Ducasse to include a subset of Pillar in the >> Pharo image[1] . >> >> I'd like to extend that proposal a little bit it in order to do very >> simple presentations. This should allow to describe at least part of >> the slides used in the MOOC course [3]. >> >> This will be _a possible_ solution to the question brought up in the >> thread 'Writing "powerpoint" like presentations in Pharo?'. >> >> Another use is to write instructions with executable content within >> the image ("Assistants"). >> >> So below is the a proposal for a Pillar syntax _subset_ for class >> comments and _simple_ presentations. >> The numbering scheme follows the 'Pillar syntax cheat sheet' [2] >> >> >> >> >> MINI PILLAR SYNTAX (a subset of Pillar) >> >> 1. Headers >> >> !Header 1 >> !!Header 2 >> !!!Header 3 >> >> >> 2. Lists >> >> - Unordered List >> # Ordered list >> >> >> >> 5. Emphasis >> >> ""bold"" >> >> >> 6. Code blocks >> >> [[[ >> Transcript show: 'Hello World'. >> \]]] >> >> >> 9. Annotation >> >> ${slide:title=About Pharo}$ >> >> >> >> >> Next week I plan to implement the rendering of this 'Mini Pillar' in >> Morphic using the Morphic API subset that works in Pharo and Squeak. >> >> A renderer using Bloc would also be nice. [4] >> >> Comments, suggestions, code snippets and other help is welcome. >> >> Regards >> Hannes >> >> >> >> >> -------------------------------------------------------------------------------------------------- >> [1] Pillar subset for class comments >> >> Stephane Ducasse<stepharo.self(a)gmail.com> <stepharo.self(a)gmail.com> Fri, Aug 11, 2017 at 7:09 PM >> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> <pharo-users(a)lists.pharo.org> >> >> Tx cyril >> >> For class comment I image that we want >> >> ! >> >> - >> - >> *url* >> and bold >> [[[ >> >> ]]] >> >> Did I miss something. >> >> Stef >> >> >> >> >> >> -------------------------------------------------------------------------------------------------- >> [2]http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet >> -------------------------------------------------------------------------------------------------- >> >> >> 1. Headers >> >> !Header 1 >> !!Header 2 >> !!!Header 3 >> !!!!Header 4 >> !!!!!Header 5 >> !!!!!!Header 6 >> >> 2. Lists >> >> - Unordered List >> # Ordered list >> >> 3. Table >> >> |! Left |! Right |! Centered >> |{Left |}Right| Centered >> >> >> 4. Description >> Note >> on a new line >> >> ;head >> :item >> >> >> 5. Emphasis >> >> ""bold"" >> ''italic'' >> --strikethrough-- >> __underscore__ >> ==inline code== >> @@subscript@@ >> ^^sub-script^^ >> >> 6. Code blocks >> >> [[[labÂel=ÂhelÂloSÂcriÂpt|ÂcapÂtioÂn=How to print Hello >> World|ÂlanÂguaÂge=ÂSmaÂlltalk >> Transcript show: 'Hello World'. >> \]]] >> >> >> 7. Raw >> >> >> {{{latex: >> this is how you inject raw \LaTeX in your output file >> }}} >> >> {{{marÂkdown: >> this is how you inject raw `markdown` in your output file >> }}} >> >> {{{html: >> this is how you inject raw ÂhtmÂl</Âb> in your output file >> }}} >> >> >> 8. Links >> >> Anchor @anchor (new line) >> Internal link *anchor* >> External link *Google>http://google.com* >> Image +Caption>file://image.png|width=50|label=label+ >> >> >> 9. Annotation >> Note >> on a new line >> >> Annotation @@note this is a note >> Todo item @@todo this is to do >> >> >> 10. Comments >> >> % each line starting with % is commented >> >> >> 11. References >> >> This document is copied fromhttp://www.cheatography.com/benjaminvanryseghem/cheat-sheets/pillar/ >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> ---------------------------------------------------------------------- >> [3] Example pillar code for slides >> ---------------------------------------------------------------------- >> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T… >> >> { >> "title":"To the Roots of Objects", >> "subtitle":"Learning from beauty", >> "author":"Stephane Ducasse", >> "complement":"http://stephane.ducasse.free.fr/ \\\\ >> stephane.ducasse(a)inria.fr" <http://stephane.ducasse.free.fr/%5C%5C%5C%5Cstephane.ducasse@inria.fr> >> } >> >> >> ${toc:depthLevel=2|level=0|highlight=0}$ >> >> %Les sections ne sont pas des titres de slide mais dÃ©finnissent la >> structure du doucment. Il est possible de rajouter >> "renderStructureAsSlide":false dans pillar.conf pour ne pas crÃ©er de >> slide Ã partir d'un titre. >> >> >> ${slide:title=License}$ >> >> +>file://figures/CreativeCommons.png|width=50|label=figCreativeCommons+ >> >> >> ! Introduction >> >> % >> ${toc:depthLevel=1|level=0|highlight=1}$ >> >> >> ${slide:title=Really?!|label=really}$ >> >> ${columns}$ >> >> ${column:width=50}$ >> >> %the width parameter take an Int between 1 and 100 >> %For now we have to pass a line before and after an annotation, I'll >> correct that soon in Pillar. >> - No primitive types >> - No hardcoded constructs for conditional >> - Only messages >> - Only objects >> >> ${column:width=50}$ >> >> - and this works? >> - I mean really? >> - Not even slow? >> - Can't be real! >> >> ${endColumns}$ >> >> ${slide:title=Motto}$ >> >> - Let's open our eyes, look, understand, and deeply understand the >> underlying design aspects of object-oriented programming. >> >> >> *@really* >> >> *TEST !>@really* >> >> ${slide:title=Booleans}$ >> >> [[[language=smalltalk >> 3 > 0 >> ifTrue: ['positive'] >> ifFalse: ['negative'] >> -> 'positive' >> ]]] >> >> ${slide:title=Yes ifTrue\:ifFalse\: is a message!}$ >> >> [[[language=smalltalk >> Weather isRaining >> ifTrue: [self takeMyUmbrella] >> ifFalse: [self takeMySunglasses] >> ]]] >> >> - Conceptually ==ifTrue:ifFalse:== is a message sent to an object: a >> boolean! >> - ==ifTrue:ifFalse:== is in fact radically optimized by the compiler >> but you can implement another one such ==siAlors:sinon:== and check. >> >> ${slide:title=Booleans}$ >> >> In Pharo booleans have nothing special >> - & | not >> - or: and: (lazy) >> - xor: >> - ifTrue:ifFalse: >> - ifFalse:ifTrue: >> - ... >> >> ${slide:title=Lazy Logical Operators}$ >> >> *LINK>@frm:really* >> >> [[[language=smalltalk >> false and: [1 error: 'crazy'] >> -> false and not an error >> ]]] >> >> ! Exercices >> ${toc:depthLevel=1|level=0|highlight=1}$ >> >> !! Exercise 1: Implement not >> >> ${slide:title=Exercise 1\: Implement not}$ >> >> - Propose an implementation of not in a world where you do not have >> Booleans. >> - You only have objects and messages. >> [[[language=smalltalk >> false not >> -> true >> >> true not >> -> false >> ]]] >> >> !!Exercise 2: Implement | (Or) ifTrue: ifFalse: >> >> ${toc:depthLevel=2|level=0|highlight=1}$ >> >> ${slide:title=Exercise 2\: Implement \| (Or)}$ >> >> - Propose an implementation of or in a world where you do not have >> Booleans. >> - You only have objects and messages. >> >> [[[language=smalltalk >> true | true -> true >> true | false -> true >> true | anything -> true >> >> false | true -> true >> false | false -> false >> false | anything -> anything >> ]]] >> >> ${slide:title=Exercise2\: Variation - Implement ifTrue\:ifFalse\:}$ >> >> - Propose an implementation of not in a world where you do not have >> Booleans. >> - You only have objects, messages and closures. >> >> [[[language=smalltalk >> false ifTrue: [ 3 ] ifFalse: [ 5 ] >> -> 5 >> true ifTrue: [ 3 ] ifFalse: [ 5 ] >> -> 3 >> ]]] >> >> ! Boolean Implementation >> >> ${toc:depthLevel=1|level=0|highlight=1}$ >> >> ${slide:title=Booleans Implementation Hint One}$ >> >> - The solution does not use conditionals >> - else we would obtain a recursive definition of ==ifTrue:ifFalse:== >> >> ${slide:title=Boolean Implementation Hint Two}$ >> >> - The solution uses three classes: ==Boolean==, ==True== and ==False== >> - ==false== and ==true== are unique instances described by their own >> classes >> - ==false== is an instance of the class ==False== >> - ==true== is an instance of the class ==True== >> >> +Boolean Hierarchy>file://figures/BooleanHiearchyAndInstances.png|width=50+ >> >> ${slide:title=How do we express choice in OOP?}$ >> >> - We send messages to objects >> >> [[[language=smalltalk >> aButton color >> -> Color red >> >> aPane color >> -> Color blue >> >> aWindow color >> -> Color grey >> ]]] >> >> - Let's the receiver decide >> >> - Do not ask, tell >> >> ${slide:title=Boolean not implementation}$ >> >> - Class ==Boolean== is an abstract class that implements behavior >> common to true and false. Its subclasses are ==True== and ==False==. >> Subclasses must implement methods for logical operations ==&==, >> ==not==, and controls ==and:==, ==or:==, ==ifTrue:==, ==ifFalse:==, >> ==ifTrue:ifFalse:==, ==ifFalse:ifTrue:== >> >> [[[language=smalltalk >> Boolean>>not >> "Negation. Answer true if the receiver is false, answer false if the >> receiver is true." >> self subclassResponsibility >> ]]] >> >> ${slide:title=Not implementation in two methods}$ >> >> [[[language=smalltalk >> False>>not >> "Negation -- answer true since the receiver is false." >> ^ true >> ]]] >> >> [[[language=smalltalk >> True>>not >> "Negation--answer false since the receiver is true." >> ^ false >> ]]] >> >> ${slide:title=Not implementation in two methods}$ >> >> +Not >> implementation.>file://figures/BooleanHiearchyAndInstancesWithNotMethods.png|width=80+ >> >> ${slide:title=\| (Or)}$ >> [[[language=smalltalk >> >> true | true -> true >> true | false -> true >> true | anything -> true >> >> false | true -> true >> false | false -> false >> false | anything -> anything >> >> ]]] >> >> ${slide:title=Boolean>> \| aBoolean}$ >> >> [[[language=smalltalk >> Boolean>> | aBoolean >> "Evaluating disjunction (OR). Evaluate the argument. Answer true if >> either the receiver or the argument is >> true." >> self subclassResponsibility >> ]]] >> >> ${slide:title=False>> \| aBoolean}$ >> >> [[[language=smalltalk >> false | true -> true >> false | false -> false >> false | anything -> anything >> ]]] >> >> [[[language=smalltalk >> False >> | aBoolean >> "Evaluating disjunction (OR) -- answer with the argument, aBoolean." >> ^ aBoolean >> ]]] >> >> ${slide:title=True>> \| aBoolean}$ >> >> [[[language=smalltalk >> true | true -> true >> true | false -> true >> true | anything -> true >> ]]] >> >> [[[language=smalltalk >> True>> | aBoolean >> "Evaluating disjunction (OR) -- answer true since the receiver is true." >> ^ self >> ]]] >> >> ${slide:title=Or implementation in two methods}$ >> >> +>file://figures/BooleanHiearchyAndInstancesWithOrMethods.png|width=80+ >> >> ${slide:title=Implementing ifTrue\:ifFalse\:}$ >> >> - Do you see the pattern? >> - Remember that a closure freezes execution and that value launches >> the execution of a frozen code. >> >> [[[language=smalltalk >> True>>ifTrue: aTrueBlock ifFalse: aFalseBlock >> ^ aTrueBlock value >> ]]] >> >> [[[language=smalltalk >> False>>ifTrue: aTrueBlock ifFalse: aFalseBlock >> ^ aFalseBlock value >> ]]] >> >> ${slide:title=Implementation Note}$ >> >> - Note that the Virtual Machine shortcuts calls to boolean such as >> condition for speed reason. >> - But you can implement your own conditional method and debug to see >> that sending a message is dispatching to the right object. >> >> ! So what ? >> >> ${toc:depthLevel=1|level=0|highlight=1}$ >> >> ${slide:title=Ok so what?}$ >> >> - You will probably not implement another Boolean classes >> - So is it really that totally useless? >> >> >> ${slide:title=Message sends act as case statements}$ >> >> - The execution engine will select the right method in the class of the >> receiver >> - The case statements is dynamic in the sense that it depends on the >> classes loaded and the objects to which the message is sent. >> - Each time you send a message, the system will select the method >> corresponding to the receiver. >> >> >> ${slide:title=A Class Hierarchy is a Skeleton for Dynamic Dispatch}$ >> >> - If we would have said that the ==Boolean== would be composed of only >> one class, we could not have use dynamic binding. >> - A class hierarchy is the exoskeleton for dynamic binding >> >> - Compare the solution with one class vs. a hierarchy. >> >> +One single class vs. a nice >> hierarchy.>file://figures/Design-FatVsDispatch.png|width=70+ >> >> - The hierarchy provides a way to specialize behavior. >> - It is also more declarative in the sense that you only focus on one >> class. >> - It is more modular in the sense that you can package different >> classes in different packages. >> >> ${slide:title=Avoid Conditionals}$ >> >> - Use objects and messages, when you can >> - The execution engine acts as a conditional switch: Use it! >> - Check the AntiIfCampaign. >> >> ${slide:title=Follow-up: Implement ternary logic}$ >> >> - Boolean: ==true==, ==false==, ==unknown== >> +Ternaru Logic decision table >> >> file://figures/ArrayBoolean.png|width=30|label=fig:ternLogic+ >> >> - Implementing in your own classes. >> >> ! Summary >> >> ${toc:depthLevel=1|level=0|highlight=1}$ >> >> ${slide:title=Summary}$ >> - Tell, do not ask >> - Let the receiver decide >> - Message sends as potential dynamic conditional >> - Class hiearchy builds a skeleton for dynamic dispatch >> - Avoid conditional >> >> >> >> >> ----------------------------------------- >> [4] Bloc >> Load Bloc with executing in a playground (Pharo 6.1) >> >> Metacello new >> baseline: 'Bloc'; >> repository: 'github://pharo-graphics/Bloc:pharo6.1/src'; >> load: #core >> >> >> A tutorial to use bloc is available onhttp://files.pharo.org/books/ >> Bloc Memory Game (alpha) is a first tutorial on Bloc the new graphics >> core for Pharo. Booklet written by A. Chis, S. Ducasse, A. Syrel. >> http://files.pharo.org/books-pdfs/booklet-Bloc/2017-11-09-memorygame.pdf >> >> To load the memory game >> >> Metacello new >> baseline: 'BlocTutorials'; >> repository: 'github://pharo-graphics/Tutorials/src'; >> load >> >> >> A similar booklet could be done for the title >> 'Doing a presentation / slide show / assitant with Bloc' (or similar, >> adapt .....) >> >> >> --www.tudorgirba.comwww.feenk.com >> >> "Obvious things are difficult to teach." >> >> >> >> >> >> >> >> >> -- > Cheers, > Alex > > >

Nov. 14, 2017

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

by Tudor Girba

Hi, We changed the baseline to not require Moz2D on Linux. Could you please try again? I also updated the README. Cheers, Doru > On Nov 14, 2017, at 6:25 PM, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Alex, > I understand that frustration on installation could be motivated by other issues instead of GT Documenter, but if the team ask to use "Iceberg enableMetacelloIntegration: true." in the project readme, where it also says that is supported for Pharo 6.1 and 7.0, is natural to think that something is wrong with documentation and/or in the project's expectations about its intended users and their will to invest the effort, time and motivation for "living in the edge". I understand that if we want stuff to be improved it should be tested, but also that not all the people that is willing to test stuff for Pharo 6.1 needs to live in such edge. Or the project is sending a message that is not giving the bests firsts impressions, or is going to users which are not intended . I would go for a smooth install first and then for collaboration with git. I'll make a pull request with the proposal for a better documentation, but my understanding about how you can go from the first (user of GT Documenter) to the second (developer using Git integration) is not clear. > > GT Tools has been pretty empowering. I have told that several times and I don't think that I have wrote a single line of code in their repos. But is getting more difficult just to test and use them and I think that is related with the idea that my user *needs* to be also my co-developer, starting with their ssh git key pair. If we don't make easier to contribute by just making easier to install, there will be no evolution either. > > Cheers, > > Offray > > On 14/11/17 11:45, Aliaksei Syrel wrote: >> Hi Offray, >> >> I understand your frustration, but with all respect, the fact that you have problems with Iceberg does not mean that GT Documenter or any other GT tool is responsible for described problems. >> >> Most complains about bloc, brick, whatever is because of unrelated stuff. It is a little bit disappointing. Especially for me, as one of the maintainers. But it is ok, I got used to it :) >> >> I donât remember when last time I used stable Pharo (not because it does not exist), simply live on the edge since Pharo4. If no one will use Git and report problems Iceberg will never progress. If no one will use Bloc it will never get âthereâ. Unfortunately, living on the edge is dangerous, requires effort, motivation and time. >> >> The script that Doru provided works flawlessly on OSX, we load it almost everyday. !! Bloc is tested on CI and builds are green on Windows, Linux and OSX !!. If computer (CI) manages to install it, I am pretty sure human can do it too. Looks like there is something missing in your configuration, something tiny :) Error handling in Iceberg can be definitely improved, but it is a different story. >> >> P.S. Documenter can be installed without enabled Iceberg integration. This is how CI does it. You will just not be able to contribute. >> >> Cheers, >> Alex >> >> On Tue, 14 Nov 2017 at 16:37, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: >> I have been just trying to install GT Documenter and is really frustrating (I have been unable to install it even for the first time!). >> >> This was the list of errors I got and steps I followed, in almost sequential order, just to get a (bittersweet!) taste of GT Documenter: >> >> â¢ 1st: LGit_GIT_ERROR: No ssh-agent suitable credentials found. So I go to GitHub, follow the five pages of documentation to get my SSH credentials that start at [1], then, because I still get the same error, go to the Iceberg FAQ [2], try to surpass the erro,r via command line and doesn't work, so I go to the Iceberg settings and try the manual configuration, going to the next item >> >> [1] https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-… >> [2] https://github.com/pharo-vcs/iceberg/blob/master/README.md >> >> â¢ Now I get "Instance of LGitCredentialsSSH class did not understand #ifTrue:ifFalse:". I try to make sense of it in the debugger, but is something I cannot. Anyway, I rerun it and now I get: LGit_GIT_EEXISTS: '/home/offray/Programas/Pharo/6.1a/Dev24/pharo-local/iceberg/feenkcom/gtoolkit' exists and is not an empty directory. I delete that directory and try an installation... again >> â¢ Now I get: "Instance of FileReference did not understand #notEmpty". I try to make sense of it in the debugger. My user is git, my public and private ssh keys are not empty. Despite of not making sense of all I understand that is trying to clone something at git@github.com:feenkcom/gtoolkit.git. I go to my image dir and then to `iceberg/feenkcom/gtoolkit/`. There is a git repository there, but is empty. >> â¢ Now I wonder, maybe if I can just clone the directory there, but how I say Iceberg to load it? So I run now only the Metacello part. Same error and solution that the last time but now for gtoolkit-visualizer, Brick, gtoolkit-examples, Bloc and Sparta. >> â¢ After getting my ssh keys, overcome config problems in shell and the Pharo settings, chasing these errors and solving them by cloning the repositories manually, I'm, a couple of hours later, ready to test GT Documenter, but with the last Iceberg's duplicated repository message about Sparta I give up. Is not nice to start your day accumulating frustration... that sets a bad mood for the rest of it, and you need to actively fight against. >> I have thought that Git is overcomplicated for most of the developers' tasks and communities. I don't know if the root of previous issues is in the "Iceberg enableMetacelloIntegration: true" line, but having to get your pair of keys working to just install software is overkill for the common user (and when LibGit errors are present, the documented solutions don't work seamlessly). Maybe a more sensitive solution would be just to use libgit, without any ssh auth to clone repositories and its prerequisites or even better, some download that goes to the files in the tip (or other) version without all this overhead. >> >> Anyway, as I said, I have been unable to test GT Documenter properly and getting feedback over GT Tools from the team usually requires a lot of effort in my case (insisting on getting answers or getting none). And that is just to test a promising tech that still doesn't offer saving features (just and awesome preview). I think that a more sensible approach for a good documentation toolkit for now is on Spec and creating custom syntax highlighters with SmaCC[3], that is well documented and works today. >> [3] https://medium.com/@juliendelplanque/hacking-a-simple-syntactic-highlighter… >> I understand that community is trying its best, but expressing how current offerings are not mature and constructive criticism can help on that. At the moment my feeling is that if you want to try the new shinny alpha stuff from GT Documenter, you will need to be prepared for a lot of frustration and silence. >> >> Cheers, >> >> Offray >> >> >> On 10/11/17 12:41, Tudor Girba wrote: >>> Hi, >>> >>> As shown at ESUG, GT Documenter offers an advanced viewer (and editor) for Pillar working on top of Bloc. >>> >>> You can get it by loading: >>> >>> Iceberg enableMetacelloIntegration: true. >>> Metacello new >>> baseline: 'GToolkit'; >>> repository: 'github://feenkcom/gtoolkit/src'; >>> load. >>> >>> For example, you can then inspect: >>> 'PATH_TO_ICEBERG/feenkcom/gtoolkit/doc/transcript/index.pillarâ asFileReference >>> >>> Cheers, >>> Doru >>> >>> >>> >>>> On Nov 10, 2017, at 12:58 PM, H. Hirzel <hannes.hirzel(a)gmail.com> >>>> wrote: >>>> >>>> A note: >>>> >>>> Tudor Girba wrote: >>>> >>>> <tudor(a)tudorgirba.com> >>>> Fri, Aug 25, 2017 at 1:31 PM >>>> Reply-To: Any question about pharo is welcome >>>> <pharo-users(a)lists.pharo.org> >>>> >>>> To: Any question about pharo is welcome >>>> <pharo-users(a)lists.pharo.org> >>>> >>>> >>>> Hi, >>>> >>>> As mentioned in an announcement about 10 days ago, we are building a >>>> Pillar editor with inline viewing abilities in Bloc. Here is how it >>>> looked like. Please note the embedded picture. We continued working on >>>> it since then and we will probably announce the next version this >>>> weekend: >>>> >>>> >>>> Maybe there is now enough progress to do simple presentations in Bloc? >>>> >>>> >>>> On 11/10/17, H. Hirzel >>>> <hannes.hirzel(a)gmail.com> >>>> wrote: >>>> >>>>> Hello >>>>> >>>>> In the thread 'including Pillar in Pharo image by default' it was >>>>> suggested by Stephane Ducasse to include a subset of Pillar in the >>>>> Pharo image[1] . >>>>> >>>>> I'd like to extend that proposal a little bit it in order to do very >>>>> simple presentations. This should allow to describe at least part of >>>>> the slides used in the MOOC course [3]. >>>>> >>>>> This will be _a possible_ solution to the question brought up in the >>>>> thread 'Writing "powerpoint" like presentations in Pharo?'. >>>>> >>>>> Another use is to write instructions with executable content within >>>>> the image ("Assistants"). >>>>> >>>>> So below is the a proposal for a Pillar syntax _subset_ for class >>>>> comments and _simple_ presentations. >>>>> The numbering scheme follows the 'Pillar syntax cheat sheet' [2] >>>>> >>>>> >>>>> >>>>> >>>>> MINI PILLAR SYNTAX (a subset of Pillar) >>>>> >>>>> 1. Headers >>>>> >>>>> !Header 1 >>>>> !!Header 2 >>>>> !!!Header 3 >>>>> >>>>> >>>>> 2. Lists >>>>> >>>>> - Unordered List >>>>> # Ordered list >>>>> >>>>> >>>>> >>>>> 5. Emphasis >>>>> >>>>> ""bold"" >>>>> >>>>> >>>>> 6. Code blocks >>>>> >>>>> [[[ >>>>> Transcript show: 'Hello World'. >>>>> \]]] >>>>> >>>>> >>>>> 9. Annotation >>>>> >>>>> ${slide:title=About Pharo}$ >>>>> >>>>> >>>>> >>>>> >>>>> Next week I plan to implement the rendering of this 'Mini Pillar' in >>>>> Morphic using the Morphic API subset that works in Pharo and Squeak. >>>>> >>>>> A renderer using Bloc would also be nice. [4] >>>>> >>>>> Comments, suggestions, code snippets and other help is welcome. >>>>> >>>>> Regards >>>>> Hannes >>>>> >>>>> >>>>> >>>>> >>>>> -------------------------------------------------------------------------------------------------- >>>>> [1] Pillar subset for class comments >>>>> >>>>> Stephane Ducasse >>>>> >>>>> <stepharo.self(a)gmail.com> >>>>> Fri, Aug 11, 2017 at 7:09 PM >>>>> To: Any question about pharo is welcome >>>>> <pharo-users(a)lists.pharo.org> >>>>> >>>>> >>>>> Tx cyril >>>>> >>>>> For class comment I image that we want >>>>> >>>>> ! >>>>> >>>>> - >>>>> - >>>>> *url* >>>>> and bold >>>>> [[[ >>>>> >>>>> ]]] >>>>> >>>>> Did I miss something. >>>>> >>>>> Stef >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -------------------------------------------------------------------------------------------------- >>>>> [2] >>>>> >>>>> http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet >>>>> >>>>> -------------------------------------------------------------------------------------------------- >>>>> >>>>> >>>>> 1. Headers >>>>> >>>>> !Header 1 >>>>> !!Header 2 >>>>> !!!Header 3 >>>>> !!!!Header 4 >>>>> !!!!!Header 5 >>>>> !!!!!!Header 6 >>>>> >>>>> 2. Lists >>>>> >>>>> - Unordered List >>>>> # Ordered list >>>>> >>>>> 3. Table >>>>> >>>>> |! Left |! Right |! Centered >>>>> |{Left |}Right| Centered >>>>> >>>>> >>>>> 4. Description >>>>> Note >>>>> on a new line >>>>> >>>>> ;head >>>>> :item >>>>> >>>>> >>>>> 5. Emphasis >>>>> >>>>> ""bold"" >>>>> ''italic'' >>>>> --strikethrough-- >>>>> __underscore__ >>>>> ==inline code== >>>>> @@subscript@@ >>>>> ^^sub-script^^ >>>>> >>>>> 6. Code blocks >>>>> >>>>> [[[labÂel=ÂhelÂloSÂcriÂpt|ÂcapÂtioÂn=How to print Hello >>>>> World|ÂlanÂguaÂge=ÂSmaÂlltalk >>>>> Transcript show: 'Hello World'. >>>>> \]]] >>>>> >>>>> >>>>> 7. Raw >>>>> >>>>> >>>>> {{{latex: >>>>> this is how you inject raw \LaTeX in your output file >>>>> }}} >>>>> >>>>> {{{marÂkdown: >>>>> this is how you inject raw `markdown` in your output file >>>>> }}} >>>>> >>>>> {{{html: >>>>> this is how you inject raw ÂhtmÂl</Âb> in your output file >>>>> }}} >>>>> >>>>> >>>>> 8. Links >>>>> >>>>> Anchor @anchor (new line) >>>>> Internal link *anchor* >>>>> External link *Google> >>>>> http://google.com >>>>> * >>>>> Image +Caption> >>>>> file://image.png|width=50|label=label+ >>>>> >>>>> >>>>> >>>>> 9. Annotation >>>>> Note >>>>> on a new line >>>>> >>>>> Annotation @@note this is a note >>>>> Todo item @@todo this is to do >>>>> >>>>> >>>>> 10. Comments >>>>> >>>>> % each line starting with % is commented >>>>> >>>>> >>>>> 11. References >>>>> >>>>> This document is copied from >>>>> >>>>> http://www.cheatography.com/benjaminvanryseghem/cheat-sheets/pillar/ >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> ---------------------------------------------------------------------- >>>>> [3] Example pillar code for slides >>>>> ---------------------------------------------------------------------- >>>>> >>>>> >>>>> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T… >>>>> >>>>> >>>>> { >>>>> "title":"To the Roots of Objects", >>>>> "subtitle":"Learning from beauty", >>>>> "author":"Stephane Ducasse", >>>>> "complement": >>>>> "http://stephane.ducasse.free.fr/ \\\\ >>>>> stephane.ducasse(a)inria.fr" >>>>> >>>>> } >>>>> >>>>> >>>>> ${toc:depthLevel=2|level=0|highlight=0}$ >>>>> >>>>> %Les sections ne sont pas des titres de slide mais dÃ©finnissent la >>>>> structure du doucment. Il est possible de rajouter >>>>> "renderStructureAsSlide":false dans pillar.conf pour ne pas crÃ©er de >>>>> slide Ã partir d'un titre. >>>>> >>>>> >>>>> ${slide:title=License}$ >>>>> >>>>> +> >>>>> file://figures/CreativeCommons.png|width=50|label=figCreativeCommons+ >>>>> >>>>> >>>>> >>>>> ! Introduction >>>>> >>>>> % >>>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>>> >>>>> >>>>> ${slide:title=Really?!|label=really}$ >>>>> >>>>> ${columns}$ >>>>> >>>>> ${column:width=50}$ >>>>> >>>>> %the width parameter take an Int between 1 and 100 >>>>> %For now we have to pass a line before and after an annotation, I'll >>>>> correct that soon in Pillar. >>>>> - No primitive types >>>>> - No hardcoded constructs for conditional >>>>> - Only messages >>>>> - Only objects >>>>> >>>>> ${column:width=50}$ >>>>> >>>>> - and this works? >>>>> - I mean really? >>>>> - Not even slow? >>>>> - Can't be real! >>>>> >>>>> ${endColumns}$ >>>>> >>>>> ${slide:title=Motto}$ >>>>> >>>>> - Let's open our eyes, look, understand, and deeply understand the >>>>> underlying design aspects of object-oriented programming. >>>>> >>>>> >>>>> *@really* >>>>> >>>>> *TEST !>@really* >>>>> >>>>> ${slide:title=Booleans}$ >>>>> >>>>> [[[language=smalltalk >>>>> 3 > 0 >>>>> ifTrue: ['positive'] >>>>> ifFalse: ['negative'] >>>>> -> 'positive' >>>>> ]]] >>>>> >>>>> ${slide:title=Yes ifTrue\:ifFalse\: is a message!}$ >>>>> >>>>> [[[language=smalltalk >>>>> Weather isRaining >>>>> ifTrue: [self takeMyUmbrella] >>>>> ifFalse: [self takeMySunglasses] >>>>> ]]] >>>>> >>>>> - Conceptually ==ifTrue:ifFalse:== is a message sent to an object: a >>>>> boolean! >>>>> - ==ifTrue:ifFalse:== is in fact radically optimized by the compiler >>>>> but you can implement another one such ==siAlors:sinon:== and check. >>>>> >>>>> ${slide:title=Booleans}$ >>>>> >>>>> In Pharo booleans have nothing special >>>>> - & | not >>>>> - or: and: (lazy) >>>>> - xor: >>>>> - ifTrue:ifFalse: >>>>> - ifFalse:ifTrue: >>>>> - ... >>>>> >>>>> ${slide:title=Lazy Logical Operators}$ >>>>> >>>>> *LINK>@frm:really* >>>>> >>>>> [[[language=smalltalk >>>>> false and: [1 error: 'crazy'] >>>>> -> false and not an error >>>>> ]]] >>>>> >>>>> ! Exercices >>>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>>> >>>>> !! Exercise 1: Implement not >>>>> >>>>> ${slide:title=Exercise 1\: Implement not}$ >>>>> >>>>> - Propose an implementation of not in a world where you do not have >>>>> Booleans. >>>>> - You only have objects and messages. >>>>> [[[language=smalltalk >>>>> false not >>>>> -> true >>>>> >>>>> true not >>>>> -> false >>>>> ]]] >>>>> >>>>> !!Exercise 2: Implement | (Or) ifTrue: ifFalse: >>>>> >>>>> ${toc:depthLevel=2|level=0|highlight=1}$ >>>>> >>>>> ${slide:title=Exercise 2\: Implement \| (Or)}$ >>>>> >>>>> - Propose an implementation of or in a world where you do not have >>>>> Booleans. >>>>> - You only have objects and messages. >>>>> >>>>> [[[language=smalltalk >>>>> true | true -> true >>>>> true | false -> true >>>>> true | anything -> true >>>>> >>>>> false | true -> true >>>>> false | false -> false >>>>> false | anything -> anything >>>>> ]]] >>>>> >>>>> ${slide:title=Exercise2\: Variation - Implement ifTrue\:ifFalse\:}$ >>>>> >>>>> - Propose an implementation of not in a world where you do not have >>>>> Booleans. >>>>> - You only have objects, messages and closures. >>>>> >>>>> [[[language=smalltalk >>>>> false ifTrue: [ 3 ] ifFalse: [ 5 ] >>>>> -> 5 >>>>> true ifTrue: [ 3 ] ifFalse: [ 5 ] >>>>> -> 3 >>>>> ]]] >>>>> >>>>> ! Boolean Implementation >>>>> >>>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>>> >>>>> ${slide:title=Booleans Implementation Hint One}$ >>>>> >>>>> - The solution does not use conditionals >>>>> - else we would obtain a recursive definition of ==ifTrue:ifFalse:== >>>>> >>>>> ${slide:title=Boolean Implementation Hint Two}$ >>>>> >>>>> - The solution uses three classes: ==Boolean==, ==True== and ==False== >>>>> - ==false== and ==true== are unique instances described by their own >>>>> classes >>>>> - ==false== is an instance of the class ==False== >>>>> - ==true== is an instance of the class ==True== >>>>> >>>>> +Boolean Hierarchy> >>>>> file://figures/BooleanHiearchyAndInstances.png|width=50+ >>>>> >>>>> >>>>> ${slide:title=How do we express choice in OOP?}$ >>>>> >>>>> - We send messages to objects >>>>> >>>>> [[[language=smalltalk >>>>> aButton color >>>>> -> Color red >>>>> >>>>> aPane color >>>>> -> Color blue >>>>> >>>>> aWindow color >>>>> -> Color grey >>>>> ]]] >>>>> >>>>> - Let's the receiver decide >>>>> >>>>> - Do not ask, tell >>>>> >>>>> ${slide:title=Boolean not implementation}$ >>>>> >>>>> - Class ==Boolean== is an abstract class that implements behavior >>>>> common to true and false. Its subclasses are ==True== and ==False==. >>>>> Subclasses must implement methods for logical operations ==&==, >>>>> ==not==, and controls ==and:==, ==or:==, ==ifTrue:==, ==ifFalse:==, >>>>> ==ifTrue:ifFalse:==, ==ifFalse:ifTrue:== >>>>> >>>>> [[[language=smalltalk >>>>> Boolean>>not >>>>> "Negation. Answer true if the receiver is false, answer false if the >>>>> receiver is true." >>>>> self subclassResponsibility >>>>> ]]] >>>>> >>>>> ${slide:title=Not implementation in two methods}$ >>>>> >>>>> [[[language=smalltalk >>>>> False>>not >>>>> "Negation -- answer true since the receiver is false." >>>>> ^ true >>>>> ]]] >>>>> >>>>> [[[language=smalltalk >>>>> True>>not >>>>> "Negation--answer false since the receiver is true." >>>>> ^ false >>>>> ]]] >>>>> >>>>> ${slide:title=Not implementation in two methods}$ >>>>> >>>>> +Not >>>>> implementation.> >>>>> file://figures/BooleanHiearchyAndInstancesWithNotMethods.png|width=80+ >>>>> >>>>> >>>>> ${slide:title=\| (Or)}$ >>>>> [[[language=smalltalk >>>>> >>>>> true | true -> true >>>>> true | false -> true >>>>> true | anything -> true >>>>> >>>>> false | true -> true >>>>> false | false -> false >>>>> false | anything -> anything >>>>> >>>>> ]]] >>>>> >>>>> ${slide:title=Boolean>> \| aBoolean}$ >>>>> >>>>> [[[language=smalltalk >>>>> Boolean>> | aBoolean >>>>> "Evaluating disjunction (OR). Evaluate the argument. Answer true if >>>>> either the receiver or the argument is >>>>> true." >>>>> self subclassResponsibility >>>>> ]]] >>>>> >>>>> ${slide:title=False>> \| aBoolean}$ >>>>> >>>>> [[[language=smalltalk >>>>> false | true -> true >>>>> false | false -> false >>>>> false | anything -> anything >>>>> ]]] >>>>> >>>>> [[[language=smalltalk >>>>> False >> | aBoolean >>>>> "Evaluating disjunction (OR) -- answer with the argument, aBoolean." >>>>> ^ aBoolean >>>>> ]]] >>>>> >>>>> ${slide:title=True>> \| aBoolean}$ >>>>> >>>>> [[[language=smalltalk >>>>> true | true -> true >>>>> true | false -> true >>>>> true | anything -> true >>>>> ]]] >>>>> >>>>> [[[language=smalltalk >>>>> True>> | aBoolean >>>>> "Evaluating disjunction (OR) -- answer true since the receiver is true." >>>>> ^ self >>>>> ]]] >>>>> >>>>> ${slide:title=Or implementation in two methods}$ >>>>> >>>>> +> >>>>> file://figures/BooleanHiearchyAndInstancesWithOrMethods.png|width=80+ >>>>> >>>>> >>>>> ${slide:title=Implementing ifTrue\:ifFalse\:}$ >>>>> >>>>> - Do you see the pattern? >>>>> - Remember that a closure freezes execution and that value launches >>>>> the execution of a frozen code. >>>>> >>>>> [[[language=smalltalk >>>>> True>>ifTrue: aTrueBlock ifFalse: aFalseBlock >>>>> ^ aTrueBlock value >>>>> ]]] >>>>> >>>>> [[[language=smalltalk >>>>> False>>ifTrue: aTrueBlock ifFalse: aFalseBlock >>>>> ^ aFalseBlock value >>>>> ]]] >>>>> >>>>> ${slide:title=Implementation Note}$ >>>>> >>>>> - Note that the Virtual Machine shortcuts calls to boolean such as >>>>> condition for speed reason. >>>>> - But you can implement your own conditional method and debug to see >>>>> that sending a message is dispatching to the right object. >>>>> >>>>> ! So what ? >>>>> >>>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>>> >>>>> ${slide:title=Ok so what?}$ >>>>> >>>>> - You will probably not implement another Boolean classes >>>>> - So is it really that totally useless? >>>>> >>>>> >>>>> ${slide:title=Message sends act as case statements}$ >>>>> >>>>> - The execution engine will select the right method in the class of the >>>>> receiver >>>>> - The case statements is dynamic in the sense that it depends on the >>>>> classes loaded and the objects to which the message is sent. >>>>> - Each time you send a message, the system will select the method >>>>> corresponding to the receiver. >>>>> >>>>> >>>>> ${slide:title=A Class Hierarchy is a Skeleton for Dynamic Dispatch}$ >>>>> >>>>> - If we would have said that the ==Boolean== would be composed of only >>>>> one class, we could not have use dynamic binding. >>>>> - A class hierarchy is the exoskeleton for dynamic binding >>>>> >>>>> - Compare the solution with one class vs. a hierarchy. >>>>> >>>>> +One single class vs. a nice >>>>> hierarchy.> >>>>> file://figures/Design-FatVsDispatch.png|width=70+ >>>>> >>>>> >>>>> - The hierarchy provides a way to specialize behavior. >>>>> - It is also more declarative in the sense that you only focus on one >>>>> class. >>>>> - It is more modular in the sense that you can package different >>>>> classes in different packages. >>>>> >>>>> ${slide:title=Avoid Conditionals}$ >>>>> >>>>> - Use objects and messages, when you can >>>>> - The execution engine acts as a conditional switch: Use it! >>>>> - Check the AntiIfCampaign. >>>>> >>>>> ${slide:title=Follow-up: Implement ternary logic}$ >>>>> >>>>> - Boolean: ==true==, ==false==, ==unknown== >>>>> +Ternaru Logic decision table >>>>> >>>>>> file://figures/ArrayBoolean.png|width=30|label=fig:ternLogic+ >>>>> - Implementing in your own classes. >>>>> >>>>> ! Summary >>>>> >>>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>>> >>>>> ${slide:title=Summary}$ >>>>> - Tell, do not ask >>>>> - Let the receiver decide >>>>> - Message sends as potential dynamic conditional >>>>> - Class hiearchy builds a skeleton for dynamic dispatch >>>>> - Avoid conditional >>>>> >>>>> >>>>> >>>>> >>>>> ----------------------------------------- >>>>> [4] Bloc >>>>> Load Bloc with executing in a playground (Pharo 6.1) >>>>> >>>>> Metacello new >>>>> baseline: 'Bloc'; >>>>> repository: 'github://pharo-graphics/Bloc:pharo6.1/src'; >>>>> load: #core >>>>> >>>>> >>>>> A tutorial to use bloc is available on >>>>> >>>>> http://files.pharo.org/books/ >>>>> >>>>> Bloc Memory Game (alpha) is a first tutorial on Bloc the new graphics >>>>> core for Pharo. Booklet written by A. Chis, S. Ducasse, A. Syrel. >>>>> >>>>> >>>>> http://files.pharo.org/books-pdfs/booklet-Bloc/2017-11-09-memorygame.pdf >>>>> >>>>> >>>>> To load the memory game >>>>> >>>>> Metacello new >>>>> baseline: 'BlocTutorials'; >>>>> repository: 'github://pharo-graphics/Tutorials/src'; >>>>> load >>>>> >>>>> >>>>> A similar booklet could be done for the title >>>>> 'Doing a presentation / slide show / assitant with Bloc' (or similar, >>>>> adapt .....) >>>>> >>>>> >>> -- >>> >>> www.tudorgirba.com >>> www.feenk.com >>> >>> >>> "Obvious things are difficult to teach." >>> >>> >>> >>> >>> >>> >>> >> >> -- >> Cheers, >> Alex > -- www.tudorgirba.com www.feenk.com "There are no old things, there are only old ways of looking at them."

Nov. 14, 2017

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

by Offray Vladimir Luna CÃ¡rdenas

Alex, I understand that frustration on installation could be motivated by other issues instead of GT Documenter, but if the team ask to use "|Iceberg enableMetacelloIntegration: true." |in the project readme, where it also says that is supported for Pharo 6.1 and 7.0, is natural to think that something is wrong with documentation and/or in the project's expectations about its intended users and their will to invest the effort, time and motivation for "living in the edge". I understand that if we want stuff to be improved it should be tested, but also that not all the people that is willing to test stuff for Pharo 6.1 needs to live in such edge. Or the project is sending a message that is not giving the bests firsts impressions, or is going to users which are not intended . I would go for a smooth install first and then for collaboration with git. I'll make a pull request with the proposal for a better documentation, but my understanding about how you can go from the first (user of GT Documenter) to the second (developer using Git integration) is not clear. GT Tools has been pretty empowering. I have told that several times and I don't think that I have wrote a single line of code in their repos. But is getting more difficult just to test and use them and I think that is related with the idea that my user *needs* to be also my co-developer, starting with their ssh git key pair. If we don't make easier to contribute by just making easier to install, there will be no evolution either. Cheers, Offray On 14/11/17 11:45, Aliaksei Syrel wrote: > Hi Offray, > > I understand your frustration, but with all respect, the fact that you > have problems with Iceberg does not mean that GT Documenter or any > other GT tool is responsible for described problems. > > Most complains about bloc, brick, whatever is because of unrelated > stuff. It is a little bit disappointing. Especially for me, as one of > the maintainers. But it is ok, I got used to it :) > > I donât remember when last time I used stable Pharo (not because it > does not exist), simply live on the edge since Pharo4. If no one will > use Git and report problems Iceberg will never progress. If no one > will use Bloc it will never get âthereâ. Unfortunately, living on the > edge is dangerous, requires effort, motivation and time. > > The script that Doru provided works flawlessly on OSX, we load it > almost everyday. !! Bloc is tested on CI and builds are green on > Windows, Linux and OSX !!. If computer (CI) manages to install it, I > am pretty sure human can do it too. Looks like there is something > missing in your configuration, something tiny :) Error handling in > Iceberg can be definitely improved, but it is a different story. > > P.S. Documenter can be installed without enabled Iceberg integration. > This is how CI does it. You will just not be able to contribute. > > Cheers, > Alex > > On Tue, 14 Nov 2017 at 16:37, Offray Vladimir Luna CÃ¡rdenas > <offray.luna(a)mutabit.com <mailto:offray.luna@mutabit.com>> wrote: > > I have been just trying to install GT Documenter and is really > frustrating (I have been unable to install it even for the first > time!). > > This was the list of errors I got and steps I followed, in almost > sequential order, just to get a (bittersweet!) taste of GT Documenter: > > * 1st: LGit_GIT_ERROR: No ssh-agent suitable credentials found. > So I go to GitHub, follow the five pages of documentation to > get my SSH credentials that start at [1], then, because I > still get the same error, go to the Iceberg FAQ [2], try to > surpass the erro,r via command line and doesn't work, so I go > to the Iceberg settings and try the manual configuration, > going to the next item > > [1] > https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-… > [2] https://github.com/pharo-vcs/iceberg/blob/master/README.md > > * Now I get "Instance of LGitCredentialsSSH class did not > understand #ifTrue:ifFalse:". I try to make sense of it in the > debugger, but is something I cannot. Anyway, I rerun it and > now I get: LGit_GIT_EEXISTS: > '/home/offray/Programas/Pharo/6.1a/Dev24/pharo-local/iceberg/feenkcom/gtoolkit' > exists and is not an empty directory. I delete that directory > and try an installation... again > * Now I get: "Instance of FileReference did not understand > #notEmpty". I try to make sense of it in the debugger. My user > is git, my public and private ssh keys are not empty. Despite > of not making sense of all I understand that is trying to > clone something at git@github.com:feenkcom/gtoolkit.git > <mailto:git@github.com:feenkcom/gtoolkit.git>. I go to my > image dir and then to `iceberg/feenkcom/gtoolkit/`. There is a > git repository there, but is empty. > * Now I wonder, maybe if I can just clone the directory there, > but how I say Iceberg to load it? So I run now only the > Metacello part. Same error and solution that the last time but > now for gtoolkit-visualizer, Brick, gtoolkit-examples, Bloc > and Sparta. > * After getting my ssh keys, overcome config problems in shell > and the Pharo settings, chasing these errors and solving them > by cloning the repositories manually, I'm, a couple of hours > later, ready to test GT Documenter, but with the last > Iceberg's duplicated repository message about Sparta I give > up. Is not nice to start your day accumulating frustration... > that sets a bad mood for the rest of it, and you need to > actively fight against. > > I have thought that Git is overcomplicated for most of the > developers' tasks and communities. I don't know if the root of > previous issues is in the "Iceberg enableMetacelloIntegration: > true" line, but having to get your pair of keys working to just > install software is overkill for the common user (and when LibGit > errors are present, the documented solutions don't work > seamlessly). Maybe a more sensitive solution would be just to use > libgit, without any ssh auth to clone repositories and its > prerequisites or even better, some download that goes to the files > in the tip (or other) version without all this overhead. > > Anyway, as I said, I have been unable to test GT Documenter > properly and getting feedback over GT Tools from the team usually > requires a lot of effort in my case (insisting on getting answers > or getting none). And that is just to test a promising tech that > still doesn't offer saving features (just and awesome preview). I > think that a more sensible approach for a good documentation > toolkit for now is on Spec and creating custom syntax highlighters > with SmaCC[3], that is well documented and works today. > > [3] > https://medium.com/@juliendelplanque/hacking-a-simple-syntactic-highlighter… > > I understand that community is trying its best, but expressing how > current offerings are not mature and constructive criticism can > help on that. At the moment my feeling is that if you want to try > the new shinny alpha stuff from GT Documenter, you will need to be > prepared for a lot of frustration and silence. > > Cheers, > > Offray > > > On 10/11/17 12:41, Tudor Girba wrote: >> Hi, >> >> As shown at ESUG, GT Documenter offers an advanced viewer (and editor) for Pillar working on top of Bloc. >> >> You can get it by loading: >> >> Iceberg enableMetacelloIntegration: true. >> Metacello new >> baseline: 'GToolkit'; >> repository: 'github://feenkcom/gtoolkit/src'; >> load. >> >> For example, you can then inspect: >> 'PATH_TO_ICEBERG/feenkcom/gtoolkit/doc/transcript/index.pillarâ asFileReference >> >> Cheers, >> Doru >> >> >>> On Nov 10, 2017, at 12:58 PM, H. Hirzel <hannes.hirzel(a)gmail.com> <mailto:hannes.hirzel@gmail.com> wrote: >>> >>> A note: >>> >>> Tudor Girba wrote: >>> <tudor(a)tudorgirba.com> <mailto:tudor@tudorgirba.com> Fri, Aug 25, 2017 at 1:31 PM >>> Reply-To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> <mailto:pharo-users@lists.pharo.org> >>> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> <mailto:pharo-users@lists.pharo.org> >>> >>> Hi, >>> >>> As mentioned in an announcement about 10 days ago, we are building a >>> Pillar editor with inline viewing abilities in Bloc. Here is how it >>> looked like. Please note the embedded picture. We continued working on >>> it since then and we will probably announce the next version this >>> weekend: >>> >>> >>> Maybe there is now enough progress to do simple presentations in Bloc? >>> >>> >>> On 11/10/17, H. Hirzel <hannes.hirzel(a)gmail.com> <mailto:hannes.hirzel@gmail.com> wrote: >>>> Hello >>>> >>>> In the thread 'including Pillar in Pharo image by default' it was >>>> suggested by Stephane Ducasse to include a subset of Pillar in the >>>> Pharo image[1] . >>>> >>>> I'd like to extend that proposal a little bit it in order to do very >>>> simple presentations. This should allow to describe at least part of >>>> the slides used in the MOOC course [3]. >>>> >>>> This will be _a possible_ solution to the question brought up in the >>>> thread 'Writing "powerpoint" like presentations in Pharo?'. >>>> >>>> Another use is to write instructions with executable content within >>>> the image ("Assistants"). >>>> >>>> So below is the a proposal for a Pillar syntax _subset_ for class >>>> comments and _simple_ presentations. >>>> The numbering scheme follows the 'Pillar syntax cheat sheet' [2] >>>> >>>> >>>> >>>> >>>> MINI PILLAR SYNTAX (a subset of Pillar) >>>> >>>> 1. Headers >>>> >>>> !Header 1 >>>> !!Header 2 >>>> !!!Header 3 >>>> >>>> >>>> 2. Lists >>>> >>>> - Unordered List >>>> # Ordered list >>>> >>>> >>>> >>>> 5. Emphasis >>>> >>>> ""bold"" >>>> >>>> >>>> 6. Code blocks >>>> >>>> [[[ >>>> Transcript show: 'Hello World'. >>>> \]]] >>>> >>>> >>>> 9. Annotation >>>> >>>> ${slide:title=About Pharo}$ >>>> >>>> >>>> >>>> >>>> Next week I plan to implement the rendering of this 'Mini Pillar' in >>>> Morphic using the Morphic API subset that works in Pharo and Squeak. >>>> >>>> A renderer using Bloc would also be nice. [4] >>>> >>>> Comments, suggestions, code snippets and other help is welcome. >>>> >>>> Regards >>>> Hannes >>>> >>>> >>>> >>>> >>>> -------------------------------------------------------------------------------------------------- >>>> [1] Pillar subset for class comments >>>> >>>> Stephane Ducasse >>>> <stepharo.self(a)gmail.com> <mailto:stepharo.self@gmail.com> Fri, Aug 11, 2017 at 7:09 PM >>>> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> <mailto:pharo-users@lists.pharo.org> >>>> >>>> Tx cyril >>>> >>>> For class comment I image that we want >>>> >>>> ! >>>> >>>> - >>>> - >>>> *url* >>>> and bold >>>> [[[ >>>> >>>> ]]] >>>> >>>> Did I miss something. >>>> >>>> Stef >>>> >>>> >>>> >>>> >>>> >>>> -------------------------------------------------------------------------------------------------- >>>> [2] >>>> http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet >>>> -------------------------------------------------------------------------------------------------- >>>> >>>> >>>> 1. Headers >>>> >>>> !Header 1 >>>> !!Header 2 >>>> !!!Header 3 >>>> !!!!Header 4 >>>> !!!!!Header 5 >>>> !!!!!!Header 6 >>>> >>>> 2. Lists >>>> >>>> - Unordered List >>>> # Ordered list >>>> >>>> 3. Table >>>> >>>> |! Left |! Right |! Centered >>>> |{Left |}Right| Centered >>>> >>>> >>>> 4. Description >>>> Note >>>> on a new line >>>> >>>> ;head >>>> :item >>>> >>>> >>>> 5. Emphasis >>>> >>>> ""bold"" >>>> ''italic'' >>>> --strikethrough-- >>>> __underscore__ >>>> ==inline code== >>>> @@subscript@@ >>>> ^^sub-script^^ >>>> >>>> 6. Code blocks >>>> >>>> [[[labÂel=ÂhelÂloSÂcriÂpt|ÂcapÂtioÂn=How to print Hello >>>> World|ÂlanÂguaÂge=ÂSmaÂlltalk >>>> Transcript show: 'Hello World'. >>>> \]]] >>>> >>>> >>>> 7. Raw >>>> >>>> >>>> {{{latex: >>>> this is how you inject raw \LaTeX in your output file >>>> }}} >>>> >>>> {{{marÂkdown: >>>> this is how you inject raw `markdown` in your output file >>>> }}} >>>> >>>> {{{html: >>>> this is how you inject raw ÂhtmÂl</Âb> in your output file >>>> }}} >>>> >>>> >>>> 8. Links >>>> >>>> Anchor @anchor (new line) >>>> Internal link *anchor* >>>> External link *Google>http://google.com* >>>> Image +Caption>file://image.png|width=50|label=label+ >>>> >>>> >>>> 9. Annotation >>>> Note >>>> on a new line >>>> >>>> Annotation @@note this is a note >>>> Todo item @@todo this is to do >>>> >>>> >>>> 10. Comments >>>> >>>> % each line starting with % is commented >>>> >>>> >>>> 11. References >>>> >>>> This document is copied from >>>> http://www.cheatography.com/benjaminvanryseghem/cheat-sheets/pillar/ >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> ---------------------------------------------------------------------- >>>> [3] Example pillar code for slides >>>> ---------------------------------------------------------------------- >>>> >>>> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T… >>>> >>>> { >>>> "title":"To the Roots of Objects", >>>> "subtitle":"Learning from beauty", >>>> "author":"Stephane Ducasse", >>>> "complement":"http://stephane.ducasse.free.fr/ \\\\ >>>> stephane.ducasse(a)inria.fr" >>>> <http://stephane.ducasse.free.fr/%5C%5C%5C%5Cstephane.ducasse@inria.fr> >>>> } >>>> >>>> >>>> ${toc:depthLevel=2|level=0|highlight=0}$ >>>> >>>> %Les sections ne sont pas des titres de slide mais dÃ©finnissent la >>>> structure du doucment. Il est possible de rajouter >>>> "renderStructureAsSlide":false dans pillar.conf pour ne pas crÃ©er de >>>> slide Ã partir d'un titre. >>>> >>>> >>>> ${slide:title=License}$ >>>> >>>> +>file://figures/CreativeCommons.png|width=50|label=figCreativeCommons+ >>>> >>>> >>>> ! Introduction >>>> >>>> % >>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>> >>>> >>>> ${slide:title=Really?!|label=really}$ >>>> >>>> ${columns}$ >>>> >>>> ${column:width=50}$ >>>> >>>> %the width parameter take an Int between 1 and 100 >>>> %For now we have to pass a line before and after an annotation, I'll >>>> correct that soon in Pillar. >>>> - No primitive types >>>> - No hardcoded constructs for conditional >>>> - Only messages >>>> - Only objects >>>> >>>> ${column:width=50}$ >>>> >>>> - and this works? >>>> - I mean really? >>>> - Not even slow? >>>> - Can't be real! >>>> >>>> ${endColumns}$ >>>> >>>> ${slide:title=Motto}$ >>>> >>>> - Let's open our eyes, look, understand, and deeply understand the >>>> underlying design aspects of object-oriented programming. >>>> >>>> >>>> *@really* >>>> >>>> *TEST !>@really* >>>> >>>> ${slide:title=Booleans}$ >>>> >>>> [[[language=smalltalk >>>> 3 > 0 >>>> ifTrue: ['positive'] >>>> ifFalse: ['negative'] >>>> -> 'positive' >>>> ]]] >>>> >>>> ${slide:title=Yes ifTrue\:ifFalse\: is a message!}$ >>>> >>>> [[[language=smalltalk >>>> Weather isRaining >>>> ifTrue: [self takeMyUmbrella] >>>> ifFalse: [self takeMySunglasses] >>>> ]]] >>>> >>>> - Conceptually ==ifTrue:ifFalse:== is a message sent to an object: a >>>> boolean! >>>> - ==ifTrue:ifFalse:== is in fact radically optimized by the compiler >>>> but you can implement another one such ==siAlors:sinon:== and check. >>>> >>>> ${slide:title=Booleans}$ >>>> >>>> In Pharo booleans have nothing special >>>> - & | not >>>> - or: and: (lazy) >>>> - xor: >>>> - ifTrue:ifFalse: >>>> - ifFalse:ifTrue: >>>> - ... >>>> >>>> ${slide:title=Lazy Logical Operators}$ >>>> >>>> *LINK>@frm:really* >>>> >>>> [[[language=smalltalk >>>> false and: [1 error: 'crazy'] >>>> -> false and not an error >>>> ]]] >>>> >>>> ! Exercices >>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>> >>>> !! Exercise 1: Implement not >>>> >>>> ${slide:title=Exercise 1\: Implement not}$ >>>> >>>> - Propose an implementation of not in a world where you do not have >>>> Booleans. >>>> - You only have objects and messages. >>>> [[[language=smalltalk >>>> false not >>>> -> true >>>> >>>> true not >>>> -> false >>>> ]]] >>>> >>>> !!Exercise 2: Implement | (Or) ifTrue: ifFalse: >>>> >>>> ${toc:depthLevel=2|level=0|highlight=1}$ >>>> >>>> ${slide:title=Exercise 2\: Implement \| (Or)}$ >>>> >>>> - Propose an implementation of or in a world where you do not have >>>> Booleans. >>>> - You only have objects and messages. >>>> >>>> [[[language=smalltalk >>>> true | true -> true >>>> true | false -> true >>>> true | anything -> true >>>> >>>> false | true -> true >>>> false | false -> false >>>> false | anything -> anything >>>> ]]] >>>> >>>> ${slide:title=Exercise2\: Variation - Implement ifTrue\:ifFalse\:}$ >>>> >>>> - Propose an implementation of not in a world where you do not have >>>> Booleans. >>>> - You only have objects, messages and closures. >>>> >>>> [[[language=smalltalk >>>> false ifTrue: [ 3 ] ifFalse: [ 5 ] >>>> -> 5 >>>> true ifTrue: [ 3 ] ifFalse: [ 5 ] >>>> -> 3 >>>> ]]] >>>> >>>> ! Boolean Implementation >>>> >>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>> >>>> ${slide:title=Booleans Implementation Hint One}$ >>>> >>>> - The solution does not use conditionals >>>> - else we would obtain a recursive definition of ==ifTrue:ifFalse:== >>>> >>>> ${slide:title=Boolean Implementation Hint Two}$ >>>> >>>> - The solution uses three classes: ==Boolean==, ==True== and ==False== >>>> - ==false== and ==true== are unique instances described by their own >>>> classes >>>> - ==false== is an instance of the class ==False== >>>> - ==true== is an instance of the class ==True== >>>> >>>> +Boolean Hierarchy>file://figures/BooleanHiearchyAndInstances.png|width=50+ >>>> >>>> ${slide:title=How do we express choice in OOP?}$ >>>> >>>> - We send messages to objects >>>> >>>> [[[language=smalltalk >>>> aButton color >>>> -> Color red >>>> >>>> aPane color >>>> -> Color blue >>>> >>>> aWindow color >>>> -> Color grey >>>> ]]] >>>> >>>> - Let's the receiver decide >>>> >>>> - Do not ask, tell >>>> >>>> ${slide:title=Boolean not implementation}$ >>>> >>>> - Class ==Boolean== is an abstract class that implements behavior >>>> common to true and false. Its subclasses are ==True== and ==False==. >>>> Subclasses must implement methods for logical operations ==&==, >>>> ==not==, and controls ==and:==, ==or:==, ==ifTrue:==, ==ifFalse:==, >>>> ==ifTrue:ifFalse:==, ==ifFalse:ifTrue:== >>>> >>>> [[[language=smalltalk >>>> Boolean>>not >>>> "Negation. Answer true if the receiver is false, answer false if the >>>> receiver is true." >>>> self subclassResponsibility >>>> ]]] >>>> >>>> ${slide:title=Not implementation in two methods}$ >>>> >>>> [[[language=smalltalk >>>> False>>not >>>> "Negation -- answer true since the receiver is false." >>>> ^ true >>>> ]]] >>>> >>>> [[[language=smalltalk >>>> True>>not >>>> "Negation--answer false since the receiver is true." >>>> ^ false >>>> ]]] >>>> >>>> ${slide:title=Not implementation in two methods}$ >>>> >>>> +Not >>>> implementation.>file://figures/BooleanHiearchyAndInstancesWithNotMethods.png|width=80+ >>>> >>>> ${slide:title=\| (Or)}$ >>>> [[[language=smalltalk >>>> >>>> true | true -> true >>>> true | false -> true >>>> true | anything -> true >>>> >>>> false | true -> true >>>> false | false -> false >>>> false | anything -> anything >>>> >>>> ]]] >>>> >>>> ${slide:title=Boolean>> \| aBoolean}$ >>>> >>>> [[[language=smalltalk >>>> Boolean>> | aBoolean >>>> "Evaluating disjunction (OR). Evaluate the argument. Answer true if >>>> either the receiver or the argument is >>>> true." >>>> self subclassResponsibility >>>> ]]] >>>> >>>> ${slide:title=False>> \| aBoolean}$ >>>> >>>> [[[language=smalltalk >>>> false | true -> true >>>> false | false -> false >>>> false | anything -> anything >>>> ]]] >>>> >>>> [[[language=smalltalk >>>> False >> | aBoolean >>>> "Evaluating disjunction (OR) -- answer with the argument, aBoolean." >>>> ^ aBoolean >>>> ]]] >>>> >>>> ${slide:title=True>> \| aBoolean}$ >>>> >>>> [[[language=smalltalk >>>> true | true -> true >>>> true | false -> true >>>> true | anything -> true >>>> ]]] >>>> >>>> [[[language=smalltalk >>>> True>> | aBoolean >>>> "Evaluating disjunction (OR) -- answer true since the receiver is true." >>>> ^ self >>>> ]]] >>>> >>>> ${slide:title=Or implementation in two methods}$ >>>> >>>> +>file://figures/BooleanHiearchyAndInstancesWithOrMethods.png|width=80+ >>>> >>>> ${slide:title=Implementing ifTrue\:ifFalse\:}$ >>>> >>>> - Do you see the pattern? >>>> - Remember that a closure freezes execution and that value launches >>>> the execution of a frozen code. >>>> >>>> [[[language=smalltalk >>>> True>>ifTrue: aTrueBlock ifFalse: aFalseBlock >>>> ^ aTrueBlock value >>>> ]]] >>>> >>>> [[[language=smalltalk >>>> False>>ifTrue: aTrueBlock ifFalse: aFalseBlock >>>> ^ aFalseBlock value >>>> ]]] >>>> >>>> ${slide:title=Implementation Note}$ >>>> >>>> - Note that the Virtual Machine shortcuts calls to boolean such as >>>> condition for speed reason. >>>> - But you can implement your own conditional method and debug to see >>>> that sending a message is dispatching to the right object. >>>> >>>> ! So what ? >>>> >>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>> >>>> ${slide:title=Ok so what?}$ >>>> >>>> - You will probably not implement another Boolean classes >>>> - So is it really that totally useless? >>>> >>>> >>>> ${slide:title=Message sends act as case statements}$ >>>> >>>> - The execution engine will select the right method in the class of the >>>> receiver >>>> - The case statements is dynamic in the sense that it depends on the >>>> classes loaded and the objects to which the message is sent. >>>> - Each time you send a message, the system will select the method >>>> corresponding to the receiver. >>>> >>>> >>>> ${slide:title=A Class Hierarchy is a Skeleton for Dynamic Dispatch}$ >>>> >>>> - If we would have said that the ==Boolean== would be composed of only >>>> one class, we could not have use dynamic binding. >>>> - A class hierarchy is the exoskeleton for dynamic binding >>>> >>>> - Compare the solution with one class vs. a hierarchy. >>>> >>>> +One single class vs. a nice >>>> hierarchy.>file://figures/Design-FatVsDispatch.png|width=70+ >>>> >>>> - The hierarchy provides a way to specialize behavior. >>>> - It is also more declarative in the sense that you only focus on one >>>> class. >>>> - It is more modular in the sense that you can package different >>>> classes in different packages. >>>> >>>> ${slide:title=Avoid Conditionals}$ >>>> >>>> - Use objects and messages, when you can >>>> - The execution engine acts as a conditional switch: Use it! >>>> - Check the AntiIfCampaign. >>>> >>>> ${slide:title=Follow-up: Implement ternary logic}$ >>>> >>>> - Boolean: ==true==, ==false==, ==unknown== >>>> +Ternaru Logic decision table >>>>> file://figures/ArrayBoolean.png|width=30|label=fig:ternLogic+ >>>> - Implementing in your own classes. >>>> >>>> ! Summary >>>> >>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>> >>>> ${slide:title=Summary}$ >>>> - Tell, do not ask >>>> - Let the receiver decide >>>> - Message sends as potential dynamic conditional >>>> - Class hiearchy builds a skeleton for dynamic dispatch >>>> - Avoid conditional >>>> >>>> >>>> >>>> >>>> ----------------------------------------- >>>> [4] Bloc >>>> Load Bloc with executing in a playground (Pharo 6.1) >>>> >>>> Metacello new >>>> baseline: 'Bloc'; >>>> repository: 'github://pharo-graphics/Bloc:pharo6.1/src'; >>>> load: #core >>>> >>>> >>>> A tutorial to use bloc is available on >>>> http://files.pharo.org/books/ >>>> Bloc Memory Game (alpha) is a first tutorial on Bloc the new graphics >>>> core for Pharo. Booklet written by A. Chis, S. Ducasse, A. Syrel. >>>> >>>> http://files.pharo.org/books-pdfs/booklet-Bloc/2017-11-09-memorygame.pdf >>>> >>>> To load the memory game >>>> >>>> Metacello new >>>> baseline: 'BlocTutorials'; >>>> repository: 'github://pharo-graphics/Tutorials/src'; >>>> load >>>> >>>> >>>> A similar booklet could be done for the title >>>> 'Doing a presentation / slide show / assitant with Bloc' (or similar, >>>> adapt .....) >>>> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com> >> www.feenk.com <http://www.feenk.com> >> >> "Obvious things are difficult to teach." >> >> >> >> >> >> > > -- > Cheers, > Alex

Nov. 14, 2017

Re: [Pharo-users] About suggestions on Pillar editor (was Re: [ann] pillar text editor)

by Tudor Girba

Hi, Please retry again by loading the #development version in Pharo 6.1: Gofer new smalltalkhubUser: 'Pier' project: 'Pillar'; configuration; loadDevelopment. You should get the extension out of the box. Please let me know if it works. Cheers, Doru > On Nov 14, 2017, at 5:55 PM, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Hi, > > A suggestion from one year ago. Should be this converted into issues? > > Cheers, > > Offray > > On 10/10/16 13:26, Offray Vladimir Luna CÃ¡rdenas wrote: >> Hi Doru, >> >> I was exploring Stephan Eggermont's code Panel because the zooming in/out behavior implemented there, but I would like to add your Pillar text editor to the exploration. >> I would like to add two things: >> >> 1. Font decrease/increase buttons/shorcuts, because for long documents, default font size can be tiresome. >> >> 2. Augmenting the amount of syntax highlighting languages, starting with markdown. I think that this would be strategic in making writing inside the image, more appealing, giving the spread of markdown as a documentation syntax in different context (GitHub, Scholar markdown, wikis, discussion, Slack clones, etc). >> I installed the extension today on a Pharo 5 system, but trying to use it, bring me the error detailed at the end of this mail, so after having it working on Pharo, I would like to explore/help in implementing items 1 and 2, avove. >> >> Cheers, >> >> Offray >> >> Error report >> =========== >> Author: OffrayLuna >> >> Array(Object)>>shouldNotImplement >> Array(ArrayedCollection)>>add: >> [ :each | self add: each ] in Array(Collection)>>addAll: >> Array(SequenceableCollection)>>do: >> Array(Collection)>>addAll: >> [ :array | >> ({array first} >> addAll: array last; >> yourself) >> collect: [ :each | >> ('' join: each first) >> -> (each second ifNotNil: [ :second | '' join: second ]) ] ] in GTPillarHighlighter>>scriptParameters >> PPActionParser>>parseOn: >> PPDelegateParser>>parseOn: >> PPSequenceParser>>parseOn: >> PPActionParser>>parseOn: >> PPDelegateParser>>parseOn: >> PPChoiceParser>>parseOn: >> PPDelegateParser>>parseOn: >> PPChoiceParser>>parseOn: >> PPPossessiveRepeatingParser>>parseOn: >> PPDelegateParser>>parseOn: >> PPEndOfInputParser>>parseOn: >> GTPillarHighlighter(PPDelegateParser)>>parseOn: >> GTPillarHighlighter(PPParser)>>parseWithContext: >> GTPillarHighlighter(PPParser)>>parse:withContext: >> GTPillarHighlighter(PPParser)>>parse: >> GTPillarHighlighterTextDecorator>>parse:onError: >> GLMHighlighterTextParserStyler>>privateStyle: >> [ self privateStyle: text. >> view ifNotNil: [ view stylerStyledInBackground: text ] ] in [ backgroundProcess := [ self privateStyle: text. >> view ifNotNil: [ view stylerStyledInBackground: text ] ] >> forkAt: Processor userBackgroundPriority ] in GLMHighlighterTextParserStyler(SHTextStyler)>>styleInBackgroundProcess: >> [ self value. >> Processor terminateActive ] in BlockClosure>>newProcess >> =============== >> >> On 09/10/16 16:23, Tudor Girba wrote: >>> Hi, >>> >>> Pillar now ships with a text editor that also features a syntax highlighter. >>> >>> So, now, if you load the development version of Pillar: >>> >>> Gofer new >>> smalltalkhubUser: 'Pier' project: 'Pillar'; >>> configuration; >>> loadDevelopment. >>> >>> You will have an extra presentation when inspecting a .pillar file: >>> >>> <gjkebecengkghnjk.png> >>> >>> The new thing here is that the highlighter is based on the Pillar PetitParser, and it is extensible for highlighting more parts if needed. The highlighting also can support actions. For example, the picture above shows the file to the right after clicking on the reference. >>> >>> Please take a look and let me know what you think. >>> >>> Cheers, >>> Doru >>> >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "Things happen when they happen, >>> not when you talk about them happening." >>> >> > -- www.tudorgirba.com www.feenk.com "We are all great at making mistakes."

Nov. 14, 2017

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

by Offray Vladimir Luna CÃ¡rdenas

Hi Doru, On 14/11/17 11:36, Tudor Girba wrote: > Hi Offray, > > There are two issues that I take from your email. So, please allow me to address them separately: > > 1. The process of installing the new GT (with Documenter) > GT is meant to load in Pharo 6.1. It is tested tested automatically several times a day both on Windows (Appveyor) and on Linux (Travis CI), and we load it automatically on Mac when we develop. Other people managed to load it as well. That does not mean that there are no problems, but it does mean that there are no problems that we are aware of. So, we need to understand what the issue is. > From your email I understand that you are using Pharo 6.1. Is it the latest image and VM? This is what about says: "Pharo 6.0 Latest update: #60510", but is Pharo 6.1. I don't know if that gives any info on the VM or how to get it. > What is the operating system? Manjaro Linux > What is the exact loading snippet that you used? The one in the thread I'm answering. Is the same in the Readme fro gtoolkit. https://github.com/feenkcom/gtoolkit > Now, please bare in mind that GT relies on the common way of organizing GitHub projects. So, what you describe seems to have to do with Iceberg, not with GT. For example, did you manage to load any other Pharo project from GitHub? > > 2. There is something about silence which I do not understand. I do not remember a particular question that you asked and you got no answer to. If there was one, I am sorry. Please repost it. I have done. Was about giving feedback to the Pillar editor. But also happened at the beginning when I tried to get feedback on the Moose list. In fact I prefer to post questions here. There is a lot of overlap between both lists, but here I have a better answers ratio. Cheers, Offray

Nov. 14, 2017

Re: [Pharo-users] Stream API

by Stephane Ducasse

Sven >From the thread discussion here my take. - I do not think that we want to reuse any of the old streams. - So first Zn to replace the binary and MultiUglyStream and after we will have to check if we should port the design of Xtream (but not the API) to Pharo. Stef On Tue, Nov 14, 2017 at 5:59 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Denis I agree. I do not like to code in reverse order. > > > On Tue, Nov 14, 2017 at 4:49 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >> 2017-11-14 16:30 GMT+01:00 Steffen MÃ¤rcker <merkste(a)web.de>: >>> >>> I forgot to mention, that the most recent code for Pharo is already on >>> Github: https://github.com/Pharophile/Transducers >>> >>> Reducers was the name of the first very first implementation. >>> >>> (In fact, I was originally inspired by clojures Reducers lib. After >>> implementing it in Smalltalk, I developed the concept further. Later I found >>> out, that the clojure guys did the same in parallel and ended up with the >>> same abstraction but a differnt name. Hence I decided change the name in >>> order to make the relation clear.) >> >> >> I like abstraction. But I think names and order of computation should be >> changed to be more Smalltalk friendly. Because now it looks like Haskell >> with right to left order: >> >> squares := Set <~ 1000 take <~ #squared map <~ (1 to: 1000). >> fileOut writeStream <~ #isSeparator filter <~ fileIn readStream. >> >> >> Is there any reason to not change it? I would like to start expressions with >> source of data: >> >> squares := (1 to: 1000) ~> #squared map ~> 1000 take ~> Set. >> fileIn readStream ~> #isSeparator filter ~> fileOut writeStream. >> >> >> >>> >>> Am .11.2017, 16:18 Uhr, schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >>> >>>> >>>> >>>>> On 14 Nov 2017, at 16:00, Steffen MÃ¤rcker <merkste(a)web.de> wrote: >>>>> >>>>> Hi, >>>>> >>> <---Schnitt---> >>>>> >>>>> >>>>> No. Transducers is my side project. I've implemented a package for >>>>> VisualWorks. Unfortunately, I did not finish the port to Pharo yet, simply >>>>> due to a lack of time. Originally, transducers evolved in the clojure >>>>> community. I figured, the concept a good fit for Smalltalk and adapted it >>>>> accordingly. (My thesis is on conditional probabilities in model-checking of >>>>> probabilistic systems.) >>>>> >>> <---Schnitt---> >>> >>>>> >>>>> http://www.cincomsmalltalk.com/publicRepository/Transducers.html >>>>> https://clojure.org/reference/transducers >>>>> Plus some mails on this list and more on the vwnc list. Feel free to >>>>> ask; I understand, that the package comment has lots of potential for >>>>> improvement to help understanding. >>>>> >>>>> Best, Steffen >>>> >>>> >>>> Some code seems to be here: http://smalltalkhub.com/#!/~cdlm/Experiments >>>> >>>> Not sure if it is complete or what the relation is, or the difference >>>> between transducers and reducers ... >>>> >>>> >>> >>> >>> >>

Nov. 14, 2017