October 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] DesktopManaker from Ctrl-D to Ctrl-M help needed!!

by Ricardo Pacheco

Actually, I see that Ctrl-M is also not a good choice, so I will try to figure out what key combinations are available!! -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 17, 2017

Re: [Pharo-users] Roassal2 in recent Pharo 7 causes DNU #asTraitComposition

by Alistair Grant

On Tue, Oct 17, 2017 at 06:28:05AM +0000, Alistair Grant wrote: > Hi All, > > I'm attempting to load Roassal2 in to Pharo7 and am getting: > > UndefinedObject(Object)>>doesNotUnderstand: #asTraitComposition > > > It can be reproduced in a clean Pharo7 image, e.g. > Pharo7.0-32bit-d1b0e3e.image (downloaded 16 Oct 2017), and executing: > > Gofer it > smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; > configurationOf: 'Roassal2'; > loadStable. > > > OS: Ubuntu 16.04. > > I last rebuilt my image on 3 October without any problems. > > Any suggestions? I suspect the combination of Monticello and Traits > will take me quite a while to figure out. This could simply be an ordering issue, i.e. maybe Monticello / Metacello needs to ensure that the traits are loaded before the classes. Presumably at some point during the load there is a list of classes that are going to be loaded. If someone can point me to the correct location it will save some time tracking it down. Thanks! Alistair > Stack Trace: > > UndefinedObject(Object)>>doesNotUnderstand: #asTraitComposition > MCClassDefinition>>traitCompositionCompiled > [ :builder | > builder > superclass: superClass; > name: name; > layoutClass: (ObjectLayout layoutForType: type); > slots: self instanceVariables; > sharedVariables: self classVariables; > sharedPools: self sharedPoolsString; > classSlots: self classInstanceVariables; > traitComposition: self traitCompositionCompiled; > classTraitComposition: self classTraitCompositionCompiled; > comment: comment stamp: commentStamp; > category: category; > environment: superClass environment ] in [ PharoClassInstaller > make: [ :builder | > builder > superclass: superClass; > name: name; > layoutClass: (ObjectLayout layoutForType: type); > slots: self instanceVariables; > sharedVariables: self classVariables; > sharedPools: self sharedPoolsString; > classSlots: self classInstanceVariables; > traitComposition: self traitCompositionCompiled; > classTraitComposition: self classTraitCompositionCompiled; > comment: comment stamp: commentStamp; > category: category; > environment: superClass environment ] ] in MCClassDefinition>>createClass in Block: [ :builder | ... > PharoClassInstaller class(AbstractClassInstaller class)>>make: > [ PharoClassInstaller > make: [ :builder | > builder > superclass: superClass; > name: name; > layoutClass: (ObjectLayout layoutForType: type); > slots: self instanceVariables; > sharedVariables: self classVariables; > sharedPools: self sharedPoolsString; > classSlots: self classInstanceVariables; > traitComposition: self traitCompositionCompiled; > classTraitComposition: self classTraitCompositionCompiled; > comment: comment stamp: commentStamp; > category: category; > environment: superClass environment ] ] in MCClassDefinition>>createClass in Block: [ PharoClassInstaller... > BlockClosure>>on:do: > MCClassDefinition>>createClass > MCClassDefinition>>load > MCClassDefinition(MCDefinition)>>addMethodAdditionTo: > [ :each | each addMethodAdditionTo: methodAdditions ] in MCPackageLoader>>basicLoadDefinitions in Block: [ :each | each addMethodAdditionTo: methodAddition...etc... > [ :each | > | newLabel | > "Special handling for first and last element" > (count = 0 > or: [ count + 1 = size > or: [ (Time millisecondsSince: lastUpdate) >= msecs ] ]) > ifTrue: [ bar current: count. > oldLabel = (newLabel := (labelBlock cull: each) ifNil: [ oldLabel ]) > ifFalse: [ bar label: newLabel. > oldLabel := newLabel ]. > lastUpdate := Time millisecondClockValue ]. > aBlock value: each. > count := count + 1 ] in [ :bar | > labelBlock := aStringOrBlock isString > ifTrue: [ bar label: aStringOrBlock. > [ :dummyItem | aStringOrBlock ] ] > ifFalse: [ aStringOrBlock ]. > self > do: [ :each | > | newLabel | > "Special handling for first and last element" > (count = 0 > or: [ count + 1 = size > or: [ (Time millisecondsSince: lastUpdate) >= msecs ] ]) > ifTrue: [ bar current: count. > oldLabel > = (newLabel := (labelBlock cull: each) ifNil: [ oldLabel ]) > ifFalse: [ bar label: newLabel. > oldLabel := newLabel ]. > lastUpdate := Time millisecondClockValue ]. > aBlock value: each. > count := count + 1 ] ] in OrderedCollection(Collection)>>do:displayingProgress:every: in Block: [ :each | ... > OrderedCollection>>do: > [ :bar | > labelBlock := aStringOrBlock isString > ifTrue: [ bar label: aStringOrBlock. > [ :dummyItem | aStringOrBlock ] ] > ifFalse: [ aStringOrBlock ]. > self > do: [ :each | > | newLabel | > "Special handling for first and last element" > (count = 0 > or: [ count + 1 = size > or: [ (Time millisecondsSince: lastUpdate) >= msecs ] ]) > ifTrue: [ bar current: count. > oldLabel > = (newLabel := (labelBlock cull: each) ifNil: [ oldLabel ]) > ifFalse: [ bar label: newLabel. > oldLabel := newLabel ]. > lastUpdate := Time millisecondClockValue ]. > aBlock value: each. > count := count + 1 ] ] in OrderedCollection(Collection)>>do:displayingProgress:every: in Block: [ :bar | ... > BlockClosure>>cull: > [ ^ block cull: self ] in [ self prepareForRunning. > CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run in Block: [ ^ block cull: self ] > [ activeProcess psValueAt: index put: anObject. > aBlock value ] in CurrentJob(DynamicVariable)>>value:during: in Block: [ activeProcess psValueAt: index put: anObject.... > BlockClosure>>ensure: > CurrentJob(DynamicVariable)>>value:during: > CurrentJob class(DynamicVariable class)>>value:during: > [ self prepareForRunning. > CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run in Block: [ self prepareForRunning.... > BlockClosure>>ensure: > Job>>run > MorphicUIManager(UIManager)>>displayProgress:from:to:during: > ByteString(String)>>displayProgressFrom:to:during: > OrderedCollection(Collection)>>do:displayingProgress:every: > OrderedCollection(Collection)>>do:displayingProgress: > MCPackageLoader>>basicLoadDefinitions > [ self basicLoadDefinitions ] in MCPackageLoader>>basicLoad in Block: [ self basicLoadDefinitions ] > [ aBlock value ] in SourceFileArray>>deferFlushDuring: in Block: [ aBlock value ] > BlockClosure>>ensure: > > --

