April 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] FileSystem-Git status update 3

by Max Leske

Tadaaa!! And now we have push working via SSH too! :) Iâll let you know soon what is going to happen next. Right now I have to clean up the mess I made while figuring this outâ¦ BTW, I posted this on IRC but got no response. Any ideas? > In NB, how do I pass NULL into a function call without modifying the argument type? e.g. my argument has type String. passing something like `NBExternalAddress null` will be converted into a C string instead of being passed through (I know, that seems to be the point in this case but I couldn't find any other way to create NULL). Any suggestions? Cheers, Max On 08.04.2014, at 18:11, Max Leske <maxleske(a)gmail.com> wrote: > FINALLY managed to get pull via SSH working (no, there was no bug in libgit2 nor in libssh2â¦ sadlyâ¦). Next thing is push via SSH but I think I have that figured out now (hopefullyâ¦). > > Max

April 8, 2014

Bug in SSL

by Norbert Hartl

As you might know a sever bug in the openssl library har been reported to the public. This bug is pretty nasty and allows in an easy fashion to access protected data. Please consider upgrading your products and operating systems to a fixed version of openssl. https://www.openssl.org/news/secadv_20140407.txt regards, Norbert

April 8, 2014

Re: [Pharo-dev] Suggested Syntax Highlighting Features for Beginners

by J.F. Rick

I went ahead and created two cases in FogBugz for the respective issues: https://pharo.fogbugz.com/f/cases/13186/Syntax-Highlighting-Distinguish-Ass… https://pharo.fogbugz.com/f/cases/13187/Syntax-Highlighting-Messages-with-2… That way this issue won't be completely forgotten. On Fri, Apr 4, 2014 at 7:26 PM, J.F. Rick <self(a)je77.com> wrote: > On Fri, Apr 4, 2014 at 6:41 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> For assignment, I would say bold both := and the variable being assigned >> to. >> > > I like that a lot, especially since it draws the two critical elements of > variable and assignment together. On a minor note, both := and = are > currently the same color: black. That only furthers the ":= is a message" > misconception. It might be worthwhile also giving := its own color, given > its uniqueness. > > >> Underlining sounds interesting, but there are a few choices: >> a. nested underlining - self someMessage: (self otherMessage: arg 1 and: >> arg2) and: arg3 >> b. non-nested underlining - only underline #otherMessage:and: and not >> #someMessage:and: >> c. dynamically underline only message where cursor is located. >> > > I think you could do nested underlining in the same way that nested blocks > and parentheses work. someMessage: and the second and: are underlined in > black. otherMessage: and the first and: are underlined in green. That way > nesting is clear. This would also be useful for code with nested > conditionals, probably the most common occurrence of nested multi-part > messages. I also like (c) as a minimally intrusive change that could help > novices when they write code. It has the disadvantage that novices couldn't > look at a piece of foreign code and get where the multi-part messages were. > > Cheers, > > Jeff > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick > -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

April 8, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30816 Home: https://github.com/pharo-project/pharo-core

April 8, 2014

[pharo-project/pharo-core] d1c0c3: 30816

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: d1c0c338e94a0f65fa580f1c4880002b7cf9ef18 https://github.com/pharo-project/pharo-core/commit/d1c0c338e94a0f65fa580f1c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-04-08 (Tue, 08 Apr 2014) Changed paths: M Athens-Cairo.package/CairoFontMetricsProvider.class/instance/accessing/getGlyphWidth_.st M Athens-Cairo.package/CairoFreetypeFontRenderer.class/instance/accessing - font metrics/glyphsOf_from_to_.st M Athens-Cairo.package/CairoFreetypeFontRenderer.class/instance/private/convertString_len_ofFont_toGlyphs_numGlyphs_x_y_.st M Athens-Cairo.package/CairoUTF8Converter.class/definition.st A Athens-Cairo.package/CairoUTF8Converter.class/instance/accessing/buffer.st R Athens-Cairo.package/CairoUTF8Converter.class/instance/as yet unclassified/buffer.st R Athens-Cairo.package/CairoUTF8Converter.class/instance/as yet unclassified/checkBufferSpace_.st R Athens-Cairo.package/CairoUTF8Converter.class/instance/as yet unclassified/convert_from_to_.st A Athens-Cairo.package/CairoUTF8Converter.class/instance/converting/checkBufferSpace_.st A Athens-Cairo.package/CairoUTF8Converter.class/instance/converting/convertChar_.st A Athens-Cairo.package/CairoUTF8Converter.class/instance/converting/convert_from_to_.st A Athens-Cairo.package/CairoUTF8Converter.class/instance/initialize/initialize.st A Athens-Cairo.package/CairoUTF8ConverterTest.class/README.md A Athens-Cairo.package/CairoUTF8ConverterTest.class/definition.st A Athens-Cairo.package/CairoUTF8ConverterTest.class/instance/running/setUp.st A Athens-Cairo.package/CairoUTF8ConverterTest.class/instance/tests/testEncodingString.st A Athens-Cairo.package/CairoUTF8ConverterTest.class/instance/tests/testReusingConverterShouldReplaceOldData.st A Athens-Cairo.package/CairoUTF8ConverterTest.class/instance/tests/testUnicodencodingShouldTerminateWithNull.st M Athens-Examples.package/AthensSurfaceExamples.class/class/as yet unclassified/drawFontMetrics.st M Athens-Examples.package/AthensSurfaceExamples.class/class/as yet unclassified/example1.st M Athens-Examples.package/AthensSurfaceExamples.class/class/as yet unclassified/example2.st A Athens-Examples.package/AthensSurfaceExamples.class/class/opening view/openViewOn_.st M Metacello-TestsPlatform.package/MetacelloRepositorySqueakCommonTestCase.class/instance/tests/testAsRepositorySpecFor.st M Metacello-TestsPlatform.package/MetacelloRepositorySqueakCommonTestCase.class/instance/tests/testDirectoryRepository.st M Metacello-TestsPlatform.package/MetacelloRepositorySqueakCommonTestCase.class/instance/tests/testFileTreeRepository.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script469.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30816.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Traits.package/TClassDescription.class/instance/filein%2Fout/fileOutChangedMessages_on_moveSource_toFile_.st Log Message: ----------- 30816 11438 Change Sorter exports selected changes twice https://pharo.fogbugz.com/f/cases/11438 13184 Fix encoder for displaying high-range unicode chars https://pharo.fogbugz.com/f/cases/13184 12911 MetacelloRepositorySqueakCommonTestCase failing in fresh image on Windows https://pharo.fogbugz.com/f/cases/12911 http://files.pharo.org/image/30/30816.zip

April 8, 2014

Re: [Pharo-dev] Missing documentation for Pharo Launcher on UBUNTU

by Sergi Reyner

2014-04-08 13:41 GMT+01:00 Sergi Reyner <sergi.reyner(a)gmail.com>: > Desktop menu entries are pretty standard. Seems like a packaging bug to > me. It may be that there are no desktop entries provided. In my opinion, > there should be, otherwise I donÂ´t quite see the point of having a package. > Actually, looking at the file it seems that all the necessary pieces are there. I couldnÂ´t find the icon, but I guess itÂ´s provided by the pharo-vm package. Cheers, Sergi

April 8, 2014

Re: [Pharo-dev] Log of actions now on github and in markDown

by Marcus Denker

On 08 Apr 2014, at 15:20, Ben Coman <btc(a)openInWorld.com> wrote: > Pharo4Stef wrote: >> >> Hi guys >> >> I moved the changeLog of Pharo30 (and I will move all the other ones too). >> >> https://github.com/pharo-project/ChangeLogs/blob/master/Pharo30ChangeLogs.md >> >> Stef >> >> PS: do not ask me whyâ¦. better markdown than a broken click and play wiki. >> >> > > The Opal Compiler is now part of the image (not yet the default). > Is it correct that it is not the default? In 30813, World > System > Settings > Compiler > Default Compiler --> OpalCompiler > It is the default. Marcus

April 8, 2014

Re: [Pharo-dev] Log of actions now on github and in markDown

by Ben Coman

April 8, 2014

Re: [Pharo-dev] Missing documentation for Pharo Launcher on UBUNTU

by kilon alios

"Try installing just pharo-launcher (without :i386). The handling of 32bit packages within a 64bit environment was changed in ubuntu. I don't know the details, but I installed pharo-launcher in ubuntu 14.04 yesterday and it just works fine. If you can confirm, maybe the respective community page should be updated to reflect this change." no idea how to install without i386 sudo apt-get install pharo-launcher just tells me that i386 pharolauncher is already installed. Note that I have Ubuntu 13 and not 14. So what applies for you may not for me or anyone that still uses UBUNTU 13.

April 8, 2014

Re: [Pharo-dev] Missing documentation for Pharo Launcher on UBUNTU

by Sergi Reyner

2014-04-08 13:21 GMT+01:00 kilon alios <kilon.alios(a)gmail.com>: > No I see nowhere a Pharo Launcher icon. > > If this was Windows or MacOS I would agree that you could get away without > mentioning how to launch the app, though the majority of good documentation > usually mentions that. But this is Linux, a diffirent beast, it has 2 ways > of working its GUI that differs from linux distro to linux distro, in my > case Unity and terminal usage. Till now I knew that pharo installed > through UBUNTU was to be used from terminal, now you telling me that there > is an icon that I should click. Its not hard to be confused. > Desktop menu entries are pretty standard. Seems like a packaging bug to me. It may be that there are no desktop entries provided. In my opinion, there should be, otherwise I donÂ´t quite see the point of having a package. The pharo and pharolauncher binaries should also be in the path. Cheers, Sergi

April 8, 2014