Re: [Pharo-users] Rubric events

This mails arrived here empty. > On 02 Oct 2015, at 08:36, Alain Plantec via Pharo-users > wrote: > > > > >

Re: [Pharo-users] Is RubMethodEditingExample supposed to work?

--- Begin Message --- Hello, I think It was only to show how to use Rubric for text editing. Alain > On 02 Oct 2015, at 08:27, Nicolai Hess wrote: > > > > 2015-10-01 20:52 GMT+02:00 Stephan Eggermont >: > Is that supposed to be able to make changes to methods? > > Ma

Re: [Pharo-users] Rubric events

--- Begin Message --- Hello Miguel, Did you tried to subscribe to RubTextUpdatedInModel through the model of the morph (and not directly the morph) ? Cheers Alain > On 30 Sep 2015, at 16:52, Miguel Campusano wrote: > > Hello, > I'm working on modifying the styling of text by using RubTextSegme

Re: [Pharo-users] Is RubMethodEditingExample supposed to work?

2015-10-01 20:52 GMT+02:00 Stephan Eggermont : > Is that supposed to be able to make changes to methods? > Maybe it was supposed to work but isn't finished? There is another example RubPluggableTextMorphExample That one can save changes. > > Stephan > > >

[Pharo-users] Is RubMethodEditingExample supposed to work?

Is that supposed to be able to make changes to methods? Stephan

Re: [Pharo-users] Pillar for 30 gone the way of the dodo on the CI

Stephan Eggermont writes: > On 01-10-15 10:05, Peter Uhnak wrote: >> In Jenkins you specify configuration matrix (versions of pharo versus type >> (development, stable, ...)).. So it will run development for all versions, >> even pharo 30 (which is now permanently broken) > > Shouldn't #'devel

Re: [Pharo-users] Pillar for 30 gone the way of the dodo on the CI

You can exclude some of the combinations from matrix. E.g. exclude build for 30 & development. > On 01 Oct 2015, at 14:04, Stephan Eggermont wrote: > > On 01-10-15 10:05, Peter Uhnak wrote: >> In Jenkins you specify configuration matrix (versions of pharo versus type >> (development, stable,

Re: [Pharo-users] Pillar for 30 gone the way of the dodo on the CI

On 01-10-15 10:05, Peter Uhnak wrote: In Jenkins you specify configuration matrix (versions of pharo versus type (development, stable, ...)).. So it will run development for all versions, even pharo 30 (which is now permanently broken) Shouldn't #'development' for Pharo3.x then point to #'sta

Re: [Pharo-users] Pillar for 30 gone the way of the dodo on the CI

p...@highoctane.be writes: > Which is a pain as when I copy/paste a shell script full of those, I won't > do that. I agree that's a pain. But you have to do it. > Is this also doing the same thing in blocks like: > > [[[label=.bashrc|caption=Ajouts à .bashrc|language=bash > > ${SOMEVAR:-} >

Re: [Pharo-users] Pillar for 30 gone the way of the dodo on the CI

p...@highoctane.be writes: > Downloaded the book-skeleton, patched the download script so that it gets > the centos things right and the Pharo4VM. > > Now, changes in Pillar made my books unsuable, namely the introduction of > things like this: > > ${tag:parameter=value|parameter2=value2}$ > > >

Re: [Pharo-users] Pillar for 30 gone the way of the dodo on the CI

p...@highoctane.be writes: > Ok, where? in Pharo 3, open the Catalog Browser, choose Pillar, and click "Install Stable Version". You will get 2 warnings you can safely ignore. You can run the unit tests to check everything works fine (Pillar contains 2198 unit tests, in this version, covering 9

Re: [Pharo-users] Pillar for 30 gone the way of the dodo on the CI

> On 01 Oct 2015, at 10:07, Marcus Denker wrote: > > Is CI an archive? > What I mean: it seems to me not possible to keep all CI build alive “forever” as a CI server build. Shouldn’t we separate “archival of builds” from “active ci”? For Pharo itself we do that, as we do not have the manpow

Re: [Pharo-users] Pillar for 30 gone the way of the dodo on the CI

Is CI an archive? > On 01 Oct 2015, at 10:05, Peter Uhnak wrote: > > In Jenkins you specify configuration matrix (versions of pharo versus type > (development, stable, ...)).. So it will run development for all versions, > even pharo 30 (which is now permanently broken) > From: Stephan Eggerm

Re: [Pharo-users] Pillar for 30 gone the way of the dodo on the CI

In Jenkins you specify configuration matrix (versions of pharo versus type (development, stable, ...)).. So it will run development for all versions, even pharo 30 (which is now permanently broken) -Original Message- From: "Stephan Eggermont" Sent: ‎10/‎1/‎2015 9:47 AM To: "pharo-users@

Re: [Pharo-users] Pillar for 30 gone the way of the dodo on the CI

On 01-10-15 09:41, Stephan Eggermont wrote: On 30-09-15 19:57, Ferlicot D. Cyril wrote: We removed the Pillar job for Pharo 3 because we introduced an new feature not backward compatible. Why is that a reason to remove the build? You have a configuration, don't you? I would suggest: move to

Re: [Pharo-users] Pillar for 30 gone the way of the dodo on the CI

On 30-09-15 19:57, Ferlicot D. Cyril wrote: We removed the Pillar job for Pharo 3 because we introduced an new feature not backward compatible. Why is that a reason to remove the build? You have a configuration, don't you? Stephan