Re: [Pharo-dev] macOS Sierra support

2016-11-14 Thread MartinW
If I try to start the Pharo from the Download page e.g. from my Desktop I get the following information: - Pharo cannot write to the changes file named /private/var/folders/9p/h6h_ntqs2gs9kztvdp9mrm1mgn/T/AppTranslocation/1CA39D30-C5A9-4599-82F0-8FFA46606D5B/d/Pharo5.0.app/Contents/Resourc

Re: [Pharo-dev] macOS Sierra support

2016-11-14 Thread MartinW
Can someone put a note to the website (http://pharo.org/download)? It is frustrating for users to follow the link to http://files.pharo.org/platform/Pharo5.0-mac.zip from there and get a defunct Pharo installation. Sean P. DeNigris wrote > > EstebanLM wrote >> the regular download by zeroconf sh

Re: [Pharo-dev] Pharo 4.0 - display

2015-04-26 Thread MartinW
recursive wrote > This is probably already a potential known solution to the display issue > on > MAC Retina displays but I've just tried the latest CogVM with the Pharo > 4.0 > image and using Cog fixes the issue, it no longer leaves outlines of > windows or tracers. No, this is just because Cog

Re: [Pharo-dev] Pharo 4.0 - display

2015-04-19 Thread MartinW
I reported this bug some time ago together with screenshots. It only appears on retina screens: https://pharo.fogbugz.com/f/cases/14674/Artefacts-when-moving-windows-morphs-on-Retina-screen Even as it is only a minor detail, it makes Pharo's first impression look pretty bad.

[Pharo-dev] FogBugsz issue assignment

2015-01-06 Thread MartinW
Whenever I reply to an issue or resolve an issue, everybody gets automatically removed from "assigned to this issue" and I am set as the only one the issue is assigned to. Is this intended? I just entered a new bug (https://pharo.fogbugz.com/f/cases/14679/Fix-layout-glitch-in-FileDialogWindow-s-t

Re: [Pharo-dev] About your contributions: Improve Pharo right now, right there.

2014-08-07 Thread MartinW
Could you extend http://pharo.org/contribute-propose-fix a bit? And add a screenshot of Slice Maker (I attach one). The following text would have helped me (I paste the markdown. I also posted it on NoteHub for a better reading experience http://www.notehub.org/2014/8/7/how-to-propose-a-bug-fix):

Re: [Pharo-dev] Smalltalk Syntax in a Postcard contest

2014-07-08 Thread MartinW
I removed the question, but only after it was already marked to be closed by several people. Their argument was, that the question was "to broad". Once a discussion like this starts on Stackexchange sites there's always a herd behavior that's hard to stop. Can you share the code you used for your

[Pharo-dev] Smalltalk Syntax in a Postcard contest

2014-07-06 Thread MartinW
As there was a recent discussion about the Smalltalk Syntax in a Postcard, i added a contest on the Stackoverflow Programming Puzzles & Code Golf site: http://codegolf.stackexchange.com/questions/33050/smalltalk-syntax-in-a-postcard-that-actually-does-something-interesting -- View this message i

Re: [Pharo-dev] [ANN] DrGeo 14.07b

2014-06-22 Thread MartinW
Hilaire Fernandes-6 wrote > Here is another release fixing some reported killing bugs > https://dl.dropboxusercontent.com/u/21633199/DrGeo.app-14.07b.zip Hi Hilaire, the startup bug on OS X is gone :) I found another one, concerning a deprecated Method: The method UITheme>>questionIcon has been

Re: [Pharo-dev] Case 12776 Cancelling-Previous-Contents-in-a-Workspace-clears-the-current-contents

2014-04-12 Thread MartinW
btc wrote > However I have a separate but related question. > How is Workspace > System window menu > Previous Contents... > supposed to work? - Write something in a Workspace. - Close this Workspace (close the window) (accidentally...). - Suppose you want the content of this workspace back. -

Re: [Pharo-dev] [pharo3 issues] down to 17 issues

2014-04-04 Thread MartinW
When i add a new bug to the issue tracker it is automatically tagged as "fix if time". Am i supposed to change this label to higher priority if i think it's appropriate - or is someone reviewing new entered bugs and assigning priorities to them? Anyway here's the bug: https://pharo.fogbugz.com/f/ca

Re: [Pharo-dev] New Nautilus side bar buttons

2014-03-28 Thread MartinW
Just out of curiosity (this is not a rhetoric question, i just don't know it) - when should i look at the bytecode? And are there enough use cases to justify such a very prominent place in the UI? Or would a place in the context menu be enough? Or a plugin, if there are people - like compiler devel

Re: [Pharo-dev] How to upload some version from the package-cache to a StHub project

2014-02-26 Thread MartinW
Gabriel Cotelli-3 wrote > I have a whole package history in my local package cache and I want to > upload it to a new SmalltalkHub project. I've tried using the Monticello > browser but it insists in creating a new version of the package when I do > the "Save" to the new repository. > > Is there s

Re: [Pharo-dev] [OT] Where should menues go ...

2014-02-23 Thread MartinW
Torsten Bergmann wrote > http://www.omgubuntu.co.uk/2014/02/locally-integrated-menus-ubuntu-14-04 > > http://www.youtube.com/watch?v=teAFgtHWDso Well, are not Smalltalks pop-up menus (i.e. the world menu and all the other context menus) solving the problem in the most beautiful way possible? I w

Re: [Pharo-dev] Fwd: New pharo questions for Dec 17 - Stack Exchange

2013-12-17 Thread MartinW
Marcus Denker-4 wrote > 3 questions in one day… we are getting famous ;-) It is also encouraged to ask /and answer/ your own questions on Stackoverflow. I just documented how to add Nautilus menu context entrie

Re: [Pharo-dev] cannot commit with gofer to sthub (HTTP 403)

2013-09-10 Thread MartinW
Tudor Girba-2 wrote > with the url being already authenticated beforehand. > > I also tried by passing the url:username:password: explicitly, but this > has > the same 403 effect. > > Anyone knows what the issue is? At least I know that second part: *If the repository is already present* in the

Re: [Pharo-dev] [update 2.0] #20619

2013-08-24 Thread MartinW
Goubier Thierry wrote > Thanks Esteban :) > > The speedup on loading MC packages is 3x or more, so I though it is a > crime not to make it available immediately, since there is no bug reports > in all our tests and usages. > Thanks Thierry for the backport! Yes, thank you both! While i haven't m