June 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Missing Scriptaculous classes in Pharo "Seaside-3.1-portable.app"

by Paul DeBruicker

Hi William, Your image probably doesn't have the Scriptaculous classes loaded. You can load them by running the following code in a workspace: ConfigurationOfSeaside3 project stableVersion load: 'Scriptaculous' Scriptaculous isn't deprecated but isn't the future. jQuery has better support/more active users in Seaside these days. But in the context of the book I wouldn't worry about the fact that its using Scriptaculous and instead follow along and focus on learning about how you're writing/using Javascript for the browser from the Smalltalk image which will be more generally useful no matter what js library is the hot stuff now or in the future. Once you "get" Scriptaculous or jQuery changing to another for a different project is easy. Also there is a seaside list here: http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside you can join for Seaside specific questions like these. It is also available on the http://forum.world.st site. Hope this helps. Paul billgkohl wrote > I am working in Win10 and going through "Dynamic Web Development with > Seaside" book using Pharo "Seaside-3.1-portable.app". In Chapter 20.1.2, > when I attempt to add the method below to the ToDoListView class, the > classes PTDeploymentLibrary and SUDeploymentLibrary are not found in the > image. I tried using the PTDevelopmentLibrary and SUDevelopmentLibrary > classes, but the Scriptaculous effects which should be available in later > exercises does not show up. Am I way behind the web development curve in > using Scriptaculous and if so what web development environment should I be > looking at? > > ToDoListView class>>initialize > (WAAdmin register: self asApplicationAt: 'todo') > addLibrary: PTDeploymentLibrary; > addLibrary: SUDeploymentLibrary > > William Kohl -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

June 6, 2018

Re: [Pharo-dev] Iceberg "Duplicated project!"

by Martin McClure

On 06/04/2018 11:33 AM, Esteban Lorenzano wrote: > hi, > >> On 4 Jun 2018, at 19:11, Martin McClure <martin(a)hand2mouse.com> wrote: >> >> On 06/04/2018 05:34 AM, Esteban Lorenzano wrote: >>> hello Martin, >>> >>> This is becacuse metacello finds another version already registered. >> How is it already registered? This is a fresh image. The only thing that >> has happened is that it is already cloned, since I had loaded it in a >> different image. Deleting the cloned repository makes it work, but fails >> again on the next clean image until I delete the repository again. >> This does not seem correct. It was working correctly a week earlier >> (which is, I think, two Iceberg versions ago?) > it was not working properly. > what happened before is that iceberg was silently taking the version already present. > this may be the preferred behaviour but in other contexts is plain wrong, hence the need to force you to choose. Hi Esteban, Thanks for the explanation. I guess that makes sense. The terminology is a bit confusing -- "Loaded" is what you have on disk locally (but not in the image)? and "Incoming" is what's in the Git remote repository? > > this is why we introduced the #onUpgrade: protocol. > > btw, even if is not an âupgradeâ, iceberg will fail to detect a reference to (for example) tag v1.0.0 is the same as a commit SHA (we are working on this, but it will not be anytime soon). Ah, so if I'm on, say, branch "master" and my local repo is on the same SHA as the latest commit to "master" on the upstream, it will still think it's an upgrade? Nice to know that this will (someday) be smarter. I know these things take time and effort, which is appreciated. > > So, I guess you need to go for the #onUpgrade: mechanism. OK, I'll give that a try. Thanks again, -Martin

June 6, 2018

[Pharo 7.0-dev] Build #1013: 22073-BaselineOfIDE-rely-on-deprecated-classes

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1013 was: SUCCESS. The Pull Request #1491 was integrated: "22073-BaselineOfIDE-rely-on-deprecated-classes" Pull request url: https://github.com/pharo-project/pharo/pull/1491 Issue Url: https://pharo.fogbugz.com/f/cases/22073 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 5, 2018

Re: [Pharo-dev] [PROPOSAL] Put the WorldMenu in a Menu bar

by Hilaire

Can the bar menu be customized as it is the case with the World menu ? (i.e. DrGeo world menu) Hilaire Le 01/06/2018 Ã 14:22, Cyril Ferlicot D. a Ã©critÂ : > Missing features: > - What do we do when Pharo is not wide enough? > - What to do when a window is dragged behind? > - Make it parametrizable to allow users to build a bar with their own > menu builder > - Add shortcuts to open the menu windows like (maybe) > - Update it when we change the font size (this is a general Pharo problem) -- Dr. Geo http://drgeo.eu

June 5, 2018

Re: [Pharo-dev] [ANN] Epicea, Ombu and Hiedra packages have new "official" repository

by Martin Dias

