Re: [Pharo-dev] let's talk about themes (and GLMBrickThemer)

Hi esteban Next time I have a look at Bloc2 I will check if there is such concept and see how we can package it. Stef Le 2/8/16 à 12:06, Esteban Lorenzano a écrit : On 02 Aug 2016, at 08:59, stepharo > wrote: Hi esteban It looks cool. For the

Re: [Pharo-dev] Odd Commits to Soup Repo

then this is good because esteban told me that it was not some time ago :). Stef Le 2/8/16 à 20:05, monty a écrit : It's worked for me in the past. For example, when I migrated projects from a shared repo to separate repos. But the files don't always disappear immediately. Sent: Tuesday,

Re: [Pharo-dev] Bloc, Bloc 2 and Brick

Le 2/8/16 à 15:47, Ben Coman a écrit : On Tue, Aug 2, 2016 at 6:58 PM, Torsten Bergmann wrote: Hi Stef, from past discussions/threads I know "Bloc" as Pharo's possible future UI, watched the video [1] and have played with the premade image from the CI Server. Also the Brick

Re: [Pharo-dev] Odd Commits to Soup Repo

It's worked for me in the past. For example, when I migrated projects from a shared repo to separate repos. But the files don't always disappear immediately. > Sent: Tuesday, August 02, 2016 at 3:03 AM > From: stepharo > To: pharo-dev@lists.pharo.org > Subject: Re: [Pharo-dev]

Re: [Pharo-dev] Bloc, Bloc 2 and Brick

On Tue, Aug 2, 2016 at 6:58 PM, Torsten Bergmann wrote: > Hi Stef, > > from past discussions/threads I know "Bloc" as Pharo's possible future UI, > watched the video [1] and have played with the premade > image from the CI Server. Also the Brick layer (which is on top of Bloc)

Re: [Pharo-dev] let's talk about themes (and GLMBrickThemer)

Hi, I will take a look at this tomorrow and get back to you. Cheers, Doru > On Aug 2, 2016, at 12:06 PM, Esteban Lorenzano wrote: > > >> On 02 Aug 2016, at 08:59, stepharo wrote: >> >> Hi esteban >> >> It looks cool. For the error could you use a

Re: [Pharo-dev] Bloc, Bloc 2 and Brick

Hi, We are still in exploration mode with respect to design and this is why you see several internal names. We expect to have a clear structure within a couple of weeks, and there will be an announcement on that. In the end, there will be exactly one single Bloc and one single Brick. Cheers,

[Pharo-dev] [pharo-project/pharo-core] 024ef4: 60162

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 024ef4c9ddab9f907611339a771d666b6928b2e3 https://github.com/pharo-project/pharo-core/commit/024ef4c9ddab9f907611339a771d666b6928b2e3 Author: Jenkins Build Server Date:

[Pharo-dev] Bloc, Bloc 2 and Brick

Hi Stef, from past discussions/threads I know "Bloc" as Pharo's possible future UI, watched the video [1] and have played with the premade image from the CI Server. Also the Brick layer (which is on top of Bloc) was announced as a preview once [2]. Now in some of the mails it was mentioned

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60161 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] a37158: 60161

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: a371587568647e0f920cf581b6df8e87660916e0 https://github.com/pharo-project/pharo-core/commit/a371587568647e0f920cf581b6df8e87660916e0 Author: Jenkins Build Server Date:

Re: [Pharo-dev] let's talk about themes (and GLMBrickThemer)

> On 02 Aug 2016, at 08:59, stepharo wrote: > > Hi esteban > > It looks cool. For the error could you use a different one because I cannot > read it. > Else when I tried to use the same way than Setting to manage skins it did not > work > because theming is a lot of

Re: [Pharo-dev] Odd Commits to Soup Repo

On 02/08/2016 09:03, stepharo wrote: > Hi Paul > > It never works with me. Did you check that the file is really not there > after. > Hi, Since I am a little scatterbrained it happen to me all the time to commit in the wrong repo, so I delete those wrong .mcz and it works fine. > Stef > >

Re: [Pharo-dev] Odd Commits to Soup Repo

Hi Paul It never works with me. Did you check that the file is really not there after. Stef Le 28/7/16 à 22:26, Paul DeBruicker a écrit : Sure you can delete mcz from Smalltalkhub. Or at least the Web UI offers a 'Delete .mcz' button, which appears to work. Sign in Navigate to the project