- Pharo-users - lists.pharo.org

Re: [Pharo-users] [Pharocasts] New comment on SandstoneDb, simple ActiveRecord style persistence....

by Bernat Romagosa

... but now I've really weird problems when saving a dictionary. I can only save 4 entries, no matter what I do. If I try to add a 5th item, one of the four previously saved ones will be replaced by it. By the way, I ran the tests and got 6 failures and 4 errors, precisely at dictionaries, matrices and finding items, here's a shot: http://i.imgur.com/Q3sTg.png 2011/5/9 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> > Thanks Ramon, it works now :) > > > 2011/5/6 Ramon Leon <ramon.leon(a)allresnet.com> > >> On 05/06/2011 02:33 AM, Bernat Romagosa wrote: >> >>> I'm still having some trouble migrating the DB... I have an object that >>> holds a Matrix, and whenever I attempt to save the object, SandstoneDB >>> tries to remove elements from the matrix by using remove:, which it >>> shouldNotImplement. Is there an easy workaround for this? >>> >> >> Pull down the latest code, it should work now. >> >> >> -- >> Ramon Leon >> http://onsmalltalk.com >> >> >

May 9, 2011

image uptime

by Francois Stephany

Hi, Is there a way to know for how long an image is running (i.e., when the VM started it)? Cheers, Francois

May 9, 2011

Re: [Pharo-users] Monticello: How to visualize history?

by Mariano Martinez Peck

On Mon, May 9, 2011 at 12:43 AM, Nick Chen <nchen.dev(a)mac.com> wrote: > Hi > > Is there a nice way to visualize the history of Monticello repository? In > particular, I would like to be able to quickly identify the presence of > branching/merging. > > http://forum.world.st/file/n3508002/MonticelloBrowseHistory.png > > Consider the screenshot above. Without a graphical visualizer, it is hard > to > tell that LanguageOfLanguages-NC.42.mcz and > LanguageOfLanguages-jamie.42.mcz > branched out from LanguageOfLanguages-jamie.41.mcz. Their names might hint > that they do (because of the "42") but that isn't always reliable. > > Additionally, without a graphical visualizer, it is also impossible to tell > that I did a merge in LanguageOfLanguages-NC.50.mcz unless I look at the > commit message and check the ancestors. > > If no graphical visualizer exists, how do Smalltalkers normally check for > branching/merging? > > Did you know about Torch? http://soft.vub.ac.be/torch/Home.html I've cc'ed Veronica ;) Cheers Mariano > Thanks! > > -- > Nick > > -- > View this message in context: > http://forum.world.st/Monticello-How-to-visualize-history-tp3508002p3508002… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > -- Mariano http://marianopeck.wordpress.com

May 9, 2011

Re: [Pharo-users] [Pharocasts] New comment on SandstoneDb, simple ActiveRecord style persistence....

by Bernat Romagosa

Thanks Ramon, it works now :) 2011/5/6 Ramon Leon <ramon.leon(a)allresnet.com> > On 05/06/2011 02:33 AM, Bernat Romagosa wrote: > >> I'm still having some trouble migrating the DB... I have an object that >> holds a Matrix, and whenever I attempt to save the object, SandstoneDB >> tries to remove elements from the matrix by using remove:, which it >> shouldNotImplement. Is there an easy workaround for this? >> > > Pull down the latest code, it should work now. > > > -- > Ramon Leon > http://onsmalltalk.com > >

May 9, 2011

Re: [Pharo-users] Monticello: How to visualize history?

by StÃ©phane Ducasse

alex this would be a good example for mondrian :) Stef On May 9, 2011, at 12:43 AM, Nick Chen wrote: > Hi > > Is there a nice way to visualize the history of Monticello repository? In > particular, I would like to be able to quickly identify the presence of > branching/merging. > > http://forum.world.st/file/n3508002/MonticelloBrowseHistory.png > > Consider the screenshot above. Without a graphical visualizer, it is hard to > tell that LanguageOfLanguages-NC.42.mcz and LanguageOfLanguages-jamie.42.mcz > branched out from LanguageOfLanguages-jamie.41.mcz. Their names might hint > that they do (because of the "42") but that isn't always reliable. > > Additionally, without a graphical visualizer, it is also impossible to tell > that I did a merge in LanguageOfLanguages-NC.50.mcz unless I look at the > commit message and check the ancestors. > > If no graphical visualizer exists, how do Smalltalkers normally check for > branching/merging? > > Thanks! > > -- > Nick > > -- > View this message in context: http://forum.world.st/Monticello-How-to-visualize-history-tp3508002p3508002… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

May 9, 2011

Re: [Pharo-users] Monticello: How to select/unselect changes to be committed?

by Lukas Renggli

