- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] Fuel version

by David T. Lewis

On Fri, May 01, 2015 at 08:47:48PM +0200, Max Leske wrote: > > > On 01 May 2015, at 18:14, Johannes Rasche Kreuzberg <Johannes(a)Rasche-Kreuzberg.de> wrote: > > > > Max, > > > > well the ConfigurationOfFuel in Pharo 3 does not know Fuel 1.9.4 > > > > and in Pharo 4 there is no ConfigurationOfFuel > > neither in the image (ConfigBrowser) > > nor on http://smalltalkhub.mc/Pharo/MetaRepoForPharo40/main <http://smalltalkhub.mc/Pharo/MetaRepoForPharo40/main> > > Fuel is part of Pharo, so you won???t find a configuration in the meta repository. That???s why I posted the Gofer code to get the latest configuration with version 1.9.4: > FYI, I use Fuel in Squeak. It is a good way to transmit objects between images in RemoteTask (part of CommandShell/OSProcess). Dave > Gofer it > url: 'http://smalltalkhub.com/mc/Pharo/Fuel/main'; > package: 'ConfigurationOfFuel'; > load. > ((Smalltalk at: #ConfigurationOfFuel) project version: ???1.9.4') > load. > > > (See http://rmod.inria.fr/web/software/Fuel/Version1.9/Documentation/Installation) > > We have builds that make sure that version is loadable in Pharo 3 and 4, so it should work. Otherwise, please hit me up again. > > Cheers, > Max > > > > > what's up? do I oversee somthing relevant ? > > > > Johannes > > > > Am 30.04.15 um 15:04 schrieb Max Leske: > >> > >>> On 30 Apr 2015, at 14:40, Mariano Martinez Peck <marianopeck(a)gmail.com > >>> <mailto:marianopeck@gmail.com>> wrote: > >>> > >>> Johannes, > >>> > >>> The simples approach is that you materialize your object in 3.0, then > >>> load the same version as fuel from pharo 4.0 and then serialize again > >>> in 3.0. > >> > >> That should work without problems now. Just be aware that some things > >> have changed dramatically (e.g. MethodContext no longer exists, instead > >> there is now Context). For most of the objects however, migration should > >> work fine when you use the Pharo 4 version (1.9.4) in Pharo 3. > >> > >>> After that, you can materialize in 4.0. > >>> The other alternative is that in 4.0 you load older version of Fuel > >>> (the one in 3.0), then import, the expert, then load new fuel again. > >>> > >>> I have been doing this since Pharo 1.4 until 4.0 since my client's app > >>> also uses Fuel. And the process was always quite simple and only once > >>> per release. > >>> > >>> Migration is something we miss in Fuel..and even if we have promised > >>> to keep format unchanged, sometimes the evolution of Pharo itself (not > >>> the internal Fuel format representation) makes the format to be broken > >>> from one version to the other. So until we have a better automagic > >>> migration tool, the above trick should work. > >>> > >>> Also...see this > >>> link: http://rmod.inria.fr/web/software/Fuel/Version1.9/Documentation/FormatMigra… > >>> > >>> > >>> Btw...here is the scrip I used to migrate from 1.8 to 1.9... this is > >>> just an EXAMPLE of how you can do it..but do not copy it becuase it > >>> uses old version of the code repositories, etc... > >>> > >>> > >>> > >>> | oldVersion newVersion fileNames objectsByFileName materializerClass | > >>> > >>> oldVersion := '1.8'. > >>> newVersion := '1.9'. > >>> fileNames := #( > >>> > >>> '/Users/mariano/XXX/aaaaDB.fdb' > >>> '/Users/mariano/XXX/bbbbDB.fdb' > >>> '/Users/mariano/XXX/ccccDB.fdb' > >>> '/Users/mariano/XXX/ddddDB.fdb' > >>> '/Users/mariano/XXX/eeeeDB.fdb' > >>> '/Users/mariano/XXX/ffffDB.fdb' > >>> ). > >>> objectsByFileName := Dictionary new. > >>> > >>> materializerClass := Smalltalk at: #FLMaterializer. > >>> > >>> fileNames do: [ :fileName | > >>> objectsByFileName > >>> at: fileName > >>> put: (materializerClass materializeFromFileNamed: fileName). > >>> FileDirectory default copyFileNamed: fileName toFileNamed: fileName, > >>> '-', oldVersion asString ]. > >>> > >>> Gofer it > >>> squeaksource3: 'Fuel'; > >>> package: 'ConfigurationOfFuel'; > >>> load. > >> > >> This is the old repository. You should use > >> > >> Gofer it > >> url: 'http://smalltalkhub.com/mc/Pharo/Fuel/main'; > >> package: 'ConfigurationOfFuel'; > >> load. > >> ((Smalltalk at: #ConfigurationOfFuel) project version: ???1.9.4') > >> load. > >> > >> > >> (See > >> http://rmod.inria.fr/web/software/Fuel/Version1.9/Documentation/Installation) > >> > >> > >>> (ConfigurationOfFuel project version: newVersion) load. > >>> > >>> objectsByFileName keysAndValuesDo: [ :fileName :objects | > >>> FLSerializer > >>> serialize: objects > >>> toFileNamed: fileName. > >>> FileDirectory default copyFileNamed: fileName toFileNamed: fileName, > >>> '-', newVersion asString > >>> ]. > >>> > >>> > >>> > >>> On Thu, Apr 30, 2015 at 9:19 AM, Norbert Hartl <norbert(a)hartl.name > >>> <mailto:norbert@hartl.name>> wrote: > >>> > >>> > >>>> Am 30.04.2015 um 14:08 schrieb Johannes Rasche Kreuzberg > >>>> <Johannes(a)Rasche-Kreuzberg.de <mailto:Johannes@Rasche-Kreuzberg.de>>: > >>>> > >>>> Hi folks, > >>>> > >>>> I'm just migrating to Pharo 4.0 > >>>> > >>>> On materialization of objects serialized under Pharo 3 > >>>> an error was raised: different versions numbers ( 194 required ). > >>>> > >>>> Where does version 194 come from ? > >>>> Monticello from Pharo 3 offers 193 > >>>> > >>>> Johannes > >>>> > >>> You need to add the repository of Fuel, load the ConfigurationOf > >>> from there and you can upgrade to 1.9.4 > >>> > >>> The repository to add is > >>> > >>> http://smalltalkhub.com/mc/Pharo/Fuel/main > >>> > >>> Norbert > >>> > >>> > >>> > >>> > >>> -- > >>> Mariano > >>> http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/> > >> > > > > > > -- > > > > /Johannes Rasche > > Hagelberger Str. 56 > > 10965 Berlin > > fon +49 30 851 14 92 > > mobil +49 1577 175 04 75 > > mail Johannes(a)Rasche-Kreuzberg.de > > www http://Rasche-Kreuzberg.de/ > > >

May 2, 2015

Fwd: Download problem: certificate

by jannik laval

Hi guys, Does someone have a solution for this problem ? Cheers, Jannik ---------- Forwarded message ---------- From: Markus Schlager <m.slg(a)gmx.de> Date: 2015-05-02 14:32 GMT+02:00 Subject: Re: Download problem: certificate To: jannik laval <jannik.laval(a)gmail.com> Dear Jannik, When visiting https://ci.inria.fr/ firefox for example is complaining (on arch linux as well as on windows 7) that the security certificate of ci.inria.fr is not valid: error code: sec_error_unknown_issuer This seems to be a problem of missing intermediate certificates on the server of ci.inria.fr. You get this hint when checking ci.inria.fr on http://www.networking4all.com/en/support/tools/site+check/ which leads to http://www.networking4all.com/en/support/tools/site+check/report/?fqdn=ci.i… Problem description also at https://support.mozilla.org/de/questions/773136 Probably you should contact the server-admins. They might want to check the installation of their TERENA-certificate (c.f. https://www.terena.org/activities/tcs/repository/) Greetings Markus -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://www.phratch.com http://www.approchealpes.info http://car.mines-douai.fr/

May 2, 2015

Re: [Pharo-dev] [ANN]: Tiny Dev Tools for SimplePersistence and STON

by Sean P. DeNigris

