February 2017 - Pharo-users

Re: [Pharo-users] Team programming with Smalltalk

by Dimitris Chloupis

Pharo in particular, I cannot speak about other Smalltalks I have not used, when it comes to VCS its very similar to git actually. It uses source code files, it distributes them via zip files, it works locally instead of centralised , it support merges etc. Pharo works well also with usual VCS because it can export code into source code files. The image plays no role in VCS whatsoever because VCS is about code not data and image is mostly about live data and lesser about live code . So any tool will and does work with pharo outside the image. Problem arises with a majority of people that unlike me prefer to stay in the image in that case you gain more control because you have more pharo code to play with but you lose a lot of power because we are a small community not able to compete with behemorth projects like git. Another interesting thing which Pharo does emphasize is remote debugging , though not a Pharo monopoly by a long shot we do have several libraries that can achieve this and because the image format retains live state and live code execution its easy to resolve issues. Besides the image format , the fuel format has the advantage of storing only fraction of the image. You can email this or share it via git or dropbox . Like an image a fuel file is a binary file and like the image it can store live state and live code execution. This way you can isolate live bugs and share them with your team , each one in its own fuel file . Ston is also another alternative format which feels familiar for those that have worked with JSON. In the end there is nothing really special about Smalltalk , you can emulate these features in other programming language especially dynamic pure object orientated ones like Pharo . The difference is that with Pharo you avoid the custom setup, the extra download of tools and libraries and the extra glue code required. Of course the fact that those tool have been around for decades make them more polished and reliable , contrary to modern that promise the sky and the moon and deilvery very little. So overall I will say because of live coding features Pharo is ideal for teams that love to experiment and try ideas on the spot. Especially for bugs that are hard to catch because they appear in random having the ability to debug the live code and live state on the spot can really boost the performance on the team and at the same time utilize all the tool that coders in other languages can use too. On Thu, Feb 16, 2017 at 12:48 AM horrido <horrido.hobbies(a)gmail.com> wrote: > There's a debate at Hacker News about how Smalltalk is used collaboratively > in team programming: https://news.ycombinator.com/item?id=13642947 > <https://news.ycombinator.com/item?id=13642947> > > 'theamk' says: > > Sorry, I am at work right now and don't have time to watch videos. Can you > tell me more about "Smalltalk's own tooling for collaboration and version > control"? Are you referring to Monticello? I am not insisting on git, but > Monticello seems pretty limited in term of collaboration. I see commit, > diff, checkout, and remote pull/push. > > Specifically, let's imagine this scenario: we have team of tens of > programmers working on a project. A new team member joins and accidentally > breaks the code in non-obvious way. He pushes the code to main repository. > Next time, everyone else checks out the latest version of the code and > starts having weird problems. If you had 20 people on team, and they each > wasted 2 hours because the code was broken, well, you just wasted a week of > programmer time. How do you prevent it? > > In file-based word, the answer is tests and CI. What is the smalltalk way? > And please do not say "It's in the conceptual nature of programming" -- if > the scenario makes no sense in the smalltalk world (maybe you are not > supposed to have 20 people working on the same project?) please say this. > > ----- > > How would you respond? I know Smalltalk can be used in large team > programming, but since I personally have no experience with this, I cannot > respond intelligently. > > Thanks. > > > > > -- > View this message in context: > http://forum.world.st/Team-programming-with-Smalltalk-tp4934508.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Feb. 15, 2017

Team programming with Smalltalk

by horrido

There's a debate at Hacker News about how Smalltalk is used collaboratively in team programming: https://news.ycombinator.com/item?id=13642947 <https://news.ycombinator.com/item?id=13642947> 'theamk' says: Sorry, I am at work right now and don't have time to watch videos. Can you tell me more about "Smalltalk's own tooling for collaboration and version control"? Are you referring to Monticello? I am not insisting on git, but Monticello seems pretty limited in term of collaboration. I see commit, diff, checkout, and remote pull/push. Specifically, let's imagine this scenario: we have team of tens of programmers working on a project. A new team member joins and accidentally breaks the code in non-obvious way. He pushes the code to main repository. Next time, everyone else checks out the latest version of the code and starts having weird problems. If you had 20 people on team, and they each wasted 2 hours because the code was broken, well, you just wasted a week of programmer time. How do you prevent it? In file-based word, the answer is tests and CI. What is the smalltalk way? And please do not say "It's in the conceptual nature of programming" -- if the scenario makes no sense in the smalltalk world (maybe you are not supposed to have 20 people working on the same project?) please say this. ----- How would you respond? I know Smalltalk can be used in large team programming, but since I personally have no experience with this, I cannot respond intelligently. Thanks. -- View this message in context: http://forum.world.st/Team-programming-with-Smalltalk-tp4934508.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 15, 2017

