- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40203 Home: https://github.com/pharo-project/pharo-core

Sept. 5, 2014

[pharo-project/pharo-core] 6be2ce: 40203

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 6be2ce8d2158348e31d378460d4725755dce0537 https://github.com/pharo-project/pharo-core/commit/6be2ce8d2158348e31d37846… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-05 (Fri, 05 Sep 2014) Changed paths: M Growl.package/GrowlMorph.class/README.md M ReleaseTests.package/ReleaseTest.class/instance/testing/testMethodsWithUnboundGlobals.st R ScriptLoader-Tests.package/ScriptLoaderTest.class/instance/testing/testCurrentPackagesDoesNotContainScriptLoader.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script203.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40203.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40203 13927 Failing test: #testCurrentPackagesDoesNotContainScriptLoader https://pharo.fogbugz.com/f/cases/13927 13960 Growl example in comment deprecated https://pharo.fogbugz.com/f/cases/13960 7591 in 4.0, unskip #testMethodsWithUnboundGlobals https://pharo.fogbugz.com/f/cases/7591 http://files.pharo.org/image/40/40203.zip

Sept. 5, 2014

Re: [Pharo-dev] Spec license

by Yuriy Tymchuk

No it was before. https://github.com/spec-framework/spec/pull/14 May 2 On 05 Sep 2014, at 10:43, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > > Le 5 sept. 2014 Ã 09:38, Yuriy Tymchuk a Ã©crit : > >> Iâve made fixes long time ago before Ben left. >> + my change is in Pharo image. >> >> Is this enough? > > I think so. All code contributed to Pharo via Fogbugz is licensed under MIT. > Problems may come if you did a pull request on the spec git repo after the re-licensing. >

Sept. 5, 2014

Re: [Pharo-dev] Spec license

by Christophe Demarey

Le 5 sept. 2014 Ã 09:38, Yuriy Tymchuk a Ã©crit : > Iâve made fixes long time ago before Ben left. > + my change is in Pharo image. > > Is this enough? I think so. All code contributed to Pharo via Fogbugz is licensed under MIT. Problems may come if you did a pull request on the spec git repo after the re-licensing.

Sept. 5, 2014

Re: [Pharo-dev] Any changes with fonts?

by Nicolai Hess

2014-09-05 9:41 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Uhâ¦ am I the only one stuck with Bitmap DejaVu Sans? Is everybody else > able to change fonts? > > Uko > No , me too. This happens since: 40195 13185 Move embedded fonts from Freetype package into separate package https://pharo.fogbugz.com/f/cases/13185 > > > On 02 Sep 2014, at 20:47, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > > Hi, > > > > when I cannot see system fonts anymore after selecting Free Type font > checkbox in settings. Are there any changes to fonts? Of something broke > down? > > > > Uko > > >

Sept. 5, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40202 Home: https://github.com/pharo-project/pharo-core

Sept. 5, 2014

[pharo-project/pharo-core] 4c1755: 40202

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 4c1755334dd6e89f3ad10d41d3082e6aeb425c9d https://github.com/pharo-project/pharo-core/commit/4c1755334dd6e89f3ad10d41… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-05 (Fri, 05 Sep 2014) Changed paths: M Nautilus.package/PackageTreeSelection.class/instance/converting/withClassesIn_createHierarchySorter_.st R Nautilus.package/SortHierarchically.class/class/instance creation/buildHierarchyForClasses_fromPackage_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script202.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40202.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Spec-Inspector.package/EyePointerExplorer.class/instance/accessing/selectedObjectDo_.st A Spec-Inspector.package/EyePointerExplorer.class/instance/accessing/valueClass.st A Spec-Inspector.package/PointerEyeElement.class/instance/accessing/accessorCode.st A Spec-Inspector.package/PointerEyeElement.class/instance/accessing/label.st A Spec-Inspector.package/PointerEyeElement.class/instance/accessing/selectedObjectDo_.st Log Message: ----------- 40202 13849 PointerExplorer item menu needs PointerEyeElement to implement #accessorCode https://pharo.fogbugz.com/f/cases/13849 12503 unreferenced parameter in SortHierarchically>>buildHierarchyForClasses:fromPackage: https://pharo.fogbugz.com/f/cases/12503 13861 make NOCController default OController https://pharo.fogbugz.com/f/cases/13861 http://files.pharo.org/image/40/40202.zip

