Re: [Pharo-dev] Github and Fogbugz integration

Not Tiobe Index, Tiobe is based more on google search with the name of the language followed with the word "programming". Which is one of the reason its critics say its not reliable. As if there is a reliable way to measure popularity. The only popularity index I am familiar with that was using

Re: [Pharo-dev] Launcher Opening Tiny Windows

It's a known problem for any image that was saved in headless mode (not just launcher) - we should find a way to resolve this. Tim Sent from my iPhone > On 20 Aug 2017, at 00:35, Sean P. DeNigris wrote: > > Check out this screenshot. >

Re: [Pharo-dev] Github and Fogbugz integration

I also wonder when they measure the popularity of a language/community whether GitHub issues is a measure (I suspect it is), so it may be advantageous to show activity particularly for a smaller community. Like others, I'm not a big fan of fogbugz (never understood why Joel is considered a

[Pharo-dev] Launcher Opening Tiny Windows

Check out this screenshot. The red arrow points to an open "window" of a newly created Pharo 6.0 based image, minimized to the point of barely being visible. Clicking on it makes a title bar somewhat more visible, the edges of

Re: [Pharo-dev] 19609 FileReference>>base should be before last separator

Eliot Miranda-2 wrote > While basenameWithoutExtension is an intension revealing selector it is > soon ln :-) For file manipulation code that's a problem. I > wonder if something like bodyName is better because it's shorter. While I too feel a bit of pain from the long selector, I

Re: [Pharo-dev] Lowering the pain of newbies

Stephane Ducasse-3 wrote > any idea is welcome From http://forum.world.st/Woe-unto-thee-who-assigns-to-class-side-name-td4859734.html : Issue 16947: Class-side Inst Var "#name" Allowed, But Breaks System

Re: [Pharo-dev] Github and Fogbugz integration

On Sat, Aug 19, 2017 at 10:32 PM Sean P. DeNigris wrote: > > I see little reason not to allow both ways of reporting bugs. > It seems that the need to create an account in FB to even view/search > issues has been a big barrier to new(er) would-be contributors. I expect >

Re: [Pharo-dev] Github and Fogbugz integration

> I see little reason not to allow both ways of reporting bugs. It seems that the need to create an account in FB to even view/search issues has been a big barrier to new(er) would-be contributors. I expect this difficulty would be multiplied since, in the process of reporting a bug on GH,

Re: [Pharo-dev] Github and Fogbugz integration

On sam. 19 août 2017 at 21:14, Dimitris Chloupis wrote: > Useless piece of info , I think I am the first person to actually create a > github issue for Pharo. It was not for pharo code it was for pharo > documentation > >

Re: [Pharo-dev] Github and Fogbugz integration

Useless piece of info , I think I am the first person to actually create a github issue for Pharo. It was not for pharo code it was for pharo documentation https://github.com/SquareBracketAssociates/UpdatedPharoByExample/issues/1 Since then not only UPBE but also other pharo doc github repos

Re: [Pharo-dev] Latest Debian, Ubuntu and CentOS packages of the pharo-vm

Tx Holger Really tx. On Fri, Aug 18, 2017 at 11:54 AM, Holger Freyther wrote: > Hi, > > when running Pharo in production you might want to install the image and a VM > from distribution packages. So far there were no current public packages and > during the last months

Re: [Pharo-dev] Github and Fogbugz integration

Hi sean I prefer to continue to use fogbugz. Changing is really costly. Stef On Sat, Aug 19, 2017 at 6:48 PM, Sean P. DeNigris wrote: > Guillermo Polito wrote >> Sadly, this just works for the integration of commits into the main >> branches, not pull requests. For pull

Re: [Pharo-dev] Github and Fogbugz integration

Well technically you cannot stop people from using the github issue tracker for reporting bugs and by default if you are a contributor to a repo you will be alerted via email of new issues or replies to existing github issues. Both github and forgbuz issue tracker can happily coexist. There will

Re: [Pharo-dev] Github and Fogbugz integration

Guillermo Polito wrote > Sadly, this just works for the integration of commits into the main > branches, not pull requests. For pull request integration we will probably > need a home made solution. Now that we are moving development to GH, has there been any discussion of moving issue tracking

Re: [Pharo-dev] Ugly smell: really long symbols/selectors

Denis Kudriashov wrote > Which is actually shows that tests as methods are not really good idea. > Tests are supposed to be documentation but with classic SUnit we have only > two ways (classes and methods) to decompose them which is definitely not > enough for docs. He he +100. I remember us

Re: [Pharo-dev] Latest Debian, Ubuntu and CentOS packages of the pharo-vm

Holger Freyther wrote > Every time that master of pharo-vm.git is updated a new source package > will be uploaded to the Open(SUSE) Build Service and new packages will be > built and are available in a "latest" package feed. Awesome!! Esteban and I have wanted this for a long time but were unable

[Pharo-dev] [ Pharo 70 ] Build 44 PR 175 Space-analysis-resurrection

[ Pharo 70 ] Build 44 PR 175 Space-analysis-resurrection https://pharo.fogbugz.com/f/cases/20230/Space-analysis-resurrection https://github.com/pharo-project/pharo/pull/175

Re: [Pharo-dev] Little extensions to easily manage file versions

No I will have a look :) But I also need latestVersion because you need the two: to always load the latest and save latest + 1 Stef On Fri, Aug 18, 2017 at 11:38 PM, Denis Kudriashov wrote: > Do you know that there is #nextVersion method in FileReference? > > 2017-08-18