June 2018 - Pharo-users - lists.pharo.org

Help contributing a fix to pharo - docs seem out of date again?

by Tim Mackinnon

Hi - a few weeks ago, I contributed a tiny fix to Pharo 7 -and the instructions seemed to work really well. Iâve since come back to try and do some more over lunch (I was thinking Iâd like to dig out the changes I worked out for using the AST and cursor to make senders/implements work properly and not just use the selected text). My first problem was that my fork of Pharo from many months ago was out of date - I think the instructions on https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo <https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo> should probably mention this subtlety. It took me ages to figure out what to do - this was the clue (https://help.github.com/articles/syncing-a-fork/ <https://help.github.com/articles/syncing-a-fork/>) - and of particular note the the tiny bit at the bottom to ensure you Push your changes back to your GitHub fork (I slightly complicated myself by using IntelliJ to do this - doable but you need to be aware of whats going on). I did this in a separate non-pharo directory (I think thats what you would recommend right? Then you can keep updating it from time to time?) Having got my GitHub fork caught up with pharo/development - I then have the Local Repo Missing error (expected) - and now when I go to repair it I can either clone again (which is the instructions online) - or âLocate this repository in your file systemâ. As Iâve had to already check everything out to catch up to pharo/dev I chose to locate. I then get a Fetch require msg (expected) I then choose to use Fetch (Iâm not sure what the Repair repository picture is now about?) - the text does mention I will become detached, so Iâve stuck to that Iâm not sure why the âsolving a detached working copyâ is further down the page - but Iâve jumped to that It says I need to synchronise both (image and repo) - but then says its easier to do a branch - and then says a nice alternative is to create a temp branch like temp/synch - however I canât see how to do that as there is only Crete new Branch from Issue now (the picture shows that plus New Branch). Am I on the right track here? If I want try something out - do I just create myself a new issue (or is there a temp issue anyway?) Tim

June 19, 2018

Re: [Pharo-users] [Pharo-dev] [Ann] Iceberg v1.1.1

by Norbert Hartl

Hi, let me wear the project manager hat for a moment. > Am 19.06.2018 um 10:59 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Hi, > > About why 1.1.1 and not 1.2.0. Itâs not about cheap or not, but about semantics :) for me âcaring about semanticsâ is just one of the top ten justifications developers use for the changes they did. > We can agree that there is no hard rule on versionning, do we? But I try to follow the following guidelines (delta my own interpretation that adds some subjectivity :P) > - Major Version will change when we break backwards compatibility > - Minor Version will change when new features are added > - Otherwise, patch version will change. > There is only one hard rule for me and that is knowing about the risk to take. So if we take the patch version it should only include important bug fixes and nothing else. I would argue that only #864, #862, #858 and #854 qualify for such a patch if at all. Not sure about #860 because the title is not specific enough. The point for me is that I want my project to rely on something like 1.1.x because I donât want anything to change that breaks my software. And I can tell you that most developers underestimate the side-effects of changes. > So I donât assign a new version number regarding the number of changes but about what they mean... To mean they mean it is a risk to use that version and you define how big that is. > Now, I considered myself this release as a patch because mostly little bugs here and there were fixed. > Moreover, one of the changes done in the credentials manager was to *recover* some backwards compatibility for people setting up credentials in settings files. > Of course, to this we add to this that my own interpretation saying that the changes do not break compatibility nor add features :) > You see you said âmostly bugsâ and that is the error already. I mean we come from an amateurish behaviour that we change released artefacts. That is not discussable just a no-go. The reason was it would have wasted a huge amount of time to do a new version. So ok it was a loose-loose situation. Now we can do it better and I want something far less amateurish. So you can discuss your semantics about what major and minor versions in pharo mean but patch needs to be the definition of the combination: least risk - highest value. > Now, this is the kind of subjective topic that starts a flamewar, but Iâd prefer to use my time on somewhat else ^^. You may not like to talk about these things but I do. And you should listen. I have no use for an environment where people only care about coding new cool stuff. If it would be like this I would quit all my pharo businesses, move to mainstream and would use pharo only for hobbyist projects because that would be the level that can be met. Norbert > In any case, I think it is more important to discuss about the numbering as soon as we have a clear documentation on Iceberg's API... > > Regarding the bad links, I copy-pasted the text from the PR instead from the release page in Iceberg, which messes up links. > > Patch version containing the following cleanups and enhancements > > #864 <https://github.com/pharo-vcs/iceberg/issues/864> Repairing Missing repositories lead to wrong source directory > #861 <https://github.com/pharo-vcs/iceberg/pull/861> update tonel to v1.0.9 > #836 <https://github.com/pharo-vcs/iceberg/issues/836> DefaultBackendType class variable is unused > #862 <https://github.com/pharo-vcs/iceberg/issues/862> Iceberg tests are not running in Pharo 7 > #852 <https://github.com/pharo-vcs/iceberg/issues/852> Make error dialogs copy-pastable > #858 <https://github.com/pharo-vcs/iceberg/issues/858> IceTipReadOnlyTextMorph does not allow select and copy anymore > #850 <https://github.com/pharo-vcs/iceberg/issues/850> Change Detached head status from error to warning if we are on a tag > #853 <https://github.com/pharo-vcs/iceberg/issues/853> Clone dialog "username" is confusing > #860 <https://github.com/pharo-vcs/iceberg/pull/860> CredentialStore API > #854 <https://github.com/pharo-vcs/iceberg/issues/854> Error in History window > > Guille > > On Mon, Jun 18, 2018 at 9:12 PM Torsten Bergmann <astares(a)gmx.de <mailto:astares@gmx.de>> wrote: > Great - thank you! Might be a small patch release - but nonetheless important. > > BTW: the links in your mail are pointing to PR's of Pharo and not Iceberg. If you used > a template you might want to consider changing it. > > > Gesendet: Montag, 18. Juni 2018 um 17:47 Uhr > Von: "Guillermo Polito" <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> > An: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>>, "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> > Betreff: [Pharo-dev] [Ann] Iceberg v1.1.1 > Hi everybody, > > This week we have a small patch release of Iceberg, version v1.1.1. > This version will be available in the next Pharo build. > > In summary, this release fixes two issues with the new credentials manager, and introduces a couple of other enhancements/bugfixes. > > Below you will find the detailed changes log. > Enjoy, > Guille > > Integrate Iceberg 1.1.1 > https://pharo.fogbugz.com/f/cases/22168/Integrate-Iceberg-1-1-1 <https://pharo.fogbugz.com/f/cases/22168/Integrate-Iceberg-1-1-1> > https://github.com/pharo-vcs/iceberg/releases/tag/v1.1.1 <https://github.com/pharo-vcs/iceberg/releases/tag/v1.1.1> > #864 <https://github.com/pharo-project/pharo/pull/864> Repairing Missing repositories lead to wrong source directory > #861 <https://github.com/pharo-project/pharo/pull/861> update tonel to v1.0.9 > #836 <https://github.com/pharo-project/pharo/pull/836> DefaultBackendType class variable is unused > #862 <https://github.com/pharo-project/pharo/pull/862> Iceberg tests are not running in Pharo 7 > #852 <https://github.com/pharo-project/pharo/pull/852> Make error dialogs copy-pastable > #858 <https://github.com/pharo-project/pharo/pull/858> IceTipReadOnlyTextMorph does not allow select and copy anymore > #850 <https://github.com/pharo-project/pharo/pull/850> Change Detached head status from error to warning if we are on a tag > #853 <https://github.com/pharo-project/pharo/pull/853> Clone dialog "username" is confusing > #860 <https://github.com/pharo-project/pharo/pull/860> CredentialStore API > #854 <https://github.com/pharo-project/pharo/pull/854> Error in History window > > > -- > > Guille Polito > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > French National Center for Scientific Research - http://www.cnrs.fr <http://www.cnrs.fr/> > > Web: http://guillep.github.io <http://guillep.github.io/> > Phone: +33 06 52 70 66 13 > > > -- > > Guille Polito > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > French National Center for Scientific Research - http://www.cnrs.fr <http://www.cnrs.fr/> > > Web: http://guillep.github.io <http://guillep.github.io/> > Phone: +33 06 52 70 66 13