Actually you don't need to save your code to a temporary location. It is enough to opeb the changes dialog before you revert. Having the temporary copy is only useful when you screw up. Lukas On Monday, 9 May 2011, Lukas Renggli <renggli(a)gmail.com> wrote: > You can't do it automatically from the GUI. > > What I do sometimes as a workaround is to commit the package to a > temporary location (package cache), restore the old version, and > selectively load and commit the changes to the new location. > > Lukas > > On 9 May 2011 00:35, Nick Chen <nchen.dev(a)mac.com> wrote: >> Hi >> >> When I code, I usually make changes to multiple classes/methods/etc at a >> time. However, when I commit to Monticello, I would like to organize those >> changes by breaking them into logical chunks with meaningful commit >> messages. >> >> Consider the following (trivial) example. Imagine that I would like to >> commit the change to buildMenuDockOn: in one commit and the change to >> buildStatusBarWith:on: in another commit. What is the easiest way to achieve >> this? >> >> http://forum.world.st/file/n3507981/Monticello.png >> >> Other version control systems allow you to selectively stage your changes >> before committing so I suspect that this should be doable with Monticello. >> >> Thanks! >> >> -- >> Nick >> >> -- >> View this message in context: http://forum.world.st/Monticello-How-to-select-unselect-changes-to-be-commi… >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > -- Lukas Renggli www.lukas-renggli.ch

May 9, 2011

Re: [Pharo-users] Monticello: How to select/unselect changes to be committed?

by Lukas Renggli

You can't do it automatically from the GUI. What I do sometimes as a workaround is to commit the package to a temporary location (package cache), restore the old version, and selectively load and commit the changes to the new location. Lukas On 9 May 2011 00:35, Nick Chen <nchen.dev(a)mac.com> wrote: > Hi > > When I code, I usually make changes to multiple classes/methods/etc at a > time. However, when I commit to Monticello, I would like to organize those > changes by breaking them into logical chunks with meaningful commit > messages. > > Consider the following (trivial) example. Imagine that I would like to > commit the change to buildMenuDockOn: in one commit and the change to > buildStatusBarWith:on: in another commit. What is the easiest way to achieve > this? > > http://forum.world.st/file/n3507981/Monticello.png > > Other version control systems allow you to selectively stage your changes > before committing so I suspect that this should be doable with Monticello. > > Thanks! > > -- > Nick > > -- > View this message in context: http://forum.world.st/Monticello-How-to-select-unselect-changes-to-be-commi… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > -- Lukas Renggli www.lukas-renggli.ch

May 9, 2011

Monticello: How to visualize history?

by Nick Chen

Hi Is there a nice way to visualize the history of Monticello repository? In particular, I would like to be able to quickly identify the presence of branching/merging. http://forum.world.st/file/n3508002/MonticelloBrowseHistory.png Consider the screenshot above. Without a graphical visualizer, it is hard to tell that LanguageOfLanguages-NC.42.mcz and LanguageOfLanguages-jamie.42.mcz branched out from LanguageOfLanguages-jamie.41.mcz. Their names might hint that they do (because of the "42") but that isn't always reliable. Additionally, without a graphical visualizer, it is also impossible to tell that I did a merge in LanguageOfLanguages-NC.50.mcz unless I look at the commit message and check the ancestors. If no graphical visualizer exists, how do Smalltalkers normally check for branching/merging? Thanks! -- Nick -- View this message in context: http://forum.world.st/Monticello-How-to-visualize-history-tp3508002p3508002… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 8, 2011

Monticello: How to select/unselect changes to be committed?

by Nick Chen

Hi When I code, I usually make changes to multiple classes/methods/etc at a time. However, when I commit to Monticello, I would like to organize those changes by breaking them into logical chunks with meaningful commit messages. Consider the following (trivial) example. Imagine that I would like to commit the change to buildMenuDockOn: in one commit and the change to buildStatusBarWith:on: in another commit. What is the easiest way to achieve this? http://forum.world.st/file/n3507981/Monticello.png Other version control systems allow you to selectively stage your changes before committing so I suspect that this should be doable with Monticello. Thanks! -- Nick -- View this message in context: http://forum.world.st/Monticello-How-to-select-unselect-changes-to-be-commi… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 8, 2011

Re: [Pharo-users] metacello question

by StÃ©phane Ducasse

I will add that to the useless chapter and book :D On May 7, 2011, at 3:37 PM, Mariano Martinez Peck wrote: > Hi. Try just a print of that. Example: > ((ConfigurationOfXXX project version: '1.0') load: 'something') inspect. > > If you don't want to load everything, and just simulate, then try: > > ((ConfigurationOfXXX project version: '1.0') record: 'something') inspect. > > #record: that exactly the same as load: but it doesn't really load the packages. > > Or take this: > > (ConfigurationOfXXX project version: '1.0') record: 'something'. > > but instead of doing a "do it", do a "print it" > > Or....print this: > > ((ConfigurationOfXXX project version: '1.0') record: 'something') loadDirective. > > HTH > > Mariano > > > > On Sat, May 7, 2011 at 3:30 PM, Werner Kassens <wkassens(a)libello.com> wrote: > Hi, > which method can i use to simulate eg a: > (ConfigurationOfXXX project version: '1.0') load: 'something' . > so that when printing it, i can see which packages are loaded in which order without actually loading those packages? > werner > > > > > -- > Mariano > http://marianopeck.wordpress.com >

May 7, 2011