Re: [Pharo-users] Issue with Iceberg

by Nicolas Passerini

Yep, that's it. 2017-02-15 13:32 GMT-03:00 Juraj Kubelka <juraj.kubelka(a)icloud.com>: > You likely need the latest (unstable) VM because the stable one has > corrupted git library. > > Cheers, > Juraj > > > El 15-02-2017, a las 12:24, Alexandre Bergel <alexandre.bergel(a)me.com> > escribiÃ³: > > > > Hi! > > > > I have "Error: External module not foundâ when trying to clone a > repository. > > I have the VM 7.0 (built on Oct 7, 2016) and Pharo 60371 > > https://github.com/npasserini/iceberg/issues/281 > > > > Help appreciated. > > > > Cheers, > > Alexandre > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > >

Feb. 15, 2017

Re: [Pharo-users] [Data Modeling] approaches to data persistence

by Dale Henrichs

Sergio, If you find that your data set grows large enough, keep in mind that you can port your application to GemStone/S[1]. GemStone provides a scalable solution for image-based persistence while preserving smalltalkiness:) Dale [1] https://gemtalksystems.com/small-business/gsdevkit/ On 02/14/2017 10:13 AM, sergio ruiz wrote: > this is a GREAT answer.. a totally smalltalky answer! > > i need to extend this test out to include randomly accessing a million > records at a timeâ¦ > > > > On February 14, 2017 at 12:15:28 PM, Ben Coman (btc(a)openinworld.com > <mailto:btc@openinworld.com>) wrote: > >> >> >> On Wed, Feb 15, 2017 at 12:29 AM, Ben Coman <btc(a)openinworld.com >> <mailto:btc@openinworld.com>> wrote: >> >> >> >> On Tue, Feb 14, 2017 at 11:01 PM, sergio ruiz >> <sergio.rrd(a)gmail.com <mailto:sergio.rrd@gmail.com>> wrote: >> >> Hey, all.. >> >> I have been working on creating a REST interface using >> Teapot. In learning how to handle exceptions, I have been >> following along with the library example. >> >> One of the things i noticed was that, in the library example, >> they are modeling that data a little differently than i have >> been.. >> >> to persist a list of items (and easily retrieve them), i just >> gave the object an âidâ, and store them on a class variable >> as an OrderedCollection.. >> >> in the library example, I see something i really like. rather >> than saving an ordered collection, they save it as a dictionary. >> >> This dictionary goes { id -> object }.. this takes the id out >> of the the object (which i really like) and makes the id >> generation pretty much irrelevant.. >> >> my question.. is there any performance hit either way once >> this list grows to tens of thousands of records? >> >> >> >> I was curious, so nothing better than to experiment... >> >> myClass := Object subclass: #AA >> instanceVariableNames: 'id data' >> classVariableNames: '' >> package: 'AAAA'. >> myClass compile: 'id: i id:= i'. >> myClass compile: 'data: d data:= d'. >> >> N := 10 raisedTo: 7. >> o := OrderedCollection new. >> d := Dictionary new. >> { Time millisecondsToRun: [ >> 1 to: N do: [:id| o add: (AA new id: id; data: 'blahblah')]]. >> Time millisecondsToRun: [ >> 1 to: N do: [:id| d at: id put: (AA new data: 'blahblah')]]. >> } inspect. >> o := nil. >> d := nil. >> Smalltalk garbageCollect. >> >> N=5 ==> "#(5 42)" >> N=6 ==> "#(434 839)" >> N=7 ==> "#(5733 17208)" >> >> Slight modification to pre-allocate space to ignore dynamic >> growth cost... >> o := OrderedCollection new: 2 * N. >> d := Dictionary new: 2 * N. >> >> N=5 ==> "#(7 33)" >> N=6 ==> "#(411 802)" >> N=7 ==> "#(5892 15141)" >> >> cheers -ben >> >> >> Lets also bench Arrays, and be a nicer with cleaning up memory... >> >> N := 10 raisedTo: 7. >> a := Array new: 2 * N. >> atime := Smalltalk vm totalGCTime + (Time millisecondsToRun: [ >> 1 to: N do: [:id| a at: id put: (AA new data: 'blahblah')]]) - >> Smalltalk vm totalGCTime. >> a := nil. >> Smalltalk garbageCollect. >> >> o := OrderedCollection new: 2 * N. >> otime := Smalltalk vm totalGCTime + (Time millisecondsToRun: [ >> 1 to: N do: [:id| o add: (AA new id: id; data: 'blahblah')]]) - >> Smalltalk vm totalGCTime. >> o := nil. >> Smalltalk garbageCollect. >> >> d := Dictionary new: 2 * N. >> dtime := Smalltalk vm totalGCTime + (Time millisecondsToRun: [ >> 1 to: N do: [:id| d at: id put: (AA new data: 'blahblah')]]) - >> Smalltalk vm totalGCTime. >> d := nil. >> Smalltalk garbageCollect. >> >> {atime. otime. dtime} inspect. >> >> N=5 ==> "#(2 4 13)" "#(2 4 13)" "#(2 5 13)" >> N=6 ==> "#(30 48 131)" "#(28 48 131)" "#(29 47 128)" >> N=7 ==> "#(274 470 1313)" "#(259 456 1340)" "#(269 467 1306)" >> >> So insertions into Dictionaries are >> two to three times slower than OrderedCollection, and >> five to six times slower than Arrays. >> >> Now this is milliseconds, so even at the 100,000 level Dictionary >> performance >> may be a reasonable tradeoff for other benefits. >> >> cheers -ben > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: http://bit.ly/29z9fG0 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > http://www.Village-Buzz.com > http://www.ThoseOptimizeGuys.com > http://www.coffee-black.com > http://www.painlessfrugality.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101