June 19, 2018

Re: [Pharo-users] How to contribute to Pharo Launcher?

by Christophe Demarey

Thanks a lot Tim. All contributions are welcomed! Indeed, for a tool like Pharo Launcher, most complexity comes from multiple OS environments. > Le 19 juin 2018 Ã 12:05, Tim Mackinnon <tim(a)testit.works> a Ã©crit : > > Done - sorry, I wasnât clear on how best to tie it all together. I think its more obvious when we get it all onto GitHub - but for now this can work too. > > Thanks for resurrecting the project a while back - I know its had a bit of flack lately, but that more the complexity of multiple OS environments, and trying to get some more contributors to help. > > Ironically its quite nicely structured code - although it could do with a few more tests - so maybe thats one to double up on. > > Tim > >> On 19 Jun 2018, at 09:51, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: >> >> Hi Tim, >> >> Thanks a lot for your contributions. Looks good to me. It is a nice addition. >> Could you open an issue https://github.com/pharo-project/pharo-launcher/issues/new so that we can keep a trace of your contribution (we open issues for features / improvements also)? >> >> Thanks also to Cyril who helped you to commit to ST. >> >> Cheers, >> Christophe. >> >>> Le 18 juin 2018 Ã 19:20, Tim Mackinnon <tim(a)testit.works> a Ã©crit : >>> >>> While Iâm at it - improve the icon for Launch without Settings (it needed Alpha) >>> >>> Name: PharoLauncher-Core-TimM.174 >>> Author: TimM >>> Time: 18 June 2018, 6:11:54.416337 pm >>> UUID: d9433566-4f2b-0d00-85be-afca09965ccd >>> Ancestors: PharoLauncher-Core-TimM.173 >>> >>> Sorry - canât help with the windows launch problems as I donât have a windows machine any more. >>> >>>> On 18 Jun 2018, at 17:35, Tim Mackinnon <tim(a)testit.works> wrote: >>>> >>>> Ok - Iâve done a save for both packages - hopefully they are useful: >>>> >>>> Name: PharoLauncher-Spec-TimM.70 >>>> Author: TimM >>>> Time: 18 June 2018, 5:32:00.928101 pm >>>> UUID: 5e888bd7-4e2b-0d00-85bb-537409965ccd >>>> Ancestors: PharoLauncher-Spec-TimM.69 >>>> >>>> >>>> Name: PharoLauncher-Core-TimM.172 >>>> Author: TimM >>>> Time: 18 June 2018, 5:34:46.055084 pm >>>> UUID: 6a2b63e1-4e2b-0d00-85bc-0fed09965ccd >>>> Ancestors: PharoLauncher-Core-TimM.171 >>>> >>>> >>>> >>>>> On 18 Jun 2018, at 16:30, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: >>>>> >>>>> On 18/06/2018 17:27, Tim Mackinnon wrote: >>>>>> Hi Cyril - I have to confess that I donât recall what the steps are to safely commit in Monticello. I have smallish changes to 2 packages Core and Spec, and I can see that smalltalkhub repo in the MC browser and can browse my changes against it - but how do I commit both packages in there? I vaguely recall something about slices - but wasnât that a Pharo core thing? >>>>>> >>>>>> I get the impression that I donât just press save on each package against sthub do I? >>>>>> >>>>>> Sorry to be so dumb - Iâve just swapped out Monticello usage for Git usage these days. Just need a few hints to get back on track >>>>>> >>>>> >>>>> You need to save the two packages individually. >>>>> >>>>> While git is project oriented, StHub is package oriented. >>>>> >>>>> Slices are only for Pharo development. (One could adapt them to make >>>>> Monticello more project oriented but it is currently not the case). >>>>> >>>>> So in conclusion, yes you need to press save on each package. :) >>>>> >>>>>> Tim >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Cyril Ferlicot >>>>> https://ferlicot.fr >>>>> >>>> >>>> >>> >>> >> >> > >

June 19, 2018

Re: [Pharo-users] How to contribute to Pharo Launcher?

by Tim Mackinnon

Done - sorry, I wasnât clear on how best to tie it all together. I think its more obvious when we get it all onto GitHub - but for now this can work too. Thanks for resurrecting the project a while back - I know its had a bit of flack lately, but that more the complexity of multiple OS environments, and trying to get some more contributors to help. Ironically its quite nicely structured code - although it could do with a few more tests - so maybe thats one to double up on. Tim > On 19 Jun 2018, at 09:51, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > > Hi Tim, > > Thanks a lot for your contributions. Looks good to me. It is a nice addition. > Could you open an issue https://github.com/pharo-project/pharo-launcher/issues/new so that we can keep a trace of your contribution (we open issues for features / improvements also)? > > Thanks also to Cyril who helped you to commit to ST. > > Cheers, > Christophe. > >> Le 18 juin 2018 Ã 19:20, Tim Mackinnon <tim(a)testit.works> a Ã©crit : >> >> While Iâm at it - improve the icon for Launch without Settings (it needed Alpha) >> >> Name: PharoLauncher-Core-TimM.174 >> Author: TimM >> Time: 18 June 2018, 6:11:54.416337 pm >> UUID: d9433566-4f2b-0d00-85be-afca09965ccd >> Ancestors: PharoLauncher-Core-TimM.173 >> >> Sorry - canât help with the windows launch problems as I donât have a windows machine any more. >> >>> On 18 Jun 2018, at 17:35, Tim Mackinnon <tim(a)testit.works> wrote: >>> >>> Ok - Iâve done a save for both packages - hopefully they are useful: >>> >>> Name: PharoLauncher-Spec-TimM.70 >>> Author: TimM >>> Time: 18 June 2018, 5:32:00.928101 pm >>> UUID: 5e888bd7-4e2b-0d00-85bb-537409965ccd >>> Ancestors: PharoLauncher-Spec-TimM.69 >>> >>> >>> Name: PharoLauncher-Core-TimM.172 >>> Author: TimM >>> Time: 18 June 2018, 5:34:46.055084 pm >>> UUID: 6a2b63e1-4e2b-0d00-85bc-0fed09965ccd >>> Ancestors: PharoLauncher-Core-TimM.171 >>> >>> >>> >>>> On 18 Jun 2018, at 16:30, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: >>>> >>>> On 18/06/2018 17:27, Tim Mackinnon wrote: >>>>> Hi Cyril - I have to confess that I donât recall what the steps are to safely commit in Monticello. I have smallish changes to 2 packages Core and Spec, and I can see that smalltalkhub repo in the MC browser and can browse my changes against it - but how do I commit both packages in there? I vaguely recall something about slices - but wasnât that a Pharo core thing? >>>>> >>>>> I get the impression that I donât just press save on each package against sthub do I? >>>>> >>>>> Sorry to be so dumb - Iâve just swapped out Monticello usage for Git usage these days. Just need a few hints to get back on track >>>>> >>>> >>>> You need to save the two packages individually. >>>> >>>> While git is project oriented, StHub is package oriented. >>>> >>>> Slices are only for Pharo development. (One could adapt them to make >>>> Monticello more project oriented but it is currently not the case). >>>> >>>> So in conclusion, yes you need to press save on each package. :) >>>> >>>>> Tim >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Cyril Ferlicot >>>> https://ferlicot.fr >>>> >>> >>> >> >> > >

