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

Re: [Pharo-dev] WhatsUp from: 2014-10-06 until: 2014-10-19

by Damien Cassou

### Here's what I've been up to since the last WhatsUp: - migration of launcher's job to pharo/ Jenkins (instead of pharo-contribution) - launchers are now uploaded to http://files.pharo.org/platform/launcher/blessed/ - update of the mac os launcher's .app - package pharo-vm and pharo-launcher for nixos (will be in the next release of NixOS later this month) -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Oct. 6, 2014

Android VM update

by Jean Baptiste Arnaud

Hi, I just comeback from holiday, and I realise that I do not have done a announcement yet. Now the prototype of the Pharo Android VM work. - Event is managed - Resolution up to 1080p is managed. - Most of the plugins seems worked. - File plugin allow you to browse the sd card. Next: - fix the generator then jenkins. Merge with Pharo/Cog main and Make it available for the public. - die under the mountain of bug entry open by the first public release. First release will be perfect and bugless. - allow easy personalisation of the packaging, allow you to rename and change icon easily (for your own application, Squeak/Pharo Android VM, Phratch, DR geo, etc.). - refined the jumpout logic for have a better graphical update and a better idle process (less consumption, faster reactive UI, UI updating during heavy computation, etc. ). - package the android feature in the android plugin, show/hide the keyboard via primitive, etc. etc. + init configuration. - a lot of cool idea but later Here is a youtube video to show the result: http://youtu.be/lB9UV9Z7Kss You can forward this to other mailing list, I do not have access to all of them. Best Regards Dr Arnaud jbaptiste.arnaud(a)gmail.com

Oct. 6, 2014

Problems with loading Voyage-Mongo

by phil＠highoctane.be

My CI started failing on Voyage-Mongo. This used to work as of last week. Help... Loading 1.3.1 of ConfigurationOfVoyageMongo... Fetched -> ConfigurationOfMongoTalk-NorbertHartl.32 --- http://smalltalkhub.com/mc/MongoTalkTeam/mongotalk/main/ --- http://smalltalkhub.com/mc/MongoTalkTeam/mongotalk/main/ Loaded -> ConfigurationOfMongoTalk-NorbertHartl.32 --- http://smalltalkhub.com/mc/MongoTalkTeam/mongotalk/main/ --- /var/lib/jenkins/jobs/BaseWorker/workspace/package-cache Project: Magritte3 stable [3.1.5] Project: Grease release1.1 [1.1.11] Project: Seaside3 release3.1 [3.1.3] Project: Grease release1.1 [1.1.11] Project: Grease Core Tests release1.1 [1.1.11] Project: SPort2 2.34 Fetched -> FileSystem-Legacy-JohanBrichau.2 --- http://smalltalkhub.com/mc/PharoExtras/FileSystemLegacy/main/ --- http://smalltalkhub.com/mc/PharoExtras/FileSystemLegacy/main/ Project: Zinc Project stable [2.5.3] Project: Grease Slime release1.1 [1.1.11] Project: MongoTalk stable [1.6.1] Project: Grease 1.1.8 [1.1.11] Fetched -> Mongo-Squeak-NorbertHartl.16 --- http://smalltalkhub.com/mc/MongoTalkTeam/mongotalk/main/ --- http://smalltalkhub.com/mc/MongoTalkTeam/mongotalk/main/ Fetched -> Mongo-BSON-NorbertHartl.40 --- http://smalltalkhub.com/mc/MongoTalkTeam/mongotalk/main/ --- http://smalltalkhub.com/mc/MongoTalkTeam/mongotalk/main/ Fetched -> Mongo-Core-NorbertHartl.37 --- http://smalltalkhub.com/mc/MongoTalkTeam/mongotalk/main/ --- http://smalltalkhub.com/mc/MongoTalkTeam/mongotalk/main/ Fetched -> MongoQueries-NorbertHartl.7 --- http://smalltalkhub.com/mc/MongoTalkTeam/mongotalk/main/ --- http://smalltalkhub.com/mc/MongoTalkTeam/mongotalk/main/ ...RETRY-> Voyage-Model-Core-EstebanLorenzano.16 ...RETRY-> Voyage-Model-Core-EstebanLorenzano.16 ...FAILED-> Voyage-Model-Core-EstebanLorenzano.16'Errors in script loaded from /var/lib/jenkins/jobs/BaseWorker/workspace/BuildBaseWorker.st' [31mCould not resolve: Voyage-Model-Core [ Voyage-Model-Core-EstebanLorenzano.16] in /var/lib/jenkins/jobs/BaseWorker/workspace/package-cache http://smalltalkhub.com/mc/estebanlm/Voyage/main/ [0mMetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: in Block: linearLoadPackageSpec: packageSpec gofer: gofer... MetacelloPharo30Platform(MetacelloPlatform)>>do:displaying: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: MetacelloPackageSpec>>loadUsing:gofer: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [ :pkg | pkg loadUsing: self gofer: gofer ] OrderedCollection>>do: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: in Block: [ super linearLoadPackageSpecs: packageSpecs repos...etc... BlockClosure>>ensure: MetacelloLoaderPolicy>>pushLoadDirective:during: MetacelloLoaderPolicy>>pushLinearLoadDirectivesDuring:for: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>load MetacelloMCVersionSpecLoader>>load MetacelloMCVersion>>executeLoadFromArray: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [ :dict | ^ self executeLoadFromArray: anArray ] MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [ ^ aBlock value: dict ] BlockClosure>>on:do: MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [ ... BlockClosure>>ensure: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [ ... MetacelloPharo30Platform(MetacelloPlatform)>>do:displaying: MetacelloMCVersion>>fetchRequiredFromArray: MetacelloMCVersion>>doLoadRequiredFromArray: in Block: [ ... BlockClosure>>ensure: MetacelloMCVersion>>doLoadRequiredFromArray: MetacelloMCVersion>>load GoferMetacelloLoad>>loadConfiguration

Oct. 6, 2014

[pharo-project/pharo-core]

by GitHub

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

Oct. 6, 2014

[pharo-project/pharo-core] 974e81: 40285

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 974e81a20e53fe49be7d4784ff3207c7843b70f3 https://github.com/pharo-project/pharo-core/commit/974e81a20e53fe49be7d4784… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-06 (Mon, 06 Oct 2014) Changed paths: M Morphic-Widgets-Windows.package/GroupWindowMorph.class/instance/windows/addWindow_.st A OpalCompiler-Core.package/OCASTSemanticAnalyzer.class/instance/error handling/storeIntoReadOnlyVariable_.st M OpalCompiler-Core.package/OCASTSemanticAnalyzer.class/instance/error handling/storeIntoSpecialVariable_.st M OpalCompiler-Core.package/OCASTSemanticAnalyzer.class/instance/variables/lookupVariableForWrite_.st A OpalCompiler-Core.package/OCStoreIntoReadOnlyVariableError.class/README.md A OpalCompiler-Core.package/OCStoreIntoReadOnlyVariableError.class/definition.st A OpalCompiler-Core.package/OCStoreIntoReadOnlyVariableError.class/instance/accessing/description.st A OpalCompiler-Core.package/OCStoreIntoReadOnlyVariableError.class/instance/signaling/signal.st A OpalCompiler-Core.package/OCStoreIntoSpecialVariableError.class/README.md A OpalCompiler-Core.package/OCStoreIntoSpecialVariableError.class/definition.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script285.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40285.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Zinc-HTTP.package/ZnSingleThreadedServer.class/instance/initialization/initialize.st Log Message: ----------- 40285 14161 Replace Announcer>>#on:send:to:s senders in Morphic-Widgets-Windows https://pharo.fogbugz.com/f/cases/14161 14169 There are undeclared in Zinc in Pharo4 https://pharo.fogbugz.com/f/cases/14169 14146 Disable "store into argument"-exception in non-interactive mode https://pharo.fogbugz.com/f/cases/14146 http://files.pharo.org/image/40/40285.zip

Oct. 6, 2014

Re: [Pharo-dev] How to edit GT-Inspector State Variable Values in place ?

by Tudor Girba

Hi, This is not yet supported due to the UI. I wanted to get an in-place editor, but we did not get to it. We can add a dialog for the time being. Cheers, Doru On Mon, Oct 6, 2014 at 9:08 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Didn't even noticed it but yeah, very useful indeed, as your examples with > Zn show. > > http://youtu.be/M3Euu1XBo1U > > Phil > > > On Mon, Oct 6, 2014 at 9:05 AM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >> How can one edit GT-Inspector State Variable Values in place ? This used >> to be possible with the old and with the eye inspectors. >> >> Inspect 1@2, go stand on the field showing 1 or 2 for x or y, type >> something over it, accept/save and voila you edit the live object in place. >> I am using this a lot and I think this is a fundamental capability. >> >> Sven >> >> >> > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 6, 2014

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

