October 2018 - Pharo-dev - lists.pharo.org

Recommendation for password encryption?
by Mariano Martinez Peck Sept. 30, 2022

Sept. 30, 2022

Hi guys. Some time ago I asked about the best way to encrypt a password. Some of the recommendations I got was: 1) Generally for passwords you do not write a decrypt method for security purposes (eg you do not want people to be able to reverse engineer the encrypted password easily) 2) put a little salt 3) There is http://www.squeaksource.com/Cryptography/PasswordHashingFFI 4) I should not decrypt password but instead I should compare both encrypted versions to see if they are equal. My scenario is the following. I need to store database passwords in text files. So I don't want to let them as plain text. And while I understand 4), I think it's a different scenario than mine. I know that some database driver may allow you to directly send the encrypted password. But still...I have another similar scenario in which I have to store a password and then send it (unencrypted)...so I kind of really need a bi-directional encryption. Now..I would try to avoid having an external library + FFI. Any ideas what is the best thing I can do? And how could I solve 1) if I want bidirectional like in my case? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

9 26

Re: [Pharo-project] Parsing and navigating Html
by Paul DeBruicker July 16, 2020

July 16, 2020

On 12/05/2010 06:02 AM, pharo-project-request(a)lists.gforge.inria.fr wrote: > From: St?phane Ducasse<stephane.ducasse(a)inria.fr> > Subject: [Pharo-project] Parsing and navigating Html > To:"Pharo-project(a)lists.gforge.inria.fr Development" > <Pharo-project(a)lists.gforge.inria.fr> > Message-ID:<1C53DFD8-3021-4233-BC83-CE8C1EA8D103(a)inria.fr> > Content-Type: text/plain; charset=us-ascii > > Hi > > I would like extract partial information from HTML pages. > So I started to play and fix HTMLParser. > > Now does anybody know alternatives? > > Second, does anybody develop a lib to query HTML structure as with the XMLSupport package? > > Stef The Soup package on SqueakSource.com works OK.

3 4

Re: [Pharo-dev] [Vm-dev] Image crashing on startup, apparently during GC
by Eliot Miranda June 3, 2019

June 3, 2019

Hi Damien, On Fri, Mar 23, 2018 at 12:38 PM, Damien Pollet <damien.pollet(a)gmail.com> wrote: > > Here are the files (image and various outputs). Running with --leakcheck > does mention a few object leaks (see output.txt); > Indeed the image is corrupt at start-up. See below. > I'm not sure where to get or how to build an assert VM. > When you build a phar. VM under build.macos64x64/pharo.cog.spur using the mvm script (mvm -A) you produce an assert VM in PharoAssert.app. > I also realized the VM I had was from this summer (the one that comes with > a 70 image with zeroconf). The output files I include were produced by the > VM at get.pharo.org/64/vmLatest70 > > https://www.dropbox.com/s/y8yqjuzd9nsvy1u/clap-broken.tar.gz?dl=0 > > On 20 March 2018 at 18:17, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > >> >> Hi Damien, >> >> On Tue, Mar 20, 2018 at 3:12 AM, Damien Pollet <damien.pollet(a)gmail.com> >> wrote: >> >>> >>> Hi, I have a Pharo image that crashes the VM on startup. The crash >>> report below seems to incriminate GC. Should I make it available somewhere >>> online? What's most convenient? >>> >> >> Don't care. Anywhere it can be downloaded from. Also, try running with >> -leakcheck 15, preferably in an assert VM and see if that gets you >> additional information. >> >> >>> >>> Process: Pharo [64892] >>> Path: /Users/USER/*/Pharo.app/Contents/MacOS/Pharo >>> Identifier: org.pharo.Pharo >>> Version: 5.0.201708271955 (5.0.201708271955) >>> >> Right. This VM is prior to the bug fixes in VMMaker.oscog-eem.2320: Spur: Fix a bad bug in SpurPlnningCompactor. unmarkObjectsFromFirstFreeObject, used when the compactor requires more than one pass due to insufficient savedFirstFieldsSpace, expects the corpse of a moved object to be unmarked, but copyAndUnmarkObject:to:bytes:firstField: only unmarked the target. Unmarking the corpse before the copy unmarks both. This fixes a crash with ReleaseBuilder class>>saveAsNewRelease when non-use of cacheDuring: creates lots of files, enough to push the system into the multi-pass regime. Pharo urgently needs to upgrade the VM to one more up to date than 2017 08 27 (in fact more up-to-date than opensmalltalk/vm commit 0fe1e1ea108e53501a0e728736048062c83a66ce, Fri Jan 19 13:17:57 2018 -0800). The bug that VMMaker.oscog-eem.2320 fixes can result in image corruption in large images, and can occur (as it has here) at start-up, causing one's work to be irretrievably lost. > Code Type: X86-64 (Native) >>> Parent Process: ??? [64888] >>> Responsible: Pharo [64892] >>> User ID: 501 >>> >>> Date/Time: 2018-03-19 20:27:03.906 +0100 >>> OS Version: Mac OS X 10.13.3 (17D102) >>> Report Version: 12 >>> Anonymous UUID: 6D022236-78DD-6676-117F-EADA56D5D1BE >>> >>> Sleep/Wake UUID: AC9E4E55-3CDB-4B4F-A6B4-51ACB1177154 >>> >>> Time Awake Since Boot: 28000 seconds >>> Time Since Wake: 6500 seconds >>> >>> System Integrity Protection: enabled >>> >>> Crashed Thread: 0 Dispatch queue: com.apple.main-thread >>> >>> Exception Type: EXC_BAD_ACCESS (SIGABRT) >>> Exception Codes: KERN_INVALID_ADDRESS at 0x000000012b67c0b0 >>> Exception Note: EXC_CORPSE_NOTIFY >>> >>> VM Regions Near 0x12b67c0b0: >>> VM_ALLOCATE 000000011adfc000-00000001259fc000 [172.0M] >>> rw-/rwx SM=PRV >>> --> >>> STACK GUARD 0000700005613000-0000700005614000 [ 4K] >>> ---/rwx SM=NUL stack guard for thread 1 >>> >>> Application Specific Information: >>> abort() called >>> >>> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread >>> 0 libsystem_kernel.dylib 0x00007fff53fbde3e __pthread_kill + 10 >>> 1 libsystem_pthread.dylib 0x00007fff540fc150 pthread_kill + 333 >>> 2 libsystem_c.dylib 0x00007fff53f1a312 abort + 127 >>> 3 org.pharo.Pharo 0x0000000104ed8997 sigsegv + 190 >>> 4 libsystem_platform.dylib 0x00007fff540eff5a _sigtramp + 26 >>> 5 ??? 000000000000000000 0 + 0 >>> 6 org.pharo.Pharo 0x0000000104e73558 markObjects + 464 >>> 7 org.pharo.Pharo 0x0000000104e72d40 fullGC + 72 >>> 8 org.pharo.Pharo 0x0000000104e92dea primitiveFullGC + >>> 45 >>> 9 org.pharo.Pharo 0x0000000104e52425 interpret + 26715 >>> 10 org.pharo.Pharo 0x0000000104e5c7f6 >>> enterSmalltalkExecutiveImplementation + 152 >>> 11 org.pharo.Pharo 0x0000000104e4be6c interpret + 674 >>> 12 org.pharo.Pharo 0x0000000104ed9cc1 >>> -[sqSqueakMainApplication runSqueak] + 394 >>> 13 com.apple.Foundation 0x00007fff2e6d696c >>> __NSFirePerformWithOrder + 360 >>> 14 com.apple.CoreFoundation 0x00007fff2c579127 >>> __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 >>> 15 com.apple.CoreFoundation 0x00007fff2c57904f >>> __CFRunLoopDoObservers + 527 >>> 16 com.apple.CoreFoundation 0x00007fff2c55b6a8 __CFRunLoopRun + >>> 1240 >>> 17 com.apple.CoreFoundation 0x00007fff2c55af43 >>> CFRunLoopRunSpecific + 483 >>> 18 com.apple.HIToolbox 0x00007fff2b872e26 >>> RunCurrentEventLoopInMode + 286 >>> 19 com.apple.HIToolbox 0x00007fff2b872a9f >>> ReceiveNextEventCommon + 366 >>> 20 com.apple.HIToolbox 0x00007fff2b872914 >>> _BlockUntilNextEventMatchingListInModeWithFilter + 64 >>> 21 com.apple.AppKit 0x00007fff29b3df5f _DPSNextEvent + >>> 2085 >>> 22 com.apple.AppKit 0x00007fff2a2d3b4c >>> -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] >>> + 3044 >>> 23 com.apple.AppKit 0x00007fff29b32d6d -[NSApplication >>> run] + 764 >>> 24 com.apple.AppKit 0x00007fff29b01f1a NSApplicationMain >>> + 804 >>> >>> -- >>> Damien Pollet >>> type less, do more [ | ] http://people.untyped.org/damien.pollet >>> >>> >> >> >> -- >> _,,,^..^,,,_ >> best, Eliot >> >> > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > > -- _,,,^..^,,,_ best, Eliot

