- Pharo-users - lists.pharo.org

Re: [Pharo-users] installation of packages on 6.1

by Baveco, Hans

Thanks Ben! I created a github account, installed git and git bash, created SSH keys, added keys to my github account, and changed the settings in Pharo to use these keys, and finally was able to install the packages I wanted to try. (roassal2 still not installing though). Question remains, is this really the only way to get these packages that live on github into the image? I had no plans to work with git/github, but was now forced to spent quite some time on it.... Cheers, Hans From: Ben Coman <btc(a)openinworld.com> Sent: maandag 9 april 2018 22:54 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] installation of packages on 6.1 On 6 April 2018 at 00:02, Baveco, Hans <hans.baveco(a)wur.nl<mailto:hans.baveco@wur.nl>> wrote: Trying to install Territorial the installation got stuck on the installation of Roassal2 1.35, with error âLGitObjectNotInitializedâ Transcript says: âProject: Roassal2 1.35 I got an error while cloning: There was an authentication error while trying to execute the operation: error authenticating: failed connecting agent. This happens usually because you didn't provide a valid set of credentials. You may fix this problem in different ways: 1. adding your keys to ssh-agent, executing ssh-add ~/.ssh/id_rsa in your command line. 2. adding your keys in settings (open settings browser search for "Use custom SSH keys" and add your public and private keys). 3. using HTTPS instead SSH (Just use an url in the form HTTPS://etc.git) I will try to clone the HTTPS variant.â I have encountered this several times before, for different packages (on windows 7, pharo 6.1 (Image: Pharo6.0 [Latest update: #60540])) and have no idea how to deal with this. Any suggestions? Hans On Windows you need to use option 2. World Menu > Settings > etc... cheers -ben

April 11, 2018

Re: [Pharo-users] Frozen at start up

by tesonep＠gmail.com

Hi Sean, it is the exactly the same behavior. Cheers. On Tue, Apr 10, 2018 at 11:38 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > HilaireFernandes wrote > > Any idea? > > Can you try starting with `--no-default-preferences` and see if it's the > same? > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > -- Pablo Tesone. tesonep(a)gmail.com

April 11, 2018

Re: "News" section of the website down

by orsayman

Hum, I'm sorry but it still doesn't work this morning (from home). -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 11, 2018

Re: [Pharo-users] Frozen at start up

by Sean P. DeNigris

HilaireFernandes wrote > Any idea? Can you try starting with `--no-default-preferences` and see if it's the same? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 10, 2018

Re: [Pharo-users] GemStone/S on Docker?

by Jupiter Jones

Iâve copied this to the GemStone list to continue the discussion. > I wouldn't. The excellent work of Norbert was later inspired/continuated/extended officially by GemStone under a much bigger project called GsDevKit [1] > > [1] https://github.com/GsDevKit/GsDevKit_home <https://github.com/GsDevKit/GsDevKit_home> +1 GsDevKit - itâs excellent for use in both development and deployment. Thereâs also an ansible project [1] which may offer some guidance. If you were planning to build containers for GemStone, there are a bunch of possible roles a single host might play in larger systems, but as a minimum: 1. Stone - where the repository (image) is physically managed. Typically only one per deployment (or more for warm failover) 2. Gem - where the VMâs run your application or services. Instances scale with your application. 3. Shared Page Cache - essentially shared memory access to the image that can be deployed in many ways to turn your applications. Thereâs a rundown on connecting distributed systems in the GS System Admin Guide [2]. There are likely many other roles right down to transaction logs and repository extents (the physical files on disc where your image is persisted), it just depends on how far you want to go with the flexibility of the docker containers. This said, GsDevKit will setup the above three roles on a single host which will suit development and deployment of any small application. Cheers, J [1] https://github.com/GsDevKit/GsDevKit_ansible <https://github.com/GsDevKit/GsDevKit_ansible> [2] https://downloads.gemtalksystems.com/docs/GemStone64/3.4.x/GS64-SysAdminGui… <https://downloads.gemtalksystems.com/docs/GemStone64/3.4.x/GS64-SysAdminGui…>

April 10, 2018

Re: [Pharo-users] Frozen at start up

by Hilaire

