- Pharo-users - lists.pharo.org

Re: [Pharo-users] Updated Pharo Days Schedule

by Ben Coman

ditto. Also helps spread the "word" wider. On Wed, Jan 28, 2015 at 1:19 AM, Andy Burnett < andy.burnett(a)knowinnovation.com> wrote: > Any chance that the presentations will be video recorded? I can't attend > but I would love to watch. > > Cheers > Andy > > > >

Jan. 27, 2015

Updated Pharo Days Schedule

by Andy Burnett

Any chance that the presentations will be video recorded? I can't attend but I would love to watch. Cheers Andy

Jan. 27, 2015

Re: [Pharo-users] Making the halo around windows preview more contrasted

by Offray Vladimir Luna CÃ¡rdenas

Thanks Nicolai, I used an approach suggested by Merwan Ouddane in a private mail that consisted in changing "UITheme>>taskListFillStyleFor:" inside PolymorphWidgets Themes package changing the GradientFillStyle This is my result: =============================================== taskListFillStyleFor: aTasklist | aColor result | aColor := aTasklist color. result := GradientFillStyle ramp: { 0.0->aColor whiter whiter. 0.2->aColor muchDarker. 0.8->aColor darker. 1.0->aColor muchDarker}. ^ result origin: aTasklist topLeft; direction: 0 @ aTasklist height; radial: false; yourself. =============================================== Which is easier and more pleasant to my eyes Cheers, Offray El 26/01/15 a las 05:34, Nicolai Hess escribiÃ³: > 2015-01-07 18:20 GMT+01:00 Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net > <mailto:offray@riseup.net>>: > > Hi all, > > As usual, when I put the mouse over the name of a window, a small preview > appears with a grey allow with the full name of the window, but letters are > white surrounded by a pale grey making the full name really difficult to > read. There is any way to increase the contrast there between font and > background? > > > This is defined in UIThemeWatery>>#newTaskbarThumbnailIn: aThemedMorph for: aWindow > It looks better with the WateryTheme, because it uses a darker background. > You can: > - define your own theme as a Subclass of Pharo3Theme and overwrite this method > - change the background(color) of the world. > > > Thanks, > > Offray > >

Jan. 27, 2015

Updated Pharo Days Schedule

by Sven Van Caekenberghe

Hi, We updated the schedule (programme) for the Pharo Days, adding names to the talks, shifting some timings and other details a bit. http://pharodays2015.pharo.org We're happy that about 75 people registered. It will be fun and intense. Sven

Jan. 27, 2015

Re: [Pharo-users] SPEC and Athens

by Mark Rizun

Hi, Not sure if it helps but for morphs you have next "transformation to model": | morph | morph := CalendarMorph on: Date today. ^ morph asSpecAdapter Please read details here: http://spec.st/docs/insert-morph/ Mark 2015-01-27 16:57 GMT+01:00 Sebastian Heidbrink <sheidev(a)yahoo.de>: > Hi! > > Okay so I am currently trying Spec out and I need some advice. > > Which is the Model to use for a ASVGMorph ("AthensSvgMorph")? > > Is there an example availabel somewhere? > > Thanks > Sebastian > >

Jan. 27, 2015

SPEC and Athens

by Sebastian Heidbrink

Hi! Okay so I am currently trying Spec out and I need some advice. Which is the Model to use for a ASVGMorph ("AthensSvgMorph")? Is there an example availabel somewhere? Thanks Sebastian

Jan. 27, 2015

Re: [Pharo-users] Hijacking a Configuration for loading a Github Baseline

by Dale Henrichs

