- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Add MetaRepoForPharo40 to default repository group

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > 'Define Repository in MC'... just for that. Ah! Cool. I wondered what those were for. Much easier than typing the URL in. But why require that at all? The inbox is in the MC working copy browser by default, why not the MetaRepo? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Add-MetaRepoForPharo40-to-default-repository-group-tp… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 6, 2015

Re: [Pharo-dev] [Pharo4] Build is green!

by Sven Van Caekenberghe

Super, let's keep it like that, reverting everything that introduces failing tests. > On 06 Apr 2015, at 10:27, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Finally the build is green! > > https://ci.inria.fr/pharo/ > > open issues for Pharo4 are down to 12: > > https://pharo.fogbugz.com/f/filters/103/4-0-All > > > Marcus

April 6, 2015

[Pharo4] Build is green!

by Marcus Denker

Finally the build is green! https://ci.inria.fr/pharo/ <https://ci.inria.fr/pharo/> open issues for Pharo4 are down to 12: https://pharo.fogbugz.com/f/filters/103/4-0-All <https://pharo.fogbugz.com/f/filters/103/4-0-All> Marcus

April 6, 2015

Re: [Pharo-dev] Add MetaRepoForPharo40 to default repository group

by Sven Van Caekenberghe

The Configuration Browser has menu items to 'Define Repository in MC' and 'Define All Repositories in MC' just for that. > On 06 Apr 2015, at 03:11, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Why not? > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Add-MetaRepoForPharo40-to-default-repository-group-tp… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

April 6, 2015

[pharo-project/pharo-core] ec0549: 40595

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: ec05497e14b8c5ed607f8f23138f529985568645 https://github.com/pharo-project/pharo-core/commit/ec05497e14b8c5ed607f8f23… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-04-06 (Mon, 06 Apr 2015) Changed paths: M Refactoring-Tests-Core.package/RBNamespaceTest.class/instance/class tests/testModelImplementorsSenders.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script594.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script595.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40594.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40595.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40595 15287 RBNamespaceTest>>#testModelImplementorsSenders https://pharo.fogbugz.com/f/cases/15287 http://files.pharo.org/image/40/40595.zip

April 6, 2015

[pharo-project/pharo-core]

by GitHub

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

April 6, 2015

Contributing to Bloc

by kilon alios

Hey guys, these last days I have taken a look at Bloc and really like its design. So I was wondering how I can be of assistance. I am not an experienced pharo jedi like you guys but I think I could do my small part to help make Bloc into a replacement for Morphic. >From what I see Bloc some issues rendering Morphs , for example tabs (window groups) and some glitches here and there. So how am I proceed ? How I can help ?

April 6, 2015

Re: [Pharo-dev] [Vm-dev] Re: Status of Pharo VM for FreeBSD

by Esteban Lorenzano