Oct. 17, 2017

DesktopManaker from Ctrl-D to Ctrl-M help needed!!

by Ricardo Pacheco

Hello. I'm using the Desktop Manager add on in my Pharo 6, but I really dislike the fact that its key shortcuts start with Ctrl-D because it hides the Do-It command. So I looked into the code and changed in the class method DesktopManager >> desktopMenuCommandOn:, to use Ctrl-M instead of Ctrl-D. After saving the new key shortcuts are working now. Nevertheless the old Ctrl-D based are still functional. The question is, how do I disable them? In other words, I do I make the system reset its key short-cuts? Is there a tool where I can see all the active key short-cuts of the system and manage them? Thanks a lot. PD to the DesktopManager team: Your tool is really cool, thanks a lot; nevertheless is not nice to hide the Do-It command -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 17, 2017

Roassal2 in recent Pharo 7 causes DNU #asTraitComposition

by Alistair Grant

Hi All, I'm attempting to load Roassal2 in to Pharo7 and am getting: UndefinedObject(Object)>>doesNotUnderstand: #asTraitComposition It can be reproduced in a clean Pharo7 image, e.g. Pharo7.0-32bit-d1b0e3e.image (downloaded 16 Oct 2017), and executing: Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; configurationOf: 'Roassal2'; loadStable. OS: Ubuntu 16.04. I last rebuilt my image on 3 October without any problems. Any suggestions? I suspect the combination of Monticello and Traits will take me quite a while to figure out. Thanks, Alistair Stack Trace: UndefinedObject(Object)>>doesNotUnderstand: #asTraitComposition MCClassDefinition>>traitCompositionCompiled [ :builder | builder superclass: superClass; name: name; layoutClass: (ObjectLayout layoutForType: type); slots: self instanceVariables; sharedVariables: self classVariables; sharedPools: self sharedPoolsString; classSlots: self classInstanceVariables; traitComposition: self traitCompositionCompiled; classTraitComposition: self classTraitCompositionCompiled; comment: comment stamp: commentStamp; category: category; environment: superClass environment ] in [ PharoClassInstaller make: [ :builder | builder superclass: superClass; name: name; layoutClass: (ObjectLayout layoutForType: type); slots: self instanceVariables; sharedVariables: self classVariables; sharedPools: self sharedPoolsString; classSlots: self classInstanceVariables; traitComposition: self traitCompositionCompiled; classTraitComposition: self classTraitCompositionCompiled; comment: comment stamp: commentStamp; category: category; environment: superClass environment ] ] in MCClassDefinition>>createClass in Block: [ :builder | ... PharoClassInstaller class(AbstractClassInstaller class)>>make: [ PharoClassInstaller make: [ :builder | builder superclass: superClass; name: name; layoutClass: (ObjectLayout layoutForType: type); slots: self instanceVariables; sharedVariables: self classVariables; sharedPools: self sharedPoolsString; classSlots: self classInstanceVariables; traitComposition: self traitCompositionCompiled; classTraitComposition: self classTraitCompositionCompiled; comment: comment stamp: commentStamp; category: category; environment: superClass environment ] ] in MCClassDefinition>>createClass in Block: [ PharoClassInstaller... BlockClosure>>on:do: MCClassDefinition>>createClass MCClassDefinition>>load MCClassDefinition(MCDefinition)>>addMethodAdditionTo: [ :each | each addMethodAdditionTo: methodAdditions ] in MCPackageLoader>>basicLoadDefinitions in Block: [ :each | each addMethodAdditionTo: methodAddition...etc... [ :each | | newLabel | "Special handling for first and last element" (count = 0 or: [ count + 1 = size or: [ (Time millisecondsSince: lastUpdate) >= msecs ] ]) ifTrue: [ bar current: count. oldLabel = (newLabel := (labelBlock cull: each) ifNil: [ oldLabel ]) ifFalse: [ bar label: newLabel. oldLabel := newLabel ]. lastUpdate := Time millisecondClockValue ]. aBlock value: each. count := count + 1 ] in [ :bar | labelBlock := aStringOrBlock isString ifTrue: [ bar label: aStringOrBlock. [ :dummyItem | aStringOrBlock ] ] ifFalse: [ aStringOrBlock ]. self do: [ :each | | newLabel | "Special handling for first and last element" (count = 0 or: [ count + 1 = size or: [ (Time millisecondsSince: lastUpdate) >= msecs ] ]) ifTrue: [ bar current: count. oldLabel = (newLabel := (labelBlock cull: each) ifNil: [ oldLabel ]) ifFalse: [ bar label: newLabel. oldLabel := newLabel ]. lastUpdate := Time millisecondClockValue ]. aBlock value: each. count := count + 1 ] ] in OrderedCollection(Collection)>>do:displayingProgress:every: in Block: [ :each | ... OrderedCollection>>do: [ :bar | labelBlock := aStringOrBlock isString ifTrue: [ bar label: aStringOrBlock. [ :dummyItem | aStringOrBlock ] ] ifFalse: [ aStringOrBlock ]. self do: [ :each | | newLabel | "Special handling for first and last element" (count = 0 or: [ count + 1 = size or: [ (Time millisecondsSince: lastUpdate) >= msecs ] ]) ifTrue: [ bar current: count. oldLabel = (newLabel := (labelBlock cull: each) ifNil: [ oldLabel ]) ifFalse: [ bar label: newLabel. oldLabel := newLabel ]. lastUpdate := Time millisecondClockValue ]. aBlock value: each. count := count + 1 ] ] in OrderedCollection(Collection)>>do:displayingProgress:every: in Block: [ :bar | ... BlockClosure>>cull: [ ^ block cull: self ] in [ self prepareForRunning. CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run in Block: [ ^ block cull: self ] [ activeProcess psValueAt: index put: anObject. aBlock value ] in CurrentJob(DynamicVariable)>>value:during: in Block: [ activeProcess psValueAt: index put: anObject.... BlockClosure>>ensure: CurrentJob(DynamicVariable)>>value:during: CurrentJob class(DynamicVariable class)>>value:during: [ self prepareForRunning. CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run in Block: [ self prepareForRunning.... BlockClosure>>ensure: Job>>run MorphicUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: OrderedCollection(Collection)>>do:displayingProgress:every: OrderedCollection(Collection)>>do:displayingProgress: MCPackageLoader>>basicLoadDefinitions [ self basicLoadDefinitions ] in MCPackageLoader>>basicLoad in Block: [ self basicLoadDefinitions ] [ aBlock value ] in SourceFileArray>>deferFlushDuring: in Block: [ aBlock value ] BlockClosure>>ensure: --

