- Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.4] #14018
by Marcus Denker June 28, 2011

June 28, 2011

14018 ----- Issue 4464: remove MaskedTextMorph http://code.google.com/p/pharo/issues/detail?id=4464 Issue 4462: Move AlphaInfiniteForm to same category as InfiniteForm http://code.google.com/p/pharo/issues/detail?id=4462 Issue 4463: unload deprecated 12 http://code.google.com/p/pharo/issues/detail?id=4463 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Merge tool. No way to cherry pick the changes?
by Igor Stasenko June 27, 2011

June 27, 2011

I don't understand, when i merging, the merge tool showing me all the difference between current version and incoming one. It says '0 conflicts' and its ok to merge, but what if i want to choose to keep an old version for some methods, while merge the rest? What i see that there is no way to do that .. all menu items which would allow me to do that, like 'keep current version' 'use incoming verison' 'mark as conflict' are disabled. Which means that once machine decided that there is no conflict, you cannot do much. I tried to quickly hack the UI and enable those menu items , but it doesn't works, because the model itself seems like don't supports that. So, the question is how we can change that? As to me, it is certainly a missing feature, if i cannot freely choose between current and incoming version at my will, when merging. Gary (& all)? Any ideas? -- Best regards, Igor Stasenko AKA sig.

6 16

[Pharo-project] Moose out of memory
by Alain Rastoul June 27, 2011

June 27, 2011

Hi, There was a previous message in the list about an out of memory problem with Moose when running 3 times MooseScripts createModelForConfigurationOfMoose I downloaded moose suite 4.5 (Pharo 1.3) and played a bit with it reading the moose book (nice). IMHO although something is perhaps not completly clear in the vm in memory allocation and/or ui process and/or low space watcher (I tryed to debug the vm but did not succeed), here the problem seems to be in the Moose model. I suspect that the problem is just that the cache keeps a reference to the Moose model each time the script is run, see at the end of MooseScripts>>createModelForConfigurationOfMoose the model is added to a cache ((MooseModel root => MooseGroupRuntimeStorage>> byType) and takes abut 130M of memory each time. clearing the Moose cache resolve the problem. MooseModel allInstancesDo:[ :m | m remove ] seems to be working here, except that there is an exception for the root model (I don't know Moose, it may not be the best command). Perhaps the moose model should not be added by type but overriden each time (beeing identified by a "name" ?). PS: Moose is cool :) Cheers Alain

4 8

Re: [Pharo-project] [Jenkins] Kernel 1.4 with Gofer+Networking
by Marcus Denker June 27, 2011

June 27, 2011

On Jun 27, 2011, at 7:06 PM, Pavel Krivanek wrote: > Hi, > > currently it is possible to load and successfully initialize Morphic > with all packages present in the Core image at once. I already sent to > Marcus necessary scripts for Hudson. I will set it up tonight... > But we still do not have > something like MinimalMorphic image. We will do some serious Morphic cleanup over the Summer... -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] [Jenkins] Kernel 1.4 with Gofer+Networking
by Marcus Denker June 27, 2011

June 27, 2011

https://ci.lille.inria.fr/pharo/job/Pharo%20Kernel%201.4/ There is now a Pharo-Kernel-Gofer (3MB) that has networking and Gofer loaded back into the Kernel. Thanks Pavel! This is starting to get really interesting... TODO: -> Tests for Kernel -> reload everything to re-create Pharo 1.4 Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

4 5

[Pharo-project] [update 1.4] #14017
by Marcus Denker June 27, 2011

June 27, 2011

14017 ----- Issue 4458: remove ImageSegment from ShutDownList http://code.google.com/p/pharo/issues/detail?id=4458 Issue 4460: Do not try to migrate instances in ImageSegements on Disk http://code.google.com/p/pharo/issues/detail?id=4460 Issue 4459: Move Polymorph FillStyles and Borders to where their superlcass lives http://code.google.com/p/pharo/issues/detail?id=4459 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] [update 1.4] #14016
by Marcus Denker June 27, 2011

June 27, 2011

Issue 4456: 1.4: relead dirty package http://code.google.com/p/pharo/issues/detail?id=4456 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] UIManager>>chooseFileName* flavour to get full path?
by Guillermo Polito June 27, 2011

June 27, 2011

Hi! I was wondering why UITheme>>chooseFileNameIn: title: patterns: path: preview: and UITheme>>chooseFileNameIn: title: extensions: path: preview: do fd := FileDialogWindow basicNew previewType: preview; initialize; title: title; *answerFileName*. And actually there is no variant using *answerPathName* what is a bit more useful because it answers the entire path to the selected file... Thanks! Guille

3 2

[Pharo-project] [TODO] 1.3
by Marcus Denker June 27, 2011

June 27, 2011

CORE ====== -> Core is green and no issue is tagged 1.3 FULL ====== FULL has three open reports, all of which are solved but not integrated. Issue 4390: OCompletion does not respect #enabled setting; it has no "off switch" Issue 4394: GoferApiTest >> testRepositoryErrors fails in Full but not in Core Issue 4447: Appl-k shortcut not working in Pharo 1.2.2 image http://code.google.com/p/pharo/issues/list?can=2&q=milestone%3D1.3-DevImage Any help to actually get them integrated is very welcome. All of them are not real show stoppers, I suggest we release end of the week nevertheless. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] [update 1.4] #14015
by Marcus Denker June 26, 2011

June 26, 2011

14015 ----- Issue 4455: Subclasses of Obsolete classes to be removed http://code.google.com/p/pharo/issues/detail?id=4455 Issue 4454: ScriptLoader: remove 1.3 update and script methods. http://code.google.com/p/pharo/issues/detail?id=4454 Issue 4452: Build of 1.3 full is broken http://code.google.com/p/pharo/issues/detail?id=4452 TODO: there is now one package dirty. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0