April 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Meanwhile in FogBugz: issue 20000

by Stephane Ducasse

Tx torsten for these kind words. You got quoted :) https://pharoweekly.wordpress.com/2017/04/28/20000-issues-mark-in-fogbugz/ On Thu, Apr 27, 2017 at 5:49 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > > our community today hit the 20000 issues mark in FogBugz. > > https://pharo.fogbugz.com/f/cases/20000 > > And a good change to once again say THANK YOU, especially to the ones who > care most on > > - updating the bug tracker > - fixing issues > - reviewing issues > - integrating issues > - doing also the boring tasks in caring about the bugtracker > - pushing Pharo in the right direction > > Just wow and impressive! Pharo 6 will be another nice milestone in a > lively open source > Smalltalk system that we all wanted to see becoming a reality! > > Thx > T. > > BTW: > The issue 20000 is about clickable URLs in Help Browser. Currently we copy > them to clipboard - as we do > not have web browser support in the default image. I guess it is too late > to push this package into the > image due to the freeze. > > So this slices nonetheless tries to improve the situation by checking if > the unified WebBrowser support package > (which is available since a year [1]) is loaded or not. If it is loaded it > opens a real web browser. > > So when Pharo 6 is released and someone may lament about not being able > for the URLs to really work > we can point him to load the "WebBrowser" package and he should be fine. > > [1] http://lists.pharo.org/pipermail/pharo-dev_lists. > pharo.org/2016-April/120723.html > >

April 28, 2017

Re: [Pharo-dev] IMPORTANT: iceberg home changed

by Esteban Lorenzano

Hi, not really, but we want to promote pharo related stuff with the pharo prefix on the organisations (and those who in someway will fall under our umbrella).. pharo-project -> core pharo pharo-vcs -> iceberg, libgit2 bindings, in the future: an iceberg page, maybe other backends. pharo-graphics -> block/brick and upcoming graphical cool stuff pharo-gtools -> gtools + glamour, etc. pharo-nosql -> voyage family pharo-? -> I donât know, whatever in the future, with the upcoming versions of iceberg + bootstrap, projects like iceberg, gtools, etc. will be âsubtreesâ of pharo-core so is good to have them well organised. of course people are free to name their projects/organisation as they want, but I was trying to figure out a way for *us* :) (and since is very easy to change, we could just reorganise everything under pharo-project if we decide to put everything in just one repository). Esteban > On 28 Apr 2017, at 10:11, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > esteban do we have a naming convention on github? > pharo-xxx? > > Stef > > On Thu, Apr 27, 2017 at 5:51 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > As part of our work for release, I changed the home of Iceberg into his own place: https://github.com/pharo-vcs/iceberg <https://github.com/pharo-vcs/iceberg> > > So, now to install you will need: > > Metacello new > baseline: 'Iceberg'; > repository: 'github://pharo-vcs/iceberg:dev-0.4'; > load. > > I also uploaded a Configuration to the *catalog>http://catalog.pharo.org <http://catalog.pharo.org/>*, so you can load while > doing the transition. >

April 28, 2017

Re: [Pharo-dev] IMPORTANT: iceberg home changed

by Stephane Ducasse

esteban do we have a naming convention on github? pharo-xxx? Stef On Thu, Apr 27, 2017 at 5:51 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > As part of our work for release, I changed the home of Iceberg into his > own place: https://github.com/pharo-vcs/iceberg > > So, now to install you will need: > > Metacello new > baseline: 'Iceberg'; > repository: 'github://pharo-vcs/iceberg:dev-0.4'; > load. > > I also uploaded a Configuration to the *catalog>http://catalog.pharo.org*, > so you can load while > doing the transition. >

April 28, 2017

Re: [Pharo-dev] IMPORTANT: iceberg home changed

by Sean P. DeNigris

EstebanLM wrote >>Currently Iceberg (in its default configuration) can not use SSH keys to connect to github > > thatâs outdated (as the pictures, etc.) :P > you can use ssh and in theory you can also use https (then you will be > asked to provide your credentials) Awesome! I use SSH keys exclusively so that is great news :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/IMPORTANT-iceberg-home-changed-tp4944480p4944642.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 28, 2017

Re: [Pharo-dev] saving an image on windows and opening it on mac problems

by Andrei Chis

Actually if I just execute before saving on Windows the following code I get no error when opening the image on Mac: OmSessionStore allInstancesDo: [ :each | SystemAnnouncer uniqueInstance unsubscribe: each ]. On Thu, Apr 27, 2017 at 9:48 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Loaded slice 19990 and the issues is still there with the latest image+vm. > > On Thu, Apr 27, 2017 at 9:07 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> Hi. >> >> 2017-04-26 15:06 GMT+02:00 Andrei Chis <chisvasileandrei(a)gmail.com>: >> >>> >>> I saw that there are a few issues about images saved on an operating >>> system not working when opened on other operating systems: >>> - https://pharo.fogbugz.com/f/cases/19852/Unable-to-open-ima >>> ge-in-OSX-after-it-has-been-updated-in-Windows >>> - https://pharo.fogbugz.com/f/cases/19869/Infinite-loop-on-m >>> ac-when-opening-an-image-saved-on-windows >>> - https://pharo.fogbugz.com/f/cases/19272/Image-freezes-on-L >>> inux-if-it-was-previously-saved-on-Windows >>> - http://forum.world.st/Image-freezes-on-Linux-if-it-was-pre >>> viously-saved-on-Windows-td4903258.html >>> >> >> Also this can be related: >> https://pharo.fogbugz.com/f/cases/19990/UFFI-not-reset-metho >> d-cache-at-image-startup >> >> Can you reproduce original problems with this slice loaded? (it is not >> integrated yet) >> > >

