- Pharo-dev - lists.pharo.org

Pharo 3.0 on Windows 8.1

by Sven Van Caekenberghe

Pharo 3.0 on Windows 8.1 Installing and running Pharo 3.0 on a blank Windows 8.1 machine in under 1 minute. http://www.youtube.com/watch?v=FKokxrQtrg0 With an extra minute to demo some elementary interactions. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

Feb. 26, 2014

Re: [Pharo-dev] Pharo is cool

by Norbert Hartl

Here the code operates on a shared queue EventDispatcher>>#consumeQueue | block | [ true ] whileTrue: [ block := queue next. [ block value ] on: Error do: [ :err | self serializeStackFor: err. Log error: 'block execution failed. stack saved' ] ] EventDispatcher>>#serializeStackFor: anError [ FuelOutStackDebugAction serializeTestFailureContext: anError signalerContext toFileNamed: 'Stack-', (DateAndTime now printString),'.fuel' ] on: Error do: [:err| "simply continue...â ] Norbert Am 26.02.2014 um 14:40 schrieb Esteban A. Maringolo <emaringolo(a)gmail.com>: > Pharo is Cool. Definitely. > > How do you set up the "fuel dump"? > > This morning I woke up with a "out of memory" crash (the first crash > in two months), and going through the .log file didn't help much. > > Regards! > > > Esteban A. Maringolo > > > 2014-02-26 10:01 GMT-03:00 Norbert Hartl <norbert(a)hartl.name>: >> The best smalltalk/pharo moments you get if you try things you want to have just in order to see they are already there. >> >> Today FileBrowser. >> I switched one of my servers to dump to stack with fuel to disk if an exception occurs. Today I copied the files from the server to my local machine and opened a workspace starting to write an expression to open them. Then I thought it would be cool if I could use the file browser for it. So I opened it and navigated to the directory with the fuel files...et voilÃ ...as soon as I clicked on a fuel file a button "materialize" appeared which showed the stack from the server right away. >> >> Just brilliant! Well done! >> >> Norbert >

Feb. 26, 2014

Re: [Pharo-dev] expected failures

by Emilio Oca

Hi, I tend to wrap then like this: [ self operationThatShouldFail. self fail: 'why!'. ] on: Error do: [ "check that is the right error" ] > -----Mensaje original----- > De: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] En nombre de > Pharo4Stef > Enviado el: Martes, 25 de Febrero de 2014 16:51 > Para: Pharo Development List > Asunto: Re: [Pharo-dev] expected failures > > ben > > camillo once wrote a nice mail about shouldnot: Error. If I remember > correctly. > > Stef > On 25 Feb 2014, at 17:04, btc(a)openinworld.com wrote: > > > I'd like to better understand the semantics of "expected failures" in > TestRunner. It seems to me that if you want to ensure that a certain > operation fails, in a test you'd wrap it as follows... > > > > shouldFailed=false. > > [ self operationThatShouldFail ] on: Error do: [ shouldFailed := > true ]. > > self assert: shouldFailed. > > > > So is tagging methods with pragma <expectedFailure> or in method > #expectedFailures a temporary measure used to bypass a failing test when > the judgment is that it is not critical to fix immediately? What is the > process for tacking and resolving expected failures. It would give a > warm fuzzy feeling if no expected failures are reported in TestRunner. > Otherwise it leaves some residual uncertainty that something is wrong, > even though a failure is "expected". > > > > cheers -ben > >

Feb. 26, 2014

Re: [Pharo-dev] easier start with Phobos

by Pavel Krivanek

Ok, thank you, I will check that. -- Pavel 2014-02-26 14:40 GMT+01:00 Stephan Eggermont <stephan(a)stack.nl>: > This doesn't work on a mac (running Mavericks) > > c := PipeableOSProcess command: 'cd PhobosDemo.app/Contents; mkdir > Frameworks; cd Frameworks; tar -jxvf ../../../xulrunner.tar.bz2'. >

Feb. 26, 2014

Re: [Pharo-dev] New methods for the String class

by Stephan Eggermont

Eliot wrote >But the real things to learn are the Method Finder and the browser. In case you are wondering why no beginner seems to know about Method Finder: Your post made me take a look at it for the first time (after near a decade of smalltalk). Interesting class comment. Iâm pretty sure no beginner will understand it. The first thing I did was google for some blog posts and videos on it. I wouldnât have bothered if you hadnât been so clear about having to learn it. A much more simple example is needed (to start with). And that only helps after discovering that there is a tool like that. >So why aren't people taking the time to learn it today? Is it the system's fault? Is it too big? Are the readable parts of the system non-existent, or >too difficult to find? Is it some cultural change that means people can't learn such systems any more? Was it only learnable by a few people back >in the day and it remains unsuitable for a mass audience? Is it impossible to design user interfaces that invite exploration? Do people no longer >want to play with the system but instead want to use it to get something done fast, and can't spare the time to learn it properly? Are computing >languages like English, and every programming language must adopt the conventions and vocabulary of the most popular? Is inheritance too >hard to navigate to discover that SequenceableCollection has lots of useful String mehtods, and some useful methods on ByteString are in String, >etc? The system is much larger than it used to be. A larger system is much more difficult to navigate. And how should you learn it? Which subset of concepts should you learn, and in which order? Pharo by Example targets more new programmers than switching ones. Tools that were added are almost by definition designed for experienced users. They donât care enough about discoverability, as they know where they are. Inheritance is not so much a problem, that is a well known concept in mainstream languages Stephan