June 19, 2018

Re: [Pharo-users] [Pharo-dev] [Ann] Iceberg v1.1.1

by Guillermo Polito

Hi, About why 1.1.1 and not 1.2.0. It's not about cheap or not, but about semantics :) We can agree that there is no hard rule on versionning, do we? But I try to follow the following guidelines (delta my own interpretation that adds some subjectivity :P) - Major Version will change when we break backwards compatibility - Minor Version will change when new features are added - Otherwise, patch version will change. So I don't assign a new version number regarding the number of changes but about what they mean... Now, I considered myself this release as a patch because mostly little bugs here and there were fixed. Moreover, one of the changes done in the credentials manager was to *recover* some backwards compatibility for people setting up credentials in settings files. Of course, to this we add to this that my own interpretation saying that the changes do not break compatibility nor add features :) Now, this is the kind of subjective topic that starts a flamewar, but I'd prefer to use my time on somewhat else ^^. In any case, I think it is more important to discuss about the numbering as soon as we have a clear documentation on Iceberg's API... Regarding the bad links, I copy-pasted the text from the PR instead from the release page in Iceberg, which messes up links. Patch version containing the following cleanups and enhancements #864 <https://github.com/pharo-vcs/iceberg/issues/864> Repairing Missing repositories lead to wrong source directory #861 <https://github.com/pharo-vcs/iceberg/pull/861> update tonel to v1.0.9 #836 <https://github.com/pharo-vcs/iceberg/issues/836> DefaultBackendType class variable is unused #862 <https://github.com/pharo-vcs/iceberg/issues/862> Iceberg tests are not running in Pharo 7 #852 <https://github.com/pharo-vcs/iceberg/issues/852> Make error dialogs copy-pastable #858 <https://github.com/pharo-vcs/iceberg/issues/858> IceTipReadOnlyTextMorph does not allow select and copy anymore #850 <https://github.com/pharo-vcs/iceberg/issues/850> Change Detached head status from error to warning if we are on a tag #853 <https://github.com/pharo-vcs/iceberg/issues/853> Clone dialog "username" is confusing #860 <https://github.com/pharo-vcs/iceberg/pull/860> CredentialStore API #854 <https://github.com/pharo-vcs/iceberg/issues/854> Error in History window Guille On Mon, Jun 18, 2018 at 9:12 PM Torsten Bergmann <astares(a)gmx.de> wrote: > Great - thank you! Might be a small patch release - but nonetheless > important. > > BTW: the links in your mail are pointing to PR's of Pharo and not Iceberg. > If you used > a template you might want to consider changing it. > > > *Gesendet:* Montag, 18. Juni 2018 um 17:47 Uhr > *Von:* "Guillermo Polito" <guillermopolito(a)gmail.com> > *An:* "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org>, > "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org> > *Betreff:* [Pharo-dev] [Ann] Iceberg v1.1.1 > Hi everybody, > > This week we have a small patch release of Iceberg, version v1.1.1. > This version will be available in the next Pharo build. > > In summary, this release fixes two issues with the new credentials > manager, and introduces a couple of other enhancements/bugfixes. > > Below you will find the detailed changes log. > Enjoy, > Guille > > > Integrate Iceberg 1.1.1 > https://pharo.fogbugz.com/f/cases/22168/Integrate-Iceberg-1-1-1 > > https://github.com/pharo-vcs/iceberg/releases/tag/v1.1.1 > > #864 <https://github.com/pharo-project/pharo/pull/864> Repairing Missing > repositories lead to wrong source directory > #861 <https://github.com/pharo-project/pharo/pull/861> update tonel to > v1.0.9 > #836 <https://github.com/pharo-project/pharo/pull/836> DefaultBackendType > class variable is unused > #862 <https://github.com/pharo-project/pharo/pull/862> Iceberg tests are > not running in Pharo 7 > #852 <https://github.com/pharo-project/pharo/pull/852> Make error dialogs > copy-pastable > #858 <https://github.com/pharo-project/pharo/pull/858> IceTipReadOnlyTextMorph > does not allow select and copy anymore > #850 <https://github.com/pharo-project/pharo/pull/850> Change Detached > head status from error to warning if we are on a tag > #853 <https://github.com/pharo-project/pharo/pull/853> Clone dialog > "username" is confusing > #860 <https://github.com/pharo-project/pharo/pull/860> CredentialStore API > #854 <https://github.com/pharo-project/pharo/pull/854> Error in History > window > > > -- > > > > Guille Polito > > Research Engineer > > > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