Sept. 5, 2014

Re: [Pharo-dev] Any changes with fonts?

by Yuriy Tymchuk

Uhâ¦ am I the only one stuck with Bitmap DejaVu Sans? Is everybody else able to change fonts? Uko On 02 Sep 2014, at 20:47, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Hi, > > when I cannot see system fonts anymore after selecting Free Type font checkbox in settings. Are there any changes to fonts? Of something broke down? > > Uko

Sept. 5, 2014

Re: [Pharo-dev] Spec license

by Yuriy Tymchuk

Iâve made fixes long time ago before Ben left. + my change is in Pharo image. Is this enough? Uko On 04 Sep 2014, at 11:39, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > Yes, you should add a slice in the Pharo inbox with your contribution but ... it depends under which license you first published your contribution. If it was MIT, it is fine (and spec is out of law). If it was the double licensing, we will not be able to integrate it into Pharo. We should re-implement this functionality. > I know these things are boring but we should take care to avoid potential problems in the future. > > Le 4 sept. 2014 Ã 11:13, Yuriy Tymchuk a Ã©crit : > >> Oh wow, itâs amazing how complicated things can getâ¦ What you I have to do to have fixes available in Pharo? Send a slice to Pharo inbox? I just want to use dark theme in pharo and donât have ugly UI parts >> >> Uko >> >> On 04 Sep 2014, at 10:52, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: >> >>> >>> Le 3 sept. 2014 Ã 10:24, Torsten Bergmann a Ã©crit : >>> >>>> It is interesting that there is also a new Spec release [2] announced this week >>> >>> I can see in the announce: >>> Adds SpecTableLayout, thanks @webwarrior-ws >>> Removes hardcoded colors, thanks @Uko >>> >>> Do the authors of contribution (or their company if the contribution is done at work) agree on the new spec license? >>> If not, it cannot be part of the new spec and could be integrated in Pharo spec. >>> If so, we won't be able to integrate these fixes in Pharo. >>> >>> It woud be good that spec contributors clarify their position. >>> >>> Regards, >>> Christophe. >>> >> >

Sept. 5, 2014

Re: [Pharo-dev] [Vm-dev] Re: PharoLauncher on Windows not the latest version

by Nicolai Hess