Feb. 26, 2014

Re: [Pharo-dev] easier start with Phobos

by Stephan Eggermont

This doesnât work on a mac (running Mavericks) c := PipeableOSProcess command: 'cd PhobosDemo.app/Contents; mkdir Frameworks; cd Frameworks; tar -jxvf ../../../xulrunner.tar.bz2'.

Feb. 26, 2014

Re: [Pharo-dev] Pharo is cool

by Esteban A. Maringolo

Pharo is Cool. Definitely. How do you set up the "fuel dump"? This morning I woke up with a "out of memory" crash (the first crash in two months), and going through the .log file didn't help much. Regards! Esteban A. Maringolo 2014-02-26 10:01 GMT-03:00 Norbert Hartl <norbert(a)hartl.name>: > The best smalltalk/pharo moments you get if you try things you want to have just in order to see they are already there. > > Today FileBrowser. > I switched one of my servers to dump to stack with fuel to disk if an exception occurs. Today I copied the files from the server to my local machine and opened a workspace starting to write an expression to open them. Then I thought it would be cool if I could use the file browser for it. So I opened it and navigated to the directory with the fuel files...et voilÃ ...as soon as I clicked on a fuel file a button "materialize" appeared which showed the stack from the server right away. > > Just brilliant! Well done! > > Norbert

Feb. 26, 2014

Re: [Pharo-dev] Pharo is cool

by Mariano Martinez Peck

Just be careful 2: "I switched one of my servers to dump to stack with fuel to disk if an exception occurs. " Once it happened to me the stack I was taking for serializing an error was too big. Too big because it even reached the UI. The UI has lots of sensible objects that change quite frequently. So my graph to serialize was big and the graph changed quite frequently. Result: Fuel throwing error because the graph to serialize changed while being serialized. Oh...exception? Fuel out exception! exception. Oh exception? ... So yeah..the fact that Fuel was throwing an error causes a loop so be careful of that as well. On Wed, Feb 26, 2014 at 10:28 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 26.02.2014 um 14:19 schrieb Max Leske <maxleske(a)gmail.com>: > > > Cool! :) > > > > Just be careful: if you're using a large model the stack can blow up > your image with a low space warning / make it inresponsive (because the > stack referenes your model and boom, pretty much all of your instances will > becom serialized). > > > Yes, I know. But that would be a problem anyway. I think I have time. In > the fuel files are 8 (!) contexts. :) > > Norbert > > > FYI we're actively working on pruning of the serialization graph to > solve this. > > > > Max > > > > > > On 26.02.2014, at 14:01, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> The best smalltalk/pharo moments you get if you try things you want to > have just in order to see they are already there. > >> > >> Today FileBrowser. > >> I switched one of my servers to dump to stack with fuel to disk if an > exception occurs. Today I copied the files from the server to my local > machine and opened a workspace starting to write an expression to open > them. Then I thought it would be cool if I could use the file browser for > it. So I opened it and navigated to the directory with the fuel files...et > voilÃ ...as soon as I clicked on a fuel file a button "materialize" appeared > which showed the stack from the server right away. > >> > >> Just brilliant! Well done! > >> > >> Norbert > > > > > > > -- Mariano http://marianopeck.wordpress.com

Feb. 26, 2014

Re: [Pharo-dev] Pharo is cool

by Norbert Hartl

Am 26.02.2014 um 14:19 schrieb Max Leske <maxleske(a)gmail.com>: > Cool! :) > > Just be careful: if youâre using a large model the stack can blow up your image with a low space warning / make it inresponsive (because the stack referenes your model and boom, pretty much all of your instances will becom serialized). > Yes, I know. But that would be a problem anyway. I think I have time. In the fuel files are 8 (!) contexts. :) Norbert > FYI weâre actively working on pruning of the serialization graph to solve this. > > Max > > > On 26.02.2014, at 14:01, Norbert Hartl <norbert(a)hartl.name> wrote: > >> The best smalltalk/pharo moments you get if you try things you want to have just in order to see they are already there. >> >> Today FileBrowser. >> I switched one of my servers to dump to stack with fuel to disk if an exception occurs. Today I copied the files from the server to my local machine and opened a workspace starting to write an expression to open them. Then I thought it would be cool if I could use the file browser for it. So I opened it and navigated to the directory with the fuel filesâ¦et voilÃ â¦as soon as I clicked on a fuel file a button âmaterializeâ appeared which showed the stack from the server right away. >> >> Just brilliant! Well done! >> >> Norbert > >

Feb. 26, 2014

Re: [Pharo-dev] Pharo is cool

by Max Leske

Cool! :) Just be careful: if youâre using a large model the stack can blow up your image with a low space warning / make it inresponsive (because the stack referenes your model and boom, pretty much all of your instances will becom serialized). FYI weâre actively working on pruning of the serialization graph to solve this. Max On 26.02.2014, at 14:01, Norbert Hartl <norbert(a)hartl.name> wrote: > The best smalltalk/pharo moments you get if you try things you want to have just in order to see they are already there. > > Today FileBrowser. > I switched one of my servers to dump to stack with fuel to disk if an exception occurs. Today I copied the files from the server to my local machine and opened a workspace starting to write an expression to open them. Then I thought it would be cool if I could use the file browser for it. So I opened it and navigated to the directory with the fuel filesâ¦et voilÃ â¦as soon as I clicked on a fuel file a button âmaterializeâ appeared which showed the stack from the server right away. > > Just brilliant! Well done! > > Norbert

Feb. 26, 2014