- Pharo-users - lists.pharo.org

Re: [Pharo-users] moving to git and preserving monticello history

by Thierry Goubier

Le 18/02/2015 19:18, Peter UhnÃ¡k a Ã©crit : > Hi, > > we would like to switch our project over to git, however is it possible > to preserve the history? I.e. to convert mcz (or wherever monticello > stores it) to git commits, or do I have to start from scratch? Hi Peter, if you use a Gofer script to move from Monticello to Git via GitFileTree, such as the script proposed by Yuriy, it will recreates a commit for each mcz, from oldest to newest. Git will not keep the merge information contained in the mcz if you did any, but that history will still be stored in the metadata for each package in the git repository, and you can recover it, if needs be. If you do the copy over a filetree repository, you will loose all versions except the last one. Regards, Thierry

Feb. 18, 2015

Re: [Pharo-users] moving to git and preserving monticello history

by Yuriy Tymchuk

Hi, I believe that there should be a better solution, but if no one else answers, here is a script for moving between MC repositories, maybe if you make destination to be filetree repo it will work. https://gist.github.com/Uko/6898022 <https://gist.github.com/Uko/6898022> Uko > On 18 Feb 2015, at 19:18, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Hi, > > we would like to switch our project over to git, however is it possible to preserve the history? I.e. to convert mcz (or wherever monticello stores it) to git commits, or do I have to start from scratch? > > Thanks, > > Peter

Feb. 18, 2015

moving to git and preserving monticello history

by Peter UhnÃ¡k

Hi, we would like to switch our project over to git, however is it possible to preserve the history? I.e. to convert mcz (or wherever monticello stores it) to git commits, or do I have to start from scratch? Thanks, Peter

Feb. 18, 2015

Re: [Pharo-users] Issues with code formatting

by Peter UhnÃ¡k

> > BTW two questions: > 1. are these only applied if you click "format" from a source pane's > context > menu or is there another way (e.g. automatically on method save)? > There is shortcut (ctrl+shift+f on linux, couple people mentioned it being broken on Mac). There was some discussion about it being formatted when writing, but that has yet to be thought through and implemented (afaik). 2. Is there a way to view the source pretty-printed without dirtying the > source? I feel like there used to be an obvious option... maybe in the old > browser? > You could probably feed the source to RBConfigurableFormatter (or whatever the object name is), however I'm not aware of any pretty viewer.

Feb. 18, 2015

Re: [Pharo-users] Learning Spec

by blake

> > From now on it is forbidden to complain about Spec in general, unspecific > terms As a rule, complaining about ANYTHING in general, unspecific terms is pretty useless, whether you've learned about it or not. =) (Not that most of us don't do that from time-to-time. But it's a bad habit.)

Feb. 18, 2015

Re: [Pharo-users] Issues with code formatting

by Sean P. DeNigris

Nicolai Hess wrote > Settings browser -> Refactoring Engine -> Configurable Formatter In 4.0 these settings have apparently been moved to Settings browser -> Code Browsing -> Pretty Printing. BTW two questions: 1. are these only applied if you click "format" from a source pane's context menu or is there another way (e.g. automatically on method save)? 2. Is there a way to view the source pretty-printed without dirtying the source? I feel like there used to be an obvious option... maybe in the old browser? Thanks. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Issues-with-code-formatting-tp4806202p4806379.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 18, 2015

Videos PharoDays online

by Marcus Denker

Hi, Sorry for the delayâ¦ https://www.youtube.com/channel/UCp3mNigANqkesFzdm058bvw/videos

Feb. 18, 2015

Re: [Pharo-users] i feel dumb / Pharo3 > OrderedCollection >> do:

by Marcus Denker

