Re: [Pharo-users] [Moose-dev] [ann] pillar support in gtinspector

Hi, On 29/08/16 21:47, Yuriy Tymchuk wrote: [...] It pains me that we are editing Pillar in outside tools, and now we should no longer have to do that. Of course, this is not the most ideal tool support for Pillar but I think it is a reasonable start. To make things sadder: when I need

Re: [Pharo-users] standalone/runtime executable

Hi Stephan 2016-08-29 14:16 GMT-03:00 Stephan Eggermont : > On 26/08/16 18:49, Hernán Morales Durand wrote: > >> Is not fully tested but here is how you install it: >> >> Gofer it >> smalltalkhubUser: 'hernan' project: 'CodeGenerator'; >> configuration; >>

Re: [Pharo-users] Traits inheritance

Alex the explicitRequirement was removed because of the algorithms you need to check for example to update the icons or do static check each time you compile a method. Stef Le 28/8/16 à 11:17, Alexandre Bergel a écrit : Hi Petr! You have found what I think is a bug. Indeed, Nautilus may

Re: [Pharo-users] standalone/runtime executable

On 26/08/16 18:49, Hernán Morales Durand wrote: Is not fully tested but here is how you install it: Gofer it smalltalkhubUser: 'hernan' project: 'CodeGenerator'; configuration; loadDevelopment. CGSmalltalkExamples exampleNSISPharo4. CGSmalltalkExamples exampleNSISPharo5. It will

Re: [Pharo-users] More reliable VCS, Project management and tools?

Hello, Thanks for the answers! stepharo I used Kommiter to commit onto smalltalkhub and Monticello to copy changes > to my local file tree until I got and error using Komiter. > > which one? I don't remember. When the error occurred I just proceed to see what would happened. if you go to

Re: [Pharo-users] [ANN] Pillar 4.0.0

In fact, the hyperlink for chapter does not work on Enterprise Pharo but just for chapters. Because it is not links but anchor. The reason is that when we want to reference a section, the section is in the same HTML so the anchor works but when we reference a chapter, it is not in the same