Thanks I will dig on that direction. By the way, DrGeo code at SH is obsolete. Pharo7 port is at http://dev.drgeo.eu, more precisely https://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/files/head:/src/ I should update the information page. Thanks for the tips Le 10/04/2018 Ã 21:36, tesonep(a)gmail.com a Ã©critÂ : > Hi Hilaire, > Â I have seen the same problem when trying to reproduce the error with > FreeTypeFonts. > I can see that the problem arise because there is a startUp of a class > that is calling the #splash method. This method uses Delay. > As this is run during the startup of the classes, it runs with the > higher priority. Taking precedence over the Delay scheduling process. > In Pharo 7 the startup of the session runs in higher priority so it > cannot be interrupted. > This is done in that way to fix some problems during the > initialization of the session (Now, I could not remember what was fixed). > I believe this actions should be executed as a deferred action. > > Also I have found a problem with the requirement of the UIThemeWatery > class, I have fixed it extending UITheme with a new subclass (same > behavior) so the code can be loaded. > > If you want I can help you to port DrGeo to Pharo7. -- Dr. Geo http://drgeo.eu

April 10, 2018

Re: [Pharo-users] Frozen at start up

by tesonep＠gmail.com

Hi Hilaire, I have seen the same problem when trying to reproduce the error with FreeTypeFonts. I can see that the problem arise because there is a startUp of a class that is calling the #splash method. This method uses Delay. As this is run during the startup of the classes, it runs with the higher priority. Taking precedence over the Delay scheduling process. In Pharo 7 the startup of the session runs in higher priority so it cannot be interrupted. This is done in that way to fix some problems during the initialization of the session (Now, I could not remember what was fixed). I believe this actions should be executed as a deferred action. Also I have found a problem with the requirement of the UIThemeWatery class, I have fixed it extending UITheme with a new subclass (same behavior) so the code can be loaded. If you want I can help you to port DrGeo to Pharo7. Cheers, Pablo On Tue, Apr 10, 2018 at 8:32 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Hi, > I have this strange situation with a DrGeo built against P7, where DrGeo > starts, but then get frozen with this message. > Strangely the start seems not to have completed as the UI messages are not > localized in French. > > What is strange, on my PC where I built the app, this problem does not > occur. > > Any idea? > > Thanks > > Hilaire > > > -- > Dr. Geo > http://drgeo.eu > -- Pablo Tesone. tesonep(a)gmail.com

April 10, 2018

Frozen at start up

by Hilaire

Hi, I have this strange situation with a DrGeo built against P7, where DrGeo starts, but then get frozen with this message. Strangely the start seems not to have completed as the UI messages are not localized in French. What is strange, on my PC where I built the app, this problem does not occur. Any idea? Thanks Hilaire -- Dr. Geo http://drgeo.eu

April 10, 2018

Re: [Pharo-users] FreeFontProvider unload [was] Re: Black screen on Mac OSX

by Hilaire

Hi Pablo, DrGeo is shipped with two fonts, depending on the system locale at DrGeo start up, one or another one is used. So the cache need to be reset at. May be there is better to handle that, it worked pretty well until now. Hilaire Le 10/04/2018 Ã 10:53, tesonep(a)gmail.com a Ã©critÂ : > Hi Hilaire, > Â thanks for spliting the subject, I have missed the discussion in the > other thread. > > The #unload message should be used to clean up the system in case the > class is unload from the system. > That's why the logic has been move to the #resetCurrent method that is > called during the shutdown of the image. > > However, the question is not if the method should be included in a > compatibility package or if the users should send #resetCurrent. > The problem is why it is needed to clean up the font cache, it should > not be needed. The only scenario I think is if you want to replace a > font (in the Pharo world a Face, because there is a font per each > combination of face and point size) named exactly the same with > another one. I think this is no normal behavior. > > I will try to see why this is needed when loading DrGeo in Pharo7 and > fix the FT implementation not to need it. > Maybe it is hiding a bigger issue. > -- Dr. Geo http://drgeo.eu

April 10, 2018

Re: [Pharo-users] Iceberg: whom to email directly?

by Herbert VojÄÃk

Ben Coman wrote: > > > On 10 April 2018 at 23:46, Herbert VojÄÃk <herby(a)mailbox.sk > <mailto:herby@mailbox.sk>> wrote: > > I have a strict "no github account" policy. > > Whom/where should I post to report issues? > > Thanks, Herby > > > https://pharo.fogbugz.com Ironically, I ask because of https://pharo.fogbugz.com/f/cases/21684/Integrate-Iceberg-0-7#BugEvent.2001…, but, thanks. Maybe the issue in question is actually reposted / tracked. > cheers -ben

April 10, 2018