On Tue, Jun 5, 2018 at 3:30 PM HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > What are Ombu and Hiedra? Hello HernÃ¡n, this is how I described them: Ombu: "Epicea has a small subproject, named Ombu, which provides simple persistence. By default, Ombu uses STON to write the events when they are announced in the system." ------- from http://smalltalkhub.com/#!/~MartinDias/Epicea Hiedra: "It is a small Pharo project to visually connect items in a history-like graph. It uses Athens, and provides support for Morphic and Spec." ------- from https://github.com/tinchodias/hiedra which is a repo that I might close or should say in readme that it's not the official repo But not sure if I described correctly... in concrete, Hiedra is what's used from Epicea Spec UI in a TableModel to draw the links between epicea logs in the left panel. Cheers, MartÃn > > Couldn't find any description in the link. > > Cheers, > > HernÃ¡n >

June 5, 2018

[Pharo 7.0-dev] Build #1012: 22074-BaselineOfIDE-still-has-reference-to-QualityAssistant

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1012 was: FAILURE. The Pull Request #1492 was integrated: "22074-BaselineOfIDE-still-has-reference-to-QualityAssistant" Pull request url: https://github.com/pharo-project/pharo/pull/1492 Issue Url: https://pharo.fogbugz.com/f/cases/22074 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 5, 2018

Re: [Pharo-dev] [ANN] Epicea, Ombu and Hiedra packages have new "official" repository

by HernÃ¡n Morales Durand

Hello Martin, 2018-06-05 12:16 GMT-03:00 Martin Dias <tinchodias(a)gmail.com>: > Hello, > > The new "official" repository for Epicea*, Ombu* and Hiedra* packages > in Pharo >= 7 is just Pharo's github > (https://github.com/pharo-project/pharo/) > What are Ombu and Hiedra? Couldn't find any description in the link. Cheers, HernÃ¡n

June 5, 2018

Re: [Pharo-dev] [ANN] Epicea, Ombu and Hiedra packages have new "official" repository

by Martin Dias

On Tue, Jun 5, 2018 at 12:35 PM Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > > > Hello Martin, > > Thank you for the clarification. > > Can we start to change things in Epicea (like renaming tests packages to > follow the convention) or do you still need to sync the Pharo version? > > Have a nice day. > Yes, you can start. Could this be reopen? https://github.com/pharo-project/pharo/pull/377 but it was only for Ombu and don't know if it's outdated... I mean, if any other change to the involved packages was merged since the PR was created. MartÃn

June 5, 2018

Missing Scriptaculous classes in Pharo "Seaside-3.1-portable.app"

by William Kohl

I am working in Win10 and going through "Dynamic Web Development with Seaside" book using Pharo "Seaside-3.1-portable.app". In Chapter 20.1.2, when I attempt to add the method below to the ToDoListView class, the classes PTDeploymentLibrary and SUDeploymentLibrary are not found in the image. I tried using the PTDevelopmentLibrary and SUDevelopmentLibrary classes, but the Scriptaculous effects which should be available in later exercises does not show up. Am I way behind the web development curve in using Scriptaculous and if so what web development environment should I be looking at? ToDoListView class>>initialize (WAAdmin register: self asApplicationAt: 'todo') addLibrary: PTDeploymentLibrary; addLibrary: SUDeploymentLibrary William Kohl

June 5, 2018

Re: [Pharo-dev] [ANN] Epicea, Ombu and Hiedra packages have new "official" repository

by Cyril Ferlicot D.

On 05/06/2018 17:16, Martin Dias wrote: > Hello, > > The new "official" repository for Epicea*, Ombu* and Hiedra* packages > in Pharo >= 7 is just Pharo's github > (https://github.com/pharo-project/pharo/) > > This will ease to fix a bug or add a feature on those packages. At > least, will be easy to me... > > BEFORE: > 1. Developer creates PR in github.com/pharo-project/pharo/. > 2. Integrator merges PR. > 3. I merge "upstream" (smalltalkhub/Epicea) usually several of those PRs. > 4. I create a new version in ConfigurationOfEpicea (in smalltalkhub/Epicea). > 5. I create a PR in github.com/pharo-project/pharo/ to integrate the > new version in smalltalkhub. > > NOW: > Only steps 1 and 2. Yeah! > > BTW, I did deprecate: > - Smalltalkhub repo (http://smalltalkhub.com/#!/~MartinDias/Epicea) > for pharo > 6.1 (updated its readme) > - Jenkins job (https://ci.inria.fr/pharo-contribution/job/Epicea/) > > Reference to the discussion: https://github.com/pharo-project/pharo/pull/1366 > Hello Martin, Thank you for the clarification. Can we start to change things in Epicea (like renaming tests packages to follow the convention) or do you still need to sync the Pharo version? Have a nice day. > Cheers, > MartÃn > -- Cyril Ferlicot https://ferlicot.fr

June 5, 2018