June 19, 2018

Re: [Pharo-users] How to contribute to Pharo Launcher?

by Christophe Demarey

Hi Tim, Thanks a lot for your contributions. Looks good to me. It is a nice addition. Could you open an issue https://github.com/pharo-project/pharo-launcher/issues/new so that we can keep a trace of your contribution (we open issues for features / improvements also)? Thanks also to Cyril who helped you to commit to ST. Cheers, Christophe. > Le 18 juin 2018 Ã 19:20, Tim Mackinnon <tim(a)testit.works> a Ã©crit : > > While Iâm at it - improve the icon for Launch without Settings (it needed Alpha) > > Name: PharoLauncher-Core-TimM.174 > Author: TimM > Time: 18 June 2018, 6:11:54.416337 pm > UUID: d9433566-4f2b-0d00-85be-afca09965ccd > Ancestors: PharoLauncher-Core-TimM.173 > > Sorry - canât help with the windows launch problems as I donât have a windows machine any more. > >> On 18 Jun 2018, at 17:35, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Ok - Iâve done a save for both packages - hopefully they are useful: >> >> Name: PharoLauncher-Spec-TimM.70 >> Author: TimM >> Time: 18 June 2018, 5:32:00.928101 pm >> UUID: 5e888bd7-4e2b-0d00-85bb-537409965ccd >> Ancestors: PharoLauncher-Spec-TimM.69 >> >> >> Name: PharoLauncher-Core-TimM.172 >> Author: TimM >> Time: 18 June 2018, 5:34:46.055084 pm >> UUID: 6a2b63e1-4e2b-0d00-85bc-0fed09965ccd >> Ancestors: PharoLauncher-Core-TimM.171 >> >> >> >>> On 18 Jun 2018, at 16:30, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: >>> >>> On 18/06/2018 17:27, Tim Mackinnon wrote: >>>> Hi Cyril - I have to confess that I donât recall what the steps are to safely commit in Monticello. I have smallish changes to 2 packages Core and Spec, and I can see that smalltalkhub repo in the MC browser and can browse my changes against it - but how do I commit both packages in there? I vaguely recall something about slices - but wasnât that a Pharo core thing? >>>> >>>> I get the impression that I donât just press save on each package against sthub do I? >>>> >>>> Sorry to be so dumb - Iâve just swapped out Monticello usage for Git usage these days. Just need a few hints to get back on track >>>> >>> >>> You need to save the two packages individually. >>> >>> While git is project oriented, StHub is package oriented. >>> >>> Slices are only for Pharo development. (One could adapt them to make >>> Monticello more project oriented but it is currently not the case). >>> >>> So in conclusion, yes you need to press save on each package. :) >>> >>>> Tim >>>> >>>> >>>> >>> >>> >>> -- >>> Cyril Ferlicot >>> https://ferlicot.fr >>> >> >> > >

June 19, 2018

Re: [Pharo-users] [ann] gt documenter

by Tudor Girba

Hi Offray, Would you be able to retry the installation as mentioned below, and let us know if you still encounter issues? Cheers, Doru > On Jun 16, 2018, at 8:24 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > If Moz2D is installed, the fonts should work fine. > > Can you please try the installation again? And if it does not work, please let me know if in > Settings Browser / Appearance / Bloc / Preferable Sparta renderering backend > you see Moz2D or not. > > > Cheers, > Doru > > >> On Jun 15, 2018, at 2:31 PM, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: >> >> Hi Doru, >> >> Thanks for the update in Markdown. I will try to bring better Markdown >> support in Pharo by developing my ideas on a Playground for Markdown >> with syntax highlighting, image preview and so on and maybe I can help >> in incorporating them in GT Documenter on Pharo 7. >> >> I can confirm that fonts didn't work on Manjaro on 64 bits installation >> running Pharo 64b previously, but maybe in Pharo 7 installation will be >> smoother, including font installation via Moz2D integration (nix package >> manager has been a real asset in our workshops in multiple Unix >> environments, including Mac and several Gnu/Linux flavors, so maybe it >> can help with Moz2D engine and fonts integration). >> >> Cheers, >> >> Offray >> >> >> On 15/06/18 00:56, Tudor Girba wrote: >>> Hi, >>> >>> I am happy you like it. >>> >>> Fonts should work with a Pharo 64b installation on Linux, including Manjaro. Can you confirm that you use a Pharo 64bit and that it does not work? If yes, can you describe how you are installing Pharo and GToolkit? >>> >>> Markdown is certainly interesting, but it is not our focus at this point. We are building on top of Pillar. There are several reasons for it, two of them being: >>> 1. To build the experience we want to, we need deep control over the markup language and Pillar provides that in Pharo. >>> 2. Pillar is the de facto documentation markup used in Pharo, and our primary focus is to support new kinds of development workflows in this environment, including handling documentation. >>> >>> GT 2nd generation will indeed not be part of Pharo 7, but will be loadable in it. >>> >>> Cheers, >>> Doru >>> >>> >>> >>>> On Jun 15, 2018, at 3:47 AM, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: >>>> >>>> Cool! I hope to see how this could be integrated in Grafoscopio once Documenter is better integrated with Pharo, for example addressing the font issues already reported in the mailing list on Manjaro Linux (64 bits) and in the thread at [1] and also the Markdown integration possibilities (which are never answered). >>>> [1] https://twitter.com/feenkcom/status/996310432225820672 >>>> >>>> I think it will not part of Pharo 7 but, may be in Pharo 8 we can start to use it in a more confident day to day fashion. >>>> >>>> Keep the interesting work. >>>> >>>> Cheers, >>>> >>>> Offray >>>> >>>> On 13/06/18 15:57, Tudor Girba wrote: >>>>> Hi, >>>>> >>>>> We are happy to announce a new leap of GToolkit Documenter, the tool for manipulating live documents directly in the development environment: >>>>> https://github.com/feenkcom/gtoolkit-documenter >>>>> >>>>> Documenter is part of the second generation GToolkit project, it is based on Bloc and works with the latest Pillar. It is mainly developed by Juraj Kubelka. >>>>> >>>>> Attached you can see a preview of how documents look like: >>>>> >>>>> <gt-documenter.png> >>>>> >>>>> At its core it offers a live editor for manipulating Pillar documents. The interaction happens seamlessly directly in the text editor, and it can be combined with different types of previews to serve several classes of use cases: >>>>> â¢ code documentation >>>>> â¢ tutorials >>>>> â¢ interactive data notebook >>>>> >>>>> >>>>> Code documentation >>>>> ---- >>>>> Documenter complements the GToolkit Examples engine to redefine code documentation. When practicing example-driven development, examples get written as part of the typical development. Once examples exist, they can be quickly put together in a document to form documentation. For example, the linked picture shows the comment of a class containing a visual explanation: >>>>> https://twitter.com/feenkcom/status/973899862482866176 >>>>> >>>>> You can see a live example of documentation by inspecting the following snippet: >>>>> GtDocumenter editorForText: BrToggleExamples comment. >>>>> >>>>> >>>>> Tutorials: >>>>> ---- >>>>> Documenter offers a new experience of writing tutorials for Pharo by enabling the creation and embedding of Epicea change sessions directly in the document. For example, take a look at the following animation: >>>>> https://twitter.com/feenkcom/status/999975333972541440 >>>>> >>>>> The document shows a method on top, and a change preview at the bottom showing both the code and the associated diff to the state from the image. Applying the change updates both the change view (no more diff), and method preview. This speeds up significantly the process of going through a tutorial. Furthermore, given that now the document shows the diff to the current image, the reader can safely explore alternative scenario and come back to the tutorial at any time without losing the overview. >>>>> >>>>> The size of the preview can also be adjusted live: >>>>> https://twitter.com/feenkcom/status/1001152789874167808 >>>>> https://twitter.com/feenkcom/status/1001407762285375490 >>>>> >>>>> You can see a live tutorial by inspecting: >>>>> IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillarâ. >>>>> >>>>> >>>>> Interactive data notebook: >>>>> ---- >>>>> A Documenter document can also be used as an interactive notebook. Internally it essentially acts as a playground: >>>>> â¢ it supports defining variables in code snippets, and >>>>> â¢ the execution of code shows an embedded inspector. >>>>> >>>>> For example: >>>>> https://twitter.com/feenkcom/status/996310432225820672 >>>>> https://twitter.com/feenkcom/status/1002851190475026432 >>>>> >>>>> An example, can be seen by inspecting: >>>>> IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit' / 'doc' / 'gtoolkit' / 'gtoolkit.pillar'. >>>>> >>>>> >>>>> As always, please do let us know what you think. >>>>> >>>>> Enjoy, >>>>> The feenk team >>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> www.feenk.com >>>>> >>>>> "If you can't say why something is relevant, >>>>> it probably isn't." >>>>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "Being happy is a matter of choice." >>> >>> >>> >>> >>> >>> >> >> >> > > -- > www.tudorgirba.com > www.feenk.com > > "Every now and then stop and ask yourself if the war you're fighting is the right one." > > > > -- www.tudorgirba.com www.feenk.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