by Sven Van Caekenberghe

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. 6, 2014

Re: [Pharo-dev] How to edit GT-Inspector State Variable Values in place ?

by phil＠highoctane.be

Didn't even noticed it but yeah, very useful indeed, as your examples with Zn show. http://youtu.be/M3Euu1XBo1U Phil On Mon, Oct 6, 2014 at 9:05 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > How can one edit GT-Inspector State Variable Values in place ? This used > to be possible with the old and with the eye inspectors. > > Inspect 1@2, go stand on the field showing 1 or 2 for x or y, type > something over it, accept/save and voila you edit the live object in place. > I am using this a lot and I think this is a fundamental capability. > > Sven > > >

Oct. 6, 2014

How to edit GT-Inspector State Variable Values in place ?

by Sven Van Caekenberghe

How can one edit GT-Inspector State Variable Values in place ? This used to be possible with the old and with the eye inspectors. Inspect 1@2, go stand on the field showing 1 or 2 for x or y, type something over it, accept/save and voila you edit the live object in place. I am using this a lot and I think this is a fundamental capability. Sven

Oct. 6, 2014

Re: [Pharo-dev] structuring widget examples

by stepharo

Ok now I got it. Stef On 5/10/14 19:53, Tudor Girba wrote: > Hi Stef, > > I was not clear. The E.g. presentation for a class lists all examples. > So, it is expected that we get more examples for a class. Take a look > at the attached screenshot showing the examples of FileReference. > > Let's call it <example> and then we use it consistently throughout the > system. Is that Ok? > > Cheers, > Doru > > Inline image 1 > > On Sun, Oct 5, 2014 at 5:58 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > > On 5/10/14 15:10, Tudor Girba wrote: >> Hi Stef, >> >> Great. GT is already prepared for this :). If you define a >> <gtExample> on the class side, you will get an "E.g." tab with >> those examples. >> >> It's called gtExample because we did not want to interfere with >> other pragmas, but perhaps we can change it to <eg>, or >> <example>. What do you think? > > for a given class I would like to have potentially multiple > examples. I already have that in certain classes. > Then since these examples are for core classes I do not really > like the idea to get gt* > > Now first we should have many more and renaming a pragma is just > the easy part of the game. > Because I'm turning WidgetExamples into class methods examples and > trying to understand the API of UITheme > and reducing the mess. > > I want > > - UITheme to call widgets class methods > - but I have to understand the theme impact on the API. > > a kind of gigantic task. but we will see. > Stef > >> >> Cheers, >> Doru >> >> >> On Sun, Oct 5, 2014 at 2:25 PM, stepharo <stepharo(a)free.fr >> <mailto:stepharo@free.fr>> wrote: >> >> Hi guys >> >> I started to systematically defined widget example using the >> pragram <exampleWidget> >> >> >> rowPrototype >> "Answer a prototypical row" >> "self rowPrototype openInHand" >> <exampleWidget> >> >> | sampleMorphs aRow | >> sampleMorphs := (1 to: (2 + 3 atRandom)) collect: >> [:integer | EllipseMorph new extent: ((60 + (20 >> atRandom)) @ (80 + ((20 atRandom)))); color: Color random; >> setNameTo: ('egg', integer asString); yourself]. >> aRow := self inARow: sampleMorphs. >> aRow setNameTo: 'Row'. >> aRow enableDragNDrop. >> aRow cellInset: 6. >> aRow layoutInset: 8. >> aRow setBalloonText: 'Things dropped into here will >> automatically be organized into a row. Once you have added >> your own items here, you will want to remove the sample >> colored eggs that this started with, and you will want to >> change this balloon help message to one of your own!'. >> aRow color: Color veryVeryLightGray. >> ^ aRow >> >> This means that GTool will get instances for free to play >> with and the finder get really handy to browse widgets. >> >> If you want to join the effort you are welcome. >> >> Stef >> >> >> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com> >> >> "Every thing has its own flow" > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

Oct. 6, 2014