Feb. 15, 2017

Re: [Pharo-users] Issue with Iceberg

by Juraj Kubelka

You likely need the latest (unstable) VM because the stable one has corrupted git library. Cheers, Juraj > El 15-02-2017, a las 12:24, Alexandre Bergel <alexandre.bergel(a)me.com> escribiÃ³: > > Hi! > > I have "Error: External module not foundâ when trying to clone a repository. > I have the VM 7.0 (built on Oct 7, 2016) and Pharo 60371 > https://github.com/npasserini/iceberg/issues/281 > > Help appreciated. > > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Feb. 15, 2017

Issue with Iceberg

by Alexandre Bergel

Hi! I have "Error: External module not foundâ when trying to clone a repository. I have the VM 7.0 (built on Oct 7, 2016) and Pharo 60371 https://github.com/npasserini/iceberg/issues/281 Help appreciated. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 15, 2017

Re: [Pharo-users] Inspecting calculated attributes

by denker

> > I added this as an example to the Slot package: > > https://pharo.fogbugz.com/f/cases/19709/add-example-ComputedSlot <https://pharo.fogbugz.com/f/cases/19709/add-example-ComputedSlot> > > This will be in the next update. > > Very cool !! > A good example would be calculation based on other instance variables. > I took a guess... > > Object subclass: #TT > slots: { #i. #j => VirtualSlot with: [ :o | o i + 1 ] } > classVariables: { } > category: 'AAAA' > > TT>> i > ^i ifNil: [i:=0] > > TT>> i: > i: number > i := number > > TT>> j > ^j > In Playground... > (tt := TT new) inspect. > (tt i: 4) inspect. > Yes! The block can not refer to instance variables, so for more complex compilations (or if one does not want to expose accessors), one might move the code to a âcomputeâ method. As an extension, it might be good to allow the Slot to be configured with a selector: VirtualSlot with: #computeMyVar This would just need some check in #read:. Then of course, to speed things up one can do inlining by implementing #emitValue:, which could for the selector compile it to âself computeMyVarâ. Marcus

Feb. 15, 2017

Re: [Pharo-users] Inspecting calculated attributes

by Ben Coman