9 26

Recent Pharo 6.1 OSX shows lots of "Error: unsupported compressor 8 on command line"
by Tim Mackinnon April 19, 2019

April 19, 2019

I noticed that recent Pharo 6.1 zero conf downloads show lots of these errors when you run the image in the terminal. Previous versions didnât do this - is this something to do with the latest vm upgrade? ./pharo-ui PagerDuty.image /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50: Error: unsupported compressor 8 /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist' /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50: Error: unsupported compressor 8 /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist' Tim

6 6

Pharo Downloads are sluggish
by Esteban Maringolo March 13, 2019

March 13, 2019

Is there a reason why the latest version of the builds linked from the website are not hosted in some CDN, Amazon S3 or similar? Maybe in Europe the speed is fast, but where I am (Argentina) it is really slow, the screenshot shows 3.5KB/s, it averages 10KB/s, with peaks of 40KB/s. This is an pitiful boarding experience, that will make many cancel it even before getting to open the downloaded launcher. [image: node-pharo.png] The screenshot shows that is not a problem with my home connection, which isn't the fastest but is "normal" for my use cases. Regards, Esteban A. Maringolo ps: When I finished writing this email, this was the progress... [image: image.png]

4 15

Minheadless trial
by Ben Coman Dec. 5, 2018

Dec. 5, 2018

wow time flies, its been 18 months since Ronie announced his Minheadless VM branch... [1] http://forum.world.st/Minheadless-VM-flavour-status-update-td4928091.html I've been meaning this whole time to try it out. Recently in my meandering thoughts on FreeRTOS port, I guessed Minheadless might make a good starting basis to experiment with. So a quick test on Ubuntu16.04.3(Windows10-WSL)... Long ago I'd already done... git clone git@github.com:OpenSmalltalk/opensmalltalk-vm.git so I now did... cd opensmalltalk-vm git remote add ronie git@github.com:ronsaldo/opensmalltalk-vm.git git fetch ronie git checkout MinimalisticHeadless ./scripts/updateSCCSVersions cd build.minheadless.cmake/x64/pharo.stack.spur/ ./mvm VM=`pwd`/release/dist/pharo ls $VM ==> confirmed it exists cd ~/pharo wget http://files.pharo.org/image/70/latest-minimal-64.zip unzip latest-minimal-64.zip sudo $VM Pharo7.0-metacello-64bit-65cff7b.image eval "19 + 23" ==> 42 yay Particularly interesting from [1] is "using the same CMake scripts for building on the three platforms: Windows, Linux and OS X." So I thought I'd also give it a try under Windows10-VisualStudio2017. I hardly used VS before, so I'll detail what I did as a reminder for myself (and also in case someone might be able to help if I get stuck). Under a windows cmd.exe prompt (having installed git and cloned opensmalltalk-vm a long time ago) cd opensmalltalk-vm git remote add ronie git@github.com:ronsaldo/opensmalltalk-vm.git git fetch ronie git checkout -b MinimalisticHeadless ronie/MinimalisticHeadless I watched video [2] about CMake integration with Visual Studio 10. and checked the VS workloads configuration specified [2@1:13] using [3]. There is a CMakeLists.txt file in the git root folder, so.. started VS > File > Open > Folder... C:\Repos\OpenSmalltalk\opensmalltalk-vm The CMake command run ([2]@2:13) was... C:\...\cmake.exe -G "Ninja" -DCMAKE_INSTALL_PREFIX:PATH="C:\Users\Ben\CMakeBuilds\...\x86-Debug" -DCMAKE_CXX_COMPILER="C:/.../MSVC/14.14.26428/bin/HostX86/x86/cl.exe" -DCMAKE_C_COMPILER="C:/.../MSVC/14.14.26428/bin/HostX86/x86/cl.exe" -DCMAKE_BUILD_TYPE="Debug" -DCMAKE_MAKE_PROGRAM="C:\...\CMAKE\Ninja\ninja.exe" "C:\Repos\OpenSmalltalk\opensmalltalk-vm" I changed the cmake configuration [2@2:27] to "x64-Debug". For debug target [2@3:00] I chose "pharo.exe" Hey, thats pretty cool [2@4:05] that switching between targets changes the highlighting of #ifdef code. I had a moment when I was missing the "Debug and Launch Settings" menu item [2@4:40-4:55] and mentioned at [4], but maybe there was some clash with previously experimenting with git cloning opensmalltalk-vm from inside VS. After closing VS and reopening my cmd.exe git'd opensmalltalk-vm it showed up, but I didn't change any settings there. Then (with x64-Debug & pharo.exe selected) I went Cmake > Build All ==> 10 Errors, 9 Warnings, which I'll discuss in a followup post. cheers -ben [2] https://blogs.msdn.microsoft.com/vcblog/2016/10/05/cmake-support-in-visual-… [3] https://docs.microsoft.com/en-us/visualstudio/install/modify-visual-studio [4] https://blogs.msdn.microsoft.com/vcblog/2016/12/20/cmake-support-in-visual-… [5] https://developercommunity.visualstudio.com/content/problem/234808/cmake-de…