On 1/27/15 7:10 AM, Thierry Goubier wrote: > Hi Dale, > > The wildcards on tags, are they available on branch names as well? The wildcards are only applied to tags ... branch names are not expected to look like version numbers with `.` and `-` separated "possibly numeric" fields. > > I wonder about the choice for ? and *, because: > > - In RE(s), ? is 0 or 1 occurence, * is 0 or any number of occurences. > - In shells (bash?), ? is any one character, * is 0 or any number of > characters. > > i.e. ? matches less than * in both cases. In Metacello, it is the > reverse: 1.0.? matches more labels than 1.0.* I based my sytax on String>>match:. String>>match: uses `*` for "any sequence of characters" and `#` for "any character" which is different that RE and shell matching syntax ... `?` was unused so I picked it for "match this and subsequent fields". I'm open to suggestions for alternatives to the `?`:) Dale

Jan. 27, 2015

Re: [Pharo-users] Hijacking a Configuration for loading a Github Baseline

by kilon alios

No I have not used git tags so far, so I am not familiar with them. But I will keep in mind, I am considering not having versions at all, I find it a curious concept. Dale there is one thing I wanted to ask you , would it possible put in my github repo installation instructions for installing prerequisites ? For example I may use Thierry's SmaCC which I currently study to figure out how it works. I could add that to my ConfigurationOfEphestos that I have saved to Meta Repo of Pharo 4. But I dont want to touch that repo, ideally I would like to do this from the BaselineOfEphestos which is stored in my Ephestos github repo. Is that possible ? Can the baseline handle installation of dependencies and trigger other configurations ? Or is that a job only for Configurations ? I want not to have to maintain also meta repo 4, I just want to only to do all things in my github repo. On Tue, Jan 27, 2015 at 4:57 PM, Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > Kilon, > > One more point that you might find useful ... If you use tags (i.e., > v1.0.0, v1.0.1, v1.1.0), you can specify tag wildcards in the branch field > of the github repository description. > > Using Thierry's example the following resolves the latest commit on the > master branch (bleeding edge): > > github://ThierryGoubier/SmaCC:master > > Using a tag name, you can match the tagged commit: > > github://ThierryGoubier/SmaCC:v1.0.0 > github://ThierryGoubier/SmaCC:v1.1.0 > > Using a tag wildcard you can specify the latest tag 1.0.*: > > github://ThierryGoubier/SmaCC:v1.0.* > > which matches v1.0.1, v1.0.2, whichever is latest, but not v1.0.2.1. > > To match the latest tag in the 1.0 family use 1.0.?: > > github://ThierryGoubier/SmaCC:v1.0.? > > which matches v1.0.1, v1.0.2 and v1.0.2.1. > > There are more examples here[1]. > > This feature was introduced in Metacello 1.0.0-beta.32.16[2]. > > Dale > > [1] > https://github.com/dalehenrich/metacello-work/issues/277#issuecomment-58970… > [2] > https://github.com/dalehenrich/metacello-work/issues?q=milestone%3A1.0.0-be… > > > On 1/27/15 1:52 AM, kilon alios wrote: > > beautiful it worked like a charm following your instructions , I now can > brake my project to smaller ones, each one with each own github repo and > use Baselines to load each one and still allow the user to load my Project > in one single click from Configuration Browser. Love it how Pharo make this > all this so easy, with python it was a nightmare. Brilliant just Brilliant > ! :) > > On Tue, Jan 27, 2015 at 11:19 AM, Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: > >> Hi Kilon, >> >> a simple way to do that is to change your configuration so that it uses >> the baseline in your github. The SmaCC configuration for Pharo 4.0 is >> written in this way for the stable version. >> >> version204: spec >> <version: '2.0.4' imports: #('2.0-baseline')> >> spec >> for: #'pharo4.x' >> do: [ >> spec >> blessing: #stable; >> author: 'ThierryGoubier'; >> description: 'SmaCC Smalltalk Compiler Compiler for Pharo >> 4.0'. >> spec >> baseline: 'SmaCC' with: [ spec repository: >> 'github://ThierryGoubier/SmaCC:master' ]; >> import: 'SmaCC' ] >> >> Thierry >> >> >> >> 2015-01-27 10:08 GMT+01:00 kilon alios <kilon.alios(a)gmail.com>: >> >>> So I have a Configuration in the Meta repo of pharo 4 and 3 that loads >>> the latest version of my project Ephestos. >>> >>> However I have moved my development to github since I am very happy >>> with the workflow and since I discovered loading github repos via a >>> baseline I have little use for smalltalkhub. >>> >>> So my plan is this, keep the configuration in the meta repo so people >>> and me can install my project easily with one click via the wonderful >>> simple configuration browser , but I dont want anymore to load any versions >>> with it. Instead I want to tell the configuration "load the github >>> baseline" which means it will fetch the code from my github account master >>> branch which is the stable branch anyway (and the only branch so far) . >>> >>> That will allow me to never have to update that configuration again >>> since it will just load the latest code from github repo. >>> >>> The question is how to do this the easiest and cleanest way possible ? >>> >> >> > >

