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

The menu bar in question

by Hilaire

Hi, I made a Dr. Geo build with today P7. There are several issues: - The menu bar items are not translated (see screenshot1) - The menu items does not respond, nothing happens - When a DrGeo window is open maximized, it is wrongly placed at 0@0, its size is right but misplaced (see screenshot2) - There are ugly frame around DrGeo menu and buttons, I don't know if it is related to menu bar morph related modification but it's unice (see screenshot2) The build can be tested at: https://www.dropbox.com/s/a4wb7c6od4fdl9k/DrGeo.app-18.06a.zip?dl=0 Thanks Hilaire -- Dr. Geo http://drgeo.eu

June 7, 2018

[Pharo 7.0-dev] Build #1020: 22076-Enhanced-WindowAnnouncement

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

There is a new Pharo build available! The status of the build #1020 was: SUCCESS. The Pull Request #1498 was integrated: "22076-Enhanced-WindowAnnouncement" Pull request url: https://github.com/pharo-project/pharo/pull/1498 Issue Url: https://pharo.fogbugz.com/f/cases/22076 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 7, 2018

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

by Norbert Hartl

> Am 06.06.2018 um 22:00 schrieb HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: > > Hello Martin, > > 2018-06-05 15:49 GMT-03:00 Martin Dias <tinchodias(a)gmail.com>: >> 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 >> > > Ok, so this could be used by any application to log events? Like a > lite version of Beacon logger? Do you assume Beacon is not light? Doesnât really matter but a lot of people seem to assume it is not. I think the are on two different axes. Beacon is more about distribution of notifications in the system and Ombu seems to be a store only. So the combination could be cool to have a consumer in beacon that writes to an Ombu Store Norbert > I am trying to get what would be the typical use case for a "common" app. > >> 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. > > Nice! > I am trying again to make re-use of your work if possible :) > I found a reference in EpLogNodeGraphModel. But could > HiRulerController be used off the Epicea case? > Maybe could you provide a stand-alone example? > > About the documentation use case: > > Class { > #name : #HiedraExampleModel, > #superclass : #ComposableModel, > #instVars : [ > 'treeModel rulerController' > ], > #category : #HiedraExample > } > > { #category : #initialization } > HiedraExampleModel >> initializePresenter [ > > super initializePresenter. > > rulerController := HiRulerController new. > > rulerController treeModel: treeModel. > treeModel whenRootsChanged: [ > rulerController updateFromTree ]. > > ] > > > How do you evaluate that code inside Pharo? > > Thank you, > > HernÃ¡n > > > > >> >> Cheers, MartÃn >> >>> >>> Couldn't find any description in the link. >>> >>> Cheers, >>> >>> HernÃ¡n >>> >> >

June 7, 2018

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

by Paul DeBruicker

Hi Bill, If you've loaded the Scriptaculous group then maybe the thing to do is see if the SUDevelopmentLibrary exists in the image and if so change the references from the PTDeploymentLibrary & SUDeploymentLibrary to the PTDevelopmentLibrary & SUDevelopmentLibrary They'll be functionally equivalent, and are included in the Prototype-Core & Scriptaculous-Core packages respectively. The XXDeploymentLibrary classes used to refer to the reference implementations hosted on the developer site IIRC. I forget. Paul billgkohl wrote > Thanks for the reply. I executed the line of code you suggested and still > no PT or SU Deplotment library. I'm going to look at JQuery. > > Bill > > On Tue, Jun 5, 2018 at 9:38 PM Paul DeBruicker < > pdebruic@ > > wrote: > >> 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 >> >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

June 7, 2018

Re: [Pharo-dev] ApplicationSecurity Questions

by Sean P. DeNigris

hernanmd wrote > You can check a project making use of ApplicationSecurity here: > http://www.smalltalkhub.com/#!/~hernan/IGEVET > â¦it uses Iliadâ¦ I'll check it out. Thanks. Out of curiosity, why Iliad instead of Seaside? Is Iliad well-supported/maintained? Would that be your default/recommendation for new web apps? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

June 7, 2018

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

by Martin Dias

> How do you evaluate that code inside Pharo? I don't know... for some reason I used Tonel format to write it. The package could have a toy example to use it. In fact there is one in another package (probably HiedraExamples) in sthub/Epicea. MartÃn

June 7, 2018

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

by Martin Dias

HernÃ¡n: I make myself time to answer you, and I think it can feed the poor documentation of the Ombu package :) >Ok, so this could be used by any application to log events? Like a >lite version of Beacon logger? >I am trying to get what would be the typical use case for a "common" app. I don't know Beacon. The main features of Ombu are: * It's optimized to write many new entries in a small window of time: When you log something, the log writer (OmFileStore) caches it until x milliseconds passed without activity. It was important for logging a big project via Metacello; thousands of changes may be cached and written in one shot. * It's optimized to browse a large log: The OmBlockFileStore lets you parse it by chunks. It was important for Epicea UI... when you scroll a log with thousands of changes. * Safe for multiple processes logging to same file: OmFileStore uses a "Semaphore forMutualExclusion". * Safe for multiple images logging to same directory: Suppose you are logging stuff, then save the image and, without closing it, you re-open the image file (spawn) and continue logging... you must avoid conflicts that could make a log file be inconsistent. To support this case a similars, OmSessionStore checks if the "Smalltalk session" changed before writing a new entry in a log. If it changed, the new entry will be automatically written into a different file. * Link log files: For example, this information is used in Epicea UI when you click on "link logs". Also, I wrote a script in latest Pharo 7 (below). It shows only basic usage: "Create store in a directory" directory := FileSystem workingDirectory / 'mylogs'. directory ensureCreateDirectory. store := OmSessionStore newWithBaseLocator: directory. "Write 2 objects (serialized via STON)" store newEntry: (OmEntry content: 'first'); newEntry: (OmEntry content: 'second'). "Force start writing to a new file. This happens with you re-open an image" store writingFileReference. "--> [...] /mylogss/Pharo.938mzjzhbnpo7suavqkhflnr0.ombu" store resetWithNextStoreName. store writingFileReference. "--> [...] /mylogss/Pharo.938mzjt0jwolhkcqd83ji1e7h.ombu" "Write 2 objects more in the new file" store newEntry: (OmEntry content: 'third'); newEntry: (OmEntry content: 'fourth'). "(NOW BROKEN) No matter where entries were written, you can access the complete sequence easily." store entries. "--> an OrderedCollection(an OmEntry('first') an OmEntry('second') an OmEntry('third') an OmEntry('fourth'))" Regards, MartÃn