6 22

Streams and FileDialog in Pharo 6 and 7
by Torsten Bergmann Nov. 11, 2018

Nov. 11, 2018

Hi, A question to those who worked on the new streams for Pharo 7: In PHARO 6 I used the following expression to open a file dialog and let the user choose a binary file: s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). This returned - either nil (when file dialog was canceled) - a "MultiByteFileStream" instance when a file was selected The MultiByteFileStream instance already had the name of the file (= full path) and I was able to query it for further use: s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). s name inspect (for instance to display which file is processed in a window by showing the full path) Now in PHARO 7 same expression returns an instance of ZnCharacterReadStream (as MultiByteFileStream is deprecated): s := UITheme builder fileOpen: 'Choose a file' extensions: #('exe'). and ZnCharacterReadStream does not understand #name - and in fact the info about the name is totally lost/not available. To me this looks missing/broken. So what is the recommended way in Pharo 7 to open a file dialog, let the use choose a file and get a file stream but also the name? IMHO this is either broken or missing... Thanks T.

6 10

PharoLauncher : Image version determination error
by Julien Nov. 9, 2018

Nov. 9, 2018

Hello, Is there something wrong with the latest Pharo 7.0 32bits image? I got this error from Pharo Launcher: Cannot determine image version: image version file not found! Try to run this command in a shell to get more information on the problem: cd "/Users/julien/Documents/Pharo/vms/private/6521/Pharo.app/Contents/MacOS" && "/Users/julien/Documents/Pharo/vms/private/6521/Pharo.app/Contents/MacOS/Pharo" --headless "/Users/julien/Documents/Pharo/images/RTFExperiment-Iceberg/RTFExperiment-Iceberg.image" eval "(Smalltalk imagePath asFileReference parent) / 'pharo.version' writeStreamDo: [ :stream | |major minor| major := SystemVersion current major. minor := SystemVersion current minor. (major = 6 and: [ SystemVersion current highestUpdate >= 60509 ]) ifTrue: [ minor := 1 ]. stream << major asString; << minor asString ]" When trying to start it. If I run this script in the terminal, nothing is print but the process crashes returning 1 as exit code. Can someone relate this issue as well? Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40

9 20

[ANN] The STON Specification
by Sven Van Caekenberghe Nov. 6, 2018

Nov. 6, 2018

Hi, Since there can never be enough documentation I finally took some time to write a more formal description of STON as a data format. https://github.com/svenvc/ston/blob/master/ston-spec.md The idea is to let this stabilise a bit and to then update the two other documents describing STON, where necessary: https://github.com/svenvc/ston/blob/master/ston-paper.md https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… Also, the latest changes in STON have to make their way to the Pharo image as well. https://github.com/svenvc/ston All feedback is welcome. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

5 8

[ANN] 22477 DelayScheduler cleanup and refactoring [was: Where do we go now ?]
by Ben Coman Nov. 5, 2018

Nov. 5, 2018

On Fri, 13 Apr 2018 at 13:56, Benoit St-Jean via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Do we really need 8 delay schedulers (DelayMicrosecondScheduler, > DelayMillisecondScheduler, DelayNullScheduler, > DelayExperimentalSpinScheduler, DelaySpinScheduler, DelayTicklessScheduler, > DelayExperimentalCourageousScheduler, DelayExperimentalSemaphoreScheduler) > ? > I've cleaned the delay scheduling subsystem [1] to condense these alternatives and separate orthogonal functionality. After a couple of reviews this was integrated and made active in last week's Build 1273. Could anyone with test scenarios from previous issues with delays have a bash at stressing the latest build. The old(existing) DelaySpinScheduler remains in the system so it can be activated as a point of comparison (System > Settings > System > Delay Scheduler). Pending any adverse reports the final step will be to remove the old hierarchy next week. There remain separate mutex and semaphore based schedulers since: * they differ by only a couple of overridden methods * their slightly different implementations help highlight the core algorithm * they provide a simple in-Image example of different synchronisation mechanisms. * in isolating edge cases its useful to be able to compare results between implementations I've retained both microsecond and millisecond operation, but extracted into "ticker" classes orthogonal to the "scheduling" classes since: * it makes the core scheduling algorithm independent of time base * millisecond (or other custom) timebase might(?) be more efficient on smaller 32-bit embedded systems * tests can now simulate ticker time to avoid tests interfering with system's-active-scheduler VM interaction (which may be the source of some random CI failures) * delay scheduler tests are now independent of real-time (which may be the source of some random CI failures where delays are affected by varying CI server loads) * when multi-threaded FFI callbacks become available, may facilitate experimenting with: * wake-up from native timers * wake-up of embedded Pharo from the encompassing system Other refactors: * during system snapshot, save/restore of resumption times was happening at user priority which risks a race condition reported at [2]. *All* modification of resumption times now occurs at timing/highest priority. [1] https://pharo.manuscript.com/f/cases/22477/DelayScheduler-cleanup-and-refac… [2] https://pharo.manuscript.com/f/cases/18359/

