May 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Saving to local git and "Loading all file names from http://...pharo5/inbox"

by stepharo

>>>> For some reason the package manager is refreshing all packages. I don't know why it happens, and it's quite annoying (because it slows down commits), but it doesn't cause any actual problems, so don't worry about it too much. >>> As I understand it, what happens is the following: before you commit to your MC repo, you have to find the next version number; a check is then done in all relevant repos; the cached content is not used, but an actual refresh is done. All this is so that my .5 would not conflict with someone else .5 - the chance that this happens is very small, and the check does not really prevent it. >> I assumed that but can it be limited to the Repositories that are associated with the package? I am afraid that next time I travel I can not commit to my local repository (and ofcourse the speed part). :) > We should go one step further: add an option to totally disable this check to go outside the target repo, It would be cool because you imagine when we integrate a change :) > it makes little sense. But MC is a complex beast ... > >> holger > >

May 29, 2016

[ANN] New Pharo Glorp version and Book chapter

by Esteban A. Maringolo

Hello all, During the first part of the year, and sponsored by the Pharo Consortium, I started a new port of Glorp, the Object-Relational mapper, based on the latest version available in VW 8.0.1. This latest port was done from scratch in Pharo and brings features and bugfixes that were accumulated in the VW port during more than 5 years (previous Pharo port) and weren't available until now; and it uses the Garage database drivers (but not limited to them). During the last couple of months, and also by request of the Consortium, I wrote a chapter for one of the Pharo books describing Glorp as much as possible, with tutorials and key concepts. The chapter ended up being the longest in text and pages of all written; the domain is so broad and deep that I'm considering taking it to a whole book, who knows... The book is available at <https://ci.inria.fr/pharo-contribution/job/PharoBookWorkInProgress/lastSucc…>, and I will welcome suggestions and corrections as pull requests to <https://github.com/SquareBracketAssociates/PharoInProgress> The Glorp repository is the same as the previous one (http://www.smalltalkhub.com/#!/~DBXTalk/Glorp) and the current Metacello configs will load the previous version for Pharo 4 and the new version for Pharo 5. For the foreseeable future I'll continue maintaining Glorp, but the code is MIT and I'm open to contributions (I'll set up a Github repo in the next days). Also I've been running production software based on Glorp for a few years now, so my experience with it cover most of its features and usage patterns, so if you have particular questions not covered by the book chapter or any other material feel free to ask me, this mailing list or to the Glorp mailing list at <glorp-group(a)googlegroups.com>. Best regards! Esteban A. Maringolo

May 29, 2016

Re: [Pharo-users] Is lazy evaluation of infinite series possible?

by Evan Donahue

Hello, I know infinite series are mentioned in the numerical methods book, although I haven't worked with those classes specifically. http://files.pharo.org/books/numerical-methods/2016-04-NumericalMethods.pdf You could also use a LazyList, depending on what you were doing, from http://smalltalkhub.com/#!/~EvanDonahue/Lazy/ x := 3. Float e raisedTo: x. " = 20.085536923187664" eX := LazyList wholes collect: [ :n | (x raisedTo: n) / n factorial ]. (eX take: 20) sum asFloat. " = 20.085536921517672" 2 * (Float e raisedTo: x). " = 40.17107384637533" twoEX := eX with: eX collect: [ :a :b | a + b ]. (twoEX take: 20) sum asFloat. " = 40.171073843035344" Will either of those work? Evan -- View this message in context: http://forum.world.st/Is-lazy-evaluation-of-infinite-series-possible-tp4897… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 29, 2016

Re: [Pharo-users] Saving to local git and "Loading all file names from http://...pharo5/inbox"

by Thierry Goubier

