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

Re: [Pharo-dev] [pharo-project/pharo-core] 9ebdd6: 40099

by stepharo

Thanks pavel. We should continue to repackage and clean. Tools for example. I'm currently working on Polymorph. Stef > Great, now the shrinking to the basic image does not have any > overrides nor ugly hacks. > https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo-4.0-Bootstrap-Step-1… > > -- Pavel > > > 2014-07-18 10:32 GMT+02:00 GitHub <noreply(a)github.com > <mailto:noreply@github.com>>: > > Branch: refs/heads/4.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 9ebdd640712f23c1c3055d066972c2034e3ca45e > https://github.com/pharo-project/pharo-core/commit/9ebdd640712f23c1c3055d06… > Author: Jenkins Build Server <board(a)pharo-project.org > <mailto:board@pharo-project.org>> > Date: 2014-07-18 (Fri, 18 Jul 2014) > > Changed paths: > R Graphics-Primitives.package/Color.class/class/as yet > unclassified/aaFontsColormapDepth.st > R Graphics-Primitives.package/Color.class/class/as yet > unclassified/cachedColormapFrom_to_.st > A > Graphics-Primitives.package/Color.class/class/colormaps/aaFontsColormapDepth.st > A > Graphics-Primitives.package/Color.class/class/colormaps/cachedColormapFrom_to_.st > M > Graphics-Primitives.package/Color.class/instance/printing/shortPrintString.st > M > Graphics-Primitives.package/EllipseMidpointTracer.class/definition.st > <http://definition.st> > M > Graphics-Primitives.package/EllipseMidpointTracer.class/instance/initialize/on_.st > A NativeBoost-Unix.package/UnixEnvironment.class/README.md > A > NativeBoost-Unix.package/UnixEnvironment.class/class/testing/isDefaultFor_.st > A NativeBoost-Unix.package/UnixEnvironment.class/definition.st > <http://definition.st> > A > NativeBoost-Unix.package/UnixEnvironment.class/instance/accessing/environ.st > <http://environ.st> > A > NativeBoost-Unix.package/UnixEnvironment.class/instance/enumeration/keysAndValuesDo_.st > A > NativeBoost-Unix.package/UnixEnvironment.class/instance/private/environAt_.st > A > NativeBoost-Unix.package/UnixEnvironment.class/instance/private/setEnv_value_.st > A NativeBoost-Win32.package/Win32Environment.class/README.md > A > NativeBoost-Win32.package/Win32Environment.class/class/testing/isDefaultFor_.st > A > NativeBoost-Win32.package/Win32Environment.class/definition.st > <http://definition.st> > A > NativeBoost-Win32.package/Win32Environment.class/instance/accessing/environmentStrings.st > A > NativeBoost-Win32.package/Win32Environment.class/instance/enumeration/keysAndValuesDo_.st > A > NativeBoost-Win32.package/Win32Environment.class/instance/private/getEnvSize_.st > A > NativeBoost-Win32.package/Win32Environment.class/instance/private/getEnv_.st > A > NativeBoost-Win32.package/Win32Environment.class/instance/private/getEnv_buffer_size_.st > A > NativeBoost-Win32.package/Win32Environment.class/instance/private/setEnv_value_.st > A > NativeBoost-Win32.package/Win32Environment.class/instance/private/unsetEnv_.st > A > ReleaseTests.package/ReleaseTest.class/instance/testing/testAllClassPoolBindingAreClassVariables.st > A > ReleaseTests.package/ReleaseTest.class/instance/testing/testAllGlobalBindingAreGlobalVariables.st > A ScriptLoader40.package/ScriptLoader.class/instance/pharo - > scripts/script99.st <http://script99.st> > A ScriptLoader40.package/ScriptLoader.class/instance/pharo - > updates/update40099.st <http://update40099.st> > M > ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st > M Slot.package/ClassVariable.class/README.md > M > Slot.package/ClassVariable.class/instance/meta-object-protocol/link_.st > A > Slot.package/ClassVariable.class/instance/testing/isClassVariable.st > M Slot.package/GlobalVariable.class/README.md > A Slot.package/GlobalVariable.class/instance/as yet > unclassified/definingClass.st > M > Slot.package/GlobalVariable.class/instance/meta-object-protocol/link_.st > A > Slot.package/GlobalVariable.class/instance/testing/isGlobalVariable.st > R > Slot.package/LiteralVariable.class/instance/meta-object-protocol/link_.st > A > Slot.package/LiteralVariable.class/instance/testing/isClassVariable.st > A > Slot.package/LiteralVariable.class/instance/testing/isGlobalVariable.st > R System-Platforms.package/UnixEnvironment.class/README.md > R > System-Platforms.package/UnixEnvironment.class/class/testing/isDefaultFor_.st > R System-Platforms.package/UnixEnvironment.class/definition.st > <http://definition.st> > R > System-Platforms.package/UnixEnvironment.class/instance/accessing/environ.st > <http://environ.st> > R > System-Platforms.package/UnixEnvironment.class/instance/enumeration/keysAndValuesDo_.st > R > System-Platforms.package/UnixEnvironment.class/instance/private/environAt_.st > R > System-Platforms.package/UnixEnvironment.class/instance/private/setEnv_value_.st > R System-Platforms.package/Win32Environment.class/README.md > R > System-Platforms.package/Win32Environment.class/class/testing/isDefaultFor_.st > R > System-Platforms.package/Win32Environment.class/definition.st > <http://definition.st> > R > System-Platforms.package/Win32Environment.class/instance/accessing/environmentStrings.st > R > System-Platforms.package/Win32Environment.class/instance/enumeration/keysAndValuesDo_.st > R > System-Platforms.package/Win32Environment.class/instance/private/getEnvSize_.st > R > System-Platforms.package/Win32Environment.class/instance/private/getEnv_.st > R > System-Platforms.package/Win32Environment.class/instance/private/getEnv_buffer_size_.st > R > System-Platforms.package/Win32Environment.class/instance/private/setEnv_value_.st > R > System-Platforms.package/Win32Environment.class/instance/private/unsetEnv_.st > M > Tests.package/OSEnvironmentTest.class/instance/tests/testEnvironmentFor.st > > Log Message: > ----------- > 40099 > 13576 Small code critique cleanup Graphics-Primitives > https://pharo.fogbugz.com/f/cases/13576 > > 13587 add tests to make sure globals and class vars use the right > bindings > https://pharo.fogbugz.com/f/cases/13587 > > 13580 move UnixEnvironment and Win32Environment to NativeBoost > https://pharo.fogbugz.com/f/cases/13580 > > http://files.pharo.org/image/40/40099.zip > > >

