August 2014 - Pharo-dev - lists.pharo.org

Duplicate repositories in fresh Image

by Ben Coman

Aug. 9, 2014

Re: [Pharo-dev] Submitted Improved Pharo Help (Case 13811) - but couldn't compare it?

by Ben Coman

Tim Mackinnon wrote: > Guys - Iâve incorporate the feedback from Nicolai from my previous help text submission and I thought I had the submission steps down pat - however I hit a strange problem when I was submitting my slice, and I want to check Iâm doing things right? > > My changes are very simple - 1 class method (to name my help entry) and class comment changes to improve the help text. > > I had been happily making changes and versioning them in my own local MC directory repo. > > When I went to submit my change - I didnât have a dirty package (as I had just versioned it locally) - but I donât think thats a problem right? I just created a +Slice, entered my Fobgugz number and then selected my Package by scrolling through the list of packages. > > However when I wen to compare my change against the Pharo40inbox - it kept saying that there were no changes? I donât understand that - as the inbox has my previous submission 6.mcz and something by Stefan 7.mcx - so I was expecting to see the single class method change as well as the class comment change? Did I do something wrong? > > To make sure, I went back - made a small text change, so that I had a dirty package, and then followed the same steps in the video - and this time it did show me a change against Pharo40Inbox, but it was just my small text change? So Iâm worried that Iâve done something funny - but I canât work out what? > > Could someone just set me straight? > I'm not sure of the exact expected behaviour, but I wonder what happens if you clear out your package cache direct of files, and also do "MCFileBasedRepository allSubInstances do: [ :mcfbr | mcfbr flushCache] " Disclaimer: Thats just a guess from a few minutes digging. I'm not really familiar with the architecture, and #flushCache is 'private' in MCFileBasedRepository, but also is in 'actions' in MCHttpRepository. cheers -ben > Tim > >

Aug. 9, 2014

Submitted Improved Pharo Help (Case 13811) - but couldn't compare it?

by Tim Mackinnon

Guys - Iâve incorporate the feedback from Nicolai from my previous help text submission and I thought I had the submission steps down pat - however I hit a strange problem when I was submitting my slice, and I want to check Iâm doing things right? My changes are very simple - 1 class method (to name my help entry) and class comment changes to improve the help text. I had been happily making changes and versioning them in my own local MC directory repo. When I went to submit my change - I didnât have a dirty package (as I had just versioned it locally) - but I donât think thats a problem right? I just created a +Slice, entered my Fobgugz number and then selected my Package by scrolling through the list of packages. However when I wen to compare my change against the Pharo40inbox - it kept saying that there were no changes? I donât understand that - as the inbox has my previous submission 6.mcz and something by Stefan 7.mcx - so I was expecting to see the single class method change as well as the class comment change? Did I do something wrong? To make sure, I went back - made a small text change, so that I had a dirty package, and then followed the same steps in the video - and this time it did show me a change against Pharo40Inbox, but it was just my small text change? So Iâm worried that Iâve done something funny - but I canât work out what? Could someone just set me straight? Tim

Aug. 9, 2014

NBWin32 vs OSWindows

by Tudor Girba

Hi, I am working on a little tool that requires a couple of interactions with either a command line interface or a DLL whose API I do not know :). First, I would like to thank the authors for both NBWin32 and OSWindows. Having these possibilities at our fingertips makes the difference. Second, I am still not clear how to judge the difference between these two. For example, the functionality of WinShell (from OSWindows) seems to exist one-to-one in NBWin32Shell. Is it correct to assume that I should just focus on NBWin32? Third, how do I trigger a custom command line with a blocking call and how do I capture the output of the command? For example, suppose I just need to do a "dir" and capture the output. How do I do that? Are there examples? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Aug. 9, 2014

Re: [Pharo-dev] building vm on OSX 10.9: 'features.h' not found

by Max Leske

On 09.08.2014, at 12:17, Ben Coman <btc(a)openInWorld.com> wrote: > copied to [vm-dev] Thanks Ben. > > Max Leske wrote: >> >> On 09.08.2014, at 09:20, Max Leske <maxleske(a)gmail.com> wrote: >> >> >>> On 09.08.2014, at 08:39, Andreas Wacknitz <a.wacknitz(a)gmx.de> wrote: >>> >>> >>>> Am 09.08.2014 um 08:13 schrieb Andreas Wacknitz <a.wacknitz(a)gmx.de>: >>>> >>>> >>>>> Hi Max, >>>>> >>>>> I had the same problems when I was building the VM for OpenSolaris. >>>>> My simple solution was to change the generated build/config.h such that the #include wonât happen: >>>>> Simply uncomment the line â#define HAVE_FEATURES_H 1â >>>>> >>>> Upps, of course comment out this line :) >>>> >>> Perfect! Thanks. >>> >> >> Lol, that wouldnât even have been necessary in my case. The problem went away as soon as I realized that I hade used #buildUnix32 instead of #buildMacOSX32â¦ *facepalm*. >> >> Because Iâm sick of doing everything by hand and reinventing the wheel every couple of weeks Iâve written a script that removes deprecated compiler flags, fixes invalid includes, updates the repo, gets the MacOSX10.6 SDK, checks for homebrew dependencies and so on. If you want to use it, just call it like so: >> >> ./build_vm_OSX10.9.sh /path/to/pharo-vm >> >> The script is in my github repo: https://github.com/theseion/stuff/blob/master/build_vm_OSX10.9.sh >> >> Feel free to copy and modify it. >> >> @Esteban >> If you want you can put it into the pharo-vm repo too. >> >> Cheers, >> Max >> >> >>> >>>>> Regards, >>>>> Andreas >>>>> >>>>> Am 09.08.2014 um 00:19 schrieb Max Leske <maxleske(a)gmail.com>: >>>>> >>>>> >>>>>> Apparently stuff has changed since I last built a VM. Now I canât get past this annoying error: >>>>>> >>>>>> -- Generating done >>>>>> -- Build files have been written to: /Users/theseion/devel/git/pharo-vm/build >>>>>> Scanning dependencies of target SqueakSSL >>>>>> [ 1%] Building C object SqueakSSL/CMakeFiles/SqueakSSL.dir/Users/theseion/devel/git/pharo-vm/src/plugins/SqueakSSL/SqueakSSL.c.o >>>>>> In file included from /Users/theseion/devel/git/pharo-vm/src/plugins/SqueakSSL/SqueakSSL.c:21: >>>>>> In file included from /Users/theseion/devel/git/pharo-vm/platforms/Cross/vm/sqVirtualMachine.h:24: >>>>>> In file included from /Users/theseion/devel/git/pharo-vm/platforms/Cross/vm/sqMemoryAccess.h:18: >>>>>> In file included from /Users/theseion/devel/git/pharo-vm/build/config.h:141: >>>>>> /Users/theseion/devel/git/pharo-vm/platforms/unix/vm/glibc.h:1:10: fatal error: 'features.h' file not >>>>>> found >>>>>> #include <features.h> >>>>>> ^ >>>>>> 1 error generated. >>>>>> make[2]: *** [SqueakSSL/CMakeFiles/SqueakSSL.dir/Users/theseion/devel/git/pharo-vm/src/plugins/SqueakSSL/SqueakSSL.c.o] Error 1 >>>>>> make[1]: *** [SqueakSSL/CMakeFiles/SqueakSSL.dir/all] Error 2 >>>>>> make: *** [all] Error 2 >>>>>> >>>>>> >>>>>> Iâve done everything suggested by the readme on github and Iâve symlinked /usr/include to /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk/usr/include just in case, but no luck so far. >>>>>> >>>>>> Any ideas? >>>>>> >>>>>> Cheers, >>>>>> Max >>>>>> >>>>> >>>> >> >> >> >> >

Aug. 9, 2014

Re: [Pharo-dev] building vm on OSX 10.9: 'features.h' not found

by Ben Coman

Aug. 9, 2014

Re: [Pharo-dev] building vm on OSX 10.9: 'features.h' not found

by Max Leske

On 09.08.2014, at 09:20, Max Leske <maxleske(a)gmail.com> wrote: > > On 09.08.2014, at 08:39, Andreas Wacknitz <a.wacknitz(a)gmx.de> wrote: > >> >> Am 09.08.2014 um 08:13 schrieb Andreas Wacknitz <a.wacknitz(a)gmx.de>: >> >>> Hi Max, >>> >>> I had the same problems when I was building the VM for OpenSolaris. >>> My simple solution was to change the generated build/config.h such that the #include wonât happen: >>> Simply uncomment the line â#define HAVE_FEATURES_H 1â >> Upps, of course comment out this line :) > > Perfect! Thanks. Lol, that wouldnât even have been necessary in my case. The problem went away as soon as I realized that I hade used #buildUnix32 instead of #buildMacOSX32â¦ *facepalm*. Because Iâm sick of doing everything by hand and reinventing the wheel every couple of weeks Iâve written a script that removes deprecated compiler flags, fixes invalid includes, updates the repo, gets the MacOSX10.6 SDK, checks for homebrew dependencies and so on. If you want to use it, just call it like so: ./build_vm_OSX10.9.sh /path/to/pharo-vm The script is in my github repo: https://github.com/theseion/stuff/blob/master/build_vm_OSX10.9.sh Feel free to copy and modify it. @Esteban If you want you can put it into the pharo-vm repo too. Cheers, Max > > >> >>> >>> Regards, >>> Andreas >>> >>> Am 09.08.2014 um 00:19 schrieb Max Leske <maxleske(a)gmail.com>: >>> >>>> Apparently stuff has changed since I last built a VM. Now I canât get past this annoying error: >>>> >>>> -- Generating done >>>> -- Build files have been written to: /Users/theseion/devel/git/pharo-vm/build >>>> Scanning dependencies of target SqueakSSL >>>> [ 1%] Building C object SqueakSSL/CMakeFiles/SqueakSSL.dir/Users/theseion/devel/git/pharo-vm/src/plugins/SqueakSSL/SqueakSSL.c.o >>>> In file included from /Users/theseion/devel/git/pharo-vm/src/plugins/SqueakSSL/SqueakSSL.c:21: >>>> In file included from /Users/theseion/devel/git/pharo-vm/platforms/Cross/vm/sqVirtualMachine.h:24: >>>> In file included from /Users/theseion/devel/git/pharo-vm/platforms/Cross/vm/sqMemoryAccess.h:18: >>>> In file included from /Users/theseion/devel/git/pharo-vm/build/config.h:141: >>>> /Users/theseion/devel/git/pharo-vm/platforms/unix/vm/glibc.h:1:10: fatal error: 'features.h' file not >>>> found >>>> #include <features.h> >>>> ^ >>>> 1 error generated. >>>> make[2]: *** [SqueakSSL/CMakeFiles/SqueakSSL.dir/Users/theseion/devel/git/pharo-vm/src/plugins/SqueakSSL/SqueakSSL.c.o] Error 1 >>>> make[1]: *** [SqueakSSL/CMakeFiles/SqueakSSL.dir/all] Error 2 >>>> make: *** [all] Error 2 >>>> >>>> >>>> Iâve done everything suggested by the readme on github and Iâve symlinked /usr/include to /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk/usr/include just in case, but no luck so far. >>>> >>>> Any ideas? >>>> >>>> Cheers, >>>> Max >>> >>> >> >> >

Aug. 9, 2014

Re: [Pharo-dev] [GTInspector] Showing object state using a tree

by phil＠highoctane.be

Yes, I have a local little patch for that. Maybe Dark was updated and Dawn has to follow. Sebastian? Phil On Sat, Aug 9, 2014 at 10:01 AM, Johan Brichau <johan(a)inceptive.be> wrote: > I just installed the Dark Theme with the GT Tools in a Pharo3 and they > seem to work well now. Great great! > > The Dawn theme has difficult contrasts in other tools as well (even > without GT installed). Try using the merge tool with it.... > > Johan > > On 08 Aug 2014, at 13:02, phil(a)highoctane.be wrote: > > > It works. > > > > Now, following Johan point, the debugger is hard to read in a dark > theme. See attached screenshot. > > > > Phil > > > > > > > > On Fri, Aug 8, 2014 at 11:55 AM, Andrei Chis <chisvasileandrei(a)gmail.com> > wrote: > > Use GTGenericStackDebugger instead of GTDebugger. (it was renamed some > time ago). > > > > > > Cheers, > > Andrei > > > > > > On Fri, Aug 8, 2014 at 11:51 AM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > > I have been trying to install the tools in Pharo 3 (Dark/Dawn Theme). > > > > GTInspector loads and works pretty ok at first sight. > > > > Gofer new > > url: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main'; > > configuration; > > load. > > (Smalltalk globals at: #ConfigurationOfGToolkit) loadDevelopment. "Works > but with a warning" > > (Smalltalk globals at: #GTInspector) registerToolsOn: Smalltalk tools. > "Ok" > > (Smalltalk globals at: #GTDebugger) registerToolsOn: Smalltalk tools. > "Gives: KeyNotFound: key #GTDebugger not found in SystemDictionary" > > > > Indeed there is no GTDebugger class but a set of other things. > > > > What to use ? > > > > TIA > > > > > > âPhil > > > > > > <GT08-08-14 13-00-52.png> > > >