June 7, 2018

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

by William Kohl

Thanks for the reply. I executed the line of code you suggested and still no PT or SU Deplotment library. I'm going to look at JQuery. Bill On Tue, Jun 5, 2018 at 9:38 PM Paul DeBruicker <pdebruic(a)gmail.com> wrote: > 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] [ANN] Epicea, Ombu and Hiedra packages have new "official" repository

by HernÃ¡n Morales Durand

Hello Martin, 2018-06-05 15:49 GMT-03:00 Martin Dias <tinchodias(a)gmail.com>: > 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 > Ok, so this could be used by any application to log events? Like a lite version of Beacon logger? I am trying to get what would be the typical use case for a "common" app. > 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. Nice! I am trying again to make re-use of your work if possible :) I found a reference in EpLogNodeGraphModel. But could HiRulerController be used off the Epicea case? Maybe could you provide a stand-alone example? About the documentation use case: Class { #name : #HiedraExampleModel, #superclass : #ComposableModel, #instVars : [ 'treeModel rulerController' ], #category : #HiedraExample } { #category : #initialization } HiedraExampleModel >> initializePresenter [ super initializePresenter. rulerController := HiRulerController new. rulerController treeModel: treeModel. treeModel whenRootsChanged: [ rulerController updateFromTree ]. ] How do you evaluate that code inside Pharo? Thank you, HernÃ¡n > > Cheers, MartÃn > >> >> Couldn't find any description in the link. >> >> Cheers, >> >> HernÃ¡n >> >

June 6, 2018

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

by Hilaire

Cool. Hilaire Le 06/06/2018 Ã 13:11, Guillermo Polito a Ã©critÂ : > The menu bar is populated the same way as the World menu. So if you > change the world menu, or the world menu pragma and you rebuild the > menu the menu bar will be updated accordingly. -- Dr. Geo http://drgeo.eu

June 6, 2018