yes launcher works fine with C , i am actually using a pharo 3 image with it that I downloaded with pharolauncher.I had so far one windows problem after another, for example I tried to get gitfiletree and for some reason shortcuts dont work so I tried alt+d and ctrl+d to do it , nothing. The Gofer complained that it has no loadStable message while it has so I had to do the cascade one line at a time instead. Etc Etc. Pharo needs definetly more developers on windows side. Its clear that development is unix centered but then the story is the same for most open source projects out there. Looks like windows is extremely popular with users and extremely unpopular with at least open source developers .
Do I blame them ? hell no :D On Thu, Sep 4, 2014 at 2:40 PM, Tim Mackinnon <[email protected]> wrote: > Just to check - did you confirm that it worked on your C: drive (I’m > assuming yes - but given you’ve had to cobble together a running version, > its worth making sure to you have a good baseline). I’m on OSX but don’t > have a separate drive - so I haven’t notice that (I guess if I plugged in a > portable drive, I could try that). > > Tim > > On 4 Sep 2014, at 11:15, kilon alios <[email protected]> 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 <[email protected]> > 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 <[email protected]> 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 <[email protected]> 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 <[email protected]> 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. >>>> >>>> >>> >>> >> > >
