On Tue, Nov 8, 2016 at 4:17 PM, Nicolai Hess <nicolaih...@gmail.com> wrote: > Another pulll request > https://github.com/SquareBracketAssociates/UpdatedPharoByExample/pull/180 > But I messed this one up. It contains the commits from the other pull > request.
If PR179 is merged first, it shouldn't matter (IIUC). cheers -ben > I can fix this (later) or maybe it can just be merged (can I remove a commit > from a branch with githubs web-interface(!) ? > > > 2016-11-08 1:00 GMT+01:00 Nicolai Hess <nicolaih...@gmail.com>: >> >> >> >> 2016-11-07 8:47 GMT+01:00 Nicolai Hess <nicolaih...@gmail.com>: >>> >>> Am 06.11.2016 21:04 schrieb "Dimitris Chloupis" <kilon.al...@gmail.com>: >>> > >>> > yeah as I said the chapter needs a complete rewrite. I am not even it >>> > is necessary to exist separately. >>> > >>> > On Sun, Nov 6, 2016 at 9:27 PM Nicolai Hess <nicolaih...@gmail.com> >>> > wrote: >>> >> >>> >> 2016-11-03 15:11 GMT+01:00 Nicolai Hess <nicolaih...@gmail.com>: >>> >>> >>> >>> >>> >>> >>> >>> 2016-11-03 15:02 GMT+01:00 stepharo <steph...@free.fr>: >>> >>>> >>> >>>> Hi nicolai >>> >>>> >>> >>>> I started to work on the reflection chapter. >>> >>> >>> >>> >>> >>> >>> >>> The reflection chapter (and maybe some other too) could new some new >>> >>> screenshots. >>> >> >>> >> >>> >> Actually, the reflection chapter needs some more rewrites (not only >>> >> updated screenshots). Some examples just aren't >>> >> applicable anymore because we don't have refactoring browser >>> >> preinstalled and although Nautilus can do alot, its missing >>> >> the full set of menus for creating scoped environments. >>> >> I'll try to rewrite those parts. >> >> pull request for this c hapter: >> >> https://github.com/SquareBracketAssociates/UpdatedPharoByExample/pull/179 >> >> In short: >> updated screenshots >> replace some more "explore/explorer" by inspect/inspector >> rewrote the RefactoringBrowser parts, use RBBrowserEnvironment insteand of >> BrowserEnvironment >> fix some differences in LoggingProxy (something had changed in >> ProtoObject/Object implementation), some methods like #rect: are renamed in >> the actual Pharo 5.0 image. >> #haltIf: was broken, as the example with add: / testAdd: traps into an >> infinite loop because we now call add: everytime we lookup the add: sender >> I replaced this with an example that uses Morph>>#openInWorld instead of >> OrderedCollection>>#add: >> Replaced MethodContext by Context as the name changed in Pharo 5. Added a >> description why we call the inspector on thisContext a "poor mans debugger" >> :-) >> fix some changed SystemNavigation methods. >> Some code examples show the in image method version that had changed >> (other names or otherwise refactored). >> >> so far. But I'll do another pass >> >>> >>> >> >>> >>>> >>> >>>> Now hacking PharoDoc :) >>> >>>> >>> >>>> Stef >>> >>>> >>> >>>> >>> >>>> Le 3/11/16 à 14:29, Nicolai Hess a écrit : >>> >>>>> >>> >>>>> >>> >>>>> >>> >>>>> 2016-10-27 13:32 GMT+02:00 Dimitris Chloupis >>> >>>>> <kilon.al...@gmail.com>: >>> >>>>>> >>> >>>>>> In case someone missed it I will be doing a release for version 5 >>> >>>>>> (pharo version = pbe version) this weekend , since we had Pharo 7 >>> >>>>>> initiated >>> >>>>>> few days ago. >>> >>>>>> >>> >>>>>> Essentially that means that the repo will be tagged for version 5, >>> >>>>>> which means a git commit is associated as a last commit for that >>> >>>>>> version and >>> >>>>>> there will be a frozen release - download for Pharo by Example >>> >>>>>> version 5. >>> >>>>>> After that we move to Pharo By Example version 6 or PBE6 for short >>> >>>>>> >>> >>>>>> The repo wont change otherwise and the process of submitting >>> >>>>>> commits, pull requests and issues remains the same. >>> >>>>>> >>> >>>>>> If you have found a flaw of any sort in the documentation , please >>> >>>>>> open an issue in the github issue tracker that can be found here >>> >>>>>> >>> >>>>>> >>> >>>>>> https://github.com/SquareBracketAssociates/UpdatedPharoByExample/issues >>> >>>>>> >>> >>>>>> I will try to fix any problem reported but if I cannot , the fix >>> >>>>>> will have to move to version 6 >>> >>>>>> >>> >>>>>> As always thanks to all people contributing into the impossible >>> >>>>>> .... making Pharo more amazing >>> >>>>>> >>> >>>>>> If you want to contribute feel free to do so with a pull request. >>> >>>>>> >>> >>>>>> Does not matter if you are beginner because even minor corrections >>> >>>>>> like correcting mistakes in the grammar or content of the text, >>> >>>>>> updated >>> >>>>>> pictures, or just a few lines of extra info are more than enough and >>> >>>>>> more >>> >>>>>> than welcomed. Many Pharo beginners have already done so . >>> >>>>>> >>> >>>>>> -Salute to fellow Guardians of The Light >>> >>>>> >>> >>>>> >>> >>>>> I found some problems, but I don't have time to report/fix them >>> >>>>> now, I 'll try to report them >>> >>>>> later (today or tomorrow). >>> >>>>> >>> >>>>> >>> >>>> >>> >>> >>> >>> I know fixed most text in the chapter. At least there are no notes on >>> tools that aren't there anymore and I cut those things that aren't true >>> anyone. >>> But I would like to do some more pass over it. >>> Instead of just cutting, we could add some new things. >>> Explaing the RB-Pattern syntax is maybe to much. But I would like to add >>> it. >>> Maybe I'll put some notes on criticbrower and QA. >> >> >
