- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] c12d25: 40415

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: c12d2568734ac1da30a59b1737c37eec51dc8e59 https://github.com/pharo-project/pharo-core/commit/c12d2568734ac1da30a59b17… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-12-13 (Sat, 13 Dec 2014) Changed paths: M FontChooser.package/FontChooser.class/instance/action/updateFontList.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script415.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40415.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Tools.package/NewVersionBrowser.class/class/menu/versionsBrowserListMenu_.st Log Message: ----------- 40415 14604 Revert to previous version in method versions list doesnt work https://pharo.fogbugz.com/f/cases/14604 1610 Font browser button "Update" does load fonts but font list is not updated https://pharo.fogbugz.com/f/cases/1610 http://files.pharo.org/image/40/40415.zip

Dec. 13, 2014

14616 Package Tags causing merge conflict

by Ben Coman

There are a dozen tickets to rename test packages to conform with the standard patter, e.g. ShoutTests --> Shout-Tests. The META case is... https://pharo.fogbugz.com/default.asp?14447 The <Merge> of these slices seems to be failing, for example, due to the non-existant Shout-Tests being created while reviewing the merge, prior to the second <Merge> button being pressed to approve the merge. A side-effect is that the if you cancel the merge, the new empty Shout-Tests remains in the image, which I think itself is a bug, but might be unrelated to merge conflict. To observe this... 1. Open System Browser and filter on 'shout' 2. Open Monticello and the Pharo4Inbox. 3. Select SLICE-Issue-14439... and <Merge> 4. Observe that packages Shout-Tests and SLICE-Issue-14439... have been created already, prior to actually committing the <Merge> 5. Observe that there is 1 merge conflict. 6. <Cancel> the Merge 7. Observe that packages Shout-Tests and SLICE-Issue-14439... remain Now this problem only occurs when loading the SLICE-Issue-14439...mmz, not when loading the related Shout-Tests...mcz. To observe... 1. Remove empty packages Shout-Tests and SLICE-Issue-14439... 2. In Monticello, select Shout-Tests..1.mcz and <Merge> 3. Observe no merge conflicts. =================== I managed to reproduce as follows... 1. Create a package "Case14616" 2. Add a tag "MyTag" 3. Add a class "MyClass" into "MyTag" 4. Create "SLICE-Issue-14616...", adding dirty "Case14616" 5. Save the slice to your local package-cache 6. Open a virgin Image 7. Merge "SLICE-Issue-14616...". --> Observe the merge ccnflict. I have logged https://pharo.fogbugz.com/default.asp?14616 but I am not familiar with the Monticello architecture. Could someone who is take a look? cheers -ben

Dec. 13, 2014

Re: [Pharo-dev] SODD

by Yuriy Tymchuk

> On 12 Dec 2014, at 22:53, Mark Bestley <st(a)bestley.co.uk> wrote: > > On 12/12/2014 13:08, Yuriy Tymchuk wrote: >> >>> On 12 Dec 2014, at 11:57, phil(a)highoctane.be >>> <mailto:phil@highoctane.be> wrote: >>> >>> >>> >>> On Fri, Dec 12, 2014 at 11:34 AM, Yuriy Tymchuk >>> <yuriy.tymchuk(a)me.com >>> <mailto:yuriy.tymchuk@me.com>> wrote: >>> >>> Hi, so this message is about SODD (Stack Overflow Driven >>> Development) and Pharo/Smalltalk. >>> >>> If you look at the last questions of this guy: >>> http://stackoverflow.com/users/1906070/shiran?tab=questions you >>> can see that they are about smalltalk/squeak and asked in last 2 >>> days :). >>> >>> In fact I think that we should support asking questions on SO, as >>> a lot of people are anxious to register and talk to others on >>> mailing list, and prefer to search for solutions on SO. If weâll >>> build reasonable amount of Q/A data, it can be easier for other >>> people to start with Pharo. >>> > > However the questions should be better than these last few. This asker looks like a beginner learning and I think would be better off with a tutorial which is not supported by Stack Overflow. I suspect by asking several questions in a short time they are likely to be stopped from asking questions for a bit - there is a rate limit as people who ask lots of questions tend to have poor questions are are wanting the answerers to do their work - in this case the asker is asking OK questions but that is not what we normally see in Stack Overflow (see PHP questions for what the SO system has to deal with and see that even at beginner level Smalltalkers seem to at least know how to ask questions better than for other languages.) Yes, these questions are very poor, but maybe they can be useful for someoneâ¦ My point is that maybe we can tell people that if they have problems they can also ask them on SO with âpharoâ tag. > > > You can create a good question and answer it yourself if you want to document/show something. Yes, I try to do this prom time to time. > >>> >>> Yes, there is some activity on SO and also interesting content over there. >>> >>> I find it a bit complicated to find about Pharo/Smalltalk questions in >>> an easy way. Searching by tag (Pharo) gives a list of old questions. >>> >>> How do you get the last questions in an easy way? > > I create favourites on tags e.g. smalltalk pharo etc. > Then when you login to Stack Overflow click on one of these tags > > Note these last few questions were tagged smalltalk and squeak not pharo True, thatâs why we have to promote pharo. > >> >> There is a newest tab: >> https://space.zeo.net/g/54ma0/YYDRJUBFXB7NVBG7LMXTNECCQVWXWL3K >> > > That is not a stack overflow page. Thatâs a screenshot of SO page showing that you can browse latest questions. > >> Also you can subscribe to a tag and be notified by email. >> > > I am and these questions have not shown up yet - they tend to take a day to come through > > > -- > Mark > >

Dec. 13, 2014

[pharo-project/pharo-core] 057334: 40414

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 05733457b0099abdb2ab41731299417db5eae134 https://github.com/pharo-project/pharo-core/commit/05733457b0099abdb2ab4173… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-12-13 (Sat, 13 Dec 2014) Changed paths: A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script414.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40414.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Support.package/SmalltalkImage.class/instance/snapshot and quit/executeDeferredStartupActions_.st Log Message: ----------- 40414 10287 Nil out deferredStartupActions before leaving executeDeferredStartupActions: https://pharo.fogbugz.com/f/cases/10287 http://files.pharo.org/image/40/40414.zip

Dec. 12, 2014

[pharo-project/pharo-core]

by GitHub

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

Dec. 12, 2014

Re: [Pharo-dev] SODD

by Mark Bestley

On 12/12/2014 13:08, Yuriy Tymchuk wrote: > >> On 12 Dec 2014, at 11:57, phil(a)highoctane.be >> <mailto:phil@highoctane.be> wrote: >> >> >> >> On Fri, Dec 12, 2014 at 11:34 AM, Yuriy Tymchuk >> <yuriy.tymchuk(a)me.com >> <mailto:yuriy.tymchuk@me.com>> wrote: >> >> Hi, so this message is about SODD (Stack Overflow Driven >> Development) and Pharo/Smalltalk. >> >> If you look at the last questions of this guy: >> http://stackoverflow.com/users/1906070/shiran?tab=questions you >> can see that they are about smalltalk/squeak and asked in last 2 >> days :). >> >> In fact I think that we should support asking questions on SO, as >> a lot of people are anxious to register and talk to others on >> mailing list, and prefer to search for solutions on SO. If weâll >> build reasonable amount of Q/A data, it can be easier for other >> people to start with Pharo. >> However the questions should be better than these last few. This asker looks like a beginner learning and I think would be better off with a tutorial which is not supported by Stack Overflow. I suspect by asking several questions in a short time they are likely to be stopped from asking questions for a bit - there is a rate limit as people who ask lots of questions tend to have poor questions are are wanting the answerers to do their work - in this case the asker is asking OK questions but that is not what we normally see in Stack Overflow (see PHP questions for what the SO system has to deal with and see that even at beginner level Smalltalkers seem to at least know how to ask questions better than for other languages.) You can create a good question and answer it yourself if you want to document/show something. >> >> Yes, there is some activity on SO and also interesting content over there. >> >> I find it a bit complicated to find about Pharo/Smalltalk questions in >> an easy way. Searching by tag (Pharo) gives a list of old questions. >> >> How do you get the last questions in an easy way? I create favourites on tags e.g. smalltalk pharo etc. Then when you login to Stack Overflow click on one of these tags Note these last few questions were tagged smalltalk and squeak not pharo > > There is a newest tab: > https://space.zeo.net/g/54ma0/YYDRJUBFXB7NVBG7LMXTNECCQVWXWL3K > That is not a stack overflow page. > Also you can subscribe to a tag and be notified by email. > I am and these questions have not shown up yet - they tend to take a day to come through -- Mark

Dec. 12, 2014

Re: [Pharo-dev] how do you use scripts?

by Eliot Miranda