June 19, 2018

Re: [Pharo-users] Smalltalk Programming Competition

by horrido

I appreciate what you're saying, and certainly the things you want to see funded are worthwhile. However, the goals for my programming competition are quite different, for example: #1 â raise the public profile of Smalltalk across a broad swath of the population in Canada and other countries. Word of mouth about the competition will spread beyond Canada, esp. after the winners of the competition gain some local media coverage. #2 â generate excitement and interest in kids, esp. at the high school level. There's nothing better than a sports-like competition to achieve this. #3 â by generating interest in kids, we seed the next generation of programmers with knowledge and experience in Smalltalk. This is not unlike the way interest in Linux grew from students in colleges and universities throughout recent decades. #4 â convince educators to include Smalltalk in their curriculums. I don't know what programming languages are being taught in high schools, but I know it's not Smalltalk. I tried reaching out to local school boards, but they showed no interest. In colleges and universities, the most commonly taught languages are Python and Java. At least, that's the case in North America, I don't know about Europe. I hope to open their eyes to Smalltalk. This is a decidedly marketing-based approach, something that I don't believe any other programming language has tried. It's a worthwhile experiment, and that's why I hope Smalltalkers everywhere will stand behind it. Offray Vladimir Luna CÃ¡rdenas-2 wrote > H :-), > > > On 16/06/18 18:12, horrido wrote: >> FYI, I am trying to jumpstart a Smalltalk programming competition. Read >> all >> about it here. >> <https://medium.com/@richardeng/smalltalk-programming-competition-2be77cab0e75> >> >> My plan is to use Pharo for this competition, even if it makes companies >> like Cincom and Instantiations unhappy. >> >> Any support this competition can receive would be greatly appreciated. > > I just tweeted about it. > > I'm not into a competition spirit, so I would like to think in other > possibilities to fund Pharo, even in the main goal is not reached (USD $ > 30k). For example, I remember Mozilla thinking in Mozilla Spaces (kind > of hacker/maker spaces for Open Web learning by doing in a community > mindset). Our local hackerspaces cost something like USD $6.5K a year > and it has been a good Pharo Space for almost three years of continuous > activities and several outputs and prototypes as detailed at [1]. I'm > not telling that you should invest in us particularly, but that even > from and alternative perspective that is not related with funding > individuals but communities, the same money that allows only 3 > scholarships of individuals after competing each other, would make 4 or > 5 communities sustainable in the Global South for a year, related with > Pharo and other activities and here we have the advantage of not having > a lot of technical debt with popular languages well spread in all > population, like happens in the Global North. > > [1] > http://mutabit.com/repos.fossil/grafoscopio/doc/tip/Docs/En/success-story.md > > Maybe these ideas could help in some way when combined with yours and > allow you a model for flexible funding, like the one of Indie GoGo, so > instead of a all or nothing funding for the competence, you could have a > modular approach that allow you to fund several Pharospaces across the > world, for each USD 6.5k you get, starting with those located in the > Global South (which can be more potent, more agile and cheaper). > > Just my two pesos. > > Cheers, > > Offray -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

