July 2016 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

July 19, 2016

[pharo-project/pharo-core] 6dc224: 60150

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 6dc224a5c1ded31f5f7680919cf59c7eaded1c75 https://github.com/pharo-project/pharo-core/commit/6dc224a5c1ded31f5f768091… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-19 (Tue, 19 Jul 2016) Changed paths: R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60149.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60150.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60149.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60150.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Core.package/AbstractWidgetModel.class/README.md M Spec-Core.package/ButtonModel.class/README.md M Spec-Core.package/CheckBoxModel.class/README.md M Spec-Core.package/ComposableModel.class/README.md M Spec-Core.package/ComposableModel.class/instance/instance creation/instantiateModels_.st M Spec-Core.package/DynamicComposableModel.class/README.md M Spec-Core.package/FastTableModel.class/class/example/example.st M Spec-Core.package/IconListModel.class/README.md M Spec-Core.package/IconListModel.class/class/example/example.st M Spec-Core.package/ImageModel.class/README.md M Spec-Core.package/LabelModel.class/README.md M Spec-Core.package/ListModel.class/README.md M Spec-Core.package/MenuGroupModel.class/README.md M Spec-Core.package/MenuItemModel.class/README.md M Spec-Core.package/MenuModel.class/README.md M Spec-Core.package/RadioButtonGroup.class/README.md M Spec-Core.package/RadioButtonModel.class/README.md M Spec-Core.package/SliderModel.class/README.md M Spec-Core.package/TabManagerModel.class/README.md M Spec-Core.package/TabModel.class/README.md M Spec-Core.package/TabModel.class/instance/private/defaultIcon.st M Spec-Core.package/TextInputFieldModel.class/README.md M Spec-Core.package/TextInputFieldModel.class/definition.st M Spec-Core.package/TextModel.class/README.md M Spec-Core.package/TreeModel.class/class/examples/exampleWithCustomColumnsAndNodes.st M Spec-Core.package/TreeModel.class/class/examples/exampleWithCustomColumnsAndNodesAndChildren.st M Spec-Debugger.package/SpecDebugger.class/class/icons/taskbarIcon.st A Spec-Examples.package/CustomerStatisfaction.class/README.md A Spec-Examples.package/CustomerStatisfaction.class/class/example/example.st A Spec-Examples.package/CustomerStatisfaction.class/class/example/exampleDialog.st A Spec-Examples.package/CustomerStatisfaction.class/class/example/exampleNewLayout.st A Spec-Examples.package/CustomerStatisfaction.class/class/specs/defaultSpec.st A Spec-Examples.package/CustomerStatisfaction.class/class/specs/layout.st A Spec-Examples.package/CustomerStatisfaction.class/definition.st A Spec-Examples.package/CustomerStatisfaction.class/instance/accessing/buttonBad.st A Spec-Examples.package/CustomerStatisfaction.class/instance/accessing/buttonHappy.st A Spec-Examples.package/CustomerStatisfaction.class/instance/accessing/buttonNeutral.st A Spec-Examples.package/CustomerStatisfaction.class/instance/accessing/screen.st A Spec-Examples.package/CustomerStatisfaction.class/instance/accessing/title.st A Spec-Examples.package/CustomerStatisfaction.class/instance/initialization/initializePresenter.st A Spec-Examples.package/CustomerStatisfaction.class/instance/initialization/initializeWidgets.st M Spec-Examples.package/DropListExample.class/instance/initialization/initializeWidgets.st A Spec-Examples.package/DynamicalPopup.class/README.md A Spec-Examples.package/DynamicalPopup.class/class/example/exampleAlternativeToolbar.st A Spec-Examples.package/DynamicalPopup.class/class/example/exampleDefaultToolbar.st A Spec-Examples.package/DynamicalPopup.class/definition.st A Spec-Examples.package/DynamicalPopup.class/instance/initialization/alternativeToolbar.st A Spec-Examples.package/DynamicalPopup.class/instance/initialization/defaultToolbarConfiguration.st A Spec-Examples.package/DynamicalPopup.class/instance/initialization/dynamicLayout.st A Spec-Examples.package/DynamicalPopup.class/instance/initialization/initialExtent.st A Spec-Examples.package/DynamicalPopup.class/instance/initialization/initializeWidgets.st M Spec-Examples.package/TabsExample.class/instance/private/browserTab.st M Spec-Examples.package/TabsExample.class/instance/private/dynamicTab.st M Spec-Examples.package/TabsExample.class/instance/private/objectClassTab.st M Spec-Examples.package/TabsExample.class/instance/private/objectInspectorTab.st M Spec-Inspector.package/EyeAbstractInspector.class/class/accessing/taskbarIcon.st M Spec-Inspector.package/EyeTreeInspector.class/instance/api/iconFor_error_.st M Spec-SelectEntity.package/SelectEntity.class/instance/initialization/initializeWidgets.st M Spec-Tools.package/DualChangeSorterApplication.class/class/icons/taskbarIcon.st M Spec-Tools.package/KeymapBrowser.class/class/accessing/taskbarIcon.st M Spec-Tools.package/KeymapBrowser.class/instance/initialization/initializeWidgets.st M Spec-Tools.package/KeymapBrowser.class/instance/private/menu_shifted_.st M Spec-Tools.package/MessageBrowser.class/instance/icons/taskbarIcon.st Log Message: ----------- 60150 18744 Improve class comments https://pharo.fogbugz.com/f/cases/18744 18787 Replace calls at Smalltalk ui icons in subclasses of ComposableModel https://pharo.fogbugz.com/f/cases/18787 http://files.pharo.org/image/60/60150.zip