> On 06 Apr 2015, at 10:08, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> >> On 06 Apr 2015, at 09:58, Andreas Wacknitz <a.wacknitz(a)gmx.de> wrote: >> >> >> Am 06.04.15 09:51, schrieb Esteban Lorenzano: >>>> On 06 Apr 2015, at 09:41, Andreas Wacknitz <A.Wacknitz(a)gmx.de> wrote: >>>> >>>> >>>> Am 06.04.15 09:01, schrieb Esteban Lorenzano: >>>>> Hi, >>>>> >>>>> there is no real rationale :( >>>>> the reason why they are there now and not in their corresponding #defaultInternalPlugins or #defaultExternalPlugins is historic, configurations growth organically (we would need a refactor there). >>>> I fear not so many people could do that. I am scratching my head quite often while reading the code. >>>> BTW: PharoS is being used for Stack vm's so you should either find another abbreviation for Spur or choose the full name (that's what I would prefer). >>>> Otherwise it will get even harder in the futureâ¦ >>> we plan to drop support for plain cog vm and replace it for spurâ¦ so Pharo and PharoS will be both spur VMsâ¦ no need to complicate things here. >> Ah, OK. So probably I should wait until this happened and everythings settled down. >> One more question regarding the future: I guess there will be Spur32 and Spur64 vm's, right? >> If so, what are the plans regarding NativeBoost? Will there be a 64 bit version, too? (Ok, that's more than one question :)) > > Iâm working on a replacement that takes same syntax but uses regular FFI implementation instead ASM. > This will re-orientate our efforts into a common FFI strategy in all platforms and joint with Eliot work. > In that direction, there is some important work to speed up (with a new bytecode set and functions to FFI, Ronie and Eliot were working on it), plus a threaded ffi implementation, plus 64bits, plus ARM. > So, no need on reinvent the wheel here. > NB was important and a very good idea, but sadly we cannot maintain it as-is. ah, in case it was not clear: the replacement will be backward-compatible so no need to be scared here :) > > Esteban > >> >> Regards >> Andreas >> >>> >>>>> at least: FT2Plugin and SqueakSSLPlugin should be in defaults (and in the future SDL2 too). >>>>> >>>>> for starting your build I suggest you to exclude all the additions (plugins and external libraries). >>>>> then add them one by one. >>>> I already have a running version from almost one year ago. This time I will try to get further (eg. NativeBoost) and want to enhance my documentation. >>>> But it is time consuming and I would like to spend my time with more interesting things (using Pharo :)) >>> :) >>> >>>> Cheers, >>>> Andreas >>>>> cheers, >>>>> Esteban >>>>> >>>>>> On 06 Apr 2015, at 08:49, Andreas Wacknitz <A.Wacknitz(a)gmx.de> wrote: >>>>>> >>>>>> >>>>>> Am 03.04.15 17:31, schrieb Esteban Lorenzano: >>>>>>>>>> I have more questions but I am reluctant to disturb you further as you must be quite busy atm. >>>>>>>>> ask, I will answer when I can :) >>>>>> Hi Esteban, >>>>>> >>>>>> I am trying to understand the rationale behind PharoVMBuilder>>buildUnix32 (and similar methods like >>buildMacOSX32, >>buildFreeBSD32). >>>>>> How to determine which plugins and libraries to use? >>>>>> Linux makes use of >>>>>> PharoUnixConfig new >>>>>> "generateForDebug;" >>>>>> addExternalPlugins: #( FT2Plugin SqueakSSLPlugin SDL2DisplayPlugin ); >>>>>> addThirdpartyLibraries: #( >>>>>> 'libssh2' >>>>>> 'libgit2' >>>>>> 'libsdl2'); >>>>>> >>>>>> For FreeBSD it looks like this: >>>>>> PharoFreeBSDConfig new >>>>>> "generateForDebug;" >>>>>> addExternalPlugins: #( SqueakSSLPlugin ); >>>>>> addInternalPlugins: #( UnixOSProcessPlugin ); >>>>>> addThirdpartyLibraries: #( >>>>>> 'libssh2' >>>>>> 'libgit2' ); >>>>>> >>>>>> Mac OSX: >>>>>> PharoOSXConfig new >>>>>> "generateForDebug;" >>>>>> addExternalPlugins: #( FT2Plugin SDL2DisplayPlugin ); >>>>>> addInternalPlugins: #( UnixOSProcessPlugin ); >>>>>> addThirdpartyLibraries: #( >>>>>> 'cairo' >>>>>> 'libgit2' >>>>>> 'libssh2' >>>>>> 'libsdl2'); >>>>>> >>>>>> Windows: >>>>>> PharoWindowsConfig new >>>>>> addExternalPlugins: #( FT2Plugin SqueakSSLPlugin ); >>>>>> addInternalPlugins: #( SDL2DisplayPlugin ); >>>>>> addThirdpartyLibraries: #( >>>>>> 'cairo' >>>>>> 'libssh2' >>>>>> 'libgit2' >>>>>> 'libsdl2'); >>>>>> >>>>>> I assume that FreeBSD's configuration is not up-to-date (sdl2 and cairo not yet available?). >>>>>> Should I try to configure cairo, libssh2, libgit2 and libsdl2 libraries for openindiana, like it is done for Windows and MacOSX? >>>>>> Furthermore, should I try to configure SqueakSSLPlugin, FT2Plugin and SDL2DisplayPlugin as external plugins and UnixOSProcessPlugin as internal plugin? >>>>>> >>>>>> Regards >>>>>> Andreas

April 6, 2015

Re: [Pharo-dev] [Vm-dev] Re: Status of Pharo VM for FreeBSD

by Esteban Lorenzano

> On 06 Apr 2015, at 09:58, Andreas Wacknitz <a.wacknitz(a)gmx.de> wrote: > > > Am 06.04.15 09:51, schrieb Esteban Lorenzano: >>> On 06 Apr 2015, at 09:41, Andreas Wacknitz <A.Wacknitz(a)gmx.de> wrote: >>> >>> >>> Am 06.04.15 09:01, schrieb Esteban Lorenzano: >>>> Hi, >>>> >>>> there is no real rationale :( >>>> the reason why they are there now and not in their corresponding #defaultInternalPlugins or #defaultExternalPlugins is historic, configurations growth organically (we would need a refactor there). >>> I fear not so many people could do that. I am scratching my head quite often while reading the code. >>> BTW: PharoS is being used for Stack vm's so you should either find another abbreviation for Spur or choose the full name (that's what I would prefer). >>> Otherwise it will get even harder in the futureâ¦ >> we plan to drop support for plain cog vm and replace it for spurâ¦ so Pharo and PharoS will be both spur VMsâ¦ no need to complicate things here. > Ah, OK. So probably I should wait until this happened and everythings settled down. > One more question regarding the future: I guess there will be Spur32 and Spur64 vm's, right? > If so, what are the plans regarding NativeBoost? Will there be a 64 bit version, too? (Ok, that's more than one question :)) Iâm working on a replacement that takes same syntax but uses regular FFI implementation instead ASM. This will re-orientate our efforts into a common FFI strategy in all platforms and joint with Eliot work. In that direction, there is some important work to speed up (with a new bytecode set and functions to FFI, Ronie and Eliot were working on it), plus a threaded ffi implementation, plus 64bits, plus ARM. So, no need on reinvent the wheel here. NB was important and a very good idea, but sadly we cannot maintain it as-is. Esteban > > Regards > Andreas > >> >>>> at least: FT2Plugin and SqueakSSLPlugin should be in defaults (and in the future SDL2 too). >>>> >>>> for starting your build I suggest you to exclude all the additions (plugins and external libraries). >>>> then add them one by one. >>> I already have a running version from almost one year ago. This time I will try to get further (eg. NativeBoost) and want to enhance my documentation. >>> But it is time consuming and I would like to spend my time with more interesting things (using Pharo :)) >> :) >> >>> Cheers, >>> Andreas >>>> cheers, >>>> Esteban >>>> >>>>> On 06 Apr 2015, at 08:49, Andreas Wacknitz <A.Wacknitz(a)gmx.de> wrote: >>>>> >>>>> >>>>> Am 03.04.15 17:31, schrieb Esteban Lorenzano: >>>>>>>>> I have more questions but I am reluctant to disturb you further as you must be quite busy atm. >>>>>>>> ask, I will answer when I can :) >>>>> Hi Esteban, >>>>> >>>>> I am trying to understand the rationale behind PharoVMBuilder>>buildUnix32 (and similar methods like >>buildMacOSX32, >>buildFreeBSD32). >>>>> How to determine which plugins and libraries to use? >>>>> Linux makes use of >>>>> PharoUnixConfig new >>>>> "generateForDebug;" >>>>> addExternalPlugins: #( FT2Plugin SqueakSSLPlugin SDL2DisplayPlugin ); >>>>> addThirdpartyLibraries: #( >>>>> 'libssh2' >>>>> 'libgit2' >>>>> 'libsdl2'); >>>>> >>>>> For FreeBSD it looks like this: >>>>> PharoFreeBSDConfig new >>>>> "generateForDebug;" >>>>> addExternalPlugins: #( SqueakSSLPlugin ); >>>>> addInternalPlugins: #( UnixOSProcessPlugin ); >>>>> addThirdpartyLibraries: #( >>>>> 'libssh2' >>>>> 'libgit2' ); >>>>> >>>>> Mac OSX: >>>>> PharoOSXConfig new >>>>> "generateForDebug;" >>>>> addExternalPlugins: #( FT2Plugin SDL2DisplayPlugin ); >>>>> addInternalPlugins: #( UnixOSProcessPlugin ); >>>>> addThirdpartyLibraries: #( >>>>> 'cairo' >>>>> 'libgit2' >>>>> 'libssh2' >>>>> 'libsdl2'); >>>>> >>>>> Windows: >>>>> PharoWindowsConfig new >>>>> addExternalPlugins: #( FT2Plugin SqueakSSLPlugin ); >>>>> addInternalPlugins: #( SDL2DisplayPlugin ); >>>>> addThirdpartyLibraries: #( >>>>> 'cairo' >>>>> 'libssh2' >>>>> 'libgit2' >>>>> 'libsdl2'); >>>>> >>>>> I assume that FreeBSD's configuration is not up-to-date (sdl2 and cairo not yet available?). >>>>> Should I try to configure cairo, libssh2, libgit2 and libsdl2 libraries for openindiana, like it is done for Windows and MacOSX? >>>>> Furthermore, should I try to configure SqueakSSLPlugin, FT2Plugin and SDL2DisplayPlugin as external plugins and UnixOSProcessPlugin as internal plugin? >>>>> >>>>> Regards >>>>> Andreas >>>>> >

April 6, 2015

Re: [Pharo-dev] [Vm-dev] Re: Status of Pharo VM for FreeBSD

by Andreas Wacknitz

Am 06.04.15 09:51, schrieb Esteban Lorenzano: >> On 06 Apr 2015, at 09:41, Andreas Wacknitz <A.Wacknitz(a)gmx.de> wrote: >> >> >> Am 06.04.15 09:01, schrieb Esteban Lorenzano: >>> Hi, >>> >>> there is no real rationale :( >>> the reason why they are there now and not in their corresponding #defaultInternalPlugins or #defaultExternalPlugins is historic, configurations growth organically (we would need a refactor there). >> I fear not so many people could do that. I am scratching my head quite often while reading the code. >> BTW: PharoS is being used for Stack vm's so you should either find another abbreviation for Spur or choose the full name (that's what I would prefer). >> Otherwise it will get even harder in the futureâ¦ > we plan to drop support for plain cog vm and replace it for spurâ¦ so Pharo and PharoS will be both spur VMsâ¦ no need to complicate things here. Ah, OK. So probably I should wait until this happened and everythings settled down. One more question regarding the future: I guess there will be Spur32 and Spur64 vm's, right? If so, what are the plans regarding NativeBoost? Will there be a 64 bit version, too? (Ok, that's more than one question :)) Regards Andreas > >>> at least: FT2Plugin and SqueakSSLPlugin should be in defaults (and in the future SDL2 too). >>> >>> for starting your build I suggest you to exclude all the additions (plugins and external libraries). >>> then add them one by one. >> I already have a running version from almost one year ago. This time I will try to get further (eg. NativeBoost) and want to enhance my documentation. >> But it is time consuming and I would like to spend my time with more interesting things (using Pharo :)) > :) > >> Cheers, >> Andreas >>> cheers, >>> Esteban >>> >>>> On 06 Apr 2015, at 08:49, Andreas Wacknitz <A.Wacknitz(a)gmx.de> wrote: >>>> >>>> >>>> Am 03.04.15 17:31, schrieb Esteban Lorenzano: >>>>>>>> I have more questions but I am reluctant to disturb you further as you must be quite busy atm. >>>>>>> ask, I will answer when I can :) >>>> Hi Esteban, >>>> >>>> I am trying to understand the rationale behind PharoVMBuilder>>buildUnix32 (and similar methods like >>buildMacOSX32, >>buildFreeBSD32). >>>> How to determine which plugins and libraries to use? >>>> Linux makes use of >>>> PharoUnixConfig new >>>> "generateForDebug;" >>>> addExternalPlugins: #( FT2Plugin SqueakSSLPlugin SDL2DisplayPlugin ); >>>> addThirdpartyLibraries: #( >>>> 'libssh2' >>>> 'libgit2' >>>> 'libsdl2'); >>>> >>>> For FreeBSD it looks like this: >>>> PharoFreeBSDConfig new >>>> "generateForDebug;" >>>> addExternalPlugins: #( SqueakSSLPlugin ); >>>> addInternalPlugins: #( UnixOSProcessPlugin ); >>>> addThirdpartyLibraries: #( >>>> 'libssh2' >>>> 'libgit2' ); >>>> >>>> Mac OSX: >>>> PharoOSXConfig new >>>> "generateForDebug;" >>>> addExternalPlugins: #( FT2Plugin SDL2DisplayPlugin ); >>>> addInternalPlugins: #( UnixOSProcessPlugin ); >>>> addThirdpartyLibraries: #( >>>> 'cairo' >>>> 'libgit2' >>>> 'libssh2' >>>> 'libsdl2'); >>>> >>>> Windows: >>>> PharoWindowsConfig new >>>> addExternalPlugins: #( FT2Plugin SqueakSSLPlugin ); >>>> addInternalPlugins: #( SDL2DisplayPlugin ); >>>> addThirdpartyLibraries: #( >>>> 'cairo' >>>> 'libssh2' >>>> 'libgit2' >>>> 'libsdl2'); >>>> >>>> I assume that FreeBSD's configuration is not up-to-date (sdl2 and cairo not yet available?). >>>> Should I try to configure cairo, libssh2, libgit2 and libsdl2 libraries for openindiana, like it is done for Windows and MacOSX? >>>> Furthermore, should I try to configure SqueakSSLPlugin, FT2Plugin and SDL2DisplayPlugin as external plugins and UnixOSProcessPlugin as internal plugin? >>>> >>>> Regards >>>> Andreas >>>>

April 6, 2015