Le 29/05/2016 14:04, Peter Uhnak a Ã©crit : > On Sun, May 29, 2016 at 11:21:21AM +0200, Thierry Goubier wrote: >> Le 29/05/2016 11:15, Peter UhnÃ¡k a Ã©crit : >>> > All this is so that my .5 would not conflict with someone else .5 >>> >>> How is this a problem? Because it will be "Me.5" and "You.5", so there >>> can't be any conflict. >> >> Me.5 and Me.5 are possible... >> >> Think of numbering your own stuff on two different branches. >> >> More, Metacello depends on Me.5 5 to be greater than You.5 5 for some of the >> baselines / configurations to work properly :) > > Can't it use the ancestry to decide? I suggested that to Dale... Disregard version numbers, only consider as newer if the other is in the ancestry chain. Would also be a lot more precise, because we would then use the package version UID instead of the name.version number approximation which can leads to failures or loading the wrong package in some cases. > Because my impression is from this that merges are naive, compared to > git which actually checks the ancestry of both up the common endpoint > and diffs based on that. This does not describe the Monticello merges. Monticello merges do walk the ancestry chain to find a common ancestor and does a three way merge, as git does. The problem is that the Monticello ancestry chain is often damaged for three reasons: removing part of it to reduce memory usage (Done for the Pharo3 release), removing all or part of it because your package ancestry chain is too long (I remember seeing some packages doing that on purpose?), the common ancestor doesn't exist anymore in the repositories visible to Monticello (long-lived packages that have moved between repositories, typically). When Monticello sees a version in the history, it expects the full package to be available in the repositories; if this package is the common ancestor of the merge and can't be retrieved, then the merge will fail. What GitFileTree/git does there is to ensure that if a version is in the ancestry, it can be retrieved. Git merge also use that property. Any GitFileTree-like layer would provide the same property (FossilFileTree, for example). Note: in the git documentation, it is stated that git may create virtual ancestors in some cases, to simplify/reduce the merge work. In such cases, if set up, the gitfiletree merge driver will be called for all those merges (i.e. a single merge in git may trigger multiple merges). Obvious, isn't it ;) Thierry > Peter > >> >> Thierry >> >>> >>> Peter >>> >>> On Sun, May 29, 2016 at 10:37 AM, Sven Van Caekenberghe <sven(a)stfx.eu >>> <mailto:sven@stfx.eu>> wrote: >>> >>> >>> > On 29 May 2016, at 10:28, Holger Freyther <holger(a)freyther.de <mailto:holger@freyther.de>> wrote: >>> > >>> > >>> >> On 29 May 2016, at 09:58, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: >>> >> >>> >> >>> >>> >>> >>> For some reason the package manager is refreshing all packages. I don't know why it happens, and it's quite annoying (because it slows down commits), but it doesn't cause any actual problems, so don't worry about it too much. >>> >> >>> >> As I understand it, what happens is the following: before you commit to your MC repo, you have to find the next version number; a check is then done in all relevant repos; the cached content is not used, but an actual refresh is done. All this is so that my .5 would not conflict with someone else .5 - the chance that this happens is very small, and the check does not really prevent it. >>> > >>> > I assumed that but can it be limited to the Repositories that are associated with the package? I am afraid that next time I travel I can not commit to my local repository (and ofcourse the speed part). :) >>> >>> We should go one step further: add an option to totally disable this >>> check to go outside the target repo, it makes little sense. But MC >>> is a complex beast ... >>> >>> > holger >>> >>> >>> >> >> > >

May 29, 2016

Re: [Pharo-users] Saving to local git and "Loading all file names from http://...pharo5/inbox"

by Peter Uhnak

On Sun, May 29, 2016 at 11:21:21AM +0200, Thierry Goubier wrote: > Le 29/05/2016 11:15, Peter UhnÃ¡k a Ã©crit : > > > All this is so that my .5 would not conflict with someone else .5 > > > > How is this a problem? Because it will be "Me.5" and "You.5", so there > > can't be any conflict. > > Me.5 and Me.5 are possible... > > Think of numbering your own stuff on two different branches. > > More, Metacello depends on Me.5 5 to be greater than You.5 5 for some of the > baselines / configurations to work properly :) Can't it use the ancestry to decide? Because my impression is from this that merges are naive, compared to git which actually checks the ancestry of both up the common endpoint and diffs based on that. Peter > > Thierry > > > > > Peter > > > > On Sun, May 29, 2016 at 10:37 AM, Sven Van Caekenberghe <sven(a)stfx.eu > > <mailto:sven@stfx.eu>> wrote: > > > > > > > On 29 May 2016, at 10:28, Holger Freyther <holger(a)freyther.de <mailto:holger@freyther.de>> wrote: > > > > > > > > >> On 29 May 2016, at 09:58, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: > > >> > > >> > > >>> > > >>> For some reason the package manager is refreshing all packages. I don't know why it happens, and it's quite annoying (because it slows down commits), but it doesn't cause any actual problems, so don't worry about it too much. > > >> > > >> As I understand it, what happens is the following: before you commit to your MC repo, you have to find the next version number; a check is then done in all relevant repos; the cached content is not used, but an actual refresh is done. All this is so that my .5 would not conflict with someone else .5 - the chance that this happens is very small, and the check does not really prevent it. > > > > > > I assumed that but can it be limited to the Repositories that are associated with the package? I am afraid that next time I travel I can not commit to my local repository (and ofcourse the speed part). :) > > > > We should go one step further: add an option to totally disable this > > check to go outside the target repo, it makes little sense. But MC > > is a complex beast ... > > > > > holger > > > > > > > >

May 29, 2016

QCMagritte & Voyage?

by Udo Schneider

