June 2013 - Pharo-users - lists.pharo.org

Re: [Pharo-users] baseline for seaside 3.0

by phil＠highoctane.be

works here too indeed. pharo 2.0 fresh. Le 11 juin 2013 10:54, "Sabine KnÃ¶fel" <sabine.knoefel(a)gmail.com> a Ã©crit : > Ok, I think I can answer my question myself: > > spec > project: 'Seaside30' > with: [ > spec > className: 'ConfigurationOfSeaside30'; > versionString: #'stable'; > loads: #('default'); > repository: ' > http://www.squeaksource.com/MetacelloRepository' ]. > > works. > > > > > > -- > View this message in context: > http://forum.world.st/baseline-for-seaside-3-0-tp4692630p4692747.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > >

June 11, 2013

Re: [Pharo-users] baseline for seaside 3.0

by Sabine KnÃ¶fel

Ok, I think I can answer my question myself: spec project: 'Seaside30' with: [ spec className: 'ConfigurationOfSeaside30'; versionString: #'stable'; loads: #('default'); repository: 'http://www.squeaksource.com/MetacelloRepository' ]. works. -- View this message in context: http://forum.world.st/baseline-for-seaside-3-0-tp4692630p4692747.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 11, 2013

Re: [Pharo-users] Voyage: Circular references

by Bernat Romagosa

Bump? 2013/6/6 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> > Hi! > > I'm having an issue I don't recall having had about half a year ago when > trying out Voyage. > > In my schema, a *User* has an *instVar* referencing all the *Center*s he > belongs to, and a *Center* has an *instVar* referencing all of its *User*s, > so when the Voyage serializer tries to serialize a user (or a center), it > goes into an infinite loop trying to find the end of the reference chain > and the image clogs. > > I remember saving the exact same schema a while ago without a problem, is > there something new I should know about? > > BTW, I'm using the #bleedingEdge version, with Magritte3 and all. > > Thanks! :) > > -- > Bernat Romagosa. > -- Bernat Romagosa.

June 11, 2013

Re: [Pharo-users] inspect returns iOf SystemWindow and not receiver

by Sven Van Caekenberghe

On 11 Jun 2013, at 09:57, Marcus Denker <marcus.denker(a)inria.fr> wrote: > So maybe we can > -> add #inspector that returns the tool > -> make inspect be like it was before (with documentation). +1 Lets not waste any more time on this

June 11, 2013

Re: [Pharo-users] inspect returns iOf SystemWindow and not receiver

by Sabine KnÃ¶fel

yes, I am a head-scratching person, possibly old fashioned :-), coming from other dialects and this is imho the best solution Sabine On Tue, Jun 11, 2013 at 9:58 AM, Marcus Denker-4 [via Smalltalk] <ml-node+s1294792n4692722h77(a)n4.nabble.com> wrote: > > On Jun 10, 2013, at 6:56 PM, [hidden email] wrote: > >> Am 10.06.13 18:01, schrieb Marcus Denker: >>> >>>> Breaks the Principal of Least Surprise for those you want to attract >>>> from other dialects. They may end up with a strong opinion on it :) >>> >>> >>> I am not against reverting the inspect change.. but it should be >>> documented well, else this will be changed again in the future. >>> >>> Another thing is that starting from 3.0, I am sure that nobody will ever >>> put "inspect" or "halt" anywhere as they will use meta-links >>> insteadâ¦ >> hmm. that is probably just 5 minutes away from Pharo's world domination >> ;-) >> As long as Pharo is "Smalltalk inspired", people will probably come up >> with solutions they learned in Smalltalk. I have not yet come to be a >> frequent Pharo user, but coming from another Smalltalk dialect, I would >> probably face the same problem as Sabine mentioned it. I am not sure I use >> inspect in message cascades very often, because I tend to avoid cascades in >> methods that look or feel as if I may want to inspect preliminary results, >> so I am probably unlikely to tap into the same trap often. But if I would, >> I'd be scratching my head and ask myself what the heck this could ever be >> good forâ¦ > > So maybe we can > -> add #inspector that returns the tool > -> make inspect be like it was before (with documentation). > > Marcus > > > > > > ________________________________ > If you reply to this email, your message will be added to the discussion > below: > http://forum.world.st/inspect-returns-iOf-SystemWindow-and-not-receiver-tp4… > To unsubscribe from inspect returns iOf SystemWindow and not receiver, click > here. > NAML -- View this message in context: http://forum.world.st/inspect-returns-iOf-SystemWindow-and-not-receiver-tp4… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 11, 2013

Re: [Pharo-users] inspect returns iOf SystemWindow and not receiver

by Marcus Denker