Aug. 9, 2014

Re: [Pharo-dev] [GTInspector] Showing object state using a tree

by Johan Brichau

I just installed the Dark Theme with the GT Tools in a Pharo3 and they seem to work well now. Great great! The Dawn theme has difficult contrasts in other tools as well (even without GT installed). Try using the merge tool with it.... Johan On 08 Aug 2014, at 13:02, phil(a)highoctane.be wrote: > It works. > > Now, following Johan point, the debugger is hard to read in a dark theme. See attached screenshot. > > Phil > > > > On Fri, Aug 8, 2014 at 11:55 AM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Use GTGenericStackDebugger instead of GTDebugger. (it was renamed some time ago). > > > Cheers, > Andrei > > > On Fri, Aug 8, 2014 at 11:51 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > I have been trying to install the tools in Pharo 3 (Dark/Dawn Theme). > > GTInspector loads and works pretty ok at first sight. > > Gofer new > url: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main'; > configuration; > load. > (Smalltalk globals at: #ConfigurationOfGToolkit) loadDevelopment. "Works but with a warning" > (Smalltalk globals at: #GTInspector) registerToolsOn: Smalltalk tools. "Ok" > (Smalltalk globals at: #GTDebugger) registerToolsOn: Smalltalk tools. "Gives: KeyNotFound: key #GTDebugger not found in SystemDictionary" > > Indeed there is no GTDebugger class but a set of other things. > > What to use ? > > TIA > > > âPhil > > > <GT08-08-14 13-00-52.png>

Aug. 9, 2014

Re: [Pharo-dev] building vm on OSX 10.9: 'features.h' not found

by Max Leske

On 09.08.2014, at 08:39, Andreas Wacknitz <a.wacknitz(a)gmx.de> wrote: > > Am 09.08.2014 um 08:13 schrieb Andreas Wacknitz <a.wacknitz(a)gmx.de>: > >> Hi Max, >> >> I had the same problems when I was building the VM for OpenSolaris. >> My simple solution was to change the generated build/config.h such that the #include wonât happen: >> Simply uncomment the line â#define HAVE_FEATURES_H 1â > Upps, of course comment out this line :) Perfect! Thanks. > >> >> Regards, >> Andreas >> >> Am 09.08.2014 um 00:19 schrieb Max Leske <maxleske(a)gmail.com>: >> >>> Apparently stuff has changed since I last built a VM. Now I canât get past this annoying error: >>> >>> -- Generating done >>> -- Build files have been written to: /Users/theseion/devel/git/pharo-vm/build >>> Scanning dependencies of target SqueakSSL >>> [ 1%] Building C object SqueakSSL/CMakeFiles/SqueakSSL.dir/Users/theseion/devel/git/pharo-vm/src/plugins/SqueakSSL/SqueakSSL.c.o >>> In file included from /Users/theseion/devel/git/pharo-vm/src/plugins/SqueakSSL/SqueakSSL.c:21: >>> In file included from /Users/theseion/devel/git/pharo-vm/platforms/Cross/vm/sqVirtualMachine.h:24: >>> In file included from /Users/theseion/devel/git/pharo-vm/platforms/Cross/vm/sqMemoryAccess.h:18: >>> In file included from /Users/theseion/devel/git/pharo-vm/build/config.h:141: >>> /Users/theseion/devel/git/pharo-vm/platforms/unix/vm/glibc.h:1:10: fatal error: 'features.h' file not >>> found >>> #include <features.h> >>> ^ >>> 1 error generated. >>> make[2]: *** [SqueakSSL/CMakeFiles/SqueakSSL.dir/Users/theseion/devel/git/pharo-vm/src/plugins/SqueakSSL/SqueakSSL.c.o] Error 1 >>> make[1]: *** [SqueakSSL/CMakeFiles/SqueakSSL.dir/all] Error 2 >>> make: *** [all] Error 2 >>> >>> >>> Iâve done everything suggested by the readme on github and Iâve symlinked /usr/include to /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk/usr/include just in case, but no luck so far. >>> >>> Any ideas? >>> >>> Cheers, >>> Max >> >> > >

Aug. 9, 2014