July 19, 2016

Re: [Pharo-dev] [Ann] Remote debugging tools

by Ben Coman

On Tue, Jul 19, 2016 at 10:30 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2016-07-18 18:26 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > >> I've been meaning to get a BBB. I looks like bit better platform for >> an industrial controller / robotics than the Rpi - in particular its >> Programming Realtime Unit. Knowing someone else has one maybe I'll >> get one now. In the back of my mind I've been considering whether its >> PRU could be modelled as a CPU target for Slang , so Slang could be >> re-purposed from just compiling VM, to compiling embedded programs for >> the PRU, developed from within Pharo and loaded on the fly into the >> PRU. >> > > Do you have link to BBB? (google not helps with such 3 letters). > BeagleBoneBlack. btw here is a nice overview of the PRU... http://beagleboard.org/static/presentations/MakerFaireNY20140920_UsingBeagl… and some videos... http://beagleboard.org/pru cheers -ben > >> >> >> >> >> When I read "Async evaluation ... does not wait for a result" I wonder >> >> if there a particular need for the fork is used here?... >> >> debugger evaluateAsync: [ [1/0] fork ]. >> >> >> > >> > Yes, it looks strange. Now all remote requests are executed such way >> that >> > errors will be returned as SeamlessRemoteException and server signaller >> > process will die. So instead of debugger with failed remote expression >> you >> > will see debugger with local process which performed remote message send >> > (but in case of async evaluation no result will returned to client and >> error >> > will be just ignored). To escape such "exception handler" fork is >> needed. >> > Fork will lead to unhanded error which will ask registered remote >> debugger >> > to debug it. >> >> Could you not just fork at the remote side? >> Perhaps the invocation would be #evaluateFork: >> > > Here is screen which shows "evaluate: [1/0]": > > âNo remote stack here. And on remote side there is no waiting process. > > In future real exception semantics could be supported. In that case > "evaluate: [1/0]" will open debugger with half stack from local process > (doIt from workspace) and half from remote process (where ZeroDivide > happens). > > ("debugger evaluateAsync: [1/0]" will never show any error because result > is not supposed to be returned for async) > >

July 19, 2016

Re: [Pharo-dev] Pharo 5.0 Tiny Feature Request

by Sean P. DeNigris

Sean P. DeNigris wrote > Great. Done. Slice in inbox: > SLICE-Issue-18757-Simple-Shell-Command-Eval-for-50-SeanDeNigris.1 Reviewed by the monkey. Please integrate at your earliest convenience :) https://pharo.fogbugz.com/f/cases/18757/Simple-Shell-Command-Eval-for-5-0 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-5-0-Tiny-Feature-Request-tp4901682p4907129.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 19, 2016

Re: [Pharo-dev] [Ann] Remote debugging tools