> On 18 Feb 2015, at 18:13, Cameron Sanders via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > Date: 18 Feb 2015 18:12:33 CET > Subject: i feel dumb / Pharo3 > OrderedCollection >> do: > From: Cameron Sanders <camsanders(a)aol.com> > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > I must be making some silly error here that i cannot see clearly. Why does the following leave anything in the list 'a'? Run it in a workspace. With or without the shallowCopy, i am left with a list with half of the elements in it. Always half. > > This version of Pharo3 (21.0) was downloaded last week. I am running on a Mac. > > Thanks in advance. ... Maybe I just need more coffee. > -Cam > > | a | > a := { #a. #b. #c. #d. } asOrderedCollection. > a shallowCopy do: [ :item | (a includes: item) ifTrue: [ a remove: item ]]. > a size > shallowCopy is not enoughâ¦ OrderedCollection is made up of an internal array. #copy does the right thing, just copies the array: postCopy array := array copy and for Array, copy is a shallowCopy. Marcus

Feb. 18, 2015

i feel dumb / Pharo3 > OrderedCollection >> do:

by Cameron Sanders

I must be making some silly error here that i cannot see clearly. Why does the following leave anything in the list 'a'? Run it in a workspace. With or without the shallowCopy, i am left with a list with half of the elements in it. Always half. This version of Pharo3 (21.0) was downloaded last week. I am running on a Mac. Thanks in advance. ... Maybe I just need more coffee. -Cam | a | a := { #a. #b. #c. #d. } asOrderedCollection. a shallowCopy do: [ :item | (a includes: item) ifTrue: [ a remove: item ]]. a size

Feb. 18, 2015

Re: [Pharo-users] What happens to saved inspectors?

by Blondeau Vincent

Hello Peter, If your are on Moose, you are using the Glamour inspector. Can you describe more precisely the kind of items you are inspecting? Do you inspect external resources? Or use Semaphores, forks, network? I am remembering a bug on Roassal. It used external ressources that was desallocated at image shutdown. On image relaunch, the external ressources was still pointed by a cache and the yellow cross on red appears. By the way, behind the cross, it should be a text, can you see it? I know that these kind of issues are very difficult to reproduce but if you can do it on a fresh image, it will be easier for us to help you ;) I cross-posted to the Moose mailing list where people are more aware of this kind of issues. Vincent De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de PBKResearch EnvoyÃ© : mercredi 18 fÃ©vrier 2015 17:32 Ã : 'Any question about pharo is welcome' Objet : Re: [Pharo-users] What happens to saved inspectors? ClÃ©ment I am not sure, but I think Moose uses the Glamour inspector. You get exactly the same inspector whether you select âInspectâ or âExploreâ from the world menu. As you click on an item in the current display, a new inspector pane opens to the right showing detail of the selected item, with tabs to select the form of display â the first one is always âRawâ but the others are dependent on the kind of item being displayed, e.g. if inspecting an XML document there is always a âTreeâ option. I think that sounds like Glamour, doesnât it? The main heading on the title bar is static, i.e. it always shows the item you originally inspected. When there are multiple inspector panes open, each one has its own title below the main window title, showing the item that was clicked to open it. In this case, the title of the first inspector pane, which is the same as the main window title, is also replaced by the red error display, but the titles of the other inspector panes are OK. Hope this helps. If any more detail would be helpful, let me know. Thanks Peter Kenny From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of ClÃ©ment Bera Sent: 18 February 2015 11:37 To: Any question about pharo is welcome Subject: Re: [Pharo-users] What happens to saved inspectors? Hey, Inspectors are different between Moose and Pharo 3. Can you precise, are you using the Glamour inspector, the EyeInspector or the old Morphic inspector ? I have never seen that in Pharo. Are your titles dynamic (I mean, when the object changes, can your title change ?) ? 2015-02-18 11:35 GMT+01:00 PBKResearch <peter(a)pbkresearch.co.uk<mailto:peter@pbkresearch.co.uk>>: Hello I am using Moose 5, which is essentially Pharo 3, downloaded late December 2014. I have a development project which mainly consists of a collection of workspaces and inspectors (I really do intend to turn it into a properly structured set of classes one day!). I have noticed that, whenever I save an image with some inspectors open and then reopen the image, the title bars of the inspectors have become red rectangles with a cross superimposed. Often I can work out what the title should be and carry on, but in many cases all I can do is close down the inspector and reopen it. Is this a known problem, and is there any way to work round it? Thanks for any help Peter Kenny ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Feb. 18, 2015