June 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Sticky morph after progress morph use

by phil＠highoctane.be

Well, got some leftovers of a progress bar every once in a while... Phil 2012/6/24 Hilaire Fernandes <hilaire.fernandes(a)edu.ge.ch> > On 24/06/2012 13:28, Max Leske wrote: > > + 1 for fixing that > > > But this problem does not show up with uncleaned-for-release image, > don't you? > > Thanks > > Hilaire > > > > -- > Dr. Geo -- http://www.drgeo.eu > > > -- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges Belgium

June 24, 2012

Re: [Pharo-project] Sticky morph after progress morph use

by Hilaire Fernandes

On 24/06/2012 13:28, Max Leske wrote: > + 1 for fixing that But this problem does not show up with uncleaned-for-release image, don't you? Thanks Hilaire -- Dr. Geo -- http://www.drgeo.eu

June 24, 2012

Re: [Pharo-project] Sticky morph after progress morph use

by Max Leske

+ 1 for fixing that On 24.06.2012, at 12:14, Hilaire Fernandes wrote: > Hello, > > With Pharo 1.4 I already reported about it, but when I build a drgeo > image then do a small clean up like this: > > === clean up ==== > FreeTypeFontProvider unload. > ScriptLoader new cleanUpForProduction. > StrikeFont cleanUp. > > (MCPackage named: 'Announcements-Help') unload. > (MCPackage named: 'FileSystem-Tests-Disk') unload. > (MCPackage named: 'FileSystem-Tests-Memory') unload. > (MCPackage named: 'FileSystem-Tests-Core') unload. > (MCPackage named: 'FileSystem-Tests-AnsiStreams') unload. > (MCPackage named: 'Metacello-Help') unload. > (MCPackage named: 'Regex-Help') unload. > RecentMessageList cleanUp. > Smalltalk removeEmptyMessageCategories. > Smalltalk garbageCollect > ==== end of clean up === > > > Then, in the cleaned image, in any place where the progress morph is > used, at the end of the progress process, a shaded morph (the background > of the progress morph) remains on screen like a big smelling peace of > shit - screenshot. > > What cleaning I should not do? > > Thanks > > Hilaire > > > -- > Dr. Geo -- http://www.drgeo.eu > <progress-morph-background-like-a-smelling-peace-of-shit.jpg>

June 24, 2012

[Pharo-project] Sticky morph after progress morph use

by Hilaire Fernandes

Hello, With Pharo 1.4 I already reported about it, but when I build a drgeo image then do a small clean up like this: === clean up ==== FreeTypeFontProvider unload. ScriptLoader new cleanUpForProduction. StrikeFont cleanUp. (MCPackage named: 'Announcements-Help') unload. (MCPackage named: 'FileSystem-Tests-Disk') unload. (MCPackage named: 'FileSystem-Tests-Memory') unload. (MCPackage named: 'FileSystem-Tests-Core') unload. (MCPackage named: 'FileSystem-Tests-AnsiStreams') unload. (MCPackage named: 'Metacello-Help') unload. (MCPackage named: 'Regex-Help') unload. RecentMessageList cleanUp. Smalltalk removeEmptyMessageCategories. Smalltalk garbageCollect ==== end of clean up === Then, in the cleaned image, in any place where the progress morph is used, at the end of the progress process, a shaded morph (the background of the progress morph) remains on screen like a big smelling peace of shit - screenshot. What cleaning I should not do? Thanks Hilaire -- Dr. Geo -- http://www.drgeo.eu

June 24, 2012

[Pharo-project] Tests Guard report for 20156

by Pavel Krivanek

Tests Guard report for 20156 http://code.google.com/p/pharo/wiki/TestsGuard solved failures: SUnit.Tests.Core.TestCaseTest.testAssertEqualsActualAndExpectedOrder new failures: FileSystem.Tests.Core.PathTest.testBasenameWithoutExtension

June 24, 2012

Re: [Pharo-project] better tab implementation

