October 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] smalltalkhub down

by Philippe Marschall

On 26.10.13 14:21, Sebastian Sastre wrote: > 10 hours later we're still down... Calls for blog post [1] ;-) [1] https://github.com/blog/1346-network-problems-last-friday Cheers Philippe

Oct. 28, 2013

[Fuel] How to tell Fuel *not* to encode references?

by roberto.minelli＠usi.ch

Hi, Iâm struggling with Fuel and I probably discovered my problem. When trying to serialize an object (that represents a development session, i.e., contains some meta-data (title, author, etc.) and some objects representing actions of the developer) I often encounter problem with some BlockClosureâs which are somewhat corrupt and Fuel crashes and cannot serialize them. We already discussed this issue in this mailing list a while ago with Max. I do not ask directly Fuel to serialize some BlockClosures, so my intuition is that Fuel serializes all the references to the objects I am trying to serialize. Am I right? Is there any way to tell Fuel not to do so? Cheers and thanks for the help, Roberto

Oct. 28, 2013

Re: [Pharo-dev] Startup Preferences: An Alternative

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > This is really cool, is that in the image already ? It's just something I use personally in my images (see DeNigrisPreferences on sthub), but if there's interest I will extract it... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Startup-Preferences-An-Alternative-tp4713968p4717545.… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 27, 2013

Re: [Pharo-dev] missing updates: 30503 30504

by StÃ©phane Ducasse

On Oct 27, 2013, at 6:18 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > Things got updated: > > The tracker job https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-1-Tracker/ has > now a version number check + the recent pharo version allows the #update command line handler > to detect if wrong update files were specified. Together with Stef's fix to always > merge updates the update process should now be more stable. Tx camillo. Pay attention that my change is to ignore conflict warning so it puts more responsibility on the integrators but ease the production of clean packages after complex merge. Stef > > > > On 2013-10-23, at 20:24, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> Everybody does a lot of work for Pharo, visible and invisible. >> We are complementary and we need each other - so we have to work together. >> >> On 23 Oct 2013, at 18:53, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >>> On 2013-10-23, at 16:06, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>> On 2013-10-23, at 13:48, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>>> On Oct 23, 2013, at 10:52 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>>>> On 2013-10-22, at 10:44, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>>>>>>> For retracting files you need access to files.pharo.org. >>>>>>>> >>>>>>>> This is what should be written in the readme. >>>>>>> >>>>>>> BTW have you tried that you actually have access to the machine? >>>>>>> Because I remember that it didn't work for you nor Esteban... >>>>>> >>>>>> >>>>>> So stef, did you check that you can actually edit the file? >>>>> >>>>> I cannot access it but I least I know that I should not look for it. >>>>> And next time if there is a problem I just stop integrated and continue hacking on my cool stuff and look smart. >>>> >>>> Why can't you access it? >>>> What do you want instead? >>>> How do we avoid this situation in the future? (happened already before a couple of times) >>> >>> Just to get something straight here: >>> >>> You have hardly something to complain... What you see is the tip of the iceberg. >>> I spend roughly 1-2 hours per week maintaining all the jenkins instances with all >>> the slaves and all the jobs that run (and there is Christoph to, regularly fixing >>> and tweaking things all around). >>> >>> Now running around wild and screaming that everything does not work and is not >>> documented is highly demotivating. Marcus and Esteban work on it on a daily basis. >>> If maintaining jenkins were so much fun, you would do it, but you don't. >>> >>> >>> So enjoy, and focus on the things you are truly great at: motivating people for a better pharo! >> >> >

Oct. 27, 2013

Re: [Pharo-dev] Printf - equivalent package alreadyon STH or in image?

by Sven Van Caekenberghe

Hi Phil, On 27 Oct 2013, at 17:57, phil(a)highoctane.be wrote: > I am trying out that Printf package from SS and it is decent. > > e.g. > > 'File-%02d%02d%02d-%02d%02d.ext' printf: { now year. now month. now day. now hour. now minutes.}. > > > I'll have a look at yours. > > Phil A possible alternative is using the ZTimestampFormatter from the ZTimestamp package (see ConfigurationBrowser): 'file-{1}.ext' format: { (ZTimestampFormat fromString: '0102031605') format: TimeStamp now }. => 'file-1310272012.extâ 'file-{1}.ext' format: { (ZTimestampFormat fromString: '200102031605') format: ZTimestamp now }. => 'file-201310271913.extâ The former is local time, the latter is UTC. Sven