5 6

Where to discuss strategies and tools for a comeback of Smalltalk using Scratch as entrance
by Bernhard HÃ¶fner Nov. 2, 2018

Nov. 2, 2018

> Hello Group. I like to discuss about the subject and have also some ideas. But I want to ask first for the proper list within the forum. I heard that there is a discussion ongoing and want to participate. > > I will send this question to Squeak and Pharo usegroup and to the Phratch-developer. I assume that there is a common discussion about the subject. Hopefully there is no need to open on each platform an individual thread. > > Regards, Bernhard

2 2

Source/changes file suffixes constants
by Sven Van Caekenberghe Nov. 1, 2018

Nov. 1, 2018

Hi, Current FileStream holds (in the protocol 'file reader services') some constants regarding source/changes file suffixes. Where should we move these to (as FileStream is deprecated) ? There is a class SourceFile, there is PharoFilesOpener, neither seems to fit that well. Suggestions ? Sven

2 2

ClyMethodGroup>>#fileOut dead code ?
by Sven Van Caekenberghe Nov. 1, 2018

Nov. 1, 2018

Hi, ClyMethodGroup>>#fileOut seems like dead code (it sends #trailer to a WriteStream which DNUs). It also uses the deprecated FileStream. Can it be removed ? Sven

3 2

glamorous toolkit alpha.2
by Tudor Girba Oct. 31, 2018

Oct. 31, 2018

Hi, Glamorous Toolkit has evolved quite a bit over the past months, and we now would like to announce that we reached alpha.2 version. It runs on top of Pharo 7: feenk.com/gt There quite a number of new things. Some highlights are: - We added extensive documentation for GT, Bloc and Brick. By running "GtWorld openTourâ you essentially transform the image into an elaborate wiki. - We worked on Coder, a new set of tools that are dedicated for affecting code. For example, in the picture below we see an editor on embedded examples that can be edited and run independently. And this one shows how we can visualize and edit the result of querying. Just a note: To make Coder work the way we want, we extended Brick with several widgets, and enhanced significantly the linear and grid layouts. - We added the first version of xdoc in order to serialize the Playground every time you evaluate something. As always, we are looking forward to your feedback. Have fun, The feenk team -- www.feenk.com -- www.feenk.com "Every thing should have the right to be different."

1 0

About #zipped / #unzipped
by Sven Van Caekenberghe Oct. 31, 2018

Oct. 31, 2018

Hi, Given https://pharo.fogbugz.com/f/cases/21858/Cleanup-remaining-DeprecatedFileSys… [where we need more help !!] I found String>>#zipped to be one of the users of the deprecated RWBinaryOrTextStream. Although this usage is easy enough to fix, I think the current #zipped / #unzipped on String is broken. (note also that there are no real users of these methods) Right now it seems cool that the following is an identity. 'foobar' zipped unzipped. However, the result of zipping something is actual something binary (a collection of opaque bytes). Thinking of it, the input is actually also bytes, not unencoded characters. Of course, the current methods are broken, as can be seen from a more complex (wide) string. 'Ã©lÃ¨ves FranÃ§aises @ 10 â¬' zipped unzipped. >>> <something very weird> The error results from some implicit/wrong character encoding being used. The right way to do this is to explicitly encode/decode the string. (GZipReadStream on: (ByteArray streamContents: [ :out | (GZipWriteStream on: out) nextPutAll: 'Ã©lÃ¨ves FranÃ§aises Ã 10 â¬' utf8Encoded; close ])) upToEnd utf8Decoded. >From this it would follow that #zipped / #unzipped would make more sense on ByteArray. So that the above identity would become. 'Ã©lÃ¨ves FranÃ§aises Ã 10 â¬' utf8Encoded zipped unzipped utf8Decoded. This change of signature would be comparable to what we recently did with #base64Encoded / #base64Decoded What do you think ? Sven

3 3

[Pharo 7.0-dev] Build #1358: 22608-Deprecate-FileDialog-methods-that-open-streams
by ci-pharo-ci-jenkins2＠inria.fr Oct. 31, 2018

Oct. 31, 2018

There is a new Pharo build available! The status of the build #1358 was: FAILURE. The Pull Request #1941 was integrated: "22608-Deprecate-FileDialog-methods-that-open-streams" Pull request url: https://github.com/pharo-project/pharo/pull/1941 Issue Url: https://pharo.fogbugz.com/f/cases/22608 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1357: Added a guard in LinkedList>>sort: that directly returns self if the â¦
by ci-pharo-ci-jenkins2＠inria.fr Oct. 31, 2018

Oct. 31, 2018

There is a new Pharo build available! The status of the build #1357 was: SUCCESS. The Pull Request #1921 was integrated: "Added a guard in LinkedList>>sort: that directly returns self if the â¦" Pull request url: https://github.com/pharo-project/pharo/pull/1921 Issue Url: https://pharo.fogbugz.com/f/cases/22587 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1356: Adding class OCCompilerDynamicASTPlugin (and its test class), allowiâ¦
by ci-pharo-ci-jenkins2＠inria.fr Oct. 31, 2018

Oct. 31, 2018

There is a new Pharo build available! The status of the build #1356 was: FAILURE. The Pull Request #1920 was integrated: " Adding class OCCompilerDynamicASTPlugin (and its test class), allowiâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/1920 Issue Url: https://pharo.fogbugz.com/f/cases/DynamicCompilerPlugins Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1355: 22466-Add-readWriteStream-and-readWriteStreamDo-in-FileSystem
by ci-pharo-ci-jenkins2＠inria.fr Oct. 31, 2018

Oct. 31, 2018

There is a new Pharo build available! The status of the build #1355 was: FAILURE. The Pull Request #1924 was integrated: "22466-Add-readWriteStream-and-readWriteStreamDo-in-FileSystem" Pull request url: https://github.com/pharo-project/pharo/pull/1924 Issue Url: https://pharo.fogbugz.com/f/cases/22466 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1354: 22617-MemoryFileWriteStreamclose-doesnt-flush
by ci-pharo-ci-jenkins2＠inria.fr Oct. 31, 2018