June 19, 2018

Re: [Pharo-users] Smalltalk Programming Competition

by Offray Vladimir Luna CÃ¡rdenas

H :-), On 16/06/18 18:12, horrido wrote: > FYI, I am trying to jumpstart a Smalltalk programming competition. Read all > about it here. > <https://medium.com/@richardeng/smalltalk-programming-competition-2be77cab0e…> > > My plan is to use Pharo for this competition, even if it makes companies > like Cincom and Instantiations unhappy. > > Any support this competition can receive would be greatly appreciated. I just tweeted about it. I'm not into a competition spirit, so I would like to think in other possibilities to fund Pharo, even in the main goal is not reached (USD $ 30k). For example, I remember Mozilla thinking in Mozilla Spaces (kind of hacker/maker spaces for Open Web learning by doing in a community mindset). Our local hackerspaces cost something like USD $6.5K a year and it has been a good Pharo Space for almost three years of continuous activities and several outputs and prototypes as detailed at [1]. I'm not telling that you should invest in us particularly, but that even from and alternative perspective that is not related with funding individuals but communities, the same money that allows only 3 scholarships of individuals after competing each other, would make 4 or 5 communities sustainable in the Global South for a year, related with Pharo and other activities and here we have the advantage of not having a lot of technical debt with popular languages well spread in all population, like happens in the Global North. [1] http://mutabit.com/repos.fossil/grafoscopio/doc/tip/Docs/En/success-story.md Maybe these ideas could help in some way when combined with yours and allow you a model for flexible funding, like the one of Indie GoGo, so instead of a all or nothing funding for the competence, you could have a modular approach that allow you to fund several Pharospaces across the world, for each USD 6.5k you get, starting with those located in the Global South (which can be more potent, more agile and cheaper). Just my two pesos. Cheers, Offray

June 19, 2018

Re: [Pharo-users] Lost in stream

by monty

They still use (binary) StandardFileStreams on Pharo and Squeak. But since it's done through dynamically chosen file stream factory classes (XMLFileReadStreamFactory and XMLFileWriteStreamFactory), it's easy add support for other stream classes. (The GemStone compat .mcz adds factories for GsFile read/write factories, for example). #preferredImplementation selects which implementation to use in the hierarchy when there's more than one supported (#isSupportedImplementation). ___ montyos.wordpress.com > Sent: Monday, June 18, 2018 at 1:34 AM > From: "Sven Van Caekenberghe" <sven(a)stfx.eu> > To: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] Lost in stream > > > > > On 18 Jun 2018, at 02:18, monty <monty2(a)programmer.net> wrote: > > > > Also consider using XMLParser's built-in file reading support: #parseFileNamed:/#onFileNamed:. They work cross platform (Squeak, GS), and handle character decoding. > > Monty, do these (already) work with all the latest changes in Pharo 7, I mean the deprecation of FileStream and subclasses as well as [RW|MultiByte]BinaryOrTextStream for FileReference, File and Zn streams ? > > If not, we should help you. > > Sven >

June 18, 2018