February 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Any idea for a cool name for the remote tool suite?

by phil＠highoctane.be

Reach remote worlds with Pharocket! Phil On Thu, Feb 23, 2017 at 10:35 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Philippe invented new word Pharocket :). Maybe it is the best for this > project? > > > 2017-01-30 17:09 GMT+01:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > >> Also I think its fair that the guy that wrote the code to pick the name, >> its his baby afterall, whether he is paid for it or not. He earned that >> right. >> >> On Mon, Jan 30, 2017 at 6:06 PM Dimitris Chloupis <kilon.alios(a)gmail.com> >> wrote: >> >>> Just for the record, the name does not matter >>> >>> As a matter of fact if you want the name to really sell the library/ >>> tools then the last thing you want is a name that makes any logical sense >>> >>> You have much better chance to catch attention with "Pink Elephant" than >>> "Pharo Remote tools" or whatever >>> >>> illogical names monopolise the software market >>> >>> Python >>> Ruby on Rails >>> Django >>> Blender >>> Unreal >>> Unity >>> Javascript >>> Java >>> C >>> C++ >>> Windows >>> MacOS >>> >>> and so on >>> >>> Developers choose to name their projects the craziest names and wisely so >>> >>> the name is there to catch attention, not to make sense or come up top >>> on google search. >>> >>> In the end what it matters is the code itself. >>> >>> Ruby On Rails did not become populary because we love ruby stones or we >>> love go "too...tooooooo" on rails ... its popular because the library has >>> been very useful to many people. >>> >>> And the name itself guarantees that it wont come up top in google search >>> because it has nothing unique about it. >>> >>> The rest is just marketing ;) >>> >> >

Feb. 23, 2017

Why do we have doublequoting for "?

by stepharong

about quoting ;( Hi I have a string '<li> Stéphane Ducasse and Damien Pollet, Fingerprints, Journal of Information System, 2010. </li> ' and when I do printIt in the debugger I get the following "'<li> Stéphane Ducasse and Damien Pollet, Fingerprints, Journal of Information System, 2010. </li> '" I do not get why we doublequote the character " inside string. It means that I have to remove all the " inside to string to be able to express tests. Stef

Feb. 23, 2017

Re: [Pharo-dev] Epicea - showing latest lost changes

by stepharong

I agree :) On Wed, 22 Feb 2017 18:10:35 +0100, Ben Coman <btc(a)openinworld.com> wrote: > One thing I am missing from Epicea that I used to be able to do > is being able to filter out old changes. If I've been thrashingsome > method back and forth between a few implementations,often I don't want > to see *all* the old changes,only the latest ones. > An option to restore old versions would also be nice, but I don't think > that feature existed previously. > > cheers -ben -- Using Opera's mail client: http://www.opera.com/mail/

Feb. 23, 2017

Raw pane on byteStrings

by stepharong

Hi I'm trying to debug citezen generation and I have to compare strings. Now I think that the raw views (in Pharo 50) is not good because we cannot see all the items in raw format. See the attachements. It jumps from 21 to 174 ... and what I want to see is of course in the middle. Is it me or there is something wrong there. Stef

Feb. 23, 2017

Re: [Pharo-dev] [Moose-dev] How ready is Bloc for a simple use-case?

by stepharong