On Wed, Feb 15, 2017 at 6:43 PM, denker <marcus.denker(a)inria.fr> wrote: > > On 15 Feb 2017, at 11:24, denker <marcus.denker(a)inria.fr> wrote: > > > On 15 Feb 2017, at 10:56, Ben Coman <btc(a)openinworld.com> wrote: > > > > On Wed, Feb 15, 2017 at 3:38 PM, Alistair Grant <akgrant0710(a)gmail.com> > wrote: > I'm developing a number of classes where it would be convenient to be > able to inspect what might be described as calculated attributes, i.e. > the result of a unary message send. The result isn't stored in an > instance variable, but is still useful when inspecting. > > I can obviously develop an inspector extension for my application, but > was wondering if there is a framework in place that allows a list of > attributes to be declared that can also be inspected in a similar > fashion to normal instance variables. > > Many thanks to Doru and everyone who has contributed to the GT Inspector > framework. It has significantly influenced my development and the > architecture of the software I'm currently working on (in a positive > way, of course). > > > Would it be feasible to have a "CalculationSlot" > that was read only, and each time it was read it performed the calculation? > > Using a âvirtualâ slot would be possibleâ¦ it would look like a instance > variable, > (you can read from it and the calculation is done). > > > I added this as an example to the Slot package: > > https://pharo.fogbugz.com/f/cases/19709/add-example-ComputedSlot > > Changes: > - Name is âComputedSlotâ > - added #= and #hash so changing the block is possible in the class > definition > - do not raise error but ignore writes to not interfere with object > migration done by > the class builder (e.g. when adding an ivar). > > I will add that as an example to the image. > > Very cool !! A good example would be calculation based on other instance variables. I took a guess... Object subclass: #TT slots: { #i. #j => VirtualSlot with: [ :o | o i + 1 ] } classVariables: { } category: 'AAAA' TT>> i ^i ifNil: [i:=0] TT>> i: i: number i := number TT>> j ^j In Playground... (tt := TT new) inspect. (tt i: 4) inspect. cheers -ben

Feb. 15, 2017

Re: [Pharo-users] expanding Pharo window to left and Window positioning

by Ben Coman

On Wed, Feb 15, 2017 at 6:13 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > Hi, > > what rules govern window positioning? > > I have a dual monitor setup and and sometimes extend the Pharo window over > both of them; > for some reason however World submorphs (all Windows) are locked to the > left side, which is what I am dragging, so all the windows move to the > secondary screen. > > If I expand the right side, then the windows don't move (but they are > again on the wrong screen). > Which OS are you on? I don't get this behaviour. I'm on Linux Debian 8 dual screen (laptop + 24") and even though I don't normally do it, I just tested and have no problem spanning Pharo across both screens, starting on either screen and dragging to the other. cheers -ben > > Is it possible to change this behavior? > > I tried to change World listDirection but it had no effect. > > Thanks, > Peter > >

Feb. 15, 2017

Re: [Pharo-users] Inspecting calculated attributes

by denker

> On 15 Feb 2017, at 11:24, denker <marcus.denker(a)inria.fr> wrote: > > >> On 15 Feb 2017, at 10:56, Ben Coman <btc(a)openinworld.com> wrote: >> >> >> >> On Wed, Feb 15, 2017 at 3:38 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> I'm developing a number of classes where it would be convenient to be >> able to inspect what might be described as calculated attributes, i.e. >> the result of a unary message send. The result isn't stored in an >> instance variable, but is still useful when inspecting. >> >> I can obviously develop an inspector extension for my application, but >> was wondering if there is a framework in place that allows a list of >> attributes to be declared that can also be inspected in a similar >> fashion to normal instance variables. >> >> Many thanks to Doru and everyone who has contributed to the GT Inspector >> framework. It has significantly influenced my development and the >> architecture of the software I'm currently working on (in a positive >> way, of course). >> >> >> Would it be feasible to have a "CalculationSlot" >> that was read only, and each time it was read it performed the calculation? >> > Using a âvirtualâ slot would be possibleâ¦ it would look like a instance variable, > (you can read from it and the calculation is done). > I added this as an example to the Slot package: https://pharo.fogbugz.com/f/cases/19709/add-example-ComputedSlot <https://pharo.fogbugz.com/f/cases/19709/add-example-ComputedSlot> Changes: - Name is âComputedSlotâ - added #= and #hash so changing the block is possible in the class definition - do not raise error but ignore writes to not interfere with object migration done by the class builder (e.g. when adding an ivar). I will add that as an example to the image. Marcus

Feb. 15, 2017