Hi Tudor, On Fri, Dec 12, 2014 at 3:14 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > As input for designing new features that better support scripting in > Pharo, we would benefit from a bit more input around the role scripts play > in your development life. > > To this end, I would like to invite you to share your scripting > experience. Here are some questions to start from, but feel free to diverge: > > - What kind of actions do you put in scripts? > Actions that build and/o bootstrap systems. These are typically of two different kinds: - shell scripts to launch images invoked with Smalltalk scripts - Smalltalk scripts - Do you rely on script files stored on the disk at all? > Yes. - Where do you store your scripts (in one folder, in many folders)? > Typically each project that uses one or more scripts has those scripts in the main directory or a scripts subdirectory of that project's main directory. - Do you version your scripts? > The version control system for the project does that. - Do you store them in separate files with dedicated names, or tend to put > multiple snippets in one larger file? > Definitely lots of small scripts with separate names. Some times they call each other. - Do you rely on the names of the scripts? > Yes. They typically indicate what the script does, e.g. buildspurtrunkimage.sh which in turn uses UpdateSqueakTrunkImage.st BuildSpurTrunkImage.st & LoadSpurPackages.st > - Why do you use a script file and not a class? > Ah, sometimes the script file contains a class. For example, the Newspeak bootstrap. But that class is eliminated before the image is finally saved. The choice as to whether to use a class or not depends on the complexity of the task, the usefulness of breaking things into methods etc. Sometimes the script contains many lines, sometimes it's jut way too simple for a class, e.g. BuildSqueakTrunkVMMakerImage.st: "Change the update stream to trunk, update, then build as per 4.5" [MCMcmUpdater defaultUpdateURL: 'http://source.squeak.org/trunk'; updateFromServer] valueSupplyingAnswer: true. "don't use fileIn; it causes an error when the saved image is started" Compiler evaluate: (FileStream oldFileNamed: 'BuildSqueak45VMMakerImage.st') contentsOfEntireFile The advantage that a non-class single doit script has over a class is that the former is much easier to edit with any text editor. For a class one really needs the IDE, and for some tasks one wants to edit outside of the IDE. If you want to look at some examples of scripts I use see - the shell scripts named foo.sh and the Smalltalk scripts named Foo.st, which together build Spur, in http://www.squeakvm.org/svn/squeak/branches/Cog/image - the shell scripts named foo.sh and the Smalltalk scripts named Foo.st, which together build Newspeak, in https://bitbucket.org/newspeaklanguage/nsboot_bleeding_edge/src Cheers, > Doru > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- HTH, Eliot

Dec. 12, 2014

Re: [Pharo-dev] how do you use scripts?

by stepharo

> Hi, > > As input for designing new features that better support scripting in > Pharo, we would benefit from a bit more input around the role scripts > play in your development life. > > To this end, I would like to invite you to share your scripting > experience. Here are some questions to start from, but feel free to > diverge: > > - What kind of actions do you put in scripts? some expressions > - Do you rely on script files stored on the disk at all? No Just class > > - Where do you store your scripts (in one folder, in many folders)? No never > - Do you version your scripts? No or a class methods > > - Do you store them in separate files with dedicated names, or tend to > put multiple snippets in one larger file? No > - Do you rely on the names of the scripts? No > > - Why do you use a script file and not a class? I don't > > > > Cheers, > Doru > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

Dec. 12, 2014

About Pharo books

by stepharo

Hi guys I spent a couple of days cleaning PharoForTheEntreprise. So do not stress if you chapters are not where they were used to be :). Here is what I did now there are three stages for Chapters: - Limbo (some notes) - WorkInProgress - ReadyForReviews At the end of this flow we are thinking about the following books: - Entreprise Pharo: a Web Perspective (Zinc, Neo.....) - Spec We decided to write a separate little book - Pharo: The Hidden Parts The ideas is to have many little chapters on not common aspects Stef PS: currently doing a pass on Smacc

Dec. 12, 2014

Re: [Pharo-dev] how do you use scripts?

by Sebastian Sastre