July 18, 2014

Re: [Pharo-dev] PetitParser in 3.0?

by Tudor Girba

Hi Esteban, Moose 5 is still under development. We will likely reach a stable version within one or two months. In the meantime, it is true that there are some subcomponents that are stable (such as PetitParser), but we do not have yet the capacity and the organization to be able to release it individually easily. Perhaps once we will streamline the use of tooling around Metacello it will get easier. But, if people want to create a release of PetitParser, they are of course welcome to do it. Cheers, Doru On Fri, Jul 18, 2014 at 3:13 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 18 Jul 2014, at 14:12, Stephan Eggermont <stephan(a)stack.nl> wrote: > > > Esteban wrote > >> This is a question for the moosers :) > >> Why there is no copy (with stable version) in metarepo of ll > configurations that are under the moose umbrella? > > > > That's a question of effort vs results. Moose builds on top of Pharo, > which has no stable. > > Pharo has a stable version, 3. > Bug fix releases are that: bug fixes, and does not break any compatibility. > > > There are newer builds of Pharo 3 containing bug-fixes. Moose has no > Metacello way to identify > > which build it is running on so no way to create a stable. Moose is a > large framework exercising > > large parts of the Pharo code base so almost all bug-fix releases impact > Moose. > > Thatâs not true. Bug fixes do not break Pharo and shouldnât break Moose. > The fact that you do not declare stable versions of Moose is the reason > why you cannot provide a loadable version in Pharo3. > You just continued working and breaking backward compatibility. Iâm > perfectly ok with that (in fact, I really like all the work around moose), > but you should provide a stable version for Pharo 3, like you should > provide a development version for Pharo 4. > > > The test suite of Pharo contains non-green tests so there is no easy way > to track issues. > > Again, not true. We released Pharo3 with no yellow/red tests. > > Esteban > > > > In addition there are of course the issues in Moose development itself. > > > > Stephan > > > -- www.tudorgirba.com "Every thing has its own flow"

