October 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] flow: a living full-stack #âframework for the web

by Sean P. DeNigris

sebastian(a)flowingconcept.com wrote > Your thoughts and further questions are welcomed "How does it compare to Tide" seems like a popular question ;) ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-flow-a-living-full-stack-framework-for-the-web-tp… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 10, 2014

Re: [Pharo-dev] Some methods missing in Behavior

by Marcus Denker

> On 10 Oct 2014, at 14:36, jdelgado(a)lsi.upc.edu wrote: > > Yes, evaluate: > > (Behavior new) compile: 'thisIsATest ^2' > > ah, that indeed should workâ¦ I will check and fix it in Pharo3 and Pharo4 Marcus

Oct. 10, 2014

Re: [Pharo-dev] [ANN] flow: a living full-stack #âframework for the web

by Sebastian Sastre

And now following Sven suggestion, thanks Sven!, Iâve published here is the first post about flow In this I set the starting point, showing reception and mission and starting the conversation on next steps https://medium.com/@sebastianconcpt/flow-a-living-full-stack-framework-for-… Your thoughts and further questions are welcomed On Oct 6, 2014, at 4:10 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 06 Oct 2014, at 07:43, S Krish <krishnamachari.sudhakar(a)gmail.com> wrote: > >> The links has the step by step. I am running it as I type.. > > Yeah, put that is more a setup guide, it end by saying 'and now you are ready to build your app', that is the part that I am interested in. > > Maybe a simplified Reddit clone, like in https://medium.com/@svenvc/reddit-st-in-10-cool-pharo-classes-1b5327ca0740 - this would be ideal, since we could then compare things better. > > Sven

Oct. 10, 2014

Re: [Pharo-dev] [amber-lang] Amber 0.13 released!

by H. Hirzel

