Re: [Pharo-users] Boostrap for seaside : incorrect JQuery version

I'm sorry, I should be more clear - I copy&pasted the Bootstrap 3.3.7 code from here , since 3.3.7 solved the issue I mentioned. The result is that mouse clicks behave as they should, and there is no error on browser's console anymor

Re: [Pharo-users] Boostrap for seaside : incorrect JQuery version

I found a possible solution. The Bootstrap v3.3.6 had a compatibility issue with jQuery 3.0 (please see this issue ). I tested a possible workaround with copy & pasting the bootstrap.js code into TBSDevelopmentLibrary>>jsbootstrapJsContent. This

Re: [Pharo-users] Traits for class methods?

On Mon 11 Feb 2019 at 20:36, Hilaire wrote: > With singleton you will access class variable, which you can't with a > trait, so you will need a setter, but should work I guess Hi, Since Pharo 7, Traits are statefuls. See documentation at: https://github.com/pharo-open-documentation/pharo-wiki

Re: [Pharo-users] Traits for class methods?

With singleton you will access class variable, which you can't with a trait, so you will need a setter, but should work I guess Hilaire -- Dr. Geo http://drgeo.eu

Re: [Pharo-users] Traits for class methods?

Rectifying, It does as expected and self points to the target class. This odd behavior happened to me when I implemented the initialize method on the class side of a Trait and then clicked the 'Run Script' Button on the target class. On Mon, Feb 11, 2019 at 4:52 PM Vitor Medina Cruz wrote: > It

Re: [Pharo-users] Traits for class methods?

It seems, however, that self points to the trait class, instead of the target object class. Is that correct? Instance side methods behave as expected and self points to the target object. On Mon, Feb 11, 2019 at 2:19 PM Cyril Ferlicot wrote: > On Mon, Feb 11, 2019 at 4:50 PM Konrad Hinsen > wro

Re: [Pharo-users] [ANN] Pharo Launcher 1.6 released

On Mon, 11 Feb 2019 at 18:19, Christophe Demarey < christophe.dema...@inria.fr> wrote: > Hi Ben, > > Le 8 févr. 2019 à 15:23, Ben Coman a écrit : > > > > On Fri, 1 Feb 2019 at 21:28, Christophe Demarey < > christophe.dema...@inria.fr> wrote: > >> Hi all, >> >> Pharo Launcher 1.6 has just been rel

Re: [Pharo-users] Traits for class methods?

On Mon, Feb 11, 2019 at 4:50 PM Konrad Hinsen wrote: > > Hi everyone, > > A quick question: is it possible to use traits to define class methods? > > For example, could the popular singleton pattern consisting of the > three class methods #uniqueInstance, #new, and #reset plus the instance > varia

[Pharo-users] Traits for class methods?

Hi everyone, A quick question: is it possible to use traits to define class methods? For example, could the popular singleton pattern consisting of the three class methods #uniqueInstance, #new, and #reset plus the instance variable uniqueInstance be packaged as a trait? Konrad.

Re: [Pharo-users] #pathString: sent to nil when loading with Metacello

I will log this as a bug - unless someone has any other thoughts. It looks to me that Iceberg incorrectly ignores the full path of a repository, meaning that other projects could equally collide with each other by virtue of having the same name? (e.g. #guessRegisteredRepository is guessing wrong

Re: [Pharo-users] [ANN] Pharo Launcher 1.6 released

Hi Ben, > Le 8 févr. 2019 à 15:23, Ben Coman a écrit : > > > > On Fri, 1 Feb 2019 at 21:28, Christophe Demarey > wrote: > Hi all, > > Pharo Launcher 1.6 has just been released! It is available from > http://pharo.org/download .

Re: [Pharo-users] Loading TelePharo on Pharo 7

Hi Serge. You need to add option to metacello script onConflict: or onUpgrade: with block [:warn | warn useIncoming]. I do not have computer now to give you exact code. Problem that telepharo depends on old version of Calypso but image includes the latest one. It needs to be fixed. I will look at