Oct. 31, 2018

There is a new Pharo build available! The status of the build #1354 was: SUCCESS. The Pull Request #1946 was integrated: "22617-MemoryFileWriteStreamclose-doesnt-flush" Pull request url: https://github.com/pharo-project/pharo/pull/1946 Issue Url: https://pharo.fogbugz.com/f/cases/22617 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1353: REVERT-22239-DataAndTimeTesttestAsDateAndTime-is-meaningful
by ci-pharo-ci-jenkins2＠inria.fr Oct. 30, 2018

Oct. 30, 2018

There is a new Pharo build available! The status of the build #1353 was: FAILURE. The Pull Request #1945 was integrated: "REVERT-22239-DataAndTimeTesttestAsDateAndTime-is-meaningful" Pull request url: https://github.com/pharo-project/pharo/pull/1945 Issue Url: https://pharo.fogbugz.com/f/cases/REVERT Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1352: 21667-Dropping-a-mcz-on-image-raises-an-error
by ci-pharo-ci-jenkins2＠inria.fr Oct. 30, 2018

Oct. 30, 2018

There is a new Pharo build available! The status of the build #1352 was: FAILURE. The Pull Request #1939 was integrated: "21667-Dropping-a-mcz-on-image-raises-an-error" Pull request url: https://github.com/pharo-project/pharo/pull/1939 Issue Url: https://pharo.fogbugz.com/f/cases/21667 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1351: 22615-Random-Core-can-be-removed-form-the-manual-dependencies-list-of-Collections-String
by ci-pharo-ci-jenkins2＠inria.fr Oct. 29, 2018

Oct. 29, 2018

There is a new Pharo build available! The status of the build #1351 was: FAILURE. The Pull Request #1944 was integrated: "22615-Random-Core-can-be-removed-form-the-manual-dependencies-list-of-Collections-String" Pull request url: https://github.com/pharo-project/pharo/pull/1944 Issue Url: https://pharo.fogbugz.com/f/cases/22615 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1350: 22499-modifying-a-method-in-a-trait-that-is-aliased-in-a-class-is-not-propagated-correctly-
by ci-pharo-ci-jenkins2＠inria.fr Oct. 29, 2018

Oct. 29, 2018

There is a new Pharo build available! The status of the build #1350 was: FAILURE. The Pull Request #1938 was integrated: "22499-modifying-a-method-in-a-trait-that-is-aliased-in-a-class-is-not-propagated-correctly-" Pull request url: https://github.com/pharo-project/pharo/pull/1938 Issue Url: https://pharo.fogbugz.com/f/cases/22499 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Esteban's ChangeLog week of 22 October 2018
by estebanlm＠gmail.com Oct. 29, 2018

Oct. 29, 2018