Oct. 27, 2013

Re: [Pharo-dev] Printf - equivalent package alreadyon STH or in image?

by phil＠highoctane.be

This one works I'd say. It would be great to convert people from the C side :-) On Sun, Oct 27, 2013 at 6:09 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > ah nice :) I would be happy to see a fully working version! > > On 2013-10-27, at 17:57, phil(a)highoctane.be wrote: > > > I am trying out that Printf package from SS and it is decent. > > > > e.g. > > > > 'File-%02d%02d%02d-%02d%02d.ext' printf: { now year. now month. now day. > now hour. now minutes.}. > > > > > > I'll have a look at yours. > > > > Phil > >

Oct. 27, 2013

Re: [Pharo-dev] missing updates: 30503 30504

by Camillo Bruni

Things got updated: The tracker job https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-1-Tracker/ has now a version number check + the recent pharo version allows the #update command line handler to detect if wrong update files were specified. Together with Stef's fix to always merge updates the update process should now be more stable. On 2013-10-23, at 20:24, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Everybody does a lot of work for Pharo, visible and invisible. > We are complementary and we need each other - so we have to work together. > > On 23 Oct 2013, at 18:53, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> On 2013-10-23, at 16:06, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> On 2013-10-23, at 13:48, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> On Oct 23, 2013, at 10:52 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>>> On 2013-10-22, at 10:44, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>>>>>> For retracting files you need access to files.pharo.org. >>>>>>> >>>>>>> This is what should be written in the readme. >>>>>> >>>>>> BTW have you tried that you actually have access to the machine? >>>>>> Because I remember that it didn't work for you nor Esteban... >>>>> >>>>> >>>>> So stef, did you check that you can actually edit the file? >>>> >>>> I cannot access it but I least I know that I should not look for it. >>>> And next time if there is a problem I just stop integrated and continue hacking on my cool stuff and look smart. >>> >>> Why can't you access it? >>> What do you want instead? >>> How do we avoid this situation in the future? (happened already before a couple of times) >> >> Just to get something straight here: >> >> You have hardly something to complain... What you see is the tip of the iceberg. >> I spend roughly 1-2 hours per week maintaining all the jenkins instances with all >> the slaves and all the jobs that run (and there is Christoph to, regularly fixing >> and tweaking things all around). >> >> Now running around wild and screaming that everything does not work and is not >> documented is highly demotivating. Marcus and Esteban work on it on a daily basis. >> If maintaining jenkins were so much fun, you would do it, but you don't. >> >> >> So enjoy, and focus on the things you are truly great at: motivating people for a better pharo! > >

Oct. 27, 2013

Re: [Pharo-dev] Printf - equivalent package alreadyon STH or in image?

by Camillo Bruni

ah nice :) I would be happy to see a fully working version! On 2013-10-27, at 17:57, phil(a)highoctane.be wrote: > I am trying out that Printf package from SS and it is decent. > > e.g. > > 'File-%02d%02d%02d-%02d%02d.ext' printf: { now year. now month. now day. now hour. now minutes.}. > > > I'll have a look at yours. > > Phil

Oct. 27, 2013

Re: [Pharo-dev] Printf - equivalent package alreadyon STH or in image?

by phil＠highoctane.be

I am trying out that Printf package from SS and it is decent. e.g. 'File-%02d%02d%02d-%02d%02d.ext' printf: { now year. now month. now day. now hour. now minutes.}. I'll have a look at yours. Phil

Oct. 27, 2013

Re: [Pharo-dev] Printf - equivalent package alreadyon STH or in image?

by Camillo Bruni

I started something here: http://smalltalkhub.com/#!/~dh83/c I don't remember how complete it was, but the basic printf statements worked. On 2013-10-27, at 17:51, phil(a)highoctane.be wrote: > I wondered if we had something like > > http://www.squeaksource.com/Printf > > > > > looks like generally useful for people coming from other horizons (and generally using printf formats). > > Phil >

Oct. 27, 2013