[Pharo-dev] Layout in bloc

Hi! I am working on a popup support in Bloc and I am facing a problem. Consider the following code: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= space := BlSpace new. space root layout: BlLinearLayout horizontal. 10 timesRepeat: [ | e |

Re: [Pharo-dev] About Pharo 60

Le 27/08/2016 à 14:32, Esteban Lorenzano a écrit : > yes, some years ago I made a package for this. > later Ben tried something similar with the user manager. > none of those approaches worked as general approach because you need to > “close” a lot of things… (not just the spotter… which by the

Re: [Pharo-dev] About Pharo 60

Le 27/08/2016 à 14:39, stepharo a écrit : > Cyril what would be good is to share what you are disabling and to tunr > such points into points that can be turned > but inside Pharo like that you push the logic to the system. > Since we moved to a Seaside application not so long after I joined

Re: [Pharo-dev] About better communication in the community

In context of discussion how to propose Mocketry and StateSpecs to be part of Pharo? We often said that Pharo provides the best approach to TDD but we have no mock library inside. And nobody use mocks for Pharo tests because of that 2016-08-24 6:51 GMT+02:00 stepharo : > Hi

Re: [Pharo-dev] About better communication in the community

2016-08-24 9:38 GMT+02:00 stepharo : > Igor looked at Twisty seriously and I do not think that it could handle > large cobol files. > > (you see funnily denis is doing the same with Seamless - He rewrote it > from scratch while > nick worked on it for several years). >

Re: [Pharo-dev] About better communication in the community

Hi 2016-08-24 18:58 GMT+02:00 Hernán Morales Durand : > 2. Features that goes inside Pharo are not decided by vote. They have to >> add value and share the Pharo vision (pointed in the vision document who is >> not slightly updated but still guides our steps). We try to

Re: [Pharo-dev] MorphicDoc?

Yeah my bad it would suppose to be a documentation project for Morphic. There should be some content though. But since we move to Bloc I will delete it. On Sat, 27 Aug 2016 at 12:11, Nicolai Hess wrote: > Anyone knows what is MorphicDoc (Kilon?) > I loaded the stable

Re: [Pharo-dev] About better communication in the community

Hi yuriy A package manifest is the place where we keep package rules and meta data. We should add documentation and others. I think that all the packages should have a XXXManifest. There we can define a method preUnload and after we can define a class PackageUnloader (or put the logic in

Re: [Pharo-dev] About better communication in the community

> On 27 Aug 2016, at 11:00, stepharo wrote: > > You see hernan doing positively is the best way to make that things happen > > We can have a > >preUnload hook > > Now we should check how it fits with cleanForProduction and others. > > But we should definitively have a

[Pharo-dev] Confused by remote logic ;)

KomitNewSlice>>remote ^ MCRepositoryGroup default repositories detect: [ :e | e description = 'http://smalltalkhub.com/mc/Pharo/Pharo50Inbox/main/' ] ifNone: [ MCRepositoryGroup default repositories detect: [ :e | e description =

[Pharo-dev] Polymorphic results would be good

Hi I'm cleaning Smalltalk ui icons usage again and more :) I just want to share with you. I see code like that KomitDirectoryRemote>>icon ^ 'DIR' KomitGemstoneRemote>> icon ^ Smalltalk ui icons iconNamed: #komitterGemstoneRemote It would be nice if we could be cleaner and makes sure

Re: [Pharo-dev] About Pharo 60

> On 27 Aug 2016, at 14:40, stepharo wrote: > > Hi esteban > > I think that we should identify the main hook points and slowly prepare them. > > The system should be prepared for that so that we just need to pass a context > to configure it. .. I should have that old

Re: [Pharo-dev] About better communication in the community

So I think that I will keep Eyeinspector for Spec because it works well using Spec. I will package BasicInspector Then we will see. I think that Smalltalk tools inspector is not good because it is yet another global while the tools should have a tool context (but with a registration

Re: [Pharo-dev] About Pharo 60

Hi esteban I think that we should identify the main hook points and slowly prepare them. The system should be prepared for that so that we just need to pass a context to configure it. Stef Le 27/8/16 à 14:32, Esteban Lorenzano a écrit : yes, some years ago I made a package for this.

Re: [Pharo-dev] About Pharo 60

Cyril what would be good is to share what you are disabling and to tunr such points into points that can be turned but inside Pharo like that you push the logic to the system. Now this is important to see that if people for which the value is high do not work on something why others would do

Re: [Pharo-dev] About Pharo 60

yes, some years ago I made a package for this. later Ben tried something similar with the user manager. none of those approaches worked as general approach because you need to “close” a lot of things… (not just the spotter… which by the way, NEEDS to have a setting, no idea who answered you

Re: [Pharo-dev] SmalltalkHub over https

We’ve set up Let’s Encrypt on our servers and while it’s cool it also requires some work around it. Most importantly you have to set up auto renewal (every 30 days). And if you don’t get it right it will suck. Also: use VPN :) > On 27 Aug 2016, at 13:07, stepharo wrote: > >

Re: [Pharo-dev] About Pharo 60

Le 27/08/2016 à 13:18, stepharo a écrit : > > > YES!!! > > Do you know how Settings works? > We can adapt it this way. When I improved the deployment of Synectique Tools I asked to get a simple way to disable Spotter via a setting but I got as answer "No because you can do it by removing a

Re: [Pharo-dev] broken GitFileTree/IceBerg on Windows because of ProcessWrapper

Just checked and the download URL is working. If you send me mirror URLs then I can update the configuration to support multiple download locations. Cheers, Hernán 2016-08-27 5:46 GMT-03:00 Peter Uhnak : > Hi, > > GitFileTree / IceBerg is now broken, because ProcessWrapper

Re: [Pharo-dev] About Pharo 60

Hi! There is one thing I would like, but maybe not for Pharo6 since there is a lot to do, but I would like people to have this in mind: A way to deploy commercials apps. YES!!! I would like to be able to say something like "Smalltalk lockForDeployment" and "Smalltalk

Re: [Pharo-dev] Nautilus support for class method tests, and a bugfix for test result icons not resetting when a method is modified

Tx Monty! Apparently Jenkins infra is dead :) Le 26/8/16 à 22:20, monty a écrit : https://pharo.fogbugz.com/f/cases/18974/

Re: [Pharo-dev] SmalltalkHub over https

Time and ressources. We cannot do more else it will damage what we are doing. Now if somebody wants to help he is more than welcome. Stef since Let's Encrypt offers free certs, is there any reason why smalltalkhub is not yet served over https? Maybe limitation of Zinc? I guess that's one

Re: [Pharo-dev] broken GitFileTree/IceBerg on Windows because of ProcessWrapper

Hi, Just a clarification: This is because of gitfiletree. In next versions of iceberg, we will not use ProcessWrapper (or OSSubprocess). Esteban > On 27 Aug 2016, at 11:01, stepharo wrote: > > Once you have the file we can mirror it on our server. > > I always think about

Re: [Pharo-dev] About Pharo 60

Le 24/08/2016 à 06:59, stepharo a écrit : > Hi > > We have some ideas (because people are working on items) for the Pharo 6 > roadmap > > and we will consolidate them soon and propose them to you. > > but I would like to know two kinds of points > > - what are the points you are working on

[Pharo-dev] MorphicDoc?

Anyone knows what is MorphicDoc (Kilon?) I loaded the stable configuration in Pharo 5.0, but I can not find any content. (missing dependencies / packagese maybe ? )

Re: [Pharo-dev] About better communication in the community

May be we should take the one of Pharo30 and review all the code. Le 27/8/16 à 10:51, stepharo a écrit : I took the inspector from Pharo20 and I will check if it is working in Pharo. Then I will - check EyeInspector from a package perspective (extensions and the rest) - make sure

Re: [Pharo-dev] Fraction and isPowerOfTwo

Please please please you see we need pythondoc like things let us start by adding I know it is wrong because I did not get it :) Stef Le 27/8/16 à 03:04, Nicolai Hess a écrit : 2016-08-27 2:21 GMT+02:00 monty >: 2^-5 = (1/32)

[Pharo-dev] SmalltalkHub over https

Hi, since Let's Encrypt offers free certs, is there any reason why smalltalkhub is not yet served over https? Maybe limitation of Zinc? I guess that's one benefit that we are such a small community that nobody nuked us yet... (e.g. every time you commit from free wifi (hotel, airport, caffee,

Re: [Pharo-dev] broken GitFileTree/IceBerg on Windows because of ProcessWrapper

Once you have the file we can mirror it on our server. I always think about replication but this is not always the case. Stef Le 27/8/16 à 10:46, Peter Uhnak a écrit : Hi, GitFileTree / IceBerg is now broken, because ProcessWrapper (one of the deps on Windows) is downloading plugin from

Re: [Pharo-dev] About better communication in the community

You see hernan doing positively is the best way to make that things happen We can have a preUnload hook Now we should check how it fits with cleanForProduction and others. But we should definitively have a way to express this. So let us see how we can design it and then just implement

Re: [Pharo-dev] broken GitFileTree/IceBerg on Windows because of ProcessWrapper

Hi peter, just one note from the airport. It's Iceberg, not IceBerg. It is not a compound word, but a single one. Guille Le 27 août 2016 10:47, "Peter Uhnak" a écrit : > Hi, > > GitFileTree / IceBerg is now broken, because ProcessWrapper (one of the > deps on Windows) is

Re: [Pharo-dev] About better communication in the community

I took the inspector from Pharo20 and I will check if it is working in Pharo. Then I will - check EyeInspector from a package perspective (extensions and the rest) - make sure that we can remove EyeInspector - package the attached file as BasicInspector. Now if you want to help

Re: [Pharo-dev] About better communication in the community

What we should do is to add an unload method to each of the package manifest of the corresponding projects. We should make the unload protocol a lot more present. I will start with Nautilus. Can you publish the unload process? Workspace openContents: 'GTPlayground

[Pharo-dev] broken GitFileTree/IceBerg on Windows because of ProcessWrapper

Hi, GitFileTree / IceBerg is now broken, because ProcessWrapper (one of the deps on Windows) is downloading plugin from http://leves.web.elte.hu/ProcessWrapper/ProcessWrapperPlugin.dll But of course since the domain is down, it breaks everything. Not the mention downloading dll over http.

[Pharo-dev] IceBerg and push for projects vs packages

Hi, one thing that I wanted to ask about IceBerg --- during the IceBerg talk Nico mentioned that we need to think in terms of projects. Now I understand that perspective, because that's how git behaves and that's how _I_ think, however at the same time, there is a strong push for focusing on

Re: [Pharo-dev] CI is down

something is in a strange state… the update from yesterday afternoon (there should be a 194) is not there, it is very slow… but it seems to work. Sadly I am *completely* dead after esug and will be offline the weekend. Marcus > On 26 Aug 2016, at 01:05, monty