Hello! This is my weekly ChangeLog, from 22 October 2018 to 28 October 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=22/10/2018&to=28/10/2018 ChangeLog ========= 22 October 2018: ---------------- * I (finally) finnished couple of PRs for Calypso! * [Issue 304](https://github.com/pharo-ide/Calypso/pull/346) * [Issue 335](https://github.com/pharo-ide/Calypso/pull/348) This two are the content of my work of last week. It was complicated to understand the model behind calypso and that took more time than preview. A bit of an explanation: 1. First one eliminates the extension that takes +Traits+ as if they would be superclasses of somekind. While I understand what Denis tried to do here, the premise he took is wrong: traits are not a multiple inheritance mechanism (even if they can be used to simulate it), traits are a *composition* strategy (and there is a trait composition arithmetic that is somekind complex that needs to be taken into account). As a result, the price of simulating a multiple-inheritance scenario where there is not was complexifying the model at levels way higher than desired. Also it was not working properly and patching it to make it work was resulting on re-writing all the trait arithmetic at UI level. So the right approach here is just to remove. And to be clear: I'm not oposed to the existence of a plugin that hides methods comming from traits (even if I think is incorrect because once a trait is applied, those methods actually 'belong' to the class). But in case you want something like this, it can be implemented in a much simpler way by not mixing what a superclass and a trait is. 2. Second PR also eliminates something :) This time I eliminate the inclusion of metaclasses in the extension list while displaying a package. Again, I understand what Denis tried to do: to easy the view of which classes are extended in the class side and the ones that are extended in instance side. Problem with thid is that it was breaking completely the cognitive model the system browser offers, which is already complex enough to add also an exceptional behaviour. Anyway, this list now works as before: if there are extensions classes are shown and to see the class side extensions you need to click in class side option. cheers! Esteban

1 0

Re: [Pharo-dev] Xcode projects for VM on iOS or Mac?
by John M McIntosh Oct. 29, 2018

Oct. 29, 2018

Although xCode makes much of that process easier it is just a GUI front end for a bunch of command line tools. You can re-sign and submit an app from the command line for enterprise usage, no doubt the same for the store. Apple at one time had a utility app to submit apps to the store for people needed to sub 100âs of apps at a time. .... John M. McIntosh. Corporate Smalltalk Consulting Ltd https://www.linkedin.com/in/smalltalk On Sun, Oct 28, 2018 at 21:04, Todd Blanchard via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > I'm more about wanting an iOS VM and to do that you need to build and sign through Apple's tool set as far as I know. > > And the debugging experience is much more pleasant - especially when making FFI calls into Apple's system libraries. > > CMake can build an Xcode project from a CMake build system I believe. At least there is a cross platform marine navigation project called OpenCPN (written in C++ and which relies on wxWidgets) that does this. > > So I'm not arguing to have the official builds in Xcode, but if you want to build an app and ship it on iPhone or Mac, Xcode is the build system you are going to need to submit it to the App store. > >> On Oct 28, 2018, at 12:27 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >> Hi Todd, >> >> On Fri, Oct 26, 2018 at 10:00 AM Todd Blanchard via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: >> >>> Does anyone have Xcode projects for building the VM on iOS or Mac? Can they share them or give me some tips for setting one up? >> >> First I'd like to know your use case. I presume it;'s for debugging, but it may be more for browsing. Can you say? (Personally I find raw lldb adequate for debugging). >> >> Second, my reasons for not using Xcode projects for building the Mac VMs are that >> - Xcode projects, being a serialization of an object graph, are difficult to edit, and they offer no parameterisation, so whereas there is one small set of makefiles (8 in all) for all of the 32-bit and 64-bit builds on Mac, there had to be a separate Xcode project for each build. When adding Spur this was simply unsupportable >> - clearly Xcode is not necessary for building, browsing, or debugging; people are able to accomplish all three tasks using other tools >> >> However, I do appreciate that Xcode is a more pleasant and higher-level GUI interface than the shell, make, lldb and one's favorite editor. What I would support is a tool that created an Xcode project from Makefiles; such tools used to exist. I'd love to see such a tool. What I will fight against until my dying breath is any attempt to replace the Makefile based build system with Xcode. I hope the reasons above justify why. >> >> _,,,^..^,,,_ >> best, Eliot

1 0

Re: [Pharo-dev] Xcode projects for VM on iOS or Mac?
by Eliot Miranda Oct. 29, 2018

Oct. 29, 2018

Hi Todd, On Fri, Oct 26, 2018 at 10:00 AM Todd Blanchard via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > Does anyone have Xcode projects for building the VM on iOS or Mac? Can > they share them or give me some tips for setting one up? > First I'd like to know your use case. I presume it;'s for debugging, but it may be more for browsing. Can you say? (Personally I find raw lldb adequate for debugging). Second, my reasons for not using Xcode projects for building the Mac VMs are that - Xcode projects, being a serialization of an object graph, are difficult to edit, and they offer no parameterisation, so whereas there is one small set of makefiles (8 in all) for all of the 32-bit and 64-bit builds on Mac, there had to be a separate Xcode project for each build. When adding Spur this was simply unsupportable - clearly Xcode is not necessary for building, browsing, or debugging; people are able to accomplish all three tasks using other tools However, I do appreciate that Xcode is a more pleasant and higher-level GUI interface than the shell, make, lldb and one's favorite editor. What I would support is a tool that created an Xcode project from Makefiles; such tools used to exist. I'd love to see such a tool. What I will fight against until my dying breath is any attempt to replace the Makefile based build system with Xcode. I hope the reasons above justify why. _,,,^..^,,,_ best, Eliot

2 1

Open Croquet will ahve issues in next version of Mac OS X
by LawsonEnglish Oct. 28, 2018

Oct. 28, 2018

https://blog.krestianstvo.org/en/open-croquet-for-squeak-6/ <https://blog.krestianstvo.org/en/open-croquet-for-squeak-6/> This sounds really cool, but thereâs an issue coming up: Apple is doing away with ANY support for 32-bit apps and plugins and of course, Croquet is built for 32-bits and uses 32-bit plugins all over the place. Croquet could STILL be the killer-app for Smalltalk even though it never realized its potential in the past, and it wonât be able to if something isnât done about the looming 32-bit vs 64-bit issue. Need I point out that it should work on Pharo just the same way it does on Squeak? L

2 1

Re: [Pharo-dev] Xcode projects for VM on iOS or Mac?
by Esteban Lorenzano Oct. 27, 2018

Oct. 27, 2018

Iâm sorry I forget to answer your mail :( Anyway, my response was not something you wanted to hear: I maintained the iOS version of the VM and up to three years ago (before spur) it was working, but I didnât try it since a lot of time and most of the work I did (who was based in CMakeMaker) is now not used anymore so I do not think they will work âout of the boxâ if needed. I find sad that we have to depend on otherâs Xcode projects to being able to do something, but wellâ¦ is better than nothing :) Esteban > On 26 Oct 2018, at 19:55, Todd Blanchard via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Todd Blanchard <tblanchard(a)mac.com> > Subject: Re: [Pharo-dev] Xcode projects for VM on iOS or Mac? > Date: 26 October 2018 at 19:55:24 CEST > To: John M McIntosh <johnmci(a)smalltalkconsulting.com>, Pharo Development List <pharo-dev(a)lists.pharo.org> > > > That would be super awesome! Please let me know if/when you do. > > Thanks, > -Todd Blanchard > >> On Oct 26, 2018, at 9:43 AM, John M McIntosh <johnmci(a)smalltalkconsulting.com <mailto:johnmci@smalltalkconsulting.com>> wrote: >> >> I have one. I should see about adding it to a branch. >> >> .... >> John M. McIntosh. Corporate Smalltalk Consulting Ltd https://www.linkedin.com/in/smalltalk <https://www.linkedin.com/in/smalltalk> >> >> >> >> >> On Fri, Oct 26, 2018 at 09:39, Todd Blanchard via Pharo-dev <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> wrote: >>> Does anyone have Xcode projects for building the VM on iOS or Mac? Can they share them or give me some tips for setting one up? >>> >>> Thanks, >>> -Todd > > >

1 0

Re: [Pharo-dev] Xcode projects for VM on iOS or Mac?
by John M McIntosh Oct. 26, 2018

Oct. 26, 2018

I have one. I should see about adding it to a branch. .... John M. McIntosh. Corporate Smalltalk Consulting Ltd https://www.linkedin.com/in/smalltalk On Fri, Oct 26, 2018 at 09:39, Todd Blanchard via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > Does anyone have Xcode projects for building the VM on iOS or Mac? Can they share them or give me some tips for setting one up? > > Thanks, > -Todd

2 1

Xcode projects for VM on iOS or Mac?
by Todd Blanchard Oct. 26, 2018

Oct. 26, 2018

Does anyone have Xcode projects for building the VM on iOS or Mac? Can they share them or give me some tips for setting one up? Thanks, -Todd

1 0

Effect Handlers
by Eliot Miranda Oct. 26, 2018

Oct. 26, 2018

Hi All, I found this write up instructive and well-written: https://www.quora.com/What-are-some-features-youd-want-a-new-programming-la… _,,,^..^,,,_ (phone)

1 0

[Pharo 7.0-dev] Build #1349: 22602-Add-spec-demos-to-help-menu
by ci-pharo-ci-jenkins2＠inria.fr Oct. 26, 2018

Oct. 26, 2018

There is a new Pharo build available! The status of the build #1349 was: SUCCESS. The Pull Request #1936 was integrated: "22602-Add-spec-demos-to-help-menu" Pull request url: https://github.com/pharo-project/pharo/pull/1936 Issue Url: https://pharo.fogbugz.com/f/cases/22602 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1348: 22512-Test-runner-browse-method-does-not-work
by ci-pharo-ci-jenkins2＠inria.fr Oct. 26, 2018

Oct. 26, 2018

There is a new Pharo build available! The status of the build #1348 was: SUCCESS. The Pull Request #1937 was integrated: "22512-Test-runner-browse-method-does-not-work" Pull request url: https://github.com/pharo-project/pharo/pull/1937 Issue Url: https://pharo.fogbugz.com/f/cases/22512 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1347: 22567 - Moved back Array2D and its test into collection packages.
by ci-pharo-ci-jenkins2＠inria.fr Oct. 23, 2018

Oct. 23, 2018

There is a new Pharo build available! The status of the build #1347 was: SUCCESS. The Pull Request #1919 was integrated: "22567 - Moved back Array2D and its test into collection packages." Pull request url: https://github.com/pharo-project/pharo/pull/1919 Issue Url: https://pharo.fogbugz.com/f/cases/22567 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

STON updates/improvements
by Sven Van Caekenberghe Oct. 23, 2018

Oct. 23, 2018

Hi, I have consolidated all repositories where STON code lives so that they are now all in sync, and in sync with changes from Pharo 7. http://ss3.gemtalksystems.com/ss/STON/ http://smalltalkhub.com/mc/SvenVanCaekenberghe/STON/main/ https://github.com/svenvc/ston There are 2 CI builds https://travis-ci.org/svenvc/ston https://ci.inria.fr/pharo-contribution/job/STON/ The project's format will remain FileTree (until Tonel is supported on other Smalltalk implementations). Last week I applied a couple of changes that I wanted to apply for a long time. Traits are no longer used in the implementation (which should help porting to other Smalltalk implementations). More specifically the following are used (again) - Class>>#stonOn: - ClassDescription>>#stonContainsSubObjects - Metaclass>>#stonName - Metaclass>>#stonOn: instead of - TClass>>#stonOn: - TClassDescription>>#stonContainsSubObjects - TApplyingOnClassSide>>#stonName - TApplyingOnClassSide>>#stonOn: use #instanceSide instead of #theNonMetaClass in MetaClass>>#stonOn: Reorganised the packages with sub tags. Add support for Fraction and ScaledDecimal literals (not in JSON mode). Previously a float conversion meant there was a loss of information. Change the representation of Date to include a timezone offset (since the current Date implementation is sensitive to this). 2018-10-11Z 2018-10-11+00:00 2018-10-11+02:00 A missing timezone offset is interpreted as being the local timezone offset. Add more special representations for common value style objects. One of STON's goals is to be a human readable and human editable representation of an object graph while remaining 100% correct (not losing information). The following were added for this reason: MimeType and URL using ZnMimeType and ZnUrl respectively as simplified values. MimeType['application/json'] URL['https://pharo.org'] Color Color[#red] Color{#red:1.0,#green:0.0,#blue:0.0,#alpha:0.4} FileReferences to the DiskFileSystem (effectively normal files) FILE['/tmp/foo.txt'] Here is an example of how much difference that makes. Given the following Dictionary { #background->Color red. #workdir->'/tmp/pharo/work/' asFileReference. #home->'https://pharo.org/experimental' asUrl. #datatype->'application/json' asMIMEType } asDictionary Which contains real objects as its values. was serialised by STON BEFORE the changes as { #datatype : ZnMimeType { #main : 'application', #sub : 'json' }, #background : Color { #rgb : 1072693248, #cachedDepth : 32, #cachedBitPattern : Bitmap [ 4294901760 ], #alpha : 255 }, #home : ZnUrl { #scheme : #https, #host : 'pharo.org', #segments : OrderedCollection [ 'experimental' ] }, #workdir : FileReference { #filesystem : FileSystem { #store : MacStore { #maxFileNameLength : 255 } }, #path : AbsolutePath [ 'tmp', 'pharo', 'work' ] } } which is 100% correct, but not very human friendly. Now, AFTER the changes, the STON serialisation looks as follows: { #datatype : MimeType [ 'application/json' ], #background : Color [ #red ], #home : URL [ 'https://pharo.org/experimental' ], #workdir : FILE [ '/tmp/pharo/work' ] } which is a huge improvement, IMO. What do you think ? Comments, feedback, remarks ? Any other suggestions for other object that could use this treatment ? Sven

5 11

[Pharo 7.0-dev] Build #1346: 22585 Tag ManifestSystemSupport and related classes in System-Support
by ci-pharo-ci-jenkins2＠inria.fr Oct. 23, 2018

Oct. 23, 2018

There is a new Pharo build available! The status of the build #1346 was: FAILURE. The Pull Request #1931 was integrated: "22585 Tag ManifestSystemSupport and related classes in System-Support" Pull request url: https://github.com/pharo-project/pharo/pull/1931 Issue Url: https://pharo.fogbugz.com/f/cases/22585 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1345: 22598 Tag ManifestManifestTests and other classes in Manifest-Tests
by ci-pharo-ci-jenkins2＠inria.fr Oct. 23, 2018

Oct. 23, 2018

There is a new Pharo build available! The status of the build #1345 was: FAILURE. The Pull Request #1934 was integrated: "22598 Tag ManifestManifestTests and other classes in Manifest-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/1934 Issue Url: https://pharo.fogbugz.com/f/cases/22598 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1344: 22599 Tag ManifestPharoBootstrapInitialization and related classes
by ci-pharo-ci-jenkins2＠inria.fr Oct. 23, 2018

Oct. 23, 2018

There is a new Pharo build available! The status of the build #1344 was: SUCCESS. The Pull Request #1935 was integrated: "22599 Tag ManifestPharoBootstrapInitialization and related classes" Pull request url: https://github.com/pharo-project/pharo/pull/1935 Issue Url: https://pharo.fogbugz.com/f/cases/22599 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1343: 22593-GZipReadStream-enhancement-Pharo-7-streams-and-tests
by ci-pharo-ci-jenkins2＠inria.fr Oct. 23, 2018

Oct. 23, 2018

There is a new Pharo build available! The status of the build #1343 was: SUCCESS. The Pull Request #1929 was integrated: "22593-GZipReadStream-enhancement-Pharo-7-streams-and-tests" Pull request url: https://github.com/pharo-project/pharo/pull/1929 Issue Url: https://pharo.fogbugz.com/f/cases/22593 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1342: 22223 Categorize classes in System-Changes
by ci-pharo-ci-jenkins2＠inria.fr Oct. 23, 2018

Oct. 23, 2018

There is a new Pharo build available! The status of the build #1342 was: FAILURE. The Pull Request #1930 was integrated: "22223 Categorize classes in System-Changes" Pull request url: https://github.com/pharo-project/pharo/pull/1930 Issue Url: https://pharo.fogbugz.com/f/cases/22223 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1341: 22591-MoticellowarnAboutLosingChangesTo-is-dead-code
by ci-pharo-ci-jenkins2＠inria.fr Oct. 22, 2018

Oct. 22, 2018

There is a new Pharo build available! The status of the build #1341 was: FAILURE. The Pull Request #1927 was integrated: "22591-MoticellowarnAboutLosingChangesTo-is-dead-code" Pull request url: https://github.com/pharo-project/pharo/pull/1927 Issue Url: https://pharo.fogbugz.com/f/cases/22591 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Next Pharo Sprint: Oct 26
by Marcus Denker Oct. 22, 2018

Oct. 22, 2018

We will organize a Pharo sprint / Moose dojo Oct 26, starting at 10:00am. (Local Time Paris). Goals of this sprint: â¢ Pharo 7 issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events Known Local Sprint meetings Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come https://association.pharo.org/event-2973622

1 0

Pharo Memcached client
by Sven Van Caekenberghe Oct. 18, 2018

Oct. 18, 2018

Hi, I copied the (Pharo) Memcached client to https://github.com/svenvc/memcached where is lives in Tonel format with a Baseline and a working Travis CI build against an actual memcached server in the worker. More about memcached - https://en.wikipedia.org/wiki/Memcached - http://memcached.org Acknowledgements The original project can be found at http://www.squeaksource.com/memcached.html As far as I can see it was written by Philippe Marschall and Ramon Leon. I ported the codebase to Pharo. This repository is a recent copy with some cleanups. I intend to maintain this as I need it myself. The codebase should still maintain its original portability (minus the meta info, possibly). Sven

1 0

[Pharo 7.0-dev] Build #1340: 22575-GZipReadStream-classunzipto-results-in-an-Invalid-utf8-input-detected-error
by ci-pharo-ci-jenkins2＠inria.fr Oct. 18, 2018

Oct. 18, 2018

There is a new Pharo build available! The status of the build #1340 was: FAILURE. The Pull Request #1909 was integrated: "22575-GZipReadStream-classunzipto-results-in-an-Invalid-utf8-input-detected-error" Pull request url: https://github.com/pharo-project/pharo/pull/1909 Issue Url: https://pharo.fogbugz.com/f/cases/22575 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1339: 22590-Add-support-of-text-input-different-from-keystrokes
by ci-pharo-ci-jenkins2＠inria.fr Oct. 18, 2018

Oct. 18, 2018

There is a new Pharo build available! The status of the build #1339 was: SUCCESS. The Pull Request #1923 was integrated: "22590-Add-support-of-text-input-different-from-keystrokes" Pull request url: https://github.com/pharo-project/pharo/pull/1923 Issue Url: https://pharo.fogbugz.com/f/cases/22590 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

M2 research internship
by Jannik Laval GMail Oct. 18, 2018

Oct. 18, 2018

Dear Smalltalkers, We are proposing 3 master internships about message monitoring and IoT. The development will be made in Pharo / Moose. You can find the offers on the lab's website: https://disp-lab.fr/?q=job. Internship position <https://www.disp-lab.fr/?q=content/m2-internship-monitoring-and-evaluation- exchanges-distributed-information-system> M2 Internship: Monitoring and evaluation of exchanges in a distributed information system 21 December 2018 Internship position <https://www.disp-lab.fr/?q=content/m2-internship-monitoring-application-exc hanges-iot-system> M2 Internship: Monitoring of application exchanges with an IoT system 21 December 2018 Internship position <https://www.disp-lab.fr/?q=content/m2-internship-production-dynamic-dashboa rds-monitoring-exchanges-distributed-information> M2 Internship: Production of dynamic dashboards for monitoring the exchanges of a distributed information system Please distribute to students who may be affected. Best regards -- ~~Jannik Laval~~ Enseignant-chercheur Responsable PÃ©dagogique Licence Coordonnateur de Projet IUT LumiÃ¨re, UniversitÃ© LumiÃ¨re Lyon 2 laboratoire DISP +33 4 78 77 43 06 <http://www.jannik-laval.eu> http://www.jannik-laval.eu <http://www.phratch.com> http://www.phratch.com <http://www.approchealpes.info> http://www.approchealpes.info

1 0

MemoryFileSystem
by Sven Van Caekenberghe Oct. 17, 2018

Oct. 17, 2018

Hi, In MemoryFileSystem the class MemoryWriteStream seems dead code. Agreed ? In class MemoryFileWriteStream the IV writeStream seems to be used and could be removed. Agreed ? MemoryFileWriteStream>>#close must first do a #flush. Right ? I need these for fixing https://pharo.fogbugz.com/f/cases/22466/Add-readWriteStream-and-readWriteSt… but these are actually a bit independent. Sven

1 0

[Pharo 7.0-dev] Build #1338: 22564-Spec-tests-has-a-class-that-need-to-be-moved-to-deprecated-pacakage
by ci-pharo-ci-jenkins2＠inria.fr Oct. 15, 2018

Oct. 15, 2018

There is a new Pharo build available! The status of the build #1338 was: SUCCESS. The Pull Request #1918 was integrated: "22564-Spec-tests-has-a-class-that-need-to-be-moved-to-deprecated-pacakage" Pull request url: https://github.com/pharo-project/pharo/pull/1918 Issue Url: https://pharo.fogbugz.com/f/cases/22564 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1337: 22564-Spec-tests-has-a-class-that-need-to-be-moved-to-deprecated-pacakage
by ci-pharo-ci-jenkins2＠inria.fr Oct. 15, 2018

Oct. 15, 2018

There is a new Pharo build available! The status of the build #1337 was: FAILURE. The Pull Request #1918 was integrated: "22564-Spec-tests-has-a-class-that-need-to-be-moved-to-deprecated-pacakage" Pull request url: https://github.com/pharo-project/pharo/pull/1918 Issue Url: https://pharo.fogbugz.com/f/cases/22564 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0