by Denis Kudriashov

2016-07-18 18:26 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > I've been meaning to get a BBB. I looks like bit better platform for > an industrial controller / robotics than the Rpi - in particular its > Programming Realtime Unit. Knowing someone else has one maybe I'll > get one now. In the back of my mind I've been considering whether its > PRU could be modelled as a CPU target for Slang , so Slang could be > re-purposed from just compiling VM, to compiling embedded programs for > the PRU, developed from within Pharo and loaded on the fly into the > PRU. > Do you have link to BBB? (google not helps with such 3 letters). > > >> > >> When I read "Async evaluation ... does not wait for a result" I wonder > >> if there a particular need for the fork is used here?... > >> debugger evaluateAsync: [ [1/0] fork ]. > >> > > > > Yes, it looks strange. Now all remote requests are executed such way that > > errors will be returned as SeamlessRemoteException and server signaller > > process will die. So instead of debugger with failed remote expression > you > > will see debugger with local process which performed remote message send > > (but in case of async evaluation no result will returned to client and > error > > will be just ignored). To escape such "exception handler" fork is needed. > > Fork will lead to unhanded error which will ask registered remote > debugger > > to debug it. > > Could you not just fork at the remote side? > Perhaps the invocation would be #evaluateFork: > Here is screen which shows "evaluate: [1/0]": âNo remote stack here. And on remote side there is no waiting process. In future real exception semantics could be supported. In that case "evaluate: [1/0]" will open debugger with half stack from local process (doIt from workspace) and half from remote process (where ZeroDivide happens). ("debugger evaluateAsync: [1/0]" will never show any error because result is not supposed to be returned for async)

July 19, 2016

Re: [Pharo-dev] [Ann] Remote debugging tools

by Denis Kudriashov

Hi Norbert. Big thank's for feedback. I commit new version of Seamless with compressed protocol (by gzip). Not big change but results are better. I see ~25% improvements. Here is statistics of my Seaside demo with "gziped" fuel protocol (it is default now): - 3 kb to connect debugger - 100 kb for opening debugger preview. - 100 kb for full debugger - 60 kb for selecting another context. - 868 bytes to evaluate "[1+2]" (with returned result). I improved logging in this version to collect "bytes statistics". You can analyze communication by starting SeamlessLogger and collecting statistics when you are ready: SeamlessLogger startAfresh. "to clear old history if exists" SeamlessLogger collectStatistics. "inspect it when you are ready to look at what was happen" Here is what you will see for debugger connecting: â 2016-07-18 19:11 GMT+02:00 Norbert Hartl <norbert(a)hartl.name>: > Ok, I experimented a bit with network qualities. I just tested connecting > and executing 3 + 4 on the remote side. Connecting transfers already 2-4kb > of data which should add some latency when the network is bad. Local wifi > and DSL connections work ok for the simple case because latencies are low. > > On a 3G network it can take between 4 and 7 seconds to establish the > connection and around half a second to execute 3 + 4. I defined a bad > mobile network with 20kb/s bandwidth, 10% packet loss and a delay of 100ms > in transmitting. This is equally for down and up directions. The connection > time raises to 11 seconds and the execution of 3 + 4 to 4 seconds. > > In order to be able to test I needed to tweak BasysNetwork>>#initialize to > set a timeout greater than 45 milliseconds which is pretty low. Usual > timeout settings for browsers and mobile applications are around 30 > seconds. I raised it to 10 seconds in order to test the bad network. > > To me the results are more or less expected. Well, I hoped they would be > much better :) It works reliably even over slow networks. The main problem > is that when it comes to remote debugging environments or browsers the > number of message sends is quite high. So it is to see what kind of > environment these tools can serve. For sure there is plenty of space to > optimize (I hope). I did the tests with bad/mobile networks just get a > clear mark where it cannot be used. To me personally the benchmark is DSL > upload speeds. If it is doable over these (could be 256k/s) I can connect > from the office (DSL down) the my little devices at home (DSL up) ;) > I see big room for optimizations here. Look at very small unit of communication: delivering integer result (from [1+2] evaluation). Following object is responsible for this: request := SeamlessDeliverResultRequest result: (SeamlessReturnValueResult with: 3) to: (SeamlessRequestContextReference id: 4 peerId: UUID new) . stream := ByteArray new writeStream. FLSerializer newDefault serialize: request on: stream. bytes := stream contents. bytes size. "==> 412" (ObjectTraveler on: request ) countReferences "==>10" Last line shows that only 10 objects consists full object graph of request. And Fuel serialization takes for it 412 bytes. It definitely could be improved with specialized serialization protocol. Also it could allow object traversal once which will lead to another performance improvements.