July 18, 2014

[RMOD interviews] Clara's interview online!

by Nicolas Petton

Hi guys, I just published the interview of Clara Allende here: http://nicolas-petton.fr/blog/interview-clara.html As this is my last day in the team, I won't have time to interview any other member of the team (with the exception of Camille, as the interview is done, I just have to publish it). I was hoping to interview everyone of you, but time flies. :/ Anyway, I hope you like the interview! Cheers, Nico

July 18, 2014

Re: [Pharo-dev] PetitParser in 3.0?

by Esteban Lorenzano

On 18 Jul 2014, at 14:12, Stephan Eggermont <stephan(a)stack.nl> wrote: > Esteban wrote >> This is a question for the moosers :) >> Why there is no copy (with stable version) in metarepo of ll configurations that are under the moose umbrella? > > That's a question of effort vs results. Moose builds on top of Pharo, which has no stable. Pharo has a stable version, 3. Bug fix releases are that: bug fixes, and does not break any compatibility. > There are newer builds of Pharo 3 containing bug-fixes. Moose has no Metacello way to identify > which build it is running on so no way to create a stable. Moose is a large framework exercising > large parts of the Pharo code base so almost all bug-fix releases impact Moose. Thatâs not true. Bug fixes do not break Pharo and shouldnât break Moose. The fact that you do not declare stable versions of Moose is the reason why you cannot provide a loadable version in Pharo3. You just continued working and breaking backward compatibility. Iâm perfectly ok with that (in fact, I really like all the work around moose), but you should provide a stable version for Pharo 3, like you should provide a development version for Pharo 4. > The test suite of Pharo contains non-green tests so there is no easy way to track issues. Again, not true. We released Pharo3 with no yellow/red tests. Esteban > In addition there are of course the issues in Moose development itself. > > Stephan

July 18, 2014

Silently changing classes/methods

by Yuriy Tymchuk

Hi, I need to manipulate classes/methods in my tests. E.g. create class, test something, remove it. Can I do this silently? Because otherwise I get dirty packages, Epicea log and so on. Cheers Uko

July 18, 2014

Re: [Pharo-dev] PetitParser in 3.0?

by Stephan Eggermont

Esteban wrote >This is a question for the moosers :) >Why there is no copy (with stable version) in metarepo of ll configurations that are under the moose umbrella? That's a question of effort vs results. Moose builds on top of Pharo, which has no stable. There are newer builds of Pharo 3 containing bug-fixes. Moose has no Metacello way to identify which build it is running on so no way to create a stable. Moose is a large framework exercising large parts of the Pharo code base so almost all bug-fix releases impact Moose. The test suite of Pharo contains non-green tests so there is no easy way to track issues. In addition there are of course the issues in Moose development itself. Stephan

July 18, 2014

Re: [Pharo-dev] Fun With Pharo on ci

by stepharo

Super! I should migrate and revisit also some of my chapters. Stef On 17/7/14 22:01, Stephan Eggermont wrote: > Thanks to some help by Damien, we now have FunWithPharo > on ci. It generates the whole book and separate chapters. > > Stephan > >

