Re: [Pharo-dev] Pharo Launcher ?
Sven Van Caekenberghe writes: > So I finally started using Pharo Launcher (yes I know, too late) and it is > really great ! > > Where is the documentation for it ? > > Why is it not mentioned on the main download page ? > > Where is its landing page, quick reference, 1-2-3 getting started web page ? > > I went via http://files.pharo.org/platform/launcher/ but that is highly > technical and certainly not for first time users. > > We have to promote this better. http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [ANN] Enterprise Pharo book is released!
>Is the synch done automatically? No, there is a bash script in the directory to upload the changes. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [ANN] Enterprise Pharo book is released!
On June 14, 2016 9:06:43 AM GMT+02:00, Torsten Bergmann wrote: >Nice! > >Note that the link "Deployment" on the >http://files.pharo.org/books/enterprise-pharo/ >page is broken. Anyone able to fix that? I'm on holidays but you can fix it yourself at https://github.com/SquareBracketAssociates/books.pharo.org -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
[Pharo-dev] [ANN] Enterprise Pharo book is released!
Great news everyone: the new Pharo book is finally out! "Enterprise Pharo: a Web Perspective" covers libraries and frameworks for enterprises, and in particular those doing web development. You can download it for free or buy a printed version : http://books.pharo.org/enterprise-pharo/ Other books are available at http://books.pharo.org/. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Pillar configuration bug ?
On June 1, 2016 6:31:29 PM GMT+02:00, Esteban Lorenzano
wrote:
>I’m installing pillar like this:
>
>pillar: spec
> spec project: 'Pillar' with: [
> spec
> className: 'ConfigurationOfPillar';
> loads: #('html exporter');
> repository:
> 'http://smalltalkhub.com/mc/Pier/Pillar/main' ]
>
>who, according to me, should give me elements to parse pillar
I don't have the code at hand but this not what I expect : the parser is not
necessary to export html, you just need a document model (which you could get
through a Markdown parser for example).
>export to html… but when I finish, my installation is lacking a parser.
>
>… and PRDocumentItem class>>#parser is having an undeclared behaviour
>(PRPillarParserMain is not in the system).
This has probably been fixed by Yann already in the development version.
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Screenshot of Pharo 64 bits
Clément Bera writes: > Today I helped Esteban porting the 32 to 64 bits bootstrap to Pharo. It > looks like we have a Pharo 64 bits image on 64 bits VM running on Mac & > Linux. > > Here is the wonderful screenshot showing the amazing result: very important step. Thank you! -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
[Pharo-dev] Problem with vmmaker images
Hi, the vmmaker image http://files.pharo.org/vm/src/spur/vmmaker-image.zip runs on top of Pharo 5 but with PharoV40.sources. The wget -O- get.pharo.org/vm50 downloads PharoV50.sources and not PharoV40.sources. This means scripts using the vmmaker-image need to be fixed to download PharoV40.sources manually. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [HELP WANTED] Getting ready for Pharo 5.0 release (CentOS, oldLibC, Nix, ArchLinux, and others)
Esteban Lorenzano writes: > - ubuntu ppa the ubuntu ppa package is Pharo 4 only as of now > - Nix in nix we have both pharo 4 and pharo 5 VMs. I use both everyday. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] unzip:to:
Valentin Ryckewaert writes: > Hello, > > I understood the problem with pathString and I'm ok with your opinion but I > would like to come back on the first one "fullfilename" as I understand it, > it must be a basename ? > When I read the implementation with fullfilename which would be a path > '/aPath/foo.zip'. > > newName := fullFileName copyUpToLast: FileSystem disk extensionDelimiter. > newName would be in that case : /aPath/foo' > > unzipped := FileStream newFileNamed: (pathString asFileReference / newName) > fullName. > Here the newFileNamed: parameter will be '/aPathDestination/aPath/foo' so > it could be something like '/home/home/foo' it's not correct according to > me. > > As I understand it, this message only works if fullFileName is 'foo.zip' > and is in the folder which contain Pharo image as we can't specify a path. I agree with Valentin. I have the impression this method can only unzip files in the working directory. That's a bit strange :-). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [HELP WANTED] Pre-release "First impressions count" round starting
Esteban Lorenzano writes: > So, I’m asking for reports and fixes and improvements that are not > bugfixes (even if been bug-free is the best first impression we can > have) but you believe is needed to cause a good first sight of this > release. an up-to-date Ubuntu PPA is important for anyone using Ubuntu. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Pillar vs Pandoc?
Hi Alex, Alexandre Bergel writes: > Offray is visiting us in Chile. > He showed me http://pandoc.org and it seems to be pretty cool. Looks like a > strong competitor. > I am wondering how Pillar position itself against Pandoc? AFAIK, pandoc is only a tool, not a language. Pandoc has no syntax on its own, it doesn't mean anything to "write a document in Pandoc". Nevertheless, Pandoc is nice because it accepts many formats as input and can export to many formats. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Discussing FileSystem >> #workingDirectory and VM process getcwd(3)
Mariano Martinez Peck writes: > On Tue, Mar 22, 2016 at 9:37 AM, Damien Pollet > wrote: > >> Because there is this concept called "consistency" that's interesting to >> have :p >> >> If your code wants $HOME it can ask for it explicitly, same for /. However >> if it just wants to do something in $PWD consistent with most use-cases, >> the image directory is the sensible default. >> >> > I agree with Pollet. I don't care if it is image directory or $HOME. What I > care is that $PWD of the VM process should match with FileSystem >> > workingDirectory. And right now it does not match. I was not clear enough: I agree that consistency is important and VM must answer the same as image. What that "same" should be is still unclear to me though. You propose the image folder, but this is inconsistent with other applications launched by double-click. I propose to be consistent with other applications: HOME on Linux, / on OS X. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Enterprise Pharo Book updates
Gabriel Cotelli writes: > Are the book versions available at books.pharo.org automatically > updated? It seems that are missing the last updates. no. Things are manual. Automated updated are on the continuous integration servers. https://ci.inria.fr/pharo-contribution/job/UpdatedPharoByExample/ https://ci.inria.fr/pharo-contribution/view/Books/job/DeepIntoPharo/ https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/ -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Discussing FileSystem >> #workingDirectory and VM process getcwd(3)
Damien Pollet writes: > On 22 March 2016 at 12:56, Damien Cassou wrote: > >> typical applications ran with double-click are bound to the HOME >> directory. Why do you want to do it differently? >> > > Only on Linux. On OS X it's / so, why do you want to make it the image directory? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Discussing FileSystem >> #workingDirectory and VM process getcwd(3)
Mariano Martinez Peck writes: > 1) *If Pharo was launched from double click* then we do not care about its > location and I think it's correct to default to image location: > > 1.1) FileSystem >> #workingDirectory refers to the directory containing > the .image file > 1.2) The VM process getcmd() is the default one of the particular OS ($HOME > in my OSX). > > So...there is a mismatch between #workingDirectory and VM's process cmd. > > *I think (as Damien said), that we should do a chdir() for the VM process > to match the .image location. * typical applications ran with double-click are bound to the HOME directory. Why do you want to do it differently? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Please help package Launcher with both Pharo VMs
Christophe Demarey writes: >> I don't see a script creating a pharoLauncher there. Where is it hidden/how >> is it combined? > The scripts are there: > https://github.com/pharo-project/pharo-ci/tree/master/ci-jobs/pharo the scripts there call the scripts at the root: https://github.com/pharo-project/pharo-ci/blob/master/build-windows-installer.sh https://github.com/pharo-project/pharo-ci/blob/master/build-dmg.sh -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
[Pharo-dev] Please help package Launcher with both Pharo VMs
Hi, to facilitate starting Pharo, I created the launcher. Now, there are 2 VMs that can run separate subsets of Pharo. The launcher supports that: the user "just" has to download a spur vm separately and configure it in launcher's settings. This is not beginner friendly. Could someone please package a pharo-launcher for both OS X and Windows with both VMs and the setting already set? The scripts to update are at: https://github.com/pharo-project/pharo-ci Thanks -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Space low on CI?
Max Leske writes: > The one I’ve seen (there might have been others) was > https://ci.inria.fr/pharo-contribution/computer/pharo-contribution-linux64-3 I had a problem on the same slave (94% disk full). I deleted /builds. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Little how to
stepharo writes: > Now I would love to get your ideas and their solution. getting a photo from an email address through gravatar: email := 'dam...@cassou.me'. url := 'http://www.gravatar.com/avatar/', (MD5 hashMessage: email trimBoth asLowercase) hex, '.jpg'. (ZnEasy getJpeg: url) asMorph openInHand -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] How to run a new image to execute a process
Guillaume Larcheveque writes: > I want to run the generation of a mooseModel in a new image with a new vm > process (To avoid freezing or occupying space of my first one and also have > more available memory). this is what happens for the launcher and it works on Windows: execute self needsSpurVm ifTrue: [ context singleImage launch: self class spurFullPath ] ifFalse:[ context singleImage launch: self class vmFullPath]. self class quitOnLaunch ifTrue: [ self quit ] PhLImage>>launch: aFullPathString "Use the VM that launched the current image to launch me" ^ OSProcess command: (self launchCommandWith: aFullPathString) launchCommandWith: aFullPathString | command vmCommand imagePath | vmCommand := aFullPathString isEmpty ifTrue: [ Smalltalk vm fullPath asString ] ifFalse: [ aFullPathString ]. imagePath := file pathString. command := $" asString , vmCommand , '" "' , imagePath , '"'. ^ command -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [Vm-dev] Re: [ANN] Pharo bootstrap
Guille Polito writes: > Just to tell you that I did not forget your email. Since today I'm > officially working on this, probably 2-3 days a week. I'll come back > with questions/design challenges ;) welcome back Guille!! -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Run time checking with design by contract assertions
Alain Rastoul writes: > Q: where would you define the invariants ? > > a method that is never call and is tagged ? > > myFooInvariant1 > indeed. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Run time checking with design by contract assertions
Alexandre Bergel writes: > But, all in all, what are we using pragmas here? > I can always do: > self assert: [ … ] description: … you can do that for preconditions, but for postconditions it is harder because there can be several exit points in a method. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Run time checking with design by contract assertions
Alexandre Bergel writes: > I still do not understand. I would imagine something like: > > foo > > > self bar I have the same feeling. It looks strange to me that the precondition itself decides where it applies. I have the impression that each method should list its preconditions. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] pharo intro slides?
Damir Majer writes: > Hi NG, > > I´m searching for slides which explains > - what is pharo? > - how pharo works? > - ... > > Do you have some tips / links where I can find 'pharo Intro' slides? the Pharo MOOC contains everything you need: https://ci.inria.fr/pharo-contribution/job/PharoMooc/lastSuccessfulBuild/artifact/book-result/Slides/ Look in particular at Week1 which contains the introductory courses. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Git written entirely in Smalltalk?
Ben Coman writes: > The other say I was contemplating having a git implementation written > entirely in Pharo, and today I bumped into something from your history > (~2011?) [1] indicating this might have been attempted. I'm curious > why this was abandoned in favour of libgit bindings. Max did most of the work IIRC. Then Camillo and I tried to help. But this is difficult to do because the git protocol is complex and we had not much time to dive into it. We also didn't find good documentation. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [Pharo-users] help needed for testing the order in spotter
Tudor Girba writes: > Hi, > > We need a bit of help with testing the order in Spotter. We do not have a > real solution yet, but the current one should improve the situation. > > We need a bit of feedback for this one: > https://pharo.fogbugz.com/f/cases/17656/Spotter-should-sort-search-results > > Essentially, you would need to load the latest GT-Spotter and > GT-SpotterExtensions-Core and let us know if it works better for spotting > implementors or classes. I have the impression this is already in the image. It seems to be working fine. Next time, it might help if you could just give us a Pharo expression that loads the patch. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] fully self-contained Linux VM
On February 23, 2016 1:35:48 PM GMT+01:00, "Peter Uhnák" wrote: >Hi, > >is it possible to have fully self-contained Linux VM? > >Right now if you want to use Pharo on Linux you have to install some >libraries directly in the system, which isn't particularly >user-friendly. On Linux, do it the Linux way and use a package manager. There are native packages for several distributions and if yours is not covered, you can still use Nix (which I really recommend in any cases). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [Pharo-users] Who is using Pharo Launcher and for what
Tudor Girba writes: > I use it for writing documentation and blog posts. what is the relationship between Pharo Launcher and your documentation and blog posts? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
[Pharo-dev] Looking for class
I've just tried to use to spotter to get the code of the #class method. I typed 'class' and Spotter showed a lot of methods but the method I was looking for was not in the top. In the Emacs equivalent of Spotter (helm), closest and exact matches are shown first. I guess helm uses a notion of distance to order results. In helm, I could have typed "class$" to get only methods ending with "class". -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [Pharo-users] Who is using Pharo Launcher and for what
On February 20, 2016 1:33:10 PM GMT+01:00, Tudor Girba wrote: >I use it for writing documentation and blog posts. > >Doru > >-- >www.tudorgirba.com > >"Every thing has its own flow" > >> On 20 Feb 2016, at 11:49, Damien Cassou >wrote: >> >> For my CV, I need to know who is using the stuff I'm doing. If you >use >> the Pharo Launcher, could you please tell me in which context (e.g., >> which company, open-source project) and what you use it for (e.g., >> download from CI, standard Pharo)? >> >> I don't need long paragraphs, just give me the keywords please. >> >> Thanks >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." --Winston Churchill >> Please all also tell me the company in which you work -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
[Pharo-dev] Who is using Pharo Launcher and for what
For my CV, I need to know who is using the stuff I'm doing. If you use the Pharo Launcher, could you please tell me in which context (e.g., which company, open-source project) and what you use it for (e.g., download from CI, standard Pharo)? I don't need long paragraphs, just give me the keywords please. Thanks -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
[Pharo-dev] Who is using Pillar and for what
For my CV, I need to know who is using the stuff I'm doing. If you use Pillar, could you please tell me in which context (e.g., which company, open-source project) and what you use it for (e.g., what kind of document)? I don't need long paragraphs, just give me the keywords please. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
[Pharo-dev] Any download statistics for Pharo
Hi, do we have any download statistics for Pharo? Best, -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [Pharo-users] gtoolkit 3.10 overview
Hi Tudor, Tudor Girba writes: > I promised to send a summary of the larger changes that came with the recent > integration of GToolkit 3.10. Here it is: > http://www.humane-assessment.com/blog/gtoolkit-3-10/ thank you for the detailed changelog. Please pay attention to the Settings system. I have the impression that what you did might forbid you to remove any extension in the future. What I see happening is that: 1. people start deactivating some extensions through the Settings 2. they write their Settings in a file so the settings are available for all images 3. in this file, settings are deactivated with Smalltalk code that send setting-specific messages to specific objects 4. you decide to remove an extension and remove the corresponding setting method 5. the user downloads the new Pharo and gets an error because his setting file sends messages that are not understood anymore. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Compiling the unix vm / spur
Hi Eliot, Eliot Miranda writes: > On Mon, Feb 15, 2016 at 10:37 AM, Markus Fritsche > wrote: >> I was just going to update the ubuntu ppa an wanted to supply a spur vm >> image. The compilation stopped however: >> >> -- Configuring done >> CMake Error at IA32FFIPlugin/CMakeLists.txt:11 (add_library): >> Cannot find source file: >> >> >> /home/mfritsche/src/pharo-vm-spur-2016.02.13/src/plugins/IA32FFIPlugin/IA32FFIPlugin.c >> > > That's a bug in the CMake code (which I hope will be history in a few > months). tt should be looking *only* for > > src/plugins/SqueakFFIPlugin/SqueakFFIPlugin.c > > which should include > > src/plugins/SqueakFFIPlugin/IA32FFIPlugin.c do you know what we have to change and where exactly? I also face the same problem. Thanks -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Compiling the unix vm / spur
On February 15, 2016 7:37:34 PM GMT+01:00, Markus Fritsche wrote: >Hi, > >I was just going to update the ubuntu ppa an wanted to supply a spur vm > >image. The compilation stopped however: I reported the same this morning : https://pharo.fogbugz.com/f/cases/17591/Can-t-compile-sources-2016-02-13-CMake-Error-at-IA32FFIPlugin-CMakeLists-txt -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Getting coherent shortcuts
Guille Polito writes: > I had to touch several packages, which some are not in the Pharo > repository. For this I prepared several issues for the monkey: In the TestRunner, on Linux, when I press Ctrl+a to select everything, nothing is selected. I have to press Alt+a which is not a standard Linux shortcut for selecting everything. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Getting coherent shortcuts
Guille Polito writes: > So, since today I was able to commit again, I decided to make a couple > of slices/new configurations fixing the majority of shortcuts in the > image. Like this, mac shortcuts will remain in cmd, but linux and > windows shortcuts will be with ctrl, as expected by the vast majority of > users :). The changes I made should fix 97.8882% of the shortcut > experience in linux and windows, without degrading the one in mac. Of > course, if you see any glitch, just tell. thank you very much! -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Ubuntu with Spur
On February 5, 2016 8:07:38 PM GMT+01:00, Torsten Bergmann wrote: >Is Spur already in the PPA for last stable Ubuntu or how >do I install latest spur quickly using commandline? > >Should I use zeroconf from get.pharo.org. Does it >run on latest dev version of Ubuntu? > >Thanks >T. I updated the source repository. Now, Markus must upload a new deb release. In the meantime, you can use get.pharo.org or http://nixos.org/nixpkgs/ -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [ANN] We are in "code freeze" for Pharo 5
Esteban Lorenzano writes: > We are on “just bugfixes” since some time now… I delayed the announcement > because Epicea still needs to enter and we didn’t manage to include it yet. > But well… with the exception of Epicea, no new features will be included un > Pharo 5… just bugfixes (and we have a lot of bugfixes incoming… this release > will be hard :( ) what is Epicea's integration status? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [Need help with Monkey] Removing Object>>name
Guille Polito writes: > And yes, linux VM's are not shipped with the UUID plugin... at least not > since 2014/2013... if you tell me what to change, I can release new VM sources in http://files.pharo.org/vm/src/vm-unix-sources/ -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Nitpick: Launcher Colors
"Sean P. DeNigris" writes: > I don't get the addition of alternating row colors to Launcher. As I > understand this, it's value is in a table-like situation where one wants to > track across the row in the same record. Since both panes have only one cell > per row, I don't get the purpose, and it looks really funky to me in the > dark theme. I don't care, if others agree, you can change it :-). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] "Pharo" Name Overload
Ben Coman writes: > On Wed, Jan 27, 2016 at 5:27 AM, Damien Cassou wrote: >> "Sean P. DeNigris" writes: >> >>> I now have three Pharo.app files on my Mac - Launcher, Spur, and non-Spur. >>> It >>> would be great if we can agree to call one thing Pharo, and add appropriate >>> modifiers to the other two names. >> >> I'm not an OS X user, but I have the impression that .app is reserved >> for graphical applications, one you can start with a double click. For >> me, no Pharo VM is a graphical application and thus none deserve its >> .app file in /Applications. >> >> On the contrary, what we currently call the Pharo Launcher is a >> graphical application so it deserves a .app file. I called it just >> Pharo.app because I didn't see any concurrence on the name and some in >> the Pharo board would like the launcher to be the default Pharo download >> (the one behind the big Download button on the website). > > It would be great for Pharo Launcher to be the default download, but > why can it not still be called "PharoLauncher.app". It is still just > an app on top of *real* Pharo and calling the launcher Pharo.app I > believe presents a cognitive dissonance for a newcomer to understand > the distinction. The launcher is used to start non-/more-than-Pharo > applications like Moose, so to me the launcher application is more > generic than just Pharo. Seeing a launcher is generically "a > computer program that helps a user to locate and start other computer > programs" [1] to me it makes sense to explicitly keep "Launcher" in > the app name as the default download. I disagree but I don't care enough to argue. If OS X users agree (and maybe the board as well), someone should make the change (that won't be me :-)). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] "Pharo" Name Overload
Dimitris Chloupis writes: > Spur will become the default soon enough and you will forget about the > other as you forgot about stack vm. I'm not sure this is what will happen. I have the impression that we will have one VM for Pharo 4, one VM for Pharo 5, one VM for Pharo 6... -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] "Pharo" Name Overload
"Sean P. DeNigris" writes: > I now have three Pharo.app files on my Mac - Launcher, Spur, and non-Spur. It > would be great if we can agree to call one thing Pharo, and add appropriate > modifiers to the other two names. I'm not an OS X user, but I have the impression that .app is reserved for graphical applications, one you can start with a double click. For me, no Pharo VM is a graphical application and thus none deserve its .app file in /Applications. On the contrary, what we currently call the Pharo Launcher is a graphical application so it deserves a .app file. I called it just Pharo.app because I didn't see any concurrence on the name and some in the Pharo board would like the launcher to be the default Pharo download (the one behind the big Download button on the website). We could improve the situation by putting all Pharo VMs inside the Pharo Launcher's .app file. Who volunteers? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
[Pharo-dev] Use cases for methods with optional parameters
Hi, I would like to study the impact of adding optional parameters to keyword methods in Pharo. The goal of optional parameters is to facilitate the implementation of methods where some parameters are optional. For example, Seaside has: WAComponent>>request: aRequestString label: aLabelString default: aDefaultString onAnswer: aBlock ... This method of 4 arguments has only 1 required argument (aRequestString) and 3 optional ones. In the current implementation, this results in 7 additional methods that only delegate directly or indirectly to the one above: - request: - request:default: - request:default:onAnswer: - request:label: - request:label:default: - request:label:onAnswer: - request:onAnswer: Before starting to implement anything, I need to know if it makes sense. If you want to help me, please send me all the use cases you have by giving me: - the library name (and URL if not in Catalog), or "pharo" if it's in Pharo - the class where this happens - the range of selectors that make sense For the example above, this would be: - Seaside - WAComponent - request:* Thank you very much -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [Pharo-users] [ANN] OSSubprocess first milestone
On January 14, 2016 7:33:56 PM GMT+01:00, Mariano Martinez Peck wrote: >Dear all, > >I am happy to tell you I have a first prototype of the tool for >executing >OS processes: > >https://github.com/marianopeck/OSSubprocess > > As I said many times, the main idea was to be as much as possible >FFI-based, only for executing OS commands and, from my point of view, a >better end-user API. Also, as for the first step, I had to focus on >Linux/OSX. > >I would like to thank Pharo Consortium for the sponsor of this >development >effort. Here is the first milestone! > >There are many things on my to-do but I think the code is ready for >some >usage, testing, code review and feedback! > >All classes and all methods have comments and I have quite some unit >tests. >All tests are green in my OSX and a CentOS box. > >*Important: you CANNOT have OSProcess installed in the same image as >OSSubprocess. This is because I am reusing his SIGCHLD handler and for >the >time being both cannot coexist. * > >Keep in mind that the tool may be unstable and that MAY mean a VM >crash. So >use with care, mostly the first time. If all tests passes, then there >are >much less chances of something going bad. > >Important disclaimer: my tool (OSSubproccess from now onward) is HIGHLY >influenced by a subset of the OSProcess project. There are parts which >I >even simply copied and adapted them (OSSPipe, OSSAttachableStream, >OSSUnixProcessExitStatus). Other parts, I took them as inspiration (the >idea of ThisOSProcess representing the VM process, the child watcher, >and >many others). In addition, I AM STILL USING (maybe as a first step?) >some >of the OSProcess PLUGIN (not OSProcess image side), such as the SIGCHLD >handler or the creation of pipes. > >In github url you have all the documentation of the project, included >how >to install it and use it. > >*Finally, if you test it in a OS different than OSX and CentOS please >share >with me the results (about the tests).* Tomorrow the ConfigurationOf >should >also appear in the Catalog of Pharo 5.0. > >Any feedback is appreciated. > >Best, Quick feedback: - the API seems great - thank you very much for the documentation - I wonder why you pass strings for stdout and stderr instead of streams - it would be nice to be able to subclass OSSUnixProcessExitStatus for some commands. E.g., GitProcessExitStatus could have a method isMergeConflict - how can I implement something like tail --follow -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
[Pharo-dev] Launcher 0.2.9 opens Spur images
Hi list, thanks to the awesome work of Vincent Blondeau, Stephan Eggermont and Cyril Ferlicot, Pharo Launcher 0.2.9 can be configured to open both spur and pre-spur Pharo images. You can download this version from http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher. You can safely replace your existing Launcher installation with the new one. Your images won't be affected and you will still be able to launch them. The VM coming with these builds is a pre-spur VM because Launcher is based on Pharo 4. If you want to launch Pharo 5 spur images, you need to separately download a Pharo 5 Spur VM from http://get.pharo.org/vm50 and configure the location of this VM in the Launcher settings (icon at the bottom left of the Launcher window). What I like about this release is that I didn't do anything but changing the version number in https://ci.inria.fr/pharo/view/all/job/Launcher :-). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] How to get launcher launching Spur images?
On January 13, 2016 8:27:10 PM GMT+01:00, "Esteban A. Maringolo" wrote: >Is the Ubuntu PPA updated automatically by the CI? No. Markus, on CC, is responsible for that. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
[Pharo-dev] Shutting down persona.org in November 2016
Hi, both pharo.org and pillarhub.pharocloud.com rely on persona.org for authentication. This service will disappear. --- Begin Message --- Hi Everyone, When the Mozilla Identity team transitioned Persona to community ownership, we committed resources to operational and security support throughout 2014 [1], and renewed that commitment for 2015 [2]. Due to low, declining usage, we are reallocating the project’s dedicated, ongoing resources and will shut down the persona.org services that we run. Persona.org and related domains will be taken offline on November 30th, 2016. If you run a website that relies on Persona, you will need to implement an alternative login solution for your users. We have assembled a wiki page with additional information and guidelines for migration [3], but here are the important things you need to know: Between now and November 30th, 2016, Mozilla will continue to support the Persona service at a maintenance level: * Security issues will be resolved in a timely manner and the services will be kept online, but we do not expect to develop or deploy any new features. * Support will continue to be available on the dev-identity mailing list [4] and in the #services-dev IRC channel [5]. * All websites that rely on persona.org will need to migrate to another means of authentication during this period. Beginning on November 30th, 2016, the Persona service hosted by Mozilla will be decommissioned: * All services hosted on the persona.org domain will be shut down. * Mozilla will retain control of the persona.org domain and will not transfer it to a third party. * Since the privacy of user data is of utmost importance to Mozilla, we will destroy all user data stored on the persona.org servers, and will not transfer it to third parties. We intentionally designed Persona to expose email addresses rather than opaque identifiers, which should ease the transition to other systems that provide verified email addresses. You can find guidelines on alternative login solutions on the wiki [3] and we will continue to update them over the coming year. We strongly encourage affected teams to openly discuss and blog about their migrations on the dev-identity mailing list so that others can learn from their experience. Thank you for your support and involvement with Persona. If you have any questions, please post them to the dev-identity mailing list. Ryan [1] http://identity.mozilla.com/post/78873831485/transitioning-persona-to-community-ownership [2] https://groups.google.com/forum/#!topic/mozilla.dev.identity/rPIm7GxOeNU [3] https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers [4] https://lists.mozilla.org/listinfo/dev-identity [5] http://irc.mozilla.org/#services-dev ___ Persona-notices mailing list persona-noti...@mozilla.org https://mail.mozilla.org/listinfo/persona-notices --- End Message --- -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Atomic commits
Dimitris Chloupis writes: > Most coders that use git rely on a git client of some sort, if you dont > like guis and prefer emacs, there is also magit that i hear is very good. totally agree, Magit is awesome. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Atomic commits
Hi, Nicolas Cellier writes: > I wish the commits were much more atomic than they currently are... I agree. This is important (and one of my research topics https://hal.inria.fr/hal-01116225 :-)). Martin Dias worked on EpiceaUntangler to help developers do atomic commits http://smalltalkhub.com/#!/~MartinDias/EpiceaTaskClusterer. To put that in production, we need the Random Forest algorithm implemented in Pharo. > I can still open a fresh Pharo image and browse and review the whole code > snapshot there. > Or I can navigate more easily in history with git tools. > But if I wanted a lightweight review thru web, focusing on the diffs and > navigating a bit in history without replicating the repository, I can't. Skip is working on a code review tool. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
[Pharo-dev] Pharo-contribution down
The Jenkins for pharo-contribution seems to be down: builds never finish. https://ci.inria.fr/pharo-contribution -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] pillar question
On December 29, 2015 5:56:02 PM GMT+01:00, "Clément Bera" wrote: >Is this the right place to ask questions about pillar ? > >I am trying to write documentation using pillar. I am now stuck at >conditional printing and on the contrary to my previous issues I didn't >find examples in other documentation written in pillar. > >In latex, I would do conditional printing this way: > >\newif \ifsol >\sol true >\ifsol paragraph display if sol is true \fi > >and depending if I put true or false in the variable sol, the paragraph >is >displayed or not. > >Then I can print two version of my document with different texts at >specific parts depending on this variable. > >I tried multiple ways in pillar, but I can't achieve the same result. >What >is the right way to do conditional printing in pillar ? We don't have this. But, you can use annotated paragraphs to do the same: @@hidden blabla In LaTeX, this generates a blabla environment and in HTML a div with a blabla class. You can then use latex/css tricks to show or hide these blocks -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Having Book section using Pillar?
On December 27, 2015 9:59:06 PM GMT+01:00, "Ferlicot D. Cyril" wrote: >there is not a Pillar syntax for that That's wrong. \part, \chapter, \section... are all handled the same way: configure headingLevelOffset to decide which number of exclamation marks corresponds to which latex command/HTML markup. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Adapting the launcher to Spur VM
Stephan Eggermont writes: > I've commited a PharoLauncher version that adds a setting for a spur vm > path. If you download a spur vm and point set this setting, the launcher > will start the image with the right vm is it weird if I say I love you? :-) Thank you very much -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Adapting the launcher to Spur VM
Guillermo Polito writes: > Hmm, usually an image file has a header that describes some meta data about > the image: version, some VM options, size of the image… > > If you load: > > Gofer it > squeaksource3: 'ImageWriter'; > package: ‘ImageWriter-Core'; > load. > > > You’ll get HzCogImageFormat that describes the header. Check the method > writeImageHeaderOn: byteStream forWriter: aWriter thanks Guillermo. I won't do it myself because I'm very busy and don't have much time for Pharo programming, but I hope someone using the launcher with Pharo 5 will have a look. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] MacroRecorder updates (+ another demo)
Gustavo Santos writes: > Hello guys, > > thanks for the support so far. I've been working on your suggestions. > > Some of them concerned that the example in the first demo video was too > "magic". :-P > So I made another video showing how the developer can manually configure > the tool. > Take a look: https://youtu.be/3xc3j3PjIYQ great! But you stopped the video just before showing what happens for indirect subclasses of JenkinsObject. Does macro recorder work for the sub-sub-classes as well? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
[Pharo-dev] Adapting the launcher to Spur VM
Hi, from a Pharo image, can I detect if another image needs the Spur VM or not? Best -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [IMPORTANT] Starting migration to Spur VM
Torsten Bergmann writes: > Would it make sense to close down the Pharo 5 line and start with the > Spur thing as Pharo 6 as this would make it more easily distinguishable? > Especially since Pharo 5 is very stable, already really usuable and > with Spur we do not follow our mantra of small steps. > > This would really avoid confusion afterwards within and outside of the > community. this makes a lot of sense in my opinion and I vote +1. But releasing a new Pharo currently is a lot of work, both technical and non-technical (announces, changelog, ...). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] How does Nautilus change highlighting for class definitions
Nicolai Hess writes: > 2015-12-09 14:45 GMT+01:00 Skip Lentz : > > But beware, there are multiple parts involved if you use nautilus code > pane. > - parser for syntax highlighting > - the styler itself > - completion ( you may or may not want to have NEC to popup the completion > menu) > - class / method selection dependent menu entries (Suggestions for example) > - the acceptor (on accept, a class definition is execute, a method > definition is compiled) thanks to both. > what are ini-modules? it's a tentative replacement for class-side instance creation methods that suffer from a lot of problems. It's a new concept, just like traits and slots, except that it solves the instance creation problems listed at the end of http://smalltalkhub.com/#!/~MarcoNaddeo/IniModules Thanks again -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
[Pharo-dev] How does Nautilus change highlighting for class definitions
Hi, in short: in which method is Nautilus adapting source-code highlighting based on the selection (class or method)? slightly longer: With Marco Naddeo we wanted to add ini-modules to Nautilus. Because an ini-module definition is a Smalltalk expression (just like a class definition), we want Nautilus to do source-code highlighting of an ini-module the same way it does for class definitions. How is Nautilus changing the source-code highlighting process depending on the selection (class or method)? Thank you -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Install Pharo launcher on MAC
Trussardi Dario Romano writes: > i have a macbook with Mac OS X 10.7.5 and some Pharo x.y applications. > > Now i begin a new development work and i think to started with the Pharo > launcher to manage the last and the future pharo image. > Into https://ci.inria.fr/pharo/view/Launcher/job/Launcher-Mac/ i found > this link: latest.dmg > It's the right dmg image to install ? yes > I need to do something for the old pharo applications? I don't think so > After installed the new pharo launcher, the old Pharo application is > load and works without problem? ( how they work now: open with > specific VM ) I don't understand the question. After you install the pharo launcher, you should be able to launch Pharo from the Applications menu. This will open the launcher. > In the Mac App Storei found this : > > https://itunes.apple.com/it/app/pharo-launcher/id503025789?mt=12 > It has the same name: 'pharo-launcher' but it's > another think or i wrong? this is completely different stuff > It can interact with the above? no idea -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Deployment process for Pharo :)
stepharo writes: > I'm quite sure that you will love what maximilliano is doing :) I talked to him so that he can contribute to what I already did for the Launcher. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] How to get Pharo into Ubuntu Software center
Peter Uhnák writes: > I don't use Ubuntu, but I do use Debian and I see at least these problems > > 1) Can the AptUrl ( https://wiki.ubuntu.com/AptUrl ) add a PPA repository? > From the link it seems like it can only enable/refresh them? > 2) This works out of the box only for Firefox (so you still need > instructions for Chrome, but maybe Ubuntu users don't use chrome :)) > 3) You need to specify 32bit architecture > > I have a feeling that the thrid step must be done by user, but maybe there > could be 64bit package that would execute script that would add the package > and then it would have 32bit package as dep? the best would probably be to add Pharo to the Debian official repositories. This means that Ubuntu will include Pharo as well. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Storing System Settings using STON
Yuriy Tymchuk writes:
> It is like that:
>
> [
> StoredSetting {
> #settingNodeIdentifier : '#shoreLine#autoSubmit',
> #realValue : true
> },
> StoredSetting {
> #settingNodeIdentifier : '#reIgnore',
> #realValue : Set [ ]
> }
> ]
why not:
{
'#shoreLine#autoSubmit' : true,
'#reIgnore' : Set [ ]
}
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill
[Pharo-dev] Random forest in Pharo
Hi, did anyone implement a Random Forest algorithm in Pharo? https://en.wikipedia.org/wiki/Random_forest -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [ Zn+Zdc ] Implementation of HTTPS proxying using HTTP CONNECT tunneling
Sven Van Caekenberghe writes: > Yesterday I did a first implementation of HTTPS proxying using HTTP > CONNECT tunneling for Zn+Zdc, this should now be tested by a wider > audience. With this new feature it should now be possible to access > HTTPS Urls from behind an HTTP proxy. This is for all OS platforms. > Thanks Nicolai for finding the spec reference and Torsten for the > push. I have no use for that but I think this goes in the right direction. Thank you very much! -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [OT] Slides the web way
Esteban A. Maringolo writes: > I used reveal.js vía Slides.com for a demo [1] > > It's produces really nice presentations. could you please give us the sources? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Issue Tracker Choice
Sean P. DeNigris writes: > Now that the dust has settled after the move to FogBugz, maybe we should take > another look. I know that we're already spread thin, but we all know it's a > poor fit for our / OSS workflows, and I shudder to think at how many > potential contributors gave up due to the IMHO significant barriers to > entry. could you please tell us what you don't like about FogBugz and what you would like to see in another issue tracker? Moving all the issues, writing the documentation, and updating our tools where difficult enough, we should not do it lightly. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Comment of BlockClosure>>sourceNode
Thierry Goubier writes: > 2015-10-05 14:53 GMT+02:00 Damien Cassou : > >> The comment of the following method seems to be more an explanation of >> the implementation than of the expected behavior. Should we change that >> to something like: "Return an instance of RBBlockNode representing the >> receiver's AST." >> >> Which would completely hide the reason for going backward one step in the > bytecode. > > I'd vote for adding to the current comment. the existing comment is useful, I agree. https://pharo.fogbugz.com/f/cases/16721/Comment-of-BlockClosure-sourceNode-is-unclear -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
[Pharo-dev] Comment of BlockClosure>>sourceNode
The comment of the following method seems to be more an explanation of the implementation than of the expected behavior. Should we change that to something like: "Return an instance of RBBlockNode representing the receiver's AST." BlockClosure>>sourceNode "the bytecode just before the first bytecode of the block is a bytecode that creates the complete block" ^ self method sourceNodeForPC: self startpc - 1. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Copy image from Macbook to Ubuntu system
Trussardi Dario Romano writes: > Ciao, > > i have a Pharo-1.4-one-click application run on MacBook. > > Now for security problem i need to port and run it on Ubuntu system > 14.04.3 > > I can copy from MacBook and paste on Ubuntu ? > > On the Ubuntu system i load the pharo-launcher but it > don't manage old pharo 1.4 version. copy your image from your Mac disk to Ubuntu. If you installed pharo through the PPA, you can type $ pharo-vm-x YOURIMAGE.image -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] If all Pharo projects were on GitHub...
Alexandre Bergel writes: > Why not having just one folder level? As we would have in any other > language? that's not true. In java, a Java path typically looks like: project/src/main/java/org/apache/project/base/model/MyModel.java -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Title of Pharo books page
Torsten Bergmann writes: > http://books.pharo.org > http://files.pharo.org/books/ > > The title of these pages is "Bootstrap 3 Template" instead > of "Pharo Books". Who is able to change the page? I changed it but we should wait for the cache to refresh. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [Pharo-users] Changing method icons priorities in nautilus
Peter Uhnák writes: > So would it make sense to swap the priority? I agree with you. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] If all Pharo projects were on GitHub...
philippe.b...@highoctane.be writes: > It isn't. It is actually very easy to use git. > > Time for a video :-) > > Expect that for tomorrow. tomorrow is today :-). We expect it! Thanks Philippe -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] If all Pharo projects were on GitHub...
Alexandre Bergel writes: > I have tried several times to use Git for my project. But I do not > want to spend time on configuring .gitattribute and other > configuration file. This does not go in the right direction I believe. > Why is it easier to use git with Java than it is with Pharo? I disagree, I think configuring .gitattribute (for the merge driver) is an important step forward. It means that Pharo can control the merge. Currently, it's only useful for metadata. But later, it might be useful to facilitate code merges: e.g., a method is renamed in a branch and improved in another. This should not generate a conflict. With Epicea, we might be able to avoid this conflict in the future and drive the merge successfully. Another example: two branches each adds an instance variable to the same class. This should not generate a conflict. The merge driver could detect that and merge successfully. Final example: the merge driver could run the unit tests while merging to tell the developer when a merge is correct and when it is not. The merge driver means we can merge ASTs, not lines of source code. For me, the merge driver is the future, not the past. Thanks Thierry. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] List Archive Error: lists.pharo.org
Torsten Bergmann writes: > I get an Internal Server Error on: > http://lists.pharo.org/mailman/listinfo seems to work for me -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] WhatsUp from: 2015-09-21 until: 2015-09-30
seas...@rmod.lille.inria.fr writes: ### Here's what I've been up to since the last WhatsUp: - release Pharo code to inspect Jenkins server (https://github.com/DamienCassou/pharo-jenkins) ### What's next, until 2015-09-30 (*): - work on the Launcher -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
[Pharo-dev] Remove rule "References an abstract class"
This lint rule pops up all the times and my code is always ok. I typically have to reference an abstract class when: - the abstract class takes care of choosing the concrete class to instantiate - the abstract class takes care of some shared variable for its subclasses (e.g., a cache or an shared external object) I propose to remove this rule which has never been useful for me. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [Survey] QualityAssistant experience mini-survey
Mariano Martinez Peck writes: > OK Done. > Where I can see the answers now? :) I put I didn't know many of the > features (I use it 99% of the time in Nautilus) and I do want to know now! I agree, where can we get information about the not-so-visible features? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [Pharo-users] [Moose-dev] Pillar 2.0.0: Introduction of PetitPillar
Alexandre Bergel writes: > I use Pillar for AgileVisualization. One problem I have is that the > book contains many code snippets. How can I run all the code snippet > in order to spot error? Is there an easy way for that? something like https://github.com/pillar-markup/pillar/issues/71 ? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [Pharo-users] Pillar 1.1.0 released
Hi Johan, Ferlicot Delbecque Cyril writes: > Le 13/09/2015 10:28, Johan Brichau a écrit : >> I just noticed that in the most recent version of Pillar, the instvar >> #embedded was removed from PRReference This breaks Pier… though right >> before this change I could make Pier3 work with Pillar just fine. >> >> The embedded var is used to specify that component references are to >> be embedded in the page. There are more components than Figures in >> Pier. >> > We removed that because since Figures are not link anymore we do not > need it. If the reference is a link, it is not embedded, else it is. > We plan latter to have more embedded item than Figures, maybe we can > just and a class between Reference and Figure (PREmbeddedReferences). > With that we do not need the ivar. > > But since Pier3 doesn't evolve anymore I proposed to someone to freeze > the version of Pillar needed for the stable version of Pier3. But I > didn't get an answer. I totally agree with Cyril. We can't limit the development of a dependency forever because a dependent has more or less stopped evolving. Before, a figure was a link with embedded = true. This was silly because each visitor had to do something specific for figures (e.g., in html you want a , in latex you want \includegraphics). This is totally different from what is expected of a link. Now a figure is not a link anymore, it is a reference. There can be multiple kinds of references but the embedded parameter what not of any use for Pillar anymore. So we decided to remove it, knowing that Pier used it to embed Pier components. So, Pier users have 2 solutions now: - either adapt Pier's configuration so that it uses an old version of Pillar; - or adapt Pier's code to rely on the new Pillar. This might require some adaptations to Pillar which we can discuss. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] merging in a filetree repository
Esteban Lorenzano writes: > Most of our problems here is because we insist on being interchangeable > between git and mcz. > While treating git as “just another repository” can feel appealable in > certain cases (for example, in the super-uncommon way of handle vm building > we have, when we use git and Eliot uses squeak source, then we are kind of a > mirror), this is not the most common usage: if you start a project on git, > you are expected other contributors use git too… same as in any other SVC > tool (there is not compatibility between SVN, HG, GIT, etc.) > > Of course, it looked like a good idea at the beginning, but now I think is > counterproductive (is the kind of ideas that are great at the beginning > because it provides security/confortability to users, but with time > demonstrate obsolete). > > What we actually need is tools that can load configurations from different > sources (for example, I have a project in git who uses seaside and I want a > configuration who loads both…). > But… guess what? WE ALREADY HAVE IT Metacello is perfectly capable of > doing that. Gofer is capable of doing that. Heck, even monticello is capable > of doing that as long as we do not pretend their are interchangeable! > > So, again… what we actually need is to accept reality: we do not need all > that metadata in 99% of cases! do you propose to stop using Monticello completely? Just have a snippet to load code from a directory and store packages to a directory? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] merging in a filetree repository
Alexandre Bergel writes: > Also, if I understand correctly, at each new repository I need to create a > file .gitattributes : > > *.package/monticello.meta/version merge=mcVersion > *.package/*.class/methodProperties.json merge=mcMethodProperties > *.package/*.class/properties.json merge=mcProperties > *.package/*.extension/methodProperties.json merge=mcMethodProperties > *.package/*.extension/properties.json merge=mcProperties there are many potential places for these attributes: - the git project level (you can even commit it so all contributors benefit from it) - a top-level directory where git projects are cloned - ~/.config/git/attributes if you want it for all your git projects (that's what I'm trying) - /etc/gitattributes if you want it for all users of your environment - anywhere provided the place is referenced in your global git configuration Read http://git-scm.com/docs/gitattributes for more information -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] WhatsUp from: 2015-09-07 until: 2015-09-20
seas...@rmod.lille.inria.fr writes: > ### Here's what I've been up to since the last WhatsUp: - Misc - improve Pharo flyer - Launcher - write a student project proposal to get an intern - start mocking a new GUI - Starter kit - videos - exercices - slides - finish preparing it - send it to the usb stick creator - Mooc (new course on Pharo) - clean the build - make the build pass (fix unicode characters) - improve beamer template (for PDF slides) - new lecture with screencast (create a contact book with web interface) - Pillar - progress on PetitPillar with Cyril - rewrite the default configurations implementation - helped a bit Cyril move Pillar issues to github.com/pillar-markup/pillar - fix job - proof read changes to the documentation by Cyril - fix Pillar bash script (add missing --baseDirectory because Pharo does not know its PWD) - Books - use new Travis infrastructure (sudo: false) - proof-read of an UPBE pull request - fix jobs regarding new Pillar - redo some figures to increase print quality (300dpi) - update latex installation on a slave > ### What's next, until 2015-09-20 (*): - Pillar - release new version - some bug fixing - little enhancements -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
[Pharo-dev] Pillar 1.1.0 released
Cyril Ferlicot and I have polished Pillar 1.0.0 a little. Here is 1.1.0
changelog:
- add shebang to generated pillarPostExport.sh
- improve pillarPostExport.sh messages a little
- HTML exporter
- output a if and only if the Pillar figure has both a
caption and a label
- LaTeX exporter
- output a \begin{figure} if and only if the Pillar figure has both
a caption and a label
Cyril migrated the list of issues and feature requests from
smalltalkhub.com to
https://github.com/pillar-markup/pillar/issues
Please report issues, describe feature requests and ask questions there.
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [ANN] Pillar 1.0.0.
Ferlicot D. Cyril writes: > I finished 5 months of internship into the RMoD team. I worked on Pillar > and I am glad to announce the version 1.0.0! > You can find an updated documentation of this version here : > https://ci.inria.fr/pharo-contribution/view/Books/job/EnterprisePharoBook/lastBuild/artifact/book-result/PillarChap/. Cyril has been a great student. His contributions to Pillar are all important. Now that Pillar 1.0.0 is released, we should try to move to PetitPillar (done at 90%). There might be some compatibility problems with existing documents but the great test suite (2100 tests covering 94% of the code) should limit them. The TODO list is now much larger but I guess that's a good sign: http://www.smalltalkhub.com/#!/~Pier/Pillar. Please contribute! -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Does somebody use resumable test failures?
Guillermo Polito writes: > We have a set of methods like > > #assert:description:resumable: > > That > - have no users besides the tests that test the feature (no real tests > using it) > - there are two implementations and the one in TAssertable is broken > (sends #isResumable: that has no implementors) > > Does somebody see some value in this method? Pillar uses them but I don't know why: testParseLevel1 | wiki text tree | wiki := '!foo'. tree := PRDocument new add: ((PRHeader new) level: 1; add: (PRText content: 'foo'); yourself); yourself. self assertWiki: wiki equalsTree: tree. assertWiki: aString equalsTree: aDocument "Assert that parsing aString results in aDocument." self assert: (self parser parse: aString) = aDocument description: aString resumable: true -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Launcher Issues
Sean P. DeNigris writes: > For "Issue 16115: Launcher: Update Common Tools for Moose 5.1 Release" > (https://pharo.fogbugz.com/default.asp?16115), the fix has been picked up by > the CI and I verified that it works. What is the process here? Shall I close > the issue with something like "in build #51"? I released 0.2.8 from your code. Thanks. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] [Pharo-users] Searching for similiar projects
Jigyasa Grover writes: > Further, I would like to request to put up my application on the CI Automated > Build server for Pharo. > I have already registered on INRIA and my request to join 'Pharo > Contribution' has also been approved. > Further, I am searching for similiar projects as sQuick so that it would be > easier to put for automated build using the existing build. click "New Job" in the top left corner of http://ci.inria.fr/pharo-contribution. Choose a name and select "Create from template". Choose TemplateJob (or JobTemplate, I forgot). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] https://readthedocs.org/
p...@highoctane.be writes: > How would we integrated pillar html output in here? > > https://readthedocs.org/ there is already a prototype Pillar's gitbook exporter that worked well when I wrote it. This uses the Markdown exporter. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
[Pharo-dev] Fwd: [Pharo-users] "Oops! Invalid username or password" when saving Settings on smalltalkhub
Damien Cassou writes: > I'm trying to update the description of the Pillar project at > http://www.smalltalkhub.com/#!/~Pier/Pillar/settings. Unfortunately, > when I press the green "Update" button, I face a > > Oops! Invalid username or password > > red warning on top of the page and my changes are not saved. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Can someone add me to the Pharo team
Alexandre Bergel writes: > On Smalltalkhub? > I would like to contribute to Bloc I tried but got "Invalid username or password" -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] http://mc.stfx.eu/ZincHTTPComponents
Sven Van Caekenberghe writes: > Just a quick note to help you all keep your sanity: the last days > there was a problem with the http://mc.stfx.eu/ZincHTTPComponents > repository. It hit 1000 entries, which was an internal limit for AWS > S3 that is used as the backing store for mc.stfx.eu. I had to work > around that (see Zinc-AWS if you are interested). Of course, it took a > while to realise what was happening, it was all pretty weird ;-) TLDR; > things should be back to normal now. thank you very much Sven. Your work is important. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Pay attention recent changes in the source manager can lead to loss of code
stepharo writes: > I experienced that and lost my changes. where is Epicea -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] We want to remove historyNavigation from Nautilus...
stepharo writes: > we really need to cleanup nautilus and we are thinking to remove the > history navigation. > So we hope that not that many people will cry but we should move on. > We are also cleaning the group management. what about removing the Nautilus history UI (drop-down list) but let Nautilus continue saving the information somewhere? That way, Spotter can find it. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
Re: [Pharo-dev] Comments in STON
Sven Van Caekenberghe writes: > What do you think ? this looks like a very good solution. Thank you very much Sven -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill
