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

SS3, Gemsource, book.pharo.project.org MAINTENANCE Tuesday June 25 from 12pm-4pm PDT

by Dale K. Henrichs

The 3 sites: ss3.gemstone.com, seaside.gemstone.com/ss book.pharo-project.org will be down for Maintenance on Tuesday, June 25, for 4 hours starting at 12pm PDT. The servers are being relocated from a VMware data center to the GemTalk Systems data center. I will send mail when the relocation is complete. The ss3 and gemsource sites will have new domain names when they come back online: ss3.gemstone.com -> ss3.gemtalksystems.com seaside.gemstone.com -> seaside.gemtalksystems.com The domain for book.pharo-project.org will not change. All of the old domains will continue to be usable for about a year, but I recommend that you start switching to the new domain names as soon as you can. WARNING: the new ss3.gemtalksystems.com and seaside.gemtalksystems.com sites may appear to be alive between now and 4pm PDT Tuesday, but be aware that anything saved on those sites prior to my "relocation complete email" may not be preserved. Dale

June 22, 2013

Re: [Pharo-users] Comments not working in Ubuntu 13.04

by Camillo Bruni

This is a known bug, and I thought it was fixed. Did you update your 2.0 image to the latest version? (maybe that is not possible with this bug being present). If you do not manage to update your image, can you try with a fresh 2.0 image? On 2013-06-22, at 14:33, Kenneth Payne <voxkmp(a)gmail.com> wrote: > I've just noticed that class comments have stopped working in Pharo since I > upgraded from Xubuntu 12.10 to Xubuntu 13.04. > > If I make any change to a comment or add a new comment I get an error in > RemoteString - 'RemoteSring past end of file'. > > This happens both for Pharo 2.0 images and older Pharo 1.4 images. It > happens if I add comments to new classes or to classes where I have > previously successfully added comments. > > This is where it falls down: > > > string > "Answer the receiver's string if remote files are enabled. > Use a read only copy to avoid syntax errors when accessed via > multiple processes." > > | theFile | > (sourceFileNumber == nil or: [(SourceFiles at: sourceFileNumber) == > nil]) ifTrue: [^'']. > theFile := (SourceFiles at: sourceFileNumber) readOnlyCopy. > ^[filePositionHi > theFile size ifTrue: [ > self error: 'RemoteString past end of file' ]. > theFile position: filePositionHi. > theFile nextChunk] ensure: [theFile close] > > Anyone else seen this? Anyone got a solution? > > Ken

June 22, 2013

Comments not working in Ubuntu 13.04

by Kenneth Payne

I've just noticed that class comments have stopped working in Pharo since I upgraded from Xubuntu 12.10 to Xubuntu 13.04. If I make any change to a comment or add a new comment I get an error in RemoteString - 'RemoteSring past end of file'. This happens both for Pharo 2.0 images and older Pharo 1.4 images. It happens if I add comments to new classes or to classes where I have previously successfully added comments. This is where it falls down: string "Answer the receiver's string if remote files are enabled. Use a read only copy to avoid syntax errors when accessed via multiple processes." | theFile | (sourceFileNumber == nil or: [(SourceFiles at: sourceFileNumber) == nil]) ifTrue: [^'']. theFile := (SourceFiles at: sourceFileNumber) readOnlyCopy. ^[filePositionHi > theFile size ifTrue: [ self error: 'RemoteString past end of file' ]. theFile position: filePositionHi. theFile nextChunk] ensure: [theFile close] Anyone else seen this? Anyone got a solution? Ken

June 22, 2013

Re: [Pharo-users] Log4s for Pharo

by Donald

On 6/22/2013 4:55 AM, Stuart Herring wrote: > Hi Donald, > > I tried to load it, but it depends on a Bindings-Core package > (Bindings-Core-tbn.1) which isn't in the repository. Where would I be > able to find that package? Stuart, Hmm. I thought it was in there. Let me look this weekend and find it. I guess I need to bone up on Pharo config maps. > > Regards, > Stuart > > On 16 June 2013 02:28, Donald <dmacq(a)instantiations.com> wrote: >> More info here: >> >> http://www.stic.st/conferences/stic12/stic12-abstracts/log4s-a-logging-fram… >> >> http://www.jarober.com/blog/blogView?entry=3509625595 >> >> http://www.jarober.com/blog/blogView?entry=3520403203 >> >> >> -- >> Donald [|] >> >> A bad day in [] is better than a good day in {} >> >> -- Donald [|] A bad day in [] is better than a good day in {}

June 22, 2013

Re: [Pharo-users] Log4s for Pharo

by StÃ©phane Ducasse

I go the same problem. but I tried with pharo 30 so it was on my todo to try to load it in 20. Having a configuration for loading it would be good. Once all the packages are available I could write one. Stef On Jun 22, 2013, at 10:55 AM, Stuart Herring <st-lists(a)stuartherring.com> wrote: > Hi Donald, > > I tried to load it, but it depends on a Bindings-Core package > (Bindings-Core-tbn.1) which isn't in the repository. Where would I be > able to find that package? > > Regards, > Stuart > > On 16 June 2013 02:28, Donald <dmacq(a)instantiations.com> wrote: >> More info here: >> >> http://www.stic.st/conferences/stic12/stic12-abstracts/log4s-a-logging-fram… >> >> http://www.jarober.com/blog/blogView?entry=3509625595 >> >> http://www.jarober.com/blog/blogView?entry=3520403203 >> >> >> -- >> Donald [|] >> >> A bad day in [] is better than a good day in {} >> >> >

June 22, 2013

Re: [Pharo-users] Log4s for Pharo

by Stuart Herring

Hi Donald, I tried to load it, but it depends on a Bindings-Core package (Bindings-Core-tbn.1) which isn't in the repository. Where would I be able to find that package? Regards, Stuart On 16 June 2013 02:28, Donald <dmacq(a)instantiations.com> wrote: > More info here: > > http://www.stic.st/conferences/stic12/stic12-abstracts/log4s-a-logging-fram… > > http://www.jarober.com/blog/blogView?entry=3509625595 > > http://www.jarober.com/blog/blogView?entry=3520403203 > > > -- > Donald [|] > > A bad day in [] is better than a good day in {} > >

June 22, 2013

Re: [Pharo-users] Detaching a morph

by sminni

Thanks worked using shift+alt+click, and yes it was there the next time I opened world menu morph On Sat, Jun 22, 2013 at 2:35 AM, Sean P. DeNigris [via Smalltalk] < ml-node+s1294792n4694491h25(a)n4.nabble.com> wrote: > sminni wrote > I pasted the "Workspace" menu item in the somewhere on the Pharo Window > (after detaching it - Pharo by example - Morphic - Fig 11.1) > > That's a fun example of the power of a live, dynamic environment ;) > > sminni wrote > now I am unable to get the Halo around it (tried using Alt+click on Pharo > 2.0 latest image on Win 7) > > Either hold shift down with the halo key combination, or there's a setting > (programmatically "Morph cycleHalosBothDirections: true") > > sminni wrote > - how to put it back in the menu > > You don't have to. It's only been removed from that particular instnace of > the world menu Morph. Next time you open the world menu, Workspace will > still be there. > > HTH > Cheers, > Sean > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://forum.world.st/Detaching-a-morph-tp4694465p4694491.html > To unsubscribe from Detaching a morph, click here<http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML<http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > -- Sanjay Minni 91-9900-902902 ----- --- Regards, Sanjay -- View this message in context: http://forum.world.st/Detaching-a-morph-tp4694465p4694515.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 22, 2013

Re: [Pharo-users] FileSystem Question

by StÃ©phane Ducasse

On Jun 21, 2013, at 11:01 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I know you did, but it is as you say: this should be done by someone who really understands the design. For example: I learned about #resolve: from comments at the Disk implementation level, not the Public API level where there are almost no commennts. I got into several loops using wrong methods, those should have been marked private I would guess. I know this is sad but this is the case with most of the code of colin. I did my best to add comments but guessing is always more error prone and stupid trial and error. Anyway we will improve slowly. I do not understand why writing simple method comments is difficult to do when you write the code of the methods. Stef

June 21, 2013

Re: [Pharo-users] Detaching a morph

by Sean P. DeNigris

sminni wrote > I pasted the "Workspace" menu item in the somewhere on the Pharo Window > (after detaching it - Pharo by example - Morphic - Fig 11.1) That's a fun example of the power of a live, dynamic environment ;) sminni wrote > now I am unable to get the Halo around it (tried using Alt+click on Pharo > 2.0 latest image on Win 7) Either hold shift down with the halo key combination, or there's a setting (programmatically "Morph cycleHalosBothDirections: true") sminni wrote > - how to put it back in the menu You don't have to. It's only been removed from that particular instnace of the world menu Morph. Next time you open the world menu, Workspace will still be there. HTH ----- Cheers, Sean -- View this message in context: http://forum.world.st/Detaching-a-morph-tp4694465p4694491.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 21, 2013

Re: [Pharo-users] FileSystem Question

by Sven Van Caekenberghe

I know you did, but it is as you say: this should be done by someone who really understands the design. For example: I learned about #resolve: from comments at the Disk implementation level, not the Public API level where there are almost no commennts. I got into several loops using wrong methods, those should have been marked private I would guess. On 21 Jun 2013, at 22:58, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I did my best to comment what I could really understand. > Now as soon as somebody understand more he should have the reflex to add comments. > > I was always confused by resolve: > > Stef >> Apparently it is #resolve: >> >> '/tmp/data-dir/' asFileReference resolve: 'a/b/c/file.txt' asFileReference >> >> Way too many methods on the public classes of FileSystem are undocumented. >> >> On 21 Jun 2013, at 16:31, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> Hi, >>> >>> Does anyone know how I can/should concatenate 2 FileReference paths ? >>> >>> Given /tmp/my-cache and a/b/data.txt I want to get /tmp/my-cache/a/b/data.txt in such a way that it is a correct, useable path. Next I want to do #ensureDirectory on the parent and write to the file. >>> >>> '/tmp/my-cache' asFileReference / 'a/b/data.txt' asFileReference >>> >>> does not work. >>> >>> '/tmp/my-cache' asFileReference / 'a/b/data.txt' >>> >>> works but is wrong internally. >>> >>> I can't figure out the semantics of #, >>> >>> TIA, >>> >>> Sven >> >> > >

June 21, 2013