Hi aliaksei I would love to start to play with Bloc to build a game with boxes. Now is there any tutorial that I can follow to get started? Stef > We could try to do it together and maybe even make a video (stream) of > implementation process :) > Cheers, > Alex > > On 22 February 2017 at 22:02, Aliaksei Syrel <alex.syrel(a)gmail.com> > wrote: >> Hi Peter >>>>> I wanted to ask about Bloc: >> Thanks for your interest :) >> >>>>> 1) how stable is the API? e.g. if some overhaul changes to >>>>> unify/whatever are planned >> >> Api itself is in "final" state, however naming might be improved >> (changed with or without depreciations). But don't worry user-side api >> is already in a very good shape, at least from our >>perspective :) >> >>>>> 2) I saw in the techtalk that you can align elements (to center, >>>>> bottom, ...), however is that possible with lines? Lines have to >>>>> rotate, morph shape, etc. >>> 3) Are non-straight lines possible? (e.g. bezier, arc) >>Exactly :) Lines are just bloc elements as anything else: buttons, text >> images. They can be linear, can be arcs or bezier curves (both >> quadratic or cubic). Default canvas used for rendering in >>Bloc >> (SpartaCanvas) has very good support of vector shapes and lines. >> >>>>> The idea for me is to make a simple mindmap >>> - elements with some text, icons, math symbols inside >>> - connectors (non-straight lines) between elements >> >> It is very doable. Please, don't forget that Bloc is a low level >> framework that does not contain any widgets (existing ones will be >> deleted, especially BlLine, BlText and BlTextElement). The only >> >>responsibility Bloc has is to provide a basic infrastructure that >> does not put any constraints on users. Which means that if you want to >> have a bezier line you have to subclass BlElement, >>implement >> corresponding accessors for anchor points and override >> drawPathOnSpartaCanvas: in order to display you line. You can learn >> more about canvas by checking SpartaCanvas class >>comment and method >> comments in 'api' protocol. >> >> Layouts, alignment, transformations are part of bloc and are available >> to all subclasses of BlElement. >> >> Cheers, >> Alex >> >> On 22 February 2017 at 21:32, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >>> Hi, >>> >>> I wanted to ask about Bloc: >>> >>> 1) how stable is the API? e.g. if some overhaul changes to >>> unify/whatever are planned >>> 2) I saw in the techtalk that you can align elements (to center, >>> bottom, ...), however is that possible with lines? Lines have to >>> rotate, morph shape, etc. >>> 3) Are non-straight lines possible? (e.g. bezier, arc) >>> >>> The idea for me is to make a simple mindmap >>> - elements with some text, icons, math symbols inside >>> - connectors (non-straight lines) between elements >>> >>> To me (apart from the lines) it seems like it should be already doable. >>> >>> Also either my (Morphic) Pharo is really slow, or Bloc (in the video) >>> is superfast (everything is happening instantly). >>> >>> Thanks, >>> Peter >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)list.inf.unibe.ch >>> https://www.list.inf.unibe.ch/listinfo/moose-dev >> > -- Using Opera's mail client: http://www.opera.com/mail/

Feb. 23, 2017

Re: [Pharo-dev] UnixOSProcessPlugin and accessing C array out of bounds

by stepharong