stepharo wrote > can you show an example? Sure... https://youtu.be/VyuuIthp93k ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-Tiny-Dev-Tools-for-SimplePersistence-and-STON-tp4… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 2, 2015

Re: [Pharo-dev] Are these changes good enough

by stepharo

No stef style. I burned days because of the problem of squeak license: never again. Sergio you can send a pdf. Stef Le 2/5/15 09:55, Esteban Lorenzano a Ã©crit : > INRIA style. > sounds like super bureaucracy, but let me tell you, without going into > details, that at least once it has proven useful :) > > Esteban > >> On 02 May 2015, at 01:29, Peter UhnÃ¡k <i.uhnak(a)gmail.com >> <mailto:i.uhnak@gmail.com>> wrote: >> >> On Fri, May 1, 2015 at 7:44 PM, stepharo <stepharo(a)free.fr >> <mailto:stepharo@free.fr>> wrote: >> >> Could you send the license agreement and send it to us? >> >> Ha! I completely forgot about doing this. >> I'm just surprised that legally having somewhere written something >> like "by contributing to blablabla you agree with license blablabla" >> is not enough. >> >> Peter >

May 2, 2015

Re: [Pharo-dev] [ANN]: Tiny Dev Tools for SimplePersistence and STON

by stepharo

can you show an example? Stef Le 2/5/15 04:52, Sean P. DeNigris a Ã©crit : > I often find myself writing the same boilerplate over and over for my basic > persistence needs. My usual pattern is to serialize/materialize a class-side > instance variable with accessors of the same name. > > Some time ago, I added the following to SimplePersistence (IIRC it gets > loaded by default): > aClass persist: #fieldName > which adds the necessary code automatically. > > Since I've been playing with STON a bit, I created the same in STON-Tools > and uploaded to http://smalltalkhub.com/#!/~SeanDeNigris/SeansOutbox. There > is even a test ;) > > Enjoy... > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ANN-Tiny-Dev-Tools-for-SimplePersistence-and-STON-tp4… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

May 2, 2015

Re: [Pharo-dev] TextMorph right-click?

by Ben Coman

On Sat, May 2, 2015 at 5:31 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > TextMorph new contents: 'Text'; openInWorld I don't know anything about this area, but thought it would be interesting to dig... There is only one implementor of #editView which is TextMorphEditView, a subclass of TextMorph. But... TextMorphEditView new contents: 'Text'; openInWorld right-click gives... "MessageNotUnderstood: receiver of "model" is nil" in TextMorphEditView>>handleInteraction: in this code... self editor model: editView model. "For evaluateSelection, etc" where /editView/ ivar is nil. Only TextMorphEditView>>setEditView: stores into this, and this has only one sender: PluggableTextMorph>>configureTextMorph: Then I notice method "PluggableTextMorph class >> on: text: accept:", so creating the following with usual accessors with Transcript tracing in them... Object subclass: #MyData instanceVariableNames: 'text' classVariableNames: '' category: 'MyPlay' The following lets me edit and save... (PluggableTextMorph on: (MyData new text: 'hello') text: #text accept: #text:) openInWorld Though saving doesn't clear the yellow triangle and I don't yet know how to restrict it to one line without a scroll bar (if you needed that?) cheers -ben

May 2, 2015

TextMorph right-click?

by Stephan Eggermont

How am I supposed to use TextMorph? It pops a debugger on right-click when doing a TextMorph new contents: 'Text'; openInWorld TextMorph(Object)>>doesNotUnderstand: #editView. Stephan

May 2, 2015

Re: [Pharo-dev] [QUESTION] For Dark Theme users

by Esteban Lorenzano