> On Dec 12, 2014, at 9:14 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > As input for designing new features that better support scripting in Pharo, we would benefit from a bit more input around the role scripts play in your development life. > > To this end, I would like to invite you to share your scripting experience. Here are some questions to start from, but feel free to diverge: > > - What kind of actions do you put in scripts? Automation. Mostly devops and orchestration (so they make Jenkins life easier (not true but it keeps the CI jobs more maintainable)) Truth is that developers save time too > > - Do you rely on script files stored on the disk at all? every day > > - Where do you store your scripts (in one folder, in many folders)? depends on the project In flow there are some scripts in some folders that creates a convenient syntax and we keep some of them in a hidden folder .hood > > - Do you version your scripts? git does it for me > > - Do you store them in separate files with dedicated names, or tend to put multiple snippets in one larger file? Iâm not considering snippets and scripts in the same category. For snippets I use workspaces. Typically I use a class with the name of the app and in its class side I put convenient methods. Some examples: Airflowing start. âstarts all the services used inside the image" Airflowing start. âstops them" Airflowing restart. âstops them, do 5 garbagecollects and starts" Airflowing maintainer update executeOn: âdatabaseNameâ. âexecutes the current update (a custom class with custom actions) on 1 particular database" Airflowing maintainer update execute. "executes the current update in all databasesâ There are others for many day-to-day things, including capturing monthly payments PetShop <https://github.com/flow-stack/petshop/tree/develop>âs backend uses that idea too PetShop stop; reset; start. PetShop <https://github.com/flow-stack/petshop/tree/develop>âs frontend is (is flow <https://github.com/flow-stack/flow>-based so weâre talking about Amber <http://amber-lang.net/>) using that idea too PetShop start âregisters the app, publishes shared remote objects and instantiates the main controller) Same for many other private projects > > - Do you rely on the names of the scripts? > Not only script names but also folder names. This is what makes the terminal to be more productive. More airflowing examples: $ <â youâre in the root of the project in dev $ ./actions <â type âa' and pres tab once and you get the actions folder, press tab again and it lists all of the things you can do, some of them are: getDataToSpace getRelease pullDev freshDev getFlowingWorker getStagingImage pullMaster when you do that, as you probably guessed, the script naming criteria becomes pretty close to method naming criteria Another relaying of the names of the scripts is for keeping configuration out of the image as used by ConfigurationFiles <http://smalltalkhub.com/#!/~sebastianconcept/ConfigurationFiles>: Itâs a very simple class that make a bunch of assumptions to allow you to have all the configuration files you want under conf/ directory so you can inside the image do things like: ConfigurationFiles at: #Zinc at: #port ConfigurationFiles at: #MongoDB at: #databaseName ConfigurationFiles at: #VNC at: #port etc etc And here is an example of how the VNC file looks like $ cat {imageDir}/conf/VNC.conf "############ VNC accessor. Settings for the VNC server so headless images can provide an UI through VNC clients" Dictionary new at: #use put: true; at: #localOnly put: true; at: #port put: 5908; at: #interactivePassword put: âsecret'; yourself > - Why do you use a script file and not a class? > As mentioned, I do use classes too. Mostly to do actions inside the worker images. Also to build images. The next examples use the ./load or ./build or ./cleanBuild script to create the development setup of the respective projects https://github.com/sebastianconcept/Mapless/blob/master/cleanBuild <https://github.com/sebastianconcept/Mapless/blob/master/cleanBuild> and to implement the image customization there is the {ProjectName}Builder class that those scripts file in to get that done. Here is Mapless example: https://github.com/sebastianconcept/Mapless/blob/master/MaplessBuilder.st <https://github.com/sebastianconcept/Mapless/blob/master/MaplessBuilder.st> Here is same idea used for the flowâs backend: https://github.com/flow-stack/flow/blob/master/backend/FlowBuilder.st <https://github.com/flow-stack/flow/blob/master/backend/FlowBuilder.st> BTW in flowâs root folder there is ./cleanBuild to trigger building both, back and frontend: https://github.com/flow-stack/flow/blob/master/cleanBuild <https://github.com/flow-stack/flow/blob/master/cleanBuild> here is how it cleans and triggers the build https://github.com/flow-stack/flow/blob/master/cleanBuildFrontend <https://github.com/flow-stack/flow/blob/master/cleanBuildFrontend> the frontendâs concrete implementation: https://github.com/flow-stack/flow/blob/master/frontend/build <https://github.com/flow-stack/flow/blob/master/frontend/build> Here is how it ./startAll hides a multiplatform start https://github.com/flow-stack/flow/blob/master/startAll <https://github.com/flow-stack/flow/blob/master/startAll> and here is the OS X implementation that opens one terminal per service started: https://github.com/flow-stack/flow/blob/master/.hood/platform/osx/basicStar… <https://github.com/flow-stack/flow/blob/master/.hood/platform/osx/basicStar…> > > > Cheers, > Doru > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > > "Every thing has its own flow"

Dec. 12, 2014