On Jun 10, 2013, at 6:56 PM, jtuchel(a)objektfabrik.de wrote: > Am 10.06.13 18:01, schrieb Marcus Denker: >> >>> Breaks the Principal of Least Surprise for those you want to attract from other dialects. They may end up with a strong opinion on it :) >> >> >> I am not against reverting the inspect change.. but it should be documented well, else this will be changed again in the future. >> >> Another thing is that starting from 3.0, I am sure that nobody will ever put "inspect" or "halt" anywhere as they will use meta-links >> insteadâ¦ > hmm. that is probably just 5 minutes away from Pharo's world domination ;-) > As long as Pharo is "Smalltalk inspired", people will probably come up with solutions they learned in Smalltalk. I have not yet come to be a frequent Pharo user, but coming from another Smalltalk dialect, I would probably face the same problem as Sabine mentioned it. I am not sure I use inspect in message cascades very often, because I tend to avoid cascades in methods that look or feel as if I may want to inspect preliminary results, so I am probably unlikely to tap into the same trap often. But if I would, I'd be scratching my head and ask myself what the heck this could ever be good forâ¦ So maybe we can -> add #inspector that returns the tool -> make inspect be like it was before (with documentation). Marcus

June 11, 2013

Re: [Pharo-users] inspect returns iOf SystemWindow and not receiver

by Sabine KnÃ¶fel

Thank you Marcus. I see there was a similar discussion in march in FogBuzz/Google. Next time I will look in FogBuzz before starting a diskussion here. Sabine -- View this message in context: http://forum.world.st/inspect-returns-iOf-SystemWindow-and-not-receiver-tp4… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 11, 2013

Re: [Pharo-users] baseline for seaside 3.0

by Sabine KnÃ¶fel

I take a new 2.0. image and try to load only seaside with the following code: baseline100: spec <version: '1.0-baseline'> spec for: #common do: [ spec blessing: #baseline. spec project: 'seaside' with: [ spec className: 'ConfigurationOfSeaside30'; loads: #('ALL'); versionString: '3.0.8'; repository: 'http://ss3.gemstone.com/ss/MetaRepoForPharo20' ] ] version110: spec <version: '1.1' imports: #('1.0-baseline')> spec for: #common do: [ spec blessing: #development. ] This fails when loading 'Kom''1.0.9' because projectPackage isNil. I dont need to solve this probolem, I only need a snippet how to load seaside within my Configuration of. this is the Stack: UndefinedObject(Object)>>doesNotUnderstand: #loadUsing: MetacelloMCProjectSpec>>ensureLoadedForDevelopmentUsing: MetacelloMCVersionSpecLoader>>load in Block: [:pkg | ... Array(SequenceableCollection)>>do: MetacelloMCVersionSpecLoader>>load MetacelloMCVersion>>executeLoadFromArray: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [:dict | ^ self executeLoadFromArray: anArray] MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] BlockClosure>>on:do: MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [self versionSpec loader: newLoader.... BlockClosure>>ensure: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [[self versionSpec loader: newLoader.... MetacelloPharoPlatform>>do:displaying: in Block: [:bar | ... BlockClosure>>cull: Job>>run in Block: [result := block cull: self] BlockClosure>>on:do: Job>>run in Block: [self prepareForRunning.... BlockClosure>>ensure: Job>>run MorphicUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: MetacelloPharoPlatform>>do:displaying: MetacelloMCVersion>>fetchRequiredFromArray: MetacelloMCProjectSpec>>loadVersion: in Block: [:dict | ... MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] BlockClosure>>on:do: MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: MetacelloMCProjectSpec>>loadVersion: MetacelloMCProjectSpec>>load -- View this message in context: http://forum.world.st/baseline-for-seaside-3-0-tp4692630p4692712.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 11, 2013

Re: [Pharo-users] Grabbing email attachments

by Davide Varvello

Thank Sven, I'll look at them. As Sven said, is there anyone on the list who managed SMTPClient and ZnMimePart? I just searched for SecureSMTPClient but I only found a raw description of a brittle implementation (http://forum.world.st/Combining-SqueakSSL-and-SMTPClient-td2956892.html) Davide Sven Van Caekenberghe-2 wrote > Davide, > > On 11 Jun 2013, at 00:54, Davide Varvello < > varvello@ > > wrote: > >> Hi guys, >> Is there a way to grab and save an attachment using Pharo? > > There is a SMTPClient and even a SecureSMTPClient. And there is support > for ZnMimePart. > But I don't know exactly how to combine the two, although I think somebody > once did on the list. > It could be as easy as just reading the raw message. > > HTH, > > Sven > >> TIA >> Davide >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Grabbing-email-attachments-tp4692693.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org -- View this message in context: http://forum.world.st/Grabbing-email-attachments-tp4692693p4692707.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 11, 2013

Re: [Pharo-users] Grabbing email attachments

by Sven Van Caekenberghe

Davide, On 11 Jun 2013, at 00:54, Davide Varvello <varvello(a)yahoo.com> wrote: > Hi guys, > Is there a way to grab and save an attachment using Pharo? There is a SMTPClient and even a SecureSMTPClient. And there is support for ZnMimePart. But I don't know exactly how to combine the two, although I think somebody once did on the list. It could be as easy as just reading the raw message. HTH, Sven > TIA > Davide > > > > -- > View this message in context: http://forum.world.st/Grabbing-email-attachments-tp4692693.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

June 11, 2013