> On 02 May 2015, at 04:10, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > This is maybe a little 'too' dark. > Maybe we can do a setting to choose if we want it more or less dark. yes, but we also need a good default, because most people will not tune their system until they are used to it :) So, I think we need to restore the âpreference theme settingsâ options (another brick in the wallâ¦ I mean another todo entry in my list) And in the mean time I will chose something between current and my proposal (because Iâm convinced current one does not offer good contrast). Esteban > > An other think that would be good with the dark theme is to change the color of the Test Runner because the fluo green attack the eyes when we're on the dark theme x_x. > > Since we talk about the dark theme, is that normal than the background of the RubScrolledTextMorph stay white ? Or should I use an other Rub text morph ? > > On 1 May 2015 at 13:52, phil(a)highoctane.be <mailto:phil@highoctane.be> <phil(a)highoctane.be <mailto:phil@highoctane.be>> wrote: > Dawn Theme is lighter actually. > > As long as it is not black ... > > Phil > > Le 1 mai 2015 12:34, "Esteban Lorenzano" <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> a Ã©crit : > I suppose "Down Themeâ users (cough, cough, Phil) too. > > I want to change the background color for something even darker: > > <Screen Shot 2015-05-01 at 12.33.48.png> > > > > I think it look betterâ¦ what do you think? > > (Alsoâ¦ I need to refactor this theme thingyâ¦ is really ugly :P) > > Esteban > > > > -- > Cheers > Cyril Ferlicot

May 2, 2015

Re: [Pharo-dev] [QUESTION] For Dark Theme users

by Esteban Lorenzano

> On 02 May 2015, at 04:10, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > This is maybe a little 'too' dark. > Maybe we can do a setting to choose if we want it more or less dark. > > An other think that would be good with the dark theme is to change the color of the Test Runner because the fluo green attack the eyes when we're on the dark theme x_x. > > Since we talk about the dark theme, is that normal than the background of the RubScrolledTextMorph stay white ? Or should I use an other Rub text morph ? is a bug in Rubric. you have to explicitly tell him the backgroundColor or it will default white (instead default to the theme background color, who would be the good fix). Esteban > > On 1 May 2015 at 13:52, phil(a)highoctane.be <mailto:phil@highoctane.be> <phil(a)highoctane.be <mailto:phil@highoctane.be>> wrote: > Dawn Theme is lighter actually. > > As long as it is not black ... > > Phil > > Le 1 mai 2015 12:34, "Esteban Lorenzano" <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> a Ã©crit : > I suppose "Down Themeâ users (cough, cough, Phil) too. > > I want to change the background color for something even darker: > > <Screen Shot 2015-05-01 at 12.33.48.png> > > > > I think it look betterâ¦ what do you think? > > (Alsoâ¦ I need to refactor this theme thingyâ¦ is really ugly :P) > > Esteban > > > > -- > Cheers > Cyril Ferlicot

May 2, 2015

Re: [Pharo-dev] sometimes Shout changes the selection during styling

by stepharo

Le 27/4/15 14:41, Andrei Chis a Ã©crit : > Hi, > > In the glamour debugger that we use in moose we are now having the > following problem: > - the selection of a PluggableTextMorph is, quite randomly , changed > during styling. > > If I revert the fix for issue 15240 > <https://pharo.fogbugz.com/f/cases/15240> then it works ok. > Also if I change in SHTextStyler>>#styleInBackgroundProcess: from > > sem waitTimeoutSeconds: 5. > view ifNotNil: [ view stylerStyledInBackground: text ] > > to: > > (sem waitTimeoutSeconds: 5) ifFalse: [ > view ifNotNil: [ view stylerStyledInBackground: text ] ] > > it works ok. In the second snippet we only do the styling if the > styler completed. > > > If I look at the senders of styleInBackgroundProcess: there is another > strange issue. > First PluggableTextMorph>>#setText: calls either style: > or styleInBackgroundProcess:, depending in the size of the text. > Then, PluggableTextMorph>>#setText: > calls PluggableTextMorph>>#setTextBasic:, which calls > PluggableTextMorph>>#hasUnacceptedEdits: which in turn > calls again styleInBackgroundProcess:. > So when you set the text if the size of the text is small Shout will > try to style the text with and without a background process. If you > call hasUnacceptedEdits: > manually when initializing the morph then three processes will be > started for doing the styling. Ouch. And I imagine that it can be a mess after. Thanks for looking at this issue. > > Removing the calls to styleInBackgroundProcess: from > PluggableTextMorph>>#hasUnacceptedEdits: and > PluggableTextMorph>>#basicHasUnacceptedEdits:. > also solves the problem with the changing selection. > > Cheers, > Andrei

May 2, 2015