July 19, 2016

Re: [Pharo-dev] [squeak-dev] MCSmalltalkhubRepository for Squeak?

by Norbert Hartl

Hi Eliot, you are missing the /mc/ path in the url. Use MCHttpRepository location: 'http://smalltalkhub.com/mc/NorbertHartl/ASN1/main' user: '' password: '' That should work! Norbert > Am 19.07.2016 um 00:30 schrieb Eliot Miranda <eliot.miranda(a)gmail.com>: > > > > On Mon, Jul 18, 2016 at 3:27 PM, Chris Cunningham <cunningham.cb(a)gmail.com <mailto:cunningham.cb@gmail.com>> wrote: > You should be able to just use the HTTP repository to access smalltalkhub. That's what I've been doing for a while now. > > I do have a user - and log in with the HTTP Repository, but I'm not sure it is required for just reading. > > OK, so how do I map > > MCSmalltalkhubRepository > owner: 'NorbertHartl' > project: 'ASN1' > user: '' > password: '' > > which prints its URL as http://smalltalkhub.com/NorbertHartl/ASN1/main <http://smalltalkhub.com/NorbertHartl/ASN1/main> > > to an HTTPRepository spec? > > This doesn't work: > > MCHttpRepository > location: 'http://smalltalkhub.com/NorbertHartl/ASN1/main <http://smalltalkhub.com/NorbertHartl/ASN1/main>' > user: '' > password: '' > > neither does this: > > MCHttpRepository > location: 'http://smalltalkhub.com/NorbertHartl/ASN1 <http://smalltalkhub.com/NorbertHartl/ASN1>' > user: '' > password: '' > > > -cbc > > On Mon, Jul 18, 2016 at 3:20 PM, Eliot Miranda <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>> wrote: > Hi, > > any one have MCSmalltalkhubRepository? I want to load the ASN1 code to explore a performance regression in the VM, but I must first have access to smalltalkhub. > > _,,,^..^,,,_ > best, Eliot > > > > > > > > > > > -- > _,,,^..^,,,_ > best, Eliot

July 19, 2016

Re: [Pharo-dev] git iceberg and gitfiletree

by Esteban Lorenzano

Hi, Nico can answer better, but he is also in holidays. So, here my current understanding: > On 18 Jul 2016, at 19:11, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > Hi, > > since my question in the bugtracker went under the radar, I am asking here. > > What is the underlying export format of iceberg? Is it compatible with gitfiletree? yes, project iceberg use cypress metadata-less format. > > Is it (would it be) possible to use one alongside the other? Because even now iceberg seems like much better choice in some respects (from my limited testing). I do not see why not, and also it seems like a good idea until iceberg leaves alpha version. Esteban > > So it would be cool if I could use that, and if there were issues I could always fall back to gitfiletree. > > Thanks, > Peter >

July 19, 2016

Re: [Pharo-dev] [Ann] Remote debugging tools

by Stephan Eggermont

On 18/07/16 12:03, Denis Kudriashov wrote: > I glad to release first version of RemoteDebuggingTools project. It > allows explore and debug remote images. That is a great step forwards, thank you! Stephan

July 19, 2016

Re: [Pharo-dev] [Ann] Remote debugging tools

by Tudor Girba

Great news. Thanks, Denis! Doru > On Jul 18, 2016, at 5:03 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > I glad to release first version of RemoteDebuggingTools project. It allows explore and debug remote images. > > You can read details at http://dionisiydk.blogspot.fr/2016/07/remote-debugging-tools-is-ready.html and watch demo at https://youtu.be/SgFjgQpo_nU. > > Any feedback is welcome. > > Best regards, > Denis. > > -- www.tudorgirba.com www.feenk.com "Presenting is storytelling."

July 18, 2016