All, I'm currently trying to wrap my head around QCMagritte. So far it seems to include most of what I need. I'm not sure though how/where to integrate a persistency layer (i.e. Voyage in this case). I'm either missing some place to activly take control and do saving/upgrading or any callback when objects/collections have been changed. Any pointers or sample code? Thanks, Udo

May 29, 2016

Re: [Pharo-users] (no subject)

by frankl1_miky

Thanks for all your answers, It's true that pharo community is active. I'll give you feedback about my progress. I'm having fun with Pharo Mooc at this period. Thanks for your help! -- View this message in context: http://forum.world.st/no-subject-tp4894192p4897990.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 29, 2016

Re: [Pharo-users] Saving to local git and "Loading all file names from http://...pharo5/inbox"

by Thierry Goubier

Le 29/05/2016 11:15, Peter UhnÃ¡k a Ã©crit : > > All this is so that my .5 would not conflict with someone else .5 > > How is this a problem? Because it will be "Me.5" and "You.5", so there > can't be any conflict. Me.5 and Me.5 are possible... Think of numbering your own stuff on two different branches. More, Metacello depends on Me.5 5 to be greater than You.5 5 for some of the baselines / configurations to work properly :) Thierry > > Peter > > On Sun, May 29, 2016 at 10:37 AM, Sven Van Caekenberghe <sven(a)stfx.eu > <mailto:sven@stfx.eu>> wrote: > > > > On 29 May 2016, at 10:28, Holger Freyther <holger(a)freyther.de <mailto:holger@freyther.de>> wrote: > > > > > >> On 29 May 2016, at 09:58, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: > >> > >> > >>> > >>> For some reason the package manager is refreshing all packages. I don't know why it happens, and it's quite annoying (because it slows down commits), but it doesn't cause any actual problems, so don't worry about it too much. > >> > >> As I understand it, what happens is the following: before you commit to your MC repo, you have to find the next version number; a check is then done in all relevant repos; the cached content is not used, but an actual refresh is done. All this is so that my .5 would not conflict with someone else .5 - the chance that this happens is very small, and the check does not really prevent it. > > > > I assumed that but can it be limited to the Repositories that are associated with the package? I am afraid that next time I travel I can not commit to my local repository (and ofcourse the speed part). :) > > We should go one step further: add an option to totally disable this > check to go outside the target repo, it makes little sense. But MC > is a complex beast ... > > > holger > > >

May 29, 2016

Re: [Pharo-users] Saving to local git and "Loading all file names from http://...pharo5/inbox"

by Peter UhnÃ¡k

> All this is so that my .5 would not conflict with someone else .5 How is this a problem? Because it will be "Me.5" and "You.5", so there can't be any conflict. Peter On Sun, May 29, 2016 at 10:37 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 29 May 2016, at 10:28, Holger Freyther <holger(a)freyther.de> wrote: > > > > > >> On 29 May 2016, at 09:58, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> > >> > >>> > >>> For some reason the package manager is refreshing all packages. I > don't know why it happens, and it's quite annoying (because it slows down > commits), but it doesn't cause any actual problems, so don't worry about it > too much. > >> > >> As I understand it, what happens is the following: before you commit to > your MC repo, you have to find the next version number; a check is then > done in all relevant repos; the cached content is not used, but an actual > refresh is done. All this is so that my .5 would not conflict with someone > else .5 - the chance that this happens is very small, and the check does > not really prevent it. > > > > I assumed that but can it be limited to the Repositories that are > associated with the package? I am afraid that next time I travel I can not > commit to my local repository (and ofcourse the speed part). :) > > We should go one step further: add an option to totally disable this check > to go outside the target repo, it makes little sense. But MC is a complex > beast ... > > > holger > > >

May 29, 2016

Re: [Pharo-users] Saving to local git and "Loading all file names from http://...pharo5/inbox"

by Sven Van Caekenberghe

> On 29 May 2016, at 10:28, Holger Freyther <holger(a)freyther.de> wrote: > > >> On 29 May 2016, at 09:58, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> >>> >>> For some reason the package manager is refreshing all packages. I don't know why it happens, and it's quite annoying (because it slows down commits), but it doesn't cause any actual problems, so don't worry about it too much. >> >> As I understand it, what happens is the following: before you commit to your MC repo, you have to find the next version number; a check is then done in all relevant repos; the cached content is not used, but an actual refresh is done. All this is so that my .5 would not conflict with someone else .5 - the chance that this happens is very small, and the check does not really prevent it. > > I assumed that but can it be limited to the Repositories that are associated with the package? I am afraid that next time I travel I can not commit to my local repository (and ofcourse the speed part). :) We should go one step further: add an option to totally disable this check to go outside the target repo, it makes little sense. But MC is a complex beast ... > holger

May 29, 2016