Jan. 27, 2015

Re: [Pharo-users] Hijacking a Configuration for loading a Github Baseline

by Thierry Goubier

Hi Dale, The wildcards on tags, are they available on branch names as well? I wonder about the choice for ? and *, because: - In RE(s), ? is 0 or 1 occurence, * is 0 or any number of occurences. - In shells (bash?), ? is any one character, * is 0 or any number of characters. i.e. ? matches less than * in both cases. In Metacello, it is the reverse: 1.0.? matches more labels than 1.0.* Thierry 2015-01-27 15:57 GMT+01:00 Dale Henrichs <dale.henrichs(a)gemtalksystems.com>: > Kilon, > > One more point that you might find useful ... If you use tags (i.e., > v1.0.0, v1.0.1, v1.1.0), you can specify tag wildcards in the branch field > of the github repository description. > > Using Thierry's example the following resolves the latest commit on the > master branch (bleeding edge): > > github://ThierryGoubier/SmaCC:master > > Using a tag name, you can match the tagged commit: > > github://ThierryGoubier/SmaCC:v1.0.0 > github://ThierryGoubier/SmaCC:v1.1.0 > > Using a tag wildcard you can specify the latest tag 1.0.*: > > github://ThierryGoubier/SmaCC:v1.0.* > > which matches v1.0.1, v1.0.2, whichever is latest, but not v1.0.2.1. > > To match the latest tag in the 1.0 family use 1.0.?: > > github://ThierryGoubier/SmaCC:v1.0.? > > which matches v1.0.1, v1.0.2 and v1.0.2.1. > > There are more examples here[1]. > > This feature was introduced in Metacello 1.0.0-beta.32.16[2]. > > Dale > > [1] > https://github.com/dalehenrich/metacello-work/issues/277#issuecomment-58970… > [2] > https://github.com/dalehenrich/metacello-work/issues?q=milestone%3A1.0.0-be… > > > On 1/27/15 1:52 AM, kilon alios wrote: > > beautiful it worked like a charm following your instructions , I now can > brake my project to smaller ones, each one with each own github repo and > use Baselines to load each one and still allow the user to load my Project > in one single click from Configuration Browser. Love it how Pharo make this > all this so easy, with python it was a nightmare. Brilliant just Brilliant > ! :) > > On Tue, Jan 27, 2015 at 11:19 AM, Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: > >> Hi Kilon, >> >> a simple way to do that is to change your configuration so that it uses >> the baseline in your github. The SmaCC configuration for Pharo 4.0 is >> written in this way for the stable version. >> >> version204: spec >> <version: '2.0.4' imports: #('2.0-baseline')> >> spec >> for: #'pharo4.x' >> do: [ >> spec >> blessing: #stable; >> author: 'ThierryGoubier'; >> description: 'SmaCC Smalltalk Compiler Compiler for Pharo >> 4.0'. >> spec >> baseline: 'SmaCC' with: [ spec repository: >> 'github://ThierryGoubier/SmaCC:master' ]; >> import: 'SmaCC' ] >> >> Thierry >> >> >> >> 2015-01-27 10:08 GMT+01:00 kilon alios <kilon.alios(a)gmail.com>: >> >>> So I have a Configuration in the Meta repo of pharo 4 and 3 that loads >>> the latest version of my project Ephestos. >>> >>> However I have moved my development to github since I am very happy >>> with the workflow and since I discovered loading github repos via a >>> baseline I have little use for smalltalkhub. >>> >>> So my plan is this, keep the configuration in the meta repo so people >>> and me can install my project easily with one click via the wonderful >>> simple configuration browser , but I dont want anymore to load any versions >>> with it. Instead I want to tell the configuration "load the github >>> baseline" which means it will fetch the code from my github account master >>> branch which is the stable branch anyway (and the only branch so far) . >>> >>> That will allow me to never have to update that configuration again >>> since it will just load the latest code from github repo. >>> >>> The question is how to do this the easiest and cleanest way possible ? >>> >> >> > >

Jan. 27, 2015

Re: [Pharo-users] Hijacking a Configuration for loading a Github Baseline

by Dale Henrichs

Kilon, One more point that you might find useful ... If you use tags (i.e., v1.0.0, v1.0.1, v1.1.0), you can specify tag wildcards in the branch field of the github repository description. Using Thierry's example the following resolves the latest commit on the master branch (bleeding edge): github://ThierryGoubier/SmaCC:master Using a tag name, you can match the tagged commit: github://ThierryGoubier/SmaCC:v1.0.0 github://ThierryGoubier/SmaCC:v1.1.0 Using a tag wildcard you can specify the latest tag 1.0.*: github://ThierryGoubier/SmaCC:v1.0.* which matches v1.0.1, v1.0.2, whichever is latest, but not v1.0.2.1. To match the latest tag in the 1.0 family use 1.0.?: github://ThierryGoubier/SmaCC:v1.0.? which matches v1.0.1, v1.0.2 and v1.0.2.1. There are more examples here[1]. This feature was introduced in Metacello 1.0.0-beta.32.16[2]. Dale [1] https://github.com/dalehenrich/metacello-work/issues/277#issuecomment-58970… [2] https://github.com/dalehenrich/metacello-work/issues?q=milestone%3A1.0.0-be… On 1/27/15 1:52 AM, kilon alios wrote: > beautiful it worked like a charm following your instructions , I now > can brake my project to smaller ones, each one with each own github > repo and use Baselines to load each one and still allow the user to > load my Project in one single click from Configuration Browser. Love > it how Pharo make this all this so easy, with python it was a > nightmare. Brilliant just Brilliant ! :) > > On Tue, Jan 27, 2015 at 11:19 AM, Thierry Goubier > <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: > > Hi Kilon, > > a simple way to do that is to change your configuration so that it > uses the baseline in your github. The SmaCC configuration for > Pharo 4.0 is written in this way for the stable version. > > version204: spec > <version: '2.0.4' imports: #('2.0-baseline')> > spec > for: #'pharo4.x' > do: [ > spec > blessing: #stable; > author: 'ThierryGoubier'; > description: 'SmaCC Smalltalk Compiler Compiler > for Pharo 4.0'. > spec > baseline: 'SmaCC' with: [ spec repository: > 'github://ThierryGoubier/SmaCC:master' ]; > import: 'SmaCC' ] > > Thierry > > > > 2015-01-27 10:08 GMT+01:00 kilon alios <kilon.alios(a)gmail.com > <mailto:kilon.alios@gmail.com>>: > > So I have a Configuration in the Meta repo of pharo 4 and 3 > that loads the latest version of my project Ephestos. > > However I have moved my development to github since I am very > happy with the workflow and since I discovered loading github > repos via a baseline I have little use for smalltalkhub. > > So my plan is this, keep the configuration in the meta repo so > people and me can install my project easily with one click via > the wonderful simple configuration browser , but I dont want > anymore to load any versions with it. Instead I want to tell > the configuration "load the github baseline" which means it > will fetch the code from my github account master branch which > is the stable branch anyway (and the only branch so far) . > > That will allow me to never have to update that configuration > again since it will just load the latest code from github repo. > The question is how to do this the easiest and cleanest way > possible ? > > >

Jan. 27, 2015