2014-09-05 3:01 GMT+02:00 <btc(a)openinworld.com>: > Nicolai Hess wrote: > > 2014-09-04 18:53 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > >> >> I can confirm this behaviour. It looks like FilePlugin cannot 'rename' a >> folder across drives, although it can rename a file across drives. A hack >> to demonstrate from Workspace... >> >> filePlugin := FilePluginPrims allInstances first. >> filePlugin rename: 'C:\Temp\Test\file1.txt' to: >> 'C:\Temp\Test\file2.txt'. "-->sucess" >> filePlugin rename: 'E:\Temp\Test\file1.txt' to: >> 'E:\Temp\Test\file2.txt'. "-->sucess" >> filePlugin rename: 'C:\Temp\Test\file2.txt' to: >> 'E:\Temp\Test\file3.txt'. "-->sucess" >> >> filePlugin rename: 'C:\Temp\Test\folder1' to: 'C:\Temp\Test\folder2'. >> "-->sucess" >> filePlugin rename: 'E:\Temp\Test\folder1' to: 'E:\Temp\Test\folder2'. >> "-->sucess" >> filePlugin rename: 'C:\Temp\Test\folder2' to: 'E:\Temp\Test\folder3'. >> "-->fail" >> >> I think that is more of a design constraint that a bug. VBscript has a >> similar problem [1]. I cloned Pharo-vm off github and in >> ".../platforms/wind32/plugins/FilePlugin/sqWin32FilePrims.c" found function >> sqFileRenameOldSizeNewSize uses win32api function MoveFileW which is >> documented [2] as "The MoveFile function will move (rename) either a file >> or a directory (including its children) either in the same directory or >> across directories. The one caveat is that the MoveFile function will fail >> on directory moves when the destination is on a different volume." >> >> Unix platforms don't encounter this since all volumes are mounted under >> one root. (e.g. OSX mounting usb drives under /Volumes). I guess the Unix >> equivalent might be renaming to folder across network shares, though I'm >> not familiar with how different OS's handles that. >> > > > No, there is a similiar limitation on linux as well. Even if all > directories are under a common root dir, moving files across different > harddisks/partitions doesn't work: > > 12992 Cannot move files to another volume / partition under linux > <https://pharo.fogbugz.com/default.asp?12992> > > unix/linux vm uses the system library call rename() for moving files but > this function > (http://www.gnu.org/software/libc/manual/html_node/Renaming-Files.html) > results in an error > EXDEV 'Invalid cross-device link' > if the two file names newname and oldname are on different file systems. > > > > Thanks Nicolas. So given that its similar across platforms and reflects > the system-level semantics, probably we should not change its behaviour, > and handle this case at the PharoLauncher level. > No. Why? It is still an error that we can not "move" a file. On windows and Unix you can "move" a file, of course. Commandline tools like /bin/mv for example will do a "copy to destination - delete from source" if "rename" does not work. nicolai > > However it would be useful in Image to get something like an > 'InvalidCrossVolume' exception. I'm not sure off-hand how to approach that. > > cheers -ben > > > > >> >> However we should consider consistency across platforms. Cross volume >> folder renames could be checked for, and modified to a copy/delete >> strategy. To state the obvious, the options of where to do this are: >> a. In PharoLauncher >> b. In Pharo in >> WindowsStore(FileSystemStore)>>rename:ifAbsent:to:ifPresent:fileSystem: >> c. In VM >> >> Off the cuff, I'd vote for (b.), but others will better idea of the >> approach to take. Now if indeed a copy/delete fallback strategy is >> considered beneficial, it would need to consider how timestamps are >> > > > > led. >> >> [1] >> https://groups.google.com/forum/#!topic/microsoft.public.scripting.vbscript… >> [2] >> http://msdn.microsoft.com/en-us/library/windows/desktop/aa365239(v=vs.85).a… >> >> cheers -ben >> >> btw, Since this was my first time looking a VM code, I'm happy to report >> it was dead easy to clone pharo-vm from github and review (without yet >> trying to compile). Actually I cloned on OSX so I could `find` the win32 >> FilePlugin code. >> >> >> kilon alios wrote: >> >> So I manage to get Launcher running with downloading pharolauncher zip >> and then downloading pharo 3 and joining the two folders. Launcher now runs >> but I dont want it to store images in my c drive so I go to preferences >> and tell it where in my D drive to save images (D:\software\PharoImages) I >> press enter and I am getting this error >> >> WindowsStore(Object)>>primitiveFailed: >> WindowsStore(Object)>>primitiveFailed >> WindowsStore(FileSystemStore)>>rename:ifAbsent:to:ifPresent:fileSystem: >> FileSystem>>rename:ifAbsent:to:ifPresent: >> FileSystem>>rename:to: >> FileReference>>moveTo: >> PhLRelocateImageDirectoryCommand>>execute in Block: [ :child | child >> moveTo: (self target resolvePath:...etc... >> Array(SequenceableCollection)>>collect: >> PhLRelocateImageDirectoryCommand>>execute >> PhLRelocateImageDirectoryCommand>>executeOrInform >> PhLDirectoryBasedImageRepository class>>migrateFrom:to: >> PhLDirectoryBasedImageRepository class>>location: >> PhLDirectoryBasedImageRepository class>>locationString: >> SettingDeclaration>>realValue: >> SettingDeclaration>>index: >> EditableDropListMorph(DropListMorph)>>listSelectionIndex: >> EditableDropListMorph>>content: >> PluggableTextFieldMorph>>acceptTextInModel >> PluggableTextFieldMorph(PluggableTextMorph)>>acceptBasic >> PluggableTextFieldMorph>>accept >> TextMorphForFieldView(TextMorphForEditView)>>acceptContents >> TextEditor>>accept >> TextMorphForFieldView(TextMorphForEditView)>>keyStroke: >> TextMorphForFieldView>>keyStroke: >> TextMorphForFieldView(TextMorph)>>handleKeystroke: >> KeyboardEvent>>sentTo: >> TextMorphForFieldView(Morph)>>handleEvent: >> TextMorphForFieldView(Morph)>>handleFocusEvent: >> HandMorph>>sendFocusEvent:to:clear: in Block: [ ... >> BlockClosure>>on:do: >> >> >> >> On Mon, Sep 1, 2014 at 12:06 PM, kilon alios <kilon.alios(a)gmail.com> >> wrote: >> >>> I am not back to my work pc, so if you have any ideas how to proceed I >>> am open to suggestions. >>> >>> >>> On Thu, Aug 28, 2014 at 5:17 PM, Tim Mackinnon <tim(a)testit.works> wrote: >>> >>>> Kilon - it would be good if we could percevear to try and get a fix and >>>> detailed instructions for other less confident usersâ¦ At least test Benâs >>>> updated installer so we can clear this. >>>> >>>> I appreciate the aggravation you are putting up with. >>>> >>>> Tim >>>> >>>> On 28 Aug 2014, at 10:35, kilon alios <kilon.alios(a)gmail.com> wrote: >>>> >>>> My work pc is dual boot to ubuntu and win 7 . I am not a fan of linux >>>> either, loads of problems there but nowhere near as bad as windoom. >>>> >>>> I need windoom because of a Greek OCR I use at work to scan legal >>>> documents. I have no choice other than to continue using it. >>>> >>>> I dont care what the corporate world does or the fact that almost >>>> 100% of my fellow lawyers use windoom and some still DOS. Thats their >>>> problem :D >>>> >>>> It would be nice to support what 95% of people use out there, but >>>> alas I cant take it anymore. Coding should be fun, Windoom kills my inner >>>> child. Sorry for those that have to tolerate this crap, but I am lucky >>>> enough not to . >>>> >>>> /ranting off >>>> >>>> >>>> On Thu, Aug 28, 2014 at 11:50 AM, Ben Coman <btc(a)openinworld.com> >>>> wrote: >>>> >>>>> kilon alios wrote: >>>>> >>>>>> ok thing get worse and worse >>>>>> >>>>>> I try to run pharo as administrator and pharo opens and exits >>>>>> immediately , it creates a stderr which contains the following >>>>>> >>>>>> http://pastebin.com/v9Hpx9pK >>>>>> >>>>>> I found the folder you mentioned and I deleted it , now pharo does >>>>>> not open at all even when run without "run as administrator" >>>>>> Boy I hate Windoom. I also tried Tim link , nothing, pharo opens but >>>>>> does nothing, no gui, nothing. I know it opens because i can see its >>>>>> process in the task manager which i have to terminate manually. >>>>>> I do all my coding and art on macos, I only have windows at work so i >>>>>> can test my code on windoom too, but this was the last straw, I had enough >>>>>> with this uber crappy OS for 17 years now. I am dropping support for it and >>>>>> sticking to MacOS only. >>>>>> Thanks guys for your help but it does not worth it. I hope no other >>>>>> windows user experience my problem. >>>>>> >>>>>> >>>>> I empathize. I've been a Linux advocate for years, but never made >>>>> the full desktop switch since I needed a Windows system for corporate >>>>> compatibility. Then I got a mac-mini to experiment with iPad Mobile Device >>>>> Management, and found it easier to get Latex working on it than on Windows >>>>> (for processing Pillar output), and now I find myself using it for Pharo >>>>> more every day, and my Windows box is starting to be neglected (except I >>>>> still need to migrate my old Thunderbird email archive). >>>>> >>>>> However success in the corporate world still hinges a lot on Windows >>>>> compatibility. I will still have a go at updating PharoLauncher Installer >>>>> to avoid this problem. >>>>> cheers, Ben >>>>> >>>>> P.S. @Tim, Your alternate-VM feature sound interesting. I'll check it >>>>> out. >>>>> >>>>> >>>> >>>> >>> >> >> >> > > >

Sept. 5, 2014