July 18, 2014

Re: [Pharo-dev] Pharo Not For The Enterprise

by stepharo

>> I started Fun With Pharo :) >> >> https://github.com/SquareBracketAssociates/FunWithPharo > Good. I've added the chapter. Can I just copy the ci config from > PharoForTheEnterprise to generate book & chapters? > Anything else to do than change urls? adding chapters I will have a look now. I thought that I added a conf already. > > Stephan > >

July 18, 2014

Re: [Pharo-dev] Current maintainer of PharoExtras/LDAP?

by stepharo

Excellent! We loved such enhancements. I did not check but I imagine you can commit now to the repo? Stef On 17/7/14 12:08, Udo Schneider wrote: > > What are the changes ? > SSL: > * Addition of LDAPSConnection/LDAPSWorker and instance generation > methods (e.g. LDAPSConnection>>#to:port:ssl:) to use Zodiac Sockets > instead of regular sockets. Both classes support SSL and non-SSL > connection. So it might be worth rolling them into the regular > LDAPConnection/LDAPWorker > AD: > * Addition of LDAPSearchResultReference to handle ReferenceResults. > W/o this even something simple like searching the RootDSE fails. > * Addition of LDAP URLs (not working yet) to parse ReferenceResults > * Some convenience methods to search/create/delete AD Users and > Groups. Support for (Re)Setting Passwords ... this was quite PITA to > figure out BTW ... > Misc: > * Spec based LDAP Browser (http://udos.s3.amazonaws.com/LDAPBrowser.png) > > Just a summary (omitting some bits and pieces like fetching RootDSEs, > namingContexts ...) > > CU, > > Udo > > > On 17.07.2014 09:30, Olivier Auverlot wrote: >> LDAP is so important. Improving support for Active Directory and SSL >> is really a good idea. >> >> I used the framework in many projects with Pharo 1.3 and 2.0. It >> works very well. >> >>>> But I'm hitting a few issues now which would change the base packages. >> >> What are the changes ? >> >> Best regards >> Olivier :-) >> >> Le 16 juil. 2014 Ã 19:47, stepharo a Ã©crit : >> >>> >>> On 16/7/14 19:02, Udo Schneider wrote: >>>> All, >>>> >>>> I'm currently making some changes to the LDAP package to make it >>>> play nicer with ActiveDirectory and SSL. Up to now all those >>>> changes were non-intrusive to the current packages. But I'm hitting >>>> a few issues now which would change the base packages. >>>> >>>> What's the policy on this? >>> Improving :) >>> We need stronger and better libraries. >>>> Keeping those changes in my own fork or submitting them to a >>>> maintainer (who?). >>> >>> I gave you access to the PharoExtras repo. >>> Just add tests and build the best LDAP you want :) >>> Make sure that everything work well and suits your needs. >>> I'm not sure that current design is good. At least when olivier >>> auverlot showed to me I was skeptical about the chapter we/he wrote >>> on it. >>>> In addition ... as far as I can see the current package is Pharo >>>> only (was Squeak). >>>> If "Pharo-only" is o.k. I could for instance integrate my stuff for >>>> LDAP-over-SSL in there directly (based on Zodiac). >>> Excellent idea. >>> Our goal is to make sure that people can make business. >>>> >>>> Thanks, >>>> >>>> Udo >>>> >>>> >>>> >>> >>> >> >> >> > > > >

July 18, 2014

Re: [Pharo-dev] RFB broken

by stepharo

Damien what is this looking bad selector? #wordingProvider:wordingSelector: and who is invoking it? because we should simply use a default menu. Stef On 18/7/14 13:24, Damien Cassou wrote: > On Thu, Jul 17, 2014 at 8:49 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: >> http://www.samadhiweb.com/blog/2014.05.01.rfb.pharo3.html > > thank you very much, I pushed the fix to the RFB repository >

July 18, 2014