Oct. 17, 2017

Re: [Pharo-users] Behold Pharo: The Modern Smalltalk

by john pfersich

Look and feel Sent from my iPhone > On Oct 16, 2017, at 10:41, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Hi, > > >> On 13/10/17 19:39, Andrew Glynn wrote: >> Pharo is a great OSS Smalltalk, IMHO by the best to date (Squeak >> was/is good, but the LaF was never professional enough for it to be >> taken as seriously as it deserves, it just looks too much like a toy >> although in reality it's very powerful). Having the capability to >> build-on a reliable, attractive and enjoyable base without signing >> over my great-grand-child's first born is fantastic, and a great >> achievement for those who accomplished it. > > What is the LaF ? > > Cheers, > > Offray >

Oct. 16, 2017

Re: [Pharo-users] Behold Pharo: The Modern Smalltalk

by Dimitris Chloupis

So I finally built the Python live coding library I was talking about. I named it "pylivecoding" https://github.com/kilon/pylivecoding Live codig does mean in this case , replace methosd with updated ones for each instance of a class. Same thing you would expect in Pharo. Very simple to use , only 50 lines of code. it can also work with not only modifying methods , but aslo renaming them and removing or adding new ones. I have tested it during the day, seems to work ok but of course more thoroug testing needs to be done. Of course nowhere near the Pharo experience. But the main idea is there, you open yoru favorite editor IDE, you code away and at the same time you see your code come alive with no delays or weird side effects/ requirements. Of course it works with debuggers too, I use it from my python ide, python debugger and iptyhon all the time. Again usual workflow , debug, correct, continue. No issues so far. On Sat, Oct 14, 2017 at 4:37 AM Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > I donât care about Python vs Pharo debate. I love both I use both. > > My ultimate goal is to unite the two under a single Uber powerful live > coding environment part of my project Atlas. With direct mapping between > Pharo and Python objects and no compromises. A workflow that will be > seamless that you wonât know if you use Python or Pharo libraries as the > Atlas environment will allow you to work with both languages in a symbiotic > relationship. > > That was a dream of mine that I did not dear to reveal now slowly and > steadily becomes reality. > > I am extending the live coding environment of python and later will tackle > the subject of a python image format. > > Already Atlas can use python libraries from Pharo but thatâs about it , > but after this revelation I can move to stage 2 of full synchronization > between Python and Pharo. Even now Atlas allows you to use Pharo syntax to > fully access Python libraries. But integration is skin deep and is what is > going to improve the next years. > > So it seems something good came out of this very long discussion. Atlas is > going for a big update. This thread has been a huge inspiration for me. > Super excited :) > > On Sat, 14 Oct 2017 at 03:40, Andrew Glynn <aglynn42(a)gmail.com> wrote: > >> The first language I played with, I was nearly 5, was a live environment, >> Forth. I used it on an old PDP my mother had bought that was being >> surplused at the company she worked at. I used Forth until I was in my >> early teens, it was far superior to the BASIC that most other kids I knew >> who knew any programming used. It wasn't Smalltalk, but in many of the >> areas it was used (production automation is one major area), the language >> that most often replaced it *was* Smalltalk. >> >> The biggest difference, for me, as I wrote in the article the other day, >> is the ability to build-on rather than build-with, which in turn is based >> on the environment being written in itself. Ruby *looks* very much like >> Smalltalk, but it *works* like Java; Python works *more* like Smalltalk, >> and it's a much better live environment than Java or Ruby, because more of >> it is written in itself, but too much of Python is written in C, and that >> causes problems. If the code that interprets/compiles your code follows the >> same rules, the machine code it generates will usually also follow the same >> rules, and those rules/restrictions are, for the most part, designed to >> make code more reliable. >> >> As well, RVM has proven Smalltalk (specifically Squeak / Pharo, though >> admittedly an older version) can scale to 1024 cores nearly linearly. >> >> Python has a decent developer base but it's almost all OSS and almost all >> on Linux. Very few applications in Python are in areas where reliability is >> absolutely necessary, or even all that important. Like Smalltalk, it's a >> general purpose language in a niche, but the niches are very different. For >> years, decades really, any good version of Smalltalk cost an arm and a leg >> (some of them both of each), and as a result it tended to be used only >> where things really *had* to work. >> >> Pharo is a great OSS Smalltalk, IMHO by the best to date (Squeak was/is >> good, but the LaF was never professional enough for it to be taken as >> seriously as it deserves, it just looks too much like a toy although in >> reality it's very powerful). Having the capability to build-on a reliable, >> attractive and enjoyable base without signing over my great-grand-child's >> first born is fantastic, and a great achievement for those who accomplished >> it. >> >> Kendrick is an example of what can be done if you build-*on*: it was >> built on Moose, which is built on Glamorous, which is built on Morphic, >> which itself is based on a couple of decades work olving the basic problems >> inherent to UI's and MVC-type UI's in particular. Kendrick itself was >> written in a very short time when you compare it with other epidemiology >> programs, *if* you only count the time spent on Kendrick itself. It's an >> inherently complex problem area, and it's a life or death problem area. >> That an application capable of working reliably enough to be trusted in >> that area was built in a short time, because it was built-on a couple of >> decades of OSS work, is a huge compliment to those who were involved. >> >> Unfortunately for me, I wasn't, âº. But at least I can take advantage of >> it existence now. >> >> Andrew >> >> >> >> >> >> >> >> >> >> -----Original Message----- >> >> *Date*: Fri, 06 Oct 2017 21:18:28 +0000 >> *Subject*: Re: [Pharo-users] Behold Pharo: The Modern Smalltalk >> *To*: Any question about pharo is welcome <pharo-users(a)lists.pharo.org >> <Any%20question%20about%20pharo%20is%20welcome%20%3cpharo-users(a)lists.pharo.org%3e> >> > >> Reply-to: Any question about pharo is welcome < >> pharo-users(a)lists.pharo.org> >> *From*: Dimitris Chloupis <kilon.alios(a)gmail.com >> <Dimitris%20Chloupis%20%3ckilon.alios(a)gmail.com%3e>> >> Wise not to mention Ruby and Python and Pick the worst of the worst in >> OOP. Because frankly the competition for Pharo against those two behemoths >> can be quite brutal in the flexibility and power of OOP. >> >> And no , these language can do live coding with ease. I know because I >> currently code live coding style with Python for an app I am making. Sure >> it wont provide you with a live system out of the box, but put in 10 lines >> of code and you already ready to go with hardcore live coding. At least >> Python , Ruby being practically a rip off of Smalltalk language may need >> even less. >> >> iPython which by the way is by far the most popular Python tool is the >> real deal, a full blow live coding enviroment. >> >> To my suprise its not even hard to do live coding with C/C++ including >> using image format. To my shock live coding is actually supported by both >> the OS and the hardware. Hardware has its own exception system , OS has an >> image flie format called "memory mapped files" used for DLLs and a lot of >> essential functionality. >> >> For some weird reason however its well hidden and not that much utilised >> by coders. They really love long compile times, dont ask me why. >> >> But yeah C++ even though it has come a long way with its template system, >> its still the king of ugly. That sytax, oh the horrors of that syntax..... >> yiaks !!! >> >> I am so enternal greatful that Pharo introduced me to live coding and >> opened my eyes to universe of fun and productivity. I cannot imagine coding >> an other way ever again. >> >> I really hope that we take this further though. >> >> On Wed, Oct 4, 2017 at 1:31 PM horrido <horrido.hobbies(a)gmail.com> wrote: >> >> Behold Pharo: The Modern Smalltalk >> < >> https://medium.com/smalltalk-talk/behold-pharo-the-modern-smalltalk-38e132c… >> > >> >> If you would like to suggest some edits, I'm all ears. Anything to improve >> the impact of the article. >> >> Thanks. >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >>

Oct. 16, 2017

Re: [Pharo-users] Behold Pharo: The Modern Smalltalk

by H. Hirzel

LaF = Look and Feel. If you look at recent versions LaF of Squeak has improved as well. In fact considerably compared to 3.8/3.9 where Pharo branched off. On 10/16/17, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > Hi, > > > On 13/10/17 19:39, Andrew Glynn wrote: >> Pharo is a great OSS Smalltalk, IMHO by the best to date (Squeak >> was/is good, but the LaF was never professional enough for it to be >> taken as seriously as it deserves, it just looks too much like a toy >> although in reality it's very powerful). Having the capability to >> build-on a reliable, attractive and enjoyable base without signing >> over my great-grand-child's first born is fantastic, and a great >> achievement for those who accomplished it. > > What is the LaF ? > > Cheers, > > Offray > >

Oct. 16, 2017

Re: [Pharo-users] Behold Pharo: The Modern Smalltalk

by Offray Vladimir Luna CÃ¡rdenas

I'm think that is important to remove barriers for developers coming from other environments based on files for development and documentation, but my path is different, is teaching people like journalist, hacktivist who has no previous or deep experience into developing. Starting with them, using Live Coding and mixing it with interactive documentation, scripting, and agile visualization, has been a powerful enabler. No need to think in the established tradition, because we're building our own, using alternative infrastructure to bootstrap ourselves into alternative futures. Cheers, Offray On 12/10/17 21:55, Ben Coman wrote: > On Wed, Oct 11, 2017 at 10:39 PM, Offray Vladimir Luna CÃ¡rdenas > <offray.luna(a)mutabit.com <mailto:offray.luna@mutabit.com>> wrote: > > The more I use Pharo, the less I use web documentation. > > That is a familiar path, but still an obstacle for people to get over > in trying Pharo - i.e. its a barrier of entry.Â I've previously > referred to this article by JoelOnSoftware, but to pull out a key > part... "Think of these barriers as an obstacle course that people > have to run before you can count them as your customers. If you start > out with a field of 1000 runners, about half of them will trip on the > tires; half of the survivors wonât be strong enough to jump the wall; > half of those survivors will fall off the rope ladder into the mud, > and so on, until only 1 or 2 people actually overcome all the hurdles. > With 8 or 9 barriers, everybody will have one non-negotiable deal > killer.Â This calculus means that eliminating barriers to switching is > the most important thing you have to do if you want to take over an > existing market, because eliminating just one barrier will likely > double your sales. Eliminate two barriers, and youâll double your > sales again." > > For example, Stef mentioned that the Pharo web docs were dropped > because were't used much.Â But perhaps their value is not for regular > use by the community, but more for outsiders evaluating Pharo, or > newcomers transitioning from their old workflow to a Pharo one.Â In > that case their value eliminating one barrier of entry is much greater > than measured from the number of page hits. > > > btw, What I like about Richards's articles is that... most of our > community's articles are for people already using Pharo, even if only > a newcomer of a few days working through an introductory tutorial.Â > Richard's articles target outsiders and one of the side benefits for > *me* is that it pulls in critical outside perspectives to remind me of > the barriers-of-entry stopping people using Pharo.Â Â > > Take for instance the common angst people have against working in an > Image in Smalltalk.Â There are some legitimate concerns with ending up > in a state you can't recreate, which we are addressing this with the > bootstrapping projects.Â But I think we might publicize this better to > outsiders. For example... Mr Smith knows nothing about Smalltalk and > takes an interest in Pharo.Â Smith discusses with colleague Jones who > presents a poor opinion of the Smalltalk Image approach. So Smith > never tries Pharo!Â Alternatively, if Smith has already read in an FAQ > about this common argument and how we address it by our bootstrap > process, he can inform Jones', and maybe nowÂ we've got two curious > newcomers.Â Â > > cheers -ben > >

Oct. 16, 2017

Re: [Pharo-users] FYI about Pharo MOOC

by Offray Vladimir Luna CÃ¡rdenas

If you're considering video subtitling, nothing better that Amara: http://amara.org/ It has the easiest interface for video subtitling and easy collaboration built in (no need to learn DVCS --Git, Fossil) to collaborate. Cheers, Offray On 13/10/17 01:24, Stephane Ducasse wrote: > Hello > > It would be super great :) > the files are in the github repo > https://github.com/SquareBracketAssociates/PharoMooc/tree/master/Subtitles > > Stef > > On Fri, Oct 13, 2017 at 1:25 AM, Ricardo Pacheco > <ricardo.pacheco.roldan(a)gmail.com> wrote: >> Hello Stephane, I can help with the Spanish subtitles. You can send me a file >> with the text, if you have it. My french is basic so please send also the >> English fil, to double check. >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >

Oct. 16, 2017

Re: [Pharo-users] Behold Pharo: The Modern Smalltalk

by Offray Vladimir Luna CÃ¡rdenas

Hi, On 13/10/17 19:39, Andrew Glynn wrote: > Pharo is a great OSS Smalltalk, IMHO by the best to date (Squeak > was/is good, but the LaF was never professional enough for it to be > taken as seriously as it deserves, it just looks too much like a toy > although in reality it's very powerful). Having the capability to > build-on a reliable, attractive and enjoyable base without signing > over my great-grand-child's first born is fantastic, and a great > achievement for those who accomplished it. What is the LaF ? Cheers, Offray

Oct. 16, 2017