Thanks david! On Thu, 23 Feb 2017 03:00:08 +0100, David T. Lewis <lewis(a)mail.msen.com> wrote: > Holger, > > Good catch, thank you. There were two arrays dimensioned wrong in > OSProcessPlugin in > the Smalltalk slang source. I fixed this, and the warning should be gone > after the > sources are next generated. > > Esteban, > > I fixed the oscog branch also. I could not easily test it, but it is a > small change > so hopefully should be no problem when you next generate the plugin. > > Dave > > > On Wed, Feb 22, 2017 at 04:25:05PM +0700, Holger Freyther wrote: >> Hi Esteban, >> >> while building packages for OBS and going the compile warnings (one of >> the nice things of newer compilers is the increased diagnostic) I >> noticed this: >> >> [ 196s] >> /usr/src/packages/BUILD/src/plugins/UnixOSProcessPlugin/UnixOSProcessPlugin.c:4525:20: >> warning: iteration 64u invokes undefined behavior >> [-Waggressive-loop-optimizations] >> [ 196s] if ((semaIndices[sigNum]) > 0) { >> [ 196s] ^ >> [ 196s] >> /usr/src/packages/BUILD/src/plugins/UnixOSProcessPlugin/UnixOSProcessPlugin.c:4524:9: >> note: containing loop >> [ 196s] while (sigNum <= (signalArraySize())) { >> >> while (sigNum <= (signalArraySize())) { >> if ((semaIndices[sigNum]) > 0) { >> setSignalNumberhandler(sigNum, >> (originalSignalHandlers())[sigNum]); >> } >> sigNum += 1; >> } >> >> semaIndices has signalArraySize()/NSIG number of entries and is zero >> based, it is being accessed with sigNum==NSIG which means one entry >> beyond the memory of the array? Can you confirm this? >> >> restoreDefaultSignalHandlers >> "Restore signal handlers to their original behaviors." >> >> | sigNum | >> <returnTypeC: 'void'> >> semaIndices = nil "nil if in interpreter simulation" >> ifFalse: [sigNum := 1. >> [sigNum <= self signalArraySize] whileTrue: >> [((semaIndices at: sigNum) > 0) ifTrue: >> [self setSignalNumber: sigNum >> handler: (self originalSignalHandlers at: sigNum).]. >> sigNum := sigNum + 1]] >> >> So it is one based but the array doesn't have an extra element to make >> it work? How is this normally handled in slang code? >> >> >> holger > -- Using Opera's mail client: http://www.opera.com/mail/

Feb. 23, 2017

Re: [Pharo-dev] Build Pharo VM

by stepharong

Esteban can you add a todo to remove this readme? Stef On Thu, 23 Feb 2017 15:51:07 +0100, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> On 23 Feb 2017, at 15:33, Guido Chari <charig(a)gmail.com> wrote: >> >> Hi, >> >> I am trying to compile the Pharo-VM but I was not able. Neither in OSX >> nor in Unix. I followed the instructions on >> https://github.com/pharo-project/pharo-vm. In OSX the builder at >>the >> image level runs ok but I see no output at the build directory. In >> Unix, the files in the build directory were generated but then the >> building process fails because of some cmake >>files not found from one >> of the plugins. I am using the last version from the master repo. >> So my question is, any hints on what I am doing wrong? Are there any up >> to date documentation for building the vm? > > yes: everything :) > that instructions are very old and I still do not have time to fix themâ¦ > basically, if all your dependencies are ok, doing this should be enough: > $ git clone git@github.com:pharo-project/pharo-vm.git > $ cd pharo-vm/opensmalltalk-vm/build.macos32x86/pharo.cog.spur > $ ./mvm -f > > for linux you can: > $ cd pharo-vm/opensmalltalk-vm//build.linux32x86/pharo.cog.spur/build > $ ./mvm > > Esteban > >> >> Best regards, >> Guido. > -- Using Opera's mail client: http://www.opera.com/mail/

Feb. 23, 2017

[pharo-project/pharo-core]

by GitHub

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

Feb. 23, 2017

[pharo-project/pharo-core] e65cbe: 60410

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: e65cbe9d4fdb5c5e7d5d9557e1232a5e625c5de2 https://github.com/pharo-project/pharo-core/commit/e65cbe9d4fdb5c5e7d5d9557… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-23 (Thu, 23 Feb 2017) Changed paths: R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60409.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60410.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60409.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60410.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M UnifiedFFI-Tests.package/FFICallbackTests.class/instance/tests/testCqsort.st M UnifiedFFI-Tests.package/FFICallbackTests.class/instance/tests/testCqsortWithByteArray.st Log Message: ----------- 60410 19749 FFICallbackTests needs to be skipped for now https://pharo.fogbugz.com/f/cases/19749 http://files.pharo.org/image/60/60410.zip

Feb. 23, 2017

[pharo-project/pharo-core] f6558d: 60409

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: f6558da26d4c7f3f14392533dc65b60a5c71f6ae https://github.com/pharo-project/pharo-core/commit/f6558da26d4c7f3f14392533… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-23 (Thu, 23 Feb 2017) Changed paths: R Kernel-Tests.package/ContextTest.class/instance/private/expectedFailures.st M ReflectionMirrors-Primitives-Tests.package/MirrorPrimitivesTests.class/instance/tests-write barrier/testMakingObjectReadOnly.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60408.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60409.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60408.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60409.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R WriteBarrierTests.package/WriteBarrierTest.class/instance/setup/expectedFailures.st Log Message: ----------- 60409 19748 new VMs allow enabling of WriteBarrierTests https://pharo.fogbugz.com/f/cases/19748 http://files.pharo.org/image/60/60409.zip

Feb. 23, 2017