by Tudor Girba

Hi Stef, Yes, these are the base classes. You should also publish: - LazyTabPageRemoved - LazyTabPageChanged However, please keep in mind that the lazy implementation is more of a hack to fit somehow within the original tab implementation. In the long run, we should refactor this. Doru On 23 Jun 2012, at 12:35, StÃ©phane Ducasse wrote: > Hi ben > > I publish LazyTabPage for you in pharo inbox. > Let me know if this is good for you. > > > Stef > > > Name: LazyTabPage-StephaneDucasse.1 > Author: StephaneDucasse > Time: 23 June 2012, 12:34:58.393 pm > UUID: 062bd9b4-5dbe-4b3e-91b1-3ae3a8230071 > Ancestors: > > implementation from Moose > > > > On Jun 23, 2012, at 12:15 PM, StÃ©phane Ducasse wrote: > >> Hi doru >> >> is the better tab implementation based on >> LazyTabPage >> LazyTabGroupMorph >> LazyTablPageAnnouncement >> >> ? >> >> I'm extracting them so that ben can improve nautilus. >> >> Stef >> > > -- www.tudorgirba.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."

June 24, 2012

Re: [Pharo-project] is there a way to pass a script to a vm without passing via a file?

by StÃ©phane Ducasse

Ok I will have a look. What I want is an image that launch other images with instructions I just want to know if I always have to pass scripts around and if I could instead pass code via any other means (socketâ¦) I have to see. > BasicCodeLoader

June 24, 2012

Re: [Pharo-project] start thinking on summer release of Pharo 1.4

by Sean P. DeNigris

Sean P. DeNigris wrote > > I want to review bug fixes integrated in 2.0 [1] and see if any should be > included for 1.4 per > http://forum.world.st/Backporting-fixes-tp4633625p4633635.html > > [1] > http://code.google.com/p/pharo/issues/list?can=1&q=status%3AIntegrated+Mile… > I did a first pass on the 2.0 fix list. I created an issue: Issue 6144: Port 2.0 bug fixes to 1.4 for summer release http://code.google.com/p/pharo/issues/detail?id=6144 Each comment contains a port of a fix that was integrated in 2.0 and conforms to Marcus' guidelines for including in 1.4 [2]. The slices were all created with 1.4 #14444. Please add any that I missed... Cheers, Sean [2] guidelines for bug fixes to a released version of Pharo (i.e. 1.4): - No new features. - No cleanups - If a bug was there in Pharo 1.1 already and we lived with it for years, fixing it in the current dev version is (in many cases) enough. (There are exceptions, but is does not happen often). -- View this message in context: http://forum.world.st/start-thinking-on-summer-release-of-Pharo-1-4-tp46345… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 24, 2012

Re: [Pharo-project] is there a way to pass a script to a vm without passing via a file?

by Camillo Bruni

On 2012-06-23, at 23:50, Sven Van Caekenberghe wrote: > > On 23 Jun 2012, at 22:25, Camillo Bruni wrote: > >> no no all in the image :), see BasicCodeLoader > > Very nice, but you mean EvaluateCommandLineHandler is guess ? > > If I understand it correctly, it will always quit the image after evaluating something. > Furthermore is print the results of the evaluation to stdout, no ? yes, I think that default behavior is pretty consistent with what I know from other languages. but yeah, maybe should add a default option --no-quit or so to keep the image open. otherwise there is still the st handler that keeps the image open (which I do not like that much either :/) at least both should work the same way IMO

June 23, 2012

Re: [Pharo-project] is there a way to pass a script to a vm without passing via a file?

by Sven Van Caekenberghe

On 23 Jun 2012, at 22:25, Camillo Bruni wrote: > no no all in the image :), see BasicCodeLoader Very nice, but you mean EvaluateCommandLineHandler is guess ? If I understand it correctly, it will always quit the image after evaluating something. Furthermore is print the results of the evaluation to stdout, no ? Sven

June 23, 2012