On 10/10/14, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> wrote: > These are great news. Congratulations to all! > > Any further info on how deploying works now? Is Amber now creating a single > compiled js file with the whole project? YES. Do amber init to create a project 0.13 style. This creates among a lot of other files a Gruntfile.js (http://gruntjs.com/) With grunt deploy on the command line your project is transmogrifyed into a single JavaScript file called 'the.js'. This means for deployment you only need index.html and the.js 'the.js' contains only JavaScript. No Smtk sources. A crucial feature to actually use Amber in projects. So for me this is a much larger mile stone than the modest 0.13 version number implies. --Hannes > 2014-10-10 14:17 GMT+02:00 Nicolas Petton <petton.nicolas(a)gmail.com>: > >> Hi! >> >> After three months of development we are happy to announce the release >> of Amber 0.13.1 (skipping 0.13.0 for technical reasons). The team has >> once again been busy improving Amber to make it rock more than ever! >> >> With 172 commits, this release brings several important improvements as >> well as the usual bug fixes. >> >> Highlights: >> >> * Reworked cleaner DNU handling in core. >> * `amber init` fully embraced as the way to create new project. >> * Helios IDE is extracted and is now a project on its own. >> * It is included as dev-dependency in any new project by default. >> * Movable data out of index.html: >> * list of production packages in deploy.js; >> * list of development packages in devel.js; >> * project amd mappings in local.amd.json; >> * libraries' amd mappings in lib_directory.amd.json. >> * 'Batteries included' deployment via `grunt deploy`. >> * 0.13.1 because of technical issues w/ 0.13.0 release process. >> >> Commits: https://github.com/amber-smalltalk/amber/compare/0.12.6...0.13.0 >> Issues: >> https://github.com/amber-smalltalk/amber/issues?q=is%3Aissue+is%3Aclosed+mi… >> >> API changes: >> >> - Smalltalk side: >> * String >> asSelector is now String >> asJavaScriptMethodName >> * String >> asJavaScriptSelector is now String >> >> asJavaScriptPropertyName >> * Collection >> ifEmpty:ifNotEmpty: family passes self to ifNotEmpty: >> block >> >> - JavaScript side >> * smalltalk.selector is now smalltalk.st2js >> * smalltalk.convertSelector is now smalltalk.js2st >> * Smalltalk vm is now Smalltalk core >> * boot.js's .vm is now .api >> * amber load sets' .vm is now .api >> * Internal variables smalltalk/globals/_st are now $core/$globals/$recv >> >> Additions: >> >> + smalltalk. >> + accessJavaScript >> + Object >> >> + postMessageTo: >> + postMessageTo:origin: >> + Class >> >> + heliosClass >> + SmalltalkImage >> >> + core >> + amber/boot exports >> + api >> + amber/{devel,deploy,lang} exports >> + api >> >> Removals: >> >> - ProtoObject class >> >> - heliosClass >> - Object class >> >> - heliosClass >> >> I would like to thank Herbert for all his hard work on this release. He >> has done a wonderful job as the new maintainer of Amber. Thank you! >> >> Nicolas >> -- >> Nicolas Petton >> http://nicolas-petton.fr >> >> -- >> You received this message because you are subscribed to the Google Groups >> "amber-lang" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to amber-lang+unsubscribe(a)googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Bernat Romagosa. > > -- > You received this message because you are subscribed to the Google Groups > "amber-lang" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to amber-lang+unsubscribe(a)googlegroups.com. > For more options, visit https://groups.google.com/d/optout. >

Oct. 10, 2014

Re: [Pharo-dev] Some methods missing in Behavior

by jdelgado＠lsi.upc.edu

Yes, evaluate: (Behavior new) compile: 'thisIsATestÂ ^2' Bests, Jordi > >> On 10 Oct 2014, at 13:01, jdelgado(a)lsi.upc.edu wrote: >> >> Hi, >> >> Some simple reflection tests (those using Behavior>>#compile:) do not >> work in Pharo 3.0 because Behavior>>#basicLocalSelectors and >> Behavior>>#basicLocalSelectors: do not longer exist. >> >> I added the methods to TBehavior and the tests worked again. Thus, my >> question is: Is there any deep/good reason why these methods were >> removed? Because nothing seems to be broken after I added them back. >> >> > Can you give some examples? > > Marcus > > > >

Oct. 10, 2014

Re: [Pharo-dev] OSProcess in 3.0

by Thierry Goubier

Ok, I'll update the configurations. Thanks, Thierry 2014-10-09 23:15 GMT+02:00 David T. Lewis <lewis(a)mail.msen.com>: > Darn, I think we must have both done our updates on the same day. The last > update I did was this (time stamp is GMT -4 hours) : > > CommandShell-dtl.76 Dave Lewis, 5 October 2014 5:29:32 pm > CommandShell 4.6.9 > > Improve pipe closing for PipeableOSProcess class>>command: and related > methods to support use as stand alone command processor. An expression > such as the following will now close all open handles when command > processing is complete: > > "(PipeableOSProcess command: '/bin/echo this is a test') output" > > If you could update the configuration to pick this up, that would be > great. I think it will be helpful for people who want to easily execute > commands directly from the image. > > I think the two sub-packages that you would update are > CommandShell-Base-dtl.38 and CommandShell-Piping-dtl.16 > > Thanks, > Dave > > > Hi Dave, > > > > thanks to you. I updated OSProcess to 4.5.11 and CommandShell to 4.6.8; > > are those the latest? I did it last Sunday. > > > > Thierry > > > > Le 09/10/2014 22:42, David T. Lewis a Ã©crit : > >> Thierry, > >> > >> Thanks for doing those configuration updates, I hit "send" before I saw > >> your reply. > >> > >> Dave > >> > >>> Hi Noury, > >>> > >>> no, OSProcess on Squeaksource is not dead and is integrating all the > >>> changes needed for all the platforms it is running on. > >>> > >>> And as you can see, I very recently updated the configuration to make > >>> sure it was pointing to the very latest version. > >>> > >>> Regards, > >>> > >>> Thierry > >>> > >>> Le 09/10/2014 22:30, Noury Bouraqadi a Ã©crit : > >>>> Hi, > >>>> > >>>> Just tried to install the stable version of OSProcess using the > >>>> configuration browser on a 3.0. > >>>> I noticed it is still on http://www.squeaksource.com/OSProcess. > >>>> Does it mean it is dead? if yes, what is the alternative? > >>> > >>> > >>>> Thanx > >>>> Noury > >>>> > >>>> > >>> > >>> > >> > >> > >> > >> > >> > > > > > > > >

Oct. 10, 2014

[pharo-project/pharo-core] b2faf4: 40297

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: b2faf4d2912b827f22019a38d683579d1c6385cd https://github.com/pharo-project/pharo-core/commit/b2faf4d2912b827f22019a38… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-10 (Fri, 10 Oct 2014) Changed paths: M Kernel.package/Time.class/instance/printing/print24_on_.st M Kernel.package/Time.class/instance/printing/print24_showSeconds_on_.st A KernelTests.package/TimeTest.class/instance/tests printing/testPrint24withNanos.st M Komitter.package/Komitter.class/instance/announcement/registerToAnnouncements.st M Manifest-CriticBrowser.package/CriticBrowser.class/instance/system annoucements/registerToAnnouncements.st A Morphic-Widgets-ColorPicker.package/AColorSelectorMorph.class/README.md A Morphic-Widgets-ColorPicker.package/AColorSelectorMorph.class/definition.st A Morphic-Widgets-ColorPicker.package/AColorSelectorMorph.class/instance/accessing/color_.st A Morphic-Widgets-ColorPicker.package/AColorSelectorMorph.class/instance/drawing/drawOn_.st A Morphic-Widgets-ColorPicker.package/AColorSelectorMorph.class/instance/initialization/initialize.st A Morphic-Widgets-ColorPicker.package/AColorSelectorMorph.class/instance/private/hatchForm.st A Morphic-Widgets-ColorPicker.package/AColorSelectorMorph.class/instance/protocol/defaultFillStyle.st A Morphic-Widgets-ColorPicker.package/AColorSelectorMorph.class/instance/visual properties/fillStyle_.st A Morphic-Widgets-ColorPicker.package/HColorSelectorMorph.class/README.md A Morphic-Widgets-ColorPicker.package/HColorSelectorMorph.class/definition.st A Morphic-Widgets-ColorPicker.package/HColorSelectorMorph.class/instance/accessing/color_.st A Morphic-Widgets-ColorPicker.package/HColorSelectorMorph.class/instance/protocol/defaultFillStyle.st R Morphic-Widgets-Scrolling.package/AColorSelectorMorph.class/README.md R Morphic-Widgets-Scrolling.package/AColorSelectorMorph.class/definition.st R Morphic-Widgets-Scrolling.package/AColorSelectorMorph.class/instance/accessing/color_.st R Morphic-Widgets-Scrolling.package/AColorSelectorMorph.class/instance/drawing/drawOn_.st R Morphic-Widgets-Scrolling.package/AColorSelectorMorph.class/instance/initialization/initialize.st R Morphic-Widgets-Scrolling.package/AColorSelectorMorph.class/instance/private/hatchForm.st R Morphic-Widgets-Scrolling.package/AColorSelectorMorph.class/instance/protocol/defaultFillStyle.st R Morphic-Widgets-Scrolling.package/AColorSelectorMorph.class/instance/visual properties/fillStyle_.st R Morphic-Widgets-Scrolling.package/HColorSelectorMorph.class/README.md R Morphic-Widgets-Scrolling.package/HColorSelectorMorph.class/definition.st R Morphic-Widgets-Scrolling.package/HColorSelectorMorph.class/instance/accessing/color_.st R Morphic-Widgets-Scrolling.package/HColorSelectorMorph.class/instance/protocol/defaultFillStyle.st A Morphic-Widgets-Windows.package/AbstractResizerMorph.class/instance/actions/adoptPaneColor_.st A Morphic-Widgets-Windows.package/AbstractResizerMorph.class/instance/event handling/handlesMouseOver_.st A Morphic-Widgets-Windows.package/AbstractResizerMorph.class/instance/event handling/mouseEnter_.st A Morphic-Widgets-Windows.package/AbstractResizerMorph.class/instance/event handling/mouseLeave_.st A Morphic-Widgets-Windows.package/AbstractResizerMorph.class/instance/event handling/mouseUp_.st A Morphic-Widgets-Windows.package/AbstractResizerMorph.class/instance/testing/shouldDraw.st A Morphic-Widgets-Windows.package/AbstractResizerMorph.class/instance/testing/shouldInvalidateOnMouseTransition.st A Morphic-Widgets-Windows.package/BottomLeftGripMorph.class/instance/testing/containsPoint_.st A Morphic-Widgets-Windows.package/BottomRightGripMorph.class/instance/drawing/drawOn_.st A Morphic-Widgets-Windows.package/BottomRightGripMorph.class/instance/testing/containsPoint_.st A Morphic-Widgets-Windows.package/TopLeftGripMorph.class/instance/drawing/drawOn_.st A Morphic-Widgets-Windows.package/TopLeftGripMorph.class/instance/testing/containsPoint_.st A Morphic-Widgets-Windows.package/TopRightGripMorph.class/instance/drawing/drawOn_.st A Morphic-Widgets-Windows.package/TopRightGripMorph.class/instance/testing/containsPoint_.st R Morphic-Widgets-Windows.package/WindowEdgeGripMorph.class/instance/as yet unclassified/mouseDown_.st R Morphic-Widgets-Windows.package/WindowEdgeGripMorph.class/instance/as yet unclassified/mouseMove_.st R Morphic-Widgets-Windows.package/WindowEdgeGripMorph.class/instance/as yet unclassified/normalFillStyle.st R Morphic-Widgets-Windows.package/WindowEdgeGripMorph.class/instance/as yet unclassified/pressedFillStyle.st A Morphic-Widgets-Windows.package/WindowEdgeGripMorph.class/instance/event handling/mouseDown_.st A Morphic-Widgets-Windows.package/WindowEdgeGripMorph.class/instance/event handling/mouseMove_.st A Morphic-Widgets-Windows.package/WindowEdgeGripMorph.class/instance/style/normalFillStyle.st A Morphic-Widgets-Windows.package/WindowEdgeGripMorph.class/instance/style/pressedFillStyle.st R Polymorph-Widgets.package/extension/AbstractResizerMorph/instance/adoptPaneColor_.st R Polymorph-Widgets.package/extension/AbstractResizerMorph/instance/handlesMouseOver_.st R Polymorph-Widgets.package/extension/AbstractResizerMorph/instance/mouseEnter_.st R Polymorph-Widgets.package/extension/AbstractResizerMorph/instance/mouseLeave_.st R Polymorph-Widgets.package/extension/AbstractResizerMorph/instance/mouseUp_.st R Polymorph-Widgets.package/extension/AbstractResizerMorph/instance/shouldDraw.st R Polymorph-Widgets.package/extension/AbstractResizerMorph/instance/shouldInvalidateOnMouseTransition.st R Polymorph-Widgets.package/extension/BottomLeftGripMorph/instance/containsPoint_.st R Polymorph-Widgets.package/extension/BottomRightGripMorph/instance/containsPoint_.st R Polymorph-Widgets.package/extension/BottomRightGripMorph/instance/drawOn_.st R Polymorph-Widgets.package/extension/TopLeftGripMorph/instance/containsPoint_.st R Polymorph-Widgets.package/extension/TopLeftGripMorph/instance/drawOn_.st R Polymorph-Widgets.package/extension/TopRightGripMorph/instance/containsPoint_.st R Polymorph-Widgets.package/extension/TopRightGripMorph/instance/drawOn_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script297.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40297.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40297 14210 Replace Announcer>>#on:send:to:s senders in Komitter https://pharo.fogbugz.com/f/cases/14210 14197 Little Morphic Package Reorganization https://pharo.fogbugz.com/f/cases/14197 14198 Time>>print24 prints nanos, though it claims not to https://pharo.fogbugz.com/f/cases/14198 14211 Replace Announcer>>#on:send:to:s senders in Manifest-CriticBrowser https://pharo.fogbugz.com/f/cases/14211 http://files.pharo.org/image/40/40297.zip

Oct. 10, 2014

[pharo-project/pharo-core]

by GitHub

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

Oct. 10, 2014

Re: [Pharo-dev] Some methods missing in Behavior

by Marcus Denker

> On 10 Oct 2014, at 13:01, jdelgado(a)lsi.upc.edu wrote: > > Hi, > > Some simple reflection tests (those using Behavior>>#compile:) do not work in Pharo 3.0 because Behavior>>#basicLocalSelectors and Behavior>>#basicLocalSelectors: do not longer exist. > > I added the methods to TBehavior and the tests worked again. Thus, my question is: Is there any deep/good reason why these methods were removed? Because nothing seems to be broken after I added them back. > > Can you give some examples? Marcus

Oct. 10, 2014

Re: [Pharo-dev] OSProcess in 3.0

by David T. Lewis

On Fri, Oct 10, 2014 at 08:00:29AM +0200, phil(a)highoctane.be wrote: > Le 9 oct. 2014 23:15, "David T. Lewis" <lewis(a)mail.msen.com> a ??crit : > > > > Darn, I think we must have both done our updates on the same day. The last > > update I did was this (time stamp is GMT -4 hours) : > > > > CommandShell-dtl.76 Dave Lewis, 5 October 2014 5:29:32 pm > > CommandShell 4.6.9 > > > > Improve pipe closing for PipeableOSProcess class>>command: and related > > methods to support use as stand alone command processor. An expression > > such as the following will now close all open handles when command > > processing is complete: > > > > "(PipeableOSProcess command: '/bin/echo this is a test') output" > > > > No more need for the closePipes thing then? Right. But please do test it in your applications to be sure, I really only did simple testing and I am sure there may still chances for problems in this area. > > Also, I see that there is apparently no AioPlugin support in Pharo 3.0. Or > so say the tests of OSProcess. > > What is the state of affairs there? > Ask someone to include AioPlugin in the VM builds. Dave

Oct. 10, 2014