April 27, 2017

Re: [Pharo-dev] saving an image on windows and opening it on mac problems

by Andrei Chis

Loaded slice 19990 and the issues is still there with the latest image+vm. On Thu, Apr 27, 2017 at 9:07 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi. > > 2017-04-26 15:06 GMT+02:00 Andrei Chis <chisvasileandrei(a)gmail.com>: > >> >> I saw that there are a few issues about images saved on an operating >> system not working when opened on other operating systems: >> - https://pharo.fogbugz.com/f/cases/19852/Unable-to-open-ima >> ge-in-OSX-after-it-has-been-updated-in-Windows >> - https://pharo.fogbugz.com/f/cases/19869/Infinite-loop-on-m >> ac-when-opening-an-image-saved-on-windows >> - https://pharo.fogbugz.com/f/cases/19272/Image-freezes-on-L >> inux-if-it-was-previously-saved-on-Windows >> - http://forum.world.st/Image-freezes-on-Linux-if-it-was-pre >> viously-saved-on-Windows-td4903258.html >> > > Also this can be related: > https://pharo.fogbugz.com/f/cases/19990/UFFI-not-reset- > method-cache-at-image-startup > > Can you reproduce original problems with this slice loaded? (it is not > integrated yet) >

April 27, 2017

Re: [Pharo-dev] OmSessionStore and SnapshotDone event (was: saving an image on windows and opening it on mac problems)

by Denis Kudriashov

I open issue 20004 <https://pharo.fogbugz.com/f/cases/20004/SnapshotDone-should-be-not-announce…>. We need decide what the proper logic 2017-04-27 21:15 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > > 2017-04-27 21:11 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > >> 2017-04-26 17:21 GMT+02:00 Andrei Chis <chisvasileandrei(a)gmail.com>: >> >>> Hi, >>> >>> OmSessionStore registers an action (OmSessionStore>>#store) when the >>> event SnapshotDone is triggered. >>> However this event is triggered immediately when an image is opened >>> after being saved, before the file system was reset. >>> This means that OmSessionStore>>#store is called before the file system >>> is reset. >>> Hence, if you save an image on windows and open it on mac you run into >>> issues as OmSessionStore>>#store performs file operations that will work >>> with a WindowsStore instead of a MacStore. >>> >> >> Maybe we should remove this event at all because subscribing on it is not >> safe. Users should use SessionManager registration mechanizm driven by >> categories and priorities > > > I think SnapshotDone is supposed to be announced after all startup > actions. And here is a bug where it is wrong >

April 27, 2017

Re: [Pharo-dev] OmSessionStore and SnapshotDone event (was: saving an image on windows and opening it on mac problems)

by Denis Kudriashov

2017-04-27 21:11 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > 2017-04-26 17:21 GMT+02:00 Andrei Chis <chisvasileandrei(a)gmail.com>: > >> Hi, >> >> OmSessionStore registers an action (OmSessionStore>>#store) when the >> event SnapshotDone is triggered. >> However this event is triggered immediately when an image is opened after >> being saved, before the file system was reset. >> This means that OmSessionStore>>#store is called before the file system >> is reset. >> Hence, if you save an image on windows and open it on mac you run into >> issues as OmSessionStore>>#store performs file operations that will work >> with a WindowsStore instead of a MacStore. >> > > Maybe we should remove this event at all because subscribing on it is not > safe. Users should use SessionManager registration mechanizm driven by > categories and priorities I think SnapshotDone is supposed to be announced after all startup actions. And here is a bug where it is wrong

April 27, 2017

Re: [Pharo-dev] OmSessionStore and SnapshotDone event (was: saving an image on windows and opening it on mac problems)

by Denis Kudriashov

2017-04-26 17:21 GMT+02:00 Andrei Chis <chisvasileandrei(a)gmail.com>: > Hi, > > OmSessionStore registers an action (OmSessionStore>>#store) when the > event SnapshotDone is triggered. > However this event is triggered immediately when an image is opened after > being saved, before the file system was reset. > This means that OmSessionStore>>#store is called before the file system is > reset. > Hence, if you save an image on windows and open it on mac you run into > issues as OmSessionStore>>#store performs file operations that will work > with a WindowsStore instead of a MacStore. > Maybe we should remove this event at all because subscribing on it is not safe. Users should use SessionManager registration mechanizm driven by categories and priorities

April 27, 2017

Re: [Pharo-dev] saving an image on windows and opening it on mac problems

by Denis Kudriashov

Hi. 2017-04-26 15:06 GMT+02:00 Andrei Chis <chisvasileandrei(a)gmail.com>: > > I saw that there are a few issues about images saved on an operating > system not working when opened on other operating systems: > - https://pharo.fogbugz.com/f/cases/19852/Unable-to-open- > image-in-OSX-after-it-has-been-updated-in-Windows > - https://pharo.fogbugz.com/f/cases/19869/Infinite-loop-on- > mac-when-opening-an-image-saved-on-windows > - https://pharo.fogbugz.com/f/cases/19272/Image-freezes-on- > Linux-if-it-was-previously-saved-on-Windows > - http://forum.world.st/Image-freezes-on-Linux-if-it-was- > previously-saved-on-Windows-td4903258.html > Also this can be related: https://pharo.fogbugz.com/f/cases/19990/UFFI-not-reset-method-cache-at-imag… Can you reproduce original problems with this slice loaded? (it is not integrated yet)

April 27, 2017