- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Moving to GitHub

by kilon alios

Great thats all I needed thanks Î£ÏÎ¹Ï 6 ÎÏÎ³ 2014 1:00 Ï.Î¼., Î¿ ÏÏÎ®ÏÏÎ·Ï "Dale Henrichs" < dale.henrichs(a)gemtalksystems.com> ÎÎ³ÏÎ±ÏÎµ: > Personally I think that the CofngurationOf is best used as a tag. You > *can* specify any one of branch/SHA/tag in a ConfigurationOf ... > > So you can just reference the name of the branch instead of the SHA and > you'll load the latest commit on that branch ... > > Dale > > > > > On Tue, Aug 5, 2014 at 2:08 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > >> looks very interesting but I see you pull from a specific git commit , >> what if I wanted to pull from latest commit ? >> >> >> >> On Tue, Aug 5, 2014 at 7:59 PM, Dale Henrichs < >> dale.henrichs(a)gemtalksystems.com> wrote: >> >>> Hey Uko, >>> >>> I guess I wasn't clear;( >>> >>> What is not needed when using git are the version methods with the >>> painstaking records of the mcz version associated with each file ... >>> >>> A baseline is created by subclassing BaselineOf and adding a single >>> baseline: method that contains the package/project dependencies. This >>> BaselineOfXXX is saved directly in the repository along with the packages. >>> >>> You can poke around in my External project on GitHub[1] to see more >>> detail. >>> >>> Dale >>> >>> [1] https://github.com/dalehenrich/external/tree/master/repository >>> >>> >>> On Tue, Aug 5, 2014 at 8:31 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >>> wrote: >>> >>>> Hi Dale, >>>> >>>> I wonât agree that you donât need configuration. For me the main >>>> purpose of configuration is defining dependencies. And as far as I know we >>>> donât have any other alternative. >>>> >>>> Uko >>>> >>>> On 05 Aug 2014, at 17:21, Dale Henrichs < >>>> dale.henrichs(a)gemtalksystems.com> wrote: >>>> >>>> Kilon, >>>> >>>> When working with git/github, you really don't need a configuration >>>> anymore ... the configuration functions more like tag than anything else. >>>> >>>> For day to day operations with git/github you only need a baseline[1]. >>>> The baseline just describes the package relationships and of course git >>>> manages the versions of the packages: >>>> >>>> baseline: spec >>>> <baseline> >>>> spec for: #common do: [ >>>> spec configuration: 'Seaside30' with: [ >>>> spec >>>> version: #stable; >>>> repository: 'http://www.squeaksource.com/MetacelloRepository' >>>> ]. >>>> spec >>>> package: 'Sample-Core'with: [ >>>> spec requires: 'Seaside30' ]; >>>> package: 'Sample-Tests' with: [ >>>> spec requires: 'Sample-Core' ]]. >>>> >>>> but there is no longer any need to track the version numbers of the >>>> individual mcz file. >>>> >>>> To load from a repository using a baseline you do the following: >>>> >>>> Metacello new >>>> baseline: 'External'; >>>> repository: 'github://dalehenrich/external:master/repository'; >>>> load. >>>> >>>> This is very similar to using #bleedingEdge,but a lot safer, since >>>> presumably you are using travis-ci to run tests before anything gets merged >>>> into your master branch and of course all of the packages are versioned >>>> together. >>>> >>>> To refresh the version from the master branch you do the following: >>>> >>>> Metacello new >>>> baseline: 'External'; >>>> repository: 'github://dalehenrich/external:master/repository'; >>>> get. >>>> Metacello new >>>> baseline: 'External'; >>>> repository: 'github://dalehenrich/external:master/repository'; >>>> load. >>>> >>>> This is admittedly a bit awkward, but there has been a couple year lag >>>> between the time I did the basic implementation in support of git/github >>>> and the time that folks are finally becoming interested in actually using >>>> it:) So I have focussed on functionality instead or prettiness ... I will >>>> eventually get to the point where you can do:) >>>> >>>> Metacello new >>>> baseline: 'External'; >>>> repository: 'github://dalehenrich/external:master/repository'; >>>> get; >>>> load. >>>> >>>> If you use a configuration, then the version method for the >>>> configuration would look like the following: >>>> >>>> version0900: spec >>>> <version: '0.9.0'> >>>> spec >>>> for: #'common' >>>> do: [ >>>> spec blessing: #'development'. >>>> spec description: 'initial work: first commit on custom >>>> branch'. >>>> spec author: 'dkh'. >>>> spec timestamp: '5/4/2012 14:16'. >>>> spec >>>> baseline: 'External' >>>> with: [ spec repository: ' >>>> github://dalehenrich/external:1ac58502ade7814e1590f71d615cca434b1a4fd5/repository' >>>> ] ] >>>> >>>> So version 0.9.0 is simply a tag for a particular commit ... but within >>>> the Metacello eco-system this approach can be useful. >>>> >>>> Dale >>>> >>>> [1] >>>> https://github.com/dalehenrich/metacello-work/blob/master/docs/GettingStart… >>>> >>>> >>>> On Mon, Aug 4, 2014 at 2:48 AM, kilon alios <kilon.alios(a)gmail.com> >>>> wrote: >>>> >>>>> Well lately I have been questioning the need for configurations . I am >>>>> considering doing only the second port of your blog post. Ask github for >>>>> the latest release of my project , download it, unzip it and point pharo to >>>>> the unziped directory. Then pharo can periodocally keep probing github to >>>>> see if there is a new release and prompt the user for an update. All that >>>>> with a single click from the user or even automagically. But I have to >>>>> figure out how to do that with Pharo first :) >>>>> >>>>> >>>>> On Mon, Aug 4, 2014 at 12:23 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >>>>> wrote: >>>>> >>>>>> You donât have to. Just keep your configuration (here is a guide how >>>>>> to do it >>>>>> http://sleepycoders.blogspot.ch/2014/04/how-to-distribute-your-github-pharo…) >>>>>> on some monticello repo, and assemble your image on CI. Yes, if someone >>>>>> wantâs to modify your project they have to use git, but as far as I know, >>>>>> Pharo is slowly moving git way anyway :) >>>>>> >>>>>> Cheers. >>>>>> Uko >>>>>> >>>>>> On 04 Aug 2014, at 11:17, kilon alios <kilon.alios(a)gmail.com> wrote: >>>>>> >>>>>> yeah I will also move my latest project to github. I am already more >>>>>> active with github than I am in SThub anyway. The one thing that stopped me >>>>>> so far is that I don't want to force people to install git to get the >>>>>> latest version of my project. SThub is great for this. >>>>>> >>>>>> >>>>>> On Mon, Aug 4, 2014 at 12:03 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >>>>>> wrote: >>>>>> >>>>>>> Well, thankfully I keep all my latest projects on github, and I have >>>>>>> configurations of them in the image. But CI is not working and anyway itâs >>>>>>> a strange situation. Is there any other service where I can keep my >>>>>>> configurations? Because thatâs the only thing I version with monticello are >>>>>>> configurations as I want to use gofer to load my projects. And here >>>>>>> reliability is much more important then other features. >>>>>>> >>>>>>> Uko >>>>>>> >>>>>>> >>>>>>> On 04 Aug 2014, at 10:59, kilon alios <kilon.alios(a)gmail.com> wrote: >>>>>>> >>>>>>> oh boy thats looks nasty bug, hope its not permanent. >>>>>>> >>>>>>> >>>>>>> On Mon, Aug 4, 2014 at 11:44 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com >>>>>>> > wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I was on vacation last weak, have I missed anything? Because my >>>>>>>> SmaltalkHub user does not have any projects >>>>>>>> http://smalltalkhub.com/#!/~YuriyTymchuk (and I had a bunch of >>>>>>>> them). >>>>>>>> >>>>>>>> Uko >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >

Aug. 6, 2014

Re: [Pharo-dev] What is exactly a conflict when merging in Monticello?

by Ben Coman

Aug. 6, 2014

Re: [Pharo-dev] [GTInspector] Showing object state using a tree

by Pablo R. Digonzelli

Great!. How can i install GtInspector in a pharo image? TIA Ing. Pablo Digonzelli Software Solutions IP-Solutiones SRL Metrotec SRL 25 de Mayo 521 Email: pdigonzelli(a)softsargentina.com pdigonzelli(a)gmail.com Cel: 5493815982714 ----- Mensaje original ----- De: "Tudor Girba" <tudor(a)tudorgirba.com> Para: "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org> Enviados: Martes, 5 de Agosto 2014 11:06:21 Asunto: [Pharo-dev] [GTInspector] Showing object state using a tree Hi, The GTInspector now shows the state of an object in a tree view (screenshots below). This tree view focuses on the internal structure of an object. For example, when looking at a dictionary object you will see the "array" and the "tally" attributes and not the key value pairs. Those can be accessed from another presentation of a dictionary object. So the tree is meant to be used together with the finder and the other presentations of on object. Let us know what you think. Cheers, Andrei & Doru -- www.tudorgirba.com "Every thing has its own flow"

Aug. 6, 2014

Re: [Pharo-dev] What is exactly a conflict when merging in Monticello?

by Dale Henrichs

is the method timestamp different? different protocol? a missing/extra newline? in times past it has been hard to tell when these things happen... Dale On Tue, Aug 5, 2014 at 5:57 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > Anyone can tell me what is a conflict? When merging, Monticello is telling > me there is a conflict with a old method that hasnât changed for long. How > that could be? > Am I the only one to experience this? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Aug. 6, 2014

What is exactly a conflict when merging in Monticello?

by Alexandre Bergel

Hi! Anyone can tell me what is a conflict? When merging, Monticello is telling me there is a conflict with a old method that hasnât changed for long. How that could be? Am I the only one to experience this? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 6, 2014

Re: [Pharo-dev] Moving to GitHub

by Dale Henrichs

Personally I think that the CofngurationOf is best used as a tag. You *can* specify any one of branch/SHA/tag in a ConfigurationOf ... So you can just reference the name of the branch instead of the SHA and you'll load the latest commit on that branch ... Dale On Tue, Aug 5, 2014 at 2:08 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > looks very interesting but I see you pull from a specific git commit , > what if I wanted to pull from latest commit ? > > > > On Tue, Aug 5, 2014 at 7:59 PM, Dale Henrichs < > dale.henrichs(a)gemtalksystems.com> wrote: > >> Hey Uko, >> >> I guess I wasn't clear;( >> >> What is not needed when using git are the version methods with the >> painstaking records of the mcz version associated with each file ... >> >> A baseline is created by subclassing BaselineOf and adding a single >> baseline: method that contains the package/project dependencies. This >> BaselineOfXXX is saved directly in the repository along with the packages. >> >> You can poke around in my External project on GitHub[1] to see more >> detail. >> >> Dale >> >> [1] https://github.com/dalehenrich/external/tree/master/repository >> >> >> On Tue, Aug 5, 2014 at 8:31 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >> wrote: >> >>> Hi Dale, >>> >>> I wonât agree that you donât need configuration. For me the main purpose >>> of configuration is defining dependencies. And as far as I know we donât >>> have any other alternative. >>> >>> Uko >>> >>> On 05 Aug 2014, at 17:21, Dale Henrichs < >>> dale.henrichs(a)gemtalksystems.com> wrote: >>> >>> Kilon, >>> >>> When working with git/github, you really don't need a configuration >>> anymore ... the configuration functions more like tag than anything else. >>> >>> For day to day operations with git/github you only need a baseline[1]. >>> The baseline just describes the package relationships and of course git >>> manages the versions of the packages: >>> >>> baseline: spec >>> <baseline> >>> spec for: #common do: [ >>> spec configuration: 'Seaside30' with: [ >>> spec >>> version: #stable; >>> repository: 'http://www.squeaksource.com/MetacelloRepository' ]. >>> spec >>> package: 'Sample-Core'with: [ >>> spec requires: 'Seaside30' ]; >>> package: 'Sample-Tests' with: [ >>> spec requires: 'Sample-Core' ]]. >>> >>> but there is no longer any need to track the version numbers of the >>> individual mcz file. >>> >>> To load from a repository using a baseline you do the following: >>> >>> Metacello new >>> baseline: 'External'; >>> repository: 'github://dalehenrich/external:master/repository'; >>> load. >>> >>> This is very similar to using #bleedingEdge,but a lot safer, since >>> presumably you are using travis-ci to run tests before anything gets merged >>> into your master branch and of course all of the packages are versioned >>> together. >>> >>> To refresh the version from the master branch you do the following: >>> >>> Metacello new >>> baseline: 'External'; >>> repository: 'github://dalehenrich/external:master/repository'; >>> get. >>> Metacello new >>> baseline: 'External'; >>> repository: 'github://dalehenrich/external:master/repository'; >>> load. >>> >>> This is admittedly a bit awkward, but there has been a couple year lag >>> between the time I did the basic implementation in support of git/github >>> and the time that folks are finally becoming interested in actually using >>> it:) So I have focussed on functionality instead or prettiness ... I will >>> eventually get to the point where you can do:) >>> >>> Metacello new >>> baseline: 'External'; >>> repository: 'github://dalehenrich/external:master/repository'; >>> get; >>> load. >>> >>> If you use a configuration, then the version method for the >>> configuration would look like the following: >>> >>> version0900: spec >>> <version: '0.9.0'> >>> spec >>> for: #'common' >>> do: [ >>> spec blessing: #'development'. >>> spec description: 'initial work: first commit on custom >>> branch'. >>> spec author: 'dkh'. >>> spec timestamp: '5/4/2012 14:16'. >>> spec >>> baseline: 'External' >>> with: [ spec repository: ' >>> github://dalehenrich/external:1ac58502ade7814e1590f71d615cca434b1a4fd5/repository' >>> ] ] >>> >>> So version 0.9.0 is simply a tag for a particular commit ... but within >>> the Metacello eco-system this approach can be useful. >>> >>> Dale >>> >>> [1] >>> https://github.com/dalehenrich/metacello-work/blob/master/docs/GettingStart… >>> >>> >>> On Mon, Aug 4, 2014 at 2:48 AM, kilon alios <kilon.alios(a)gmail.com> >>> wrote: >>> >>>> Well lately I have been questioning the need for configurations . I am >>>> considering doing only the second port of your blog post. Ask github for >>>> the latest release of my project , download it, unzip it and point pharo to >>>> the unziped directory. Then pharo can periodocally keep probing github to >>>> see if there is a new release and prompt the user for an update. All that >>>> with a single click from the user or even automagically. But I have to >>>> figure out how to do that with Pharo first :) >>>> >>>> >>>> On Mon, Aug 4, 2014 at 12:23 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >>>> wrote: >>>> >>>>> You donât have to. Just keep your configuration (here is a guide how >>>>> to do it >>>>> http://sleepycoders.blogspot.ch/2014/04/how-to-distribute-your-github-pharo…) >>>>> on some monticello repo, and assemble your image on CI. Yes, if someone >>>>> wantâs to modify your project they have to use git, but as far as I know, >>>>> Pharo is slowly moving git way anyway :) >>>>> >>>>> Cheers. >>>>> Uko >>>>> >>>>> On 04 Aug 2014, at 11:17, kilon alios <kilon.alios(a)gmail.com> wrote: >>>>> >>>>> yeah I will also move my latest project to github. I am already more >>>>> active with github than I am in SThub anyway. The one thing that stopped me >>>>> so far is that I don't want to force people to install git to get the >>>>> latest version of my project. SThub is great for this. >>>>> >>>>> >>>>> On Mon, Aug 4, 2014 at 12:03 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >>>>> wrote: >>>>> >>>>>> Well, thankfully I keep all my latest projects on github, and I have >>>>>> configurations of them in the image. But CI is not working and anyway itâs >>>>>> a strange situation. Is there any other service where I can keep my >>>>>> configurations? Because thatâs the only thing I version with monticello are >>>>>> configurations as I want to use gofer to load my projects. And here >>>>>> reliability is much more important then other features. >>>>>> >>>>>> Uko >>>>>> >>>>>> >>>>>> On 04 Aug 2014, at 10:59, kilon alios <kilon.alios(a)gmail.com> wrote: >>>>>> >>>>>> oh boy thats looks nasty bug, hope its not permanent. >>>>>> >>>>>> >>>>>> On Mon, Aug 4, 2014 at 11:44 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I was on vacation last weak, have I missed anything? Because my >>>>>>> SmaltalkHub user does not have any projects >>>>>>> http://smalltalkhub.com/#!/~YuriyTymchuk (and I had a bunch of >>>>>>> them). >>>>>>> >>>>>>> Uko >>>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>> >>> >> >

Aug. 5, 2014

Re: [Pharo-dev] [Pharo-users] Your success stories ...

by Esteban Lorenzano

On 05 Aug 2014, at 21:11, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > Hi, > > I just looked at this page (Firefox 31, Mac OSX 10.9.3) and the images are zoomed like 500%, they are huge. I think this is not the intent, it would be good if this is looked at. yes, we are aware. We are on our way to fix it, please be patient. Esteban > Greetings, > > On Jul 31, 2014, at 2:12 AM, stepharo <stepharo(a)free.fr> wrote: > >> "Pharo success stories" is getting started at >> >> http://www.pharo.org/success >> >> TrentoSur http://trentosur.com looks so sexy >> >> Please send me information about yours they will be added to the pending queue >> >> Stef >> >> > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > >

Aug. 5, 2014

Re: [Pharo-dev] No projects on StHub?

by kilon alios

thanks Dale this exactly what I wanted , you just made my day :) On Tue, Aug 5, 2014 at 8:01 PM, Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > > > > On Tue, Aug 5, 2014 at 8:37 AM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> >> On 05 Aug 2014, at 17:01, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> >> wrote: >> >> >> KIlon, >> >> If you use a a github reference in your configuration: >> >> github://username/projectname:commitish/repositoryDir >> >> Git is not required. Metacello will download a zipped version of the >> commitish referenced (a commitish is a branch name, SHA or tag name) and a >> read only filetree repository is created .... >> >> >> it is not required if you are not going to modify the projects, of course >> :) >> AFAIKâ¦ in your own projects, you will need the clone in disk (I suppose >> with filetree or gitfiletree)â¦ >> >> > Yes you or anyone else that wants to contribute to the project needs to > install git, but pure users of the code can use the projects without > installing git ... > > Dale >

Aug. 5, 2014

Re: [Pharo-dev] Moving to GitHub

by kilon alios

looks very interesting but I see you pull from a specific git commit , what if I wanted to pull from latest commit ? On Tue, Aug 5, 2014 at 7:59 PM, Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > Hey Uko, > > I guess I wasn't clear;( > > What is not needed when using git are the version methods with the > painstaking records of the mcz version associated with each file ... > > A baseline is created by subclassing BaselineOf and adding a single > baseline: method that contains the package/project dependencies. This > BaselineOfXXX is saved directly in the repository along with the packages. > > You can poke around in my External project on GitHub[1] to see more detail. > > Dale > > [1] https://github.com/dalehenrich/external/tree/master/repository > > > On Tue, Aug 5, 2014 at 8:31 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> > wrote: > >> Hi Dale, >> >> I wonât agree that you donât need configuration. For me the main purpose >> of configuration is defining dependencies. And as far as I know we donât >> have any other alternative. >> >> Uko >> >> On 05 Aug 2014, at 17:21, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> >> wrote: >> >> Kilon, >> >> When working with git/github, you really don't need a configuration >> anymore ... the configuration functions more like tag than anything else. >> >> For day to day operations with git/github you only need a baseline[1]. >> The baseline just describes the package relationships and of course git >> manages the versions of the packages: >> >> baseline: spec >> <baseline> >> spec for: #common do: [ >> spec configuration: 'Seaside30' with: [ >> spec >> version: #stable; >> repository: 'http://www.squeaksource.com/MetacelloRepository' ]. >> spec >> package: 'Sample-Core'with: [ >> spec requires: 'Seaside30' ]; >> package: 'Sample-Tests' with: [ >> spec requires: 'Sample-Core' ]]. >> >> but there is no longer any need to track the version numbers of the >> individual mcz file. >> >> To load from a repository using a baseline you do the following: >> >> Metacello new >> baseline: 'External'; >> repository: 'github://dalehenrich/external:master/repository'; >> load. >> >> This is very similar to using #bleedingEdge,but a lot safer, since >> presumably you are using travis-ci to run tests before anything gets merged >> into your master branch and of course all of the packages are versioned >> together. >> >> To refresh the version from the master branch you do the following: >> >> Metacello new >> baseline: 'External'; >> repository: 'github://dalehenrich/external:master/repository'; >> get. >> Metacello new >> baseline: 'External'; >> repository: 'github://dalehenrich/external:master/repository'; >> load. >> >> This is admittedly a bit awkward, but there has been a couple year lag >> between the time I did the basic implementation in support of git/github >> and the time that folks are finally becoming interested in actually using >> it:) So I have focussed on functionality instead or prettiness ... I will >> eventually get to the point where you can do:) >> >> Metacello new >> baseline: 'External'; >> repository: 'github://dalehenrich/external:master/repository'; >> get; >> load. >> >> If you use a configuration, then the version method for the configuration >> would look like the following: >> >> version0900: spec >> <version: '0.9.0'> >> spec >> for: #'common' >> do: [ >> spec blessing: #'development'. >> spec description: 'initial work: first commit on custom >> branch'. >> spec author: 'dkh'. >> spec timestamp: '5/4/2012 14:16'. >> spec >> baseline: 'External' >> with: [ spec repository: ' >> github://dalehenrich/external:1ac58502ade7814e1590f71d615cca434b1a4fd5/repository' >> ] ] >> >> So version 0.9.0 is simply a tag for a particular commit ... but within >> the Metacello eco-system this approach can be useful. >> >> Dale >> >> [1] >> https://github.com/dalehenrich/metacello-work/blob/master/docs/GettingStart… >> >> >> On Mon, Aug 4, 2014 at 2:48 AM, kilon alios <kilon.alios(a)gmail.com> >> wrote: >> >>> Well lately I have been questioning the need for configurations . I am >>> considering doing only the second port of your blog post. Ask github for >>> the latest release of my project , download it, unzip it and point pharo to >>> the unziped directory. Then pharo can periodocally keep probing github to >>> see if there is a new release and prompt the user for an update. All that >>> with a single click from the user or even automagically. But I have to >>> figure out how to do that with Pharo first :) >>> >>> >>> On Mon, Aug 4, 2014 at 12:23 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >>> wrote: >>> >>>> You donât have to. Just keep your configuration (here is a guide how to >>>> do it >>>> http://sleepycoders.blogspot.ch/2014/04/how-to-distribute-your-github-pharo…) >>>> on some monticello repo, and assemble your image on CI. Yes, if someone >>>> wantâs to modify your project they have to use git, but as far as I know, >>>> Pharo is slowly moving git way anyway :) >>>> >>>> Cheers. >>>> Uko >>>> >>>> On 04 Aug 2014, at 11:17, kilon alios <kilon.alios(a)gmail.com> wrote: >>>> >>>> yeah I will also move my latest project to github. I am already more >>>> active with github than I am in SThub anyway. The one thing that stopped me >>>> so far is that I don't want to force people to install git to get the >>>> latest version of my project. SThub is great for this. >>>> >>>> >>>> On Mon, Aug 4, 2014 at 12:03 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >>>> wrote: >>>> >>>>> Well, thankfully I keep all my latest projects on github, and I have >>>>> configurations of them in the image. But CI is not working and anyway itâs >>>>> a strange situation. Is there any other service where I can keep my >>>>> configurations? Because thatâs the only thing I version with monticello are >>>>> configurations as I want to use gofer to load my projects. And here >>>>> reliability is much more important then other features. >>>>> >>>>> Uko >>>>> >>>>> >>>>> On 04 Aug 2014, at 10:59, kilon alios <kilon.alios(a)gmail.com> wrote: >>>>> >>>>> oh boy thats looks nasty bug, hope its not permanent. >>>>> >>>>> >>>>> On Mon, Aug 4, 2014 at 11:44 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I was on vacation last weak, have I missed anything? Because my >>>>>> SmaltalkHub user does not have any projects >>>>>> http://smalltalkhub.com/#!/~YuriyTymchuk (and I had a bunch of them). >>>>>> >>>>>> Uko >>>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >> >> >

Aug. 5, 2014

Re: [Pharo-dev] Does anybody have an idea why when I open a transcript and recompile a method I get

by ClÃ©ment Bera

Because someone activated the method "mustBeBooleanMagicIn:" by default whereas it was just a hack to experiment. Basically you have an optimized message sent to a non boolean. For over a week now, in this case the code is executed as a DoIt with a non optimized message instead of raising the mustBeBoolean error. 2014-08-05 18:40 GMT+02:00 stepharo <stepharo(a)free.fr>: > Hi guys > > Does anybody have an idea why when I open a transcript and recompile a > method I get > > > UndefinedObject>>ExecuteUnOptimizedIn: (model is Undeclared) > > UndefinedObject>>ExecuteUnOptimizedIn: (model is Undeclared) > > UndefinedObject>>ExecuteUnOptimizedIn: (scroller is